A checklist for your first HR conversation campaign.

Use this checklist for a small pilot. At the end, your sponsor should be able to see who took part, what the accounts support and what the team will do next. Set those expectations before anyone is invited.

Before launch
Agree the decision, sponsor, group, access and participant information.
During the pilot
Check participation by role and test how the questions work with real answers.
At the decision
Record evidence, gaps, next steps and an owner. Decide whether to continue, adapt or stop.

1. Scope the decision

□ Write the decision the sponsor expects to make. For example, “Choose one thing we can change about how new starters get their first independent task.” □ Define the group and period. Include people with direct knowledge of different parts of the work. □ Write what evidence would count as useful. For example, each proposed change should have a recent example and a person who can verify the process. □ Name who owns the decision, who will review input and who will explain the next steps to participants.

Choose something within the sponsor’s authority. If the right owner or next decision is unclear, settle that before gathering employee input.

2. Prepare the questions and invitation

□ Write one common opening question and a few follow-ups about recent situations. Test them with a colleague who understands the work. □ Check whether the questions and participation routes are accessible to the intended group. □ Explain the purpose, what people are being asked to share, who can see it, and where to take a sensitive or urgent concern. □ Agree what information to avoid, the approved storage and access arrangements, and how people can contact the team about the campaign.

Test an ordinary answer, a vague answer, a disagreement and a sensitive response before launch. Agree who can pause the campaign if a serious problem comes up.

3. Gather and review the evidence

□ Track invited and completed counts by sufficiently broad group. Record which roles or shifts may be missing. □ Read a sample of complete conversations to look for leading wording, ambiguous questions and useful follow-ups. □ Match each proposed finding to the accounts that support it. Look for counterexamples, duplicates and alternative explanations. □ Record evidence gaps separately from interpretations. If a theme depends on only one account, say so and consider what can be checked next.

Share a draft only with the agreed reviewers. Use the level of detail they need to do their job. Check whether combinations of role, location or incident can identify someone.

4. Agree what happens after the pilot

□ Review one decision with the sponsor. List the options, the evidence behind them and the unresolved questions. □ Assign an action, owner and check-in date. □ Tell participants what you heard and what you are doing about it, in a form that respects the agreed handling of their input. □ Decide whether to repeat, adapt or stop. Record the reason and any changes you would make before expanding.

A short report can have four fields. Write “What we asked,” “What we can support,” “What is missing” and “What happens next.” Attach only what is appropriate for the audience.

Questions that come up

How large should the first campaign be?

Choose the smallest group that covers the roles needed to answer the question and meets your reporting and confidentiality needs. State whose experience the group can speak for and where coverage is limited.

How do we know a pilot was useful?

Compare the outcome with what you agreed before launch. Check whether the sponsor could take a supported next step, whether the accounts were reviewable and whether participants understood the purpose.

When should we pause a campaign?

Pause if agreed protections cannot be upheld, a sensitive response has no appropriate route, or questions repeatedly collect the wrong information. Resolve the issue before inviting more people.

Bring one performance question.

See the product on a question like yours, and what a first campaign could involve.

Book a demo