After the engagement survey
Live, 75 to 90 minutes. 30 to 80 people. The scores are in and nobody has a method for the conversation that follows.
When to use it
An organization has run its annual engagement survey, leadership has the scores, and now there is a meeting where everyone is supposed to discuss what the numbers mean. That meeting usually produces either silence or the loudest person's theory. This session replaces it: people write what they actually think without their name on it, the room turns that into themes it named itself, and leadership leaves with something it can act on rather than a slide of averages.
Do not use it when the survey itself is the problem and leadership has already decided what the answer is. A session that exists to ratify a predetermined conclusion will produce one, and the participants will know.
The question
The survey already asked the closed questions. This session is for the "why" and the "what now," so the spark must invite explanation rather than more rating.
Seeds, cultivate one with the client:
- What would have to change for the score on [dimension] to move by this time next year?
- What does this organization keep asking people to do without giving them what they need to do it?
- What is working here that we would lose if we changed the wrong thing?
- When you filled in the survey, what were you thinking about that the questions did not ask?
The question that fails: "What are your thoughts on the survey results?" It produces commentary on the instrument rather than the experience, and the most confident people commentate best.
Session settings
- Participants: set the cap to the expected headcount plus ten
- Anonymous participation: on, and this is the whole point
- Raffle: off. It defaults on, and collecting names in a session about criticizing management is a serious mistake
- Blind gather: on
- Blind then reveal voting: on
- Shuffle order: on
- Access after finish: on, so people can read the report
Run of show
| Time | What happens |
|---|---|
| 0:00 | Welcome. Say who will see the output and what leadership has committed to do with it. If they have committed to nothing, say that too |
| 0:08 | The spark, and the ground rule: write what you would say if it could never be traced to you |
| 0:13 | Gather, silent, blind. 12 to 15 minutes. Expect a slow first two minutes |
| 0:30 | Emerge. Project the draft themes. Run the correction drill with the room |
| 0:48 | Validate. Rate which themes ring true. Comments on what is missing |
| 1:03 | Enrich, brief. Any relevant context leadership has, delivered after the themes exist, never before |
| 1:12 | Evolve or Resolve. What should the next conversation be, or what does the group endorse |
| 1:25 | Close. Where the report goes and who will respond to it |
Ends at: Resolve, the closing segment, when this is the only session leadership has planned; end at Evolve instead if a second conversation is already committed and the room should choose what it is about.
Facilitator notes
Decide in advance whether executives are in the room. This is the single biggest determinant of whether the session works. If the CEO is present, contributions get safer, and no anonymity setting fixes that, because people can see who is standing at the back. Options, in order of preference: leadership joins for the last fifteen minutes only; leadership participates fully as equal anonymous contributors and says so out loud; or leadership stays out and receives the report. Get this decided before the date is booked.
The clustering will merge complaints with their opposites. "We need more direction from managers" and "managers micromanage everything" are the same topic and land together. That is the moment to run the correction drill, and it is also the most useful thirty seconds of the session, because the split it produces is usually the actual finding.
Watch for the unclustered pile. In this room it often contains the specific, uncomfortable, single-voice contributions that matter most. Read them aloud as open items. Do not let them vanish into "other."
What the group leaves with
Themes the participants named, with an indication of which ones resonate most widely, the comments about what is missing, and the ideas that fit no theme kept visible as open questions. The client receives the same thing. Nobody receives a list of who said what, because that does not exist.
The failure mode
Leadership hears the themes as an attack and responds in the room. It happens fast, usually during Validate, and it ends honest contribution for the rest of the session and for the next survey.
Prevent it by agreeing beforehand that leadership listens and does not respond during the session, and by telling the room that is the arrangement. If it happens anyway, name the process rather than the person: "Let us hold responses until the themes are complete, so we get the whole picture first." Then move to the next step immediately.
Run this session
IdeaJar is in a facilitator beta. Tell us about the room and we will get you set up.
Session creation includes a matching Survey debrief preset that applies this guide's settings checklist for you.