Employee Listening Session Kit
Fictional example: Northstar Works, a multi-site organization, is exploring where shift handovers lose useful context. Use this page to prepare a focused discussion, capture themes without naming individuals, and explain what happens after the session.
Understand the experience, not decide the solution
For facilitators and employee participants
Use the session to learn where useful handover context is available, missed, or difficult to act on. The output is a set of themes for review—not a decision, approval, or commitment to change a process.
Facilitator: explain the purpose, invite different perspectives, and keep the discussion on work experiences. Participants: describe specific situations, including what worked and what did not. Anyone may pass on a prompt. If a sensitive or individual concern comes up, acknowledge it and direct the person to the organization’s established appropriate support route rather than investigating it in the group.
For a multi-site discussion, invite contributors with different roles, shifts, and locations where practical. This broadens the perspectives in the room; it is not a quota or a claim that any group is represented.
Invite useful perspectives
Choose contributors for the work experience you need to understand
- Different points in the handover Invite people who give, receive, or rely on handover information so the discussion includes more than one side of the process.
- Different working contexts Consider variation in role, shift, and location. Tell invitees which experience the session will cover and how long it will run.
- A workable discussion group Keep the group small enough for each person to contribute. If invitations outnumber the time available, hold additional sessions rather than rushing every voice.
- A separate route for sensitive matters Do not investigate an individual or sensitive concern in the group. Pause, acknowledge it, and direct the person to the organization’s appropriate established support route.
A focused 60-minute agenda
An authored reference for the facilitator, not a live schedule or work queue.
| Time | Activity | Facilitator cue |
|---|---|---|
| 0–5 min | Welcome and scope | State the question, intended output, and what this session cannot decide. |
| 5–12 min | Set participation agreements | Invite specific examples, different views, and the option to pass; explain how notes will be summarized. |
| 12–30 min | Describe handover experiences | Ask what information is useful, missing, or hard to act on; request a recent work situation without asking for names. |
| 30–45 min | Explore patterns and contrasts | Compare when handovers work well with when context is lost. Ask what conditions differ. |
| 45–55 min | Check the emerging themes | Read back neutral summaries and ask what is missing or overstated. |
| 55–60 min | Explain the handoff | Name the reviewing role, how themes will be considered, and how participants will hear an update once the follow-up route and timing are confirmed. |
Prompts that invite concrete examples
Ask neutrally; follow the participant’s experience rather than proposing an answer.
Start with an open account of what happened, then ask for details that clarify the situation.
- What information helped you pick up the work?
- What was unclear or unavailable at the time?
- What happened next?
Compare a useful handover with a difficult one without assuming the same explanation applies to every team.
- When does the handover work better?
- What differs about the timing, context, or information available?
- Who else depends on that information?
Fictional example: a participant says, “The update came after we had already started.” The facilitator asks, “What had your team already begun, and what information would have changed the next step?” This invites detail without implying that a particular tool or role is to blame.
- Ask what happened before and after.
- Use the participant’s words where possible.
- Avoid asking for names or implying that a solution has already been chosen.
Capture themes without turning them into claims
Write what participants described separately from the facilitator’s interpretation. Keep contrasting experiences visible, and summarize without identifying who said what.
Fictional session note: “In one example, the next shift began a task before a later update arrived.” This records a described sequence, not its cause or frequency.
- Record the situation and sequence.
- Do not attach a participant’s name.
- Keep the note close to what was actually described.
Possible theme: “Timing of updates may affect whether the receiving shift has context before work begins.” This is a hypothesis for review, not a verified pattern or a promised fix.
- Label interpretations as themes to check.
- Record a contrasting example if some handovers work well.
- Leave decisions and ownership for the agreed review step.
Close with an honest follow-up handoff
Make the next step understandable without promising an outcome