Series: How to Run a Workshop People Remember (8/10)
Here's a pattern I've watched in hundreds of observed workshops: the activity runs beautifully, the energy in the room is high, and then the facilitator says "Great! So… what did we all think of that?" Three people talk. Five minutes of unstructured conversation later, the clock says time's up, and the facilitator moves on — relieved, because the activity "went well."
The activity produced an experience. The debrief is where the experience becomes learning. Skip or rush it, and the best activity in the world is just a fun fifteen minutes with a prop budget.
Why "what did we think?" fails
Open-ended, opinion-shaped, aimed at the whole room at once. It invites the confident to perform and gives the reflective nothing to chew on. A debrief needs what any good interview needs: a sequence of questions with a job each.
The sequencing logic I use is the oldest one in facilitation — What? So what? Now what? — and it's exactly why the Blind Portrait folder from part 2 ships its debrief as a script: eight questions in order, each with a purpose (which instructions were missing, what did you guess instead, where does this happen on your team). You don't have to invent a question sequence per workshop. You have to not skip it when you're behind — which is why it lives in the run sheet, with minutes attached like any other block.
Give the room a private channel
The biggest debrief handicap is that speaking in front of twenty people is a performance. Two mechanics that pull honest answers out of people who will never raise a hand:
Written before spoken. Everyone writes one answer on a sticky or a card before anyone speaks. It's much harder to quietly conform to the group when your answer already exists on paper. The Exit Ticket folder is built on exactly this: one written takeaway per person at the door, not a mic passed around the room.
An anonymous wall. For the questions people won't say out loud ("what's one thing this workshop is missing?"), QRCard's live message wall works the way the name suggests: participants scan and post, and messages appear on the screen as a wall — as a grid or drifting bullets, anonymous by design:
The facilitator's move that makes the wall earn its keep: read two or three posts out loud and respond to the critical ones first. The room learns that the anonymous channel reaches the facilitator and gets taken seriously — which is what makes it honest next time. Contrast with part 4's rule (counts, not names): the wall is the one place where anonymous text is the point, but it's still text, not identities.
Capture the trail — for yourself and for the client
Three capture habits that separate professionals from people who run workshops:
- Record the debrief, with consent. I put a note about it in the invite and say it out loud at the start. Otter.ai is the lazy, reliable option for transcription — the transcript is for your own debrief-of-the-debrief ("which questions landed, which produced silence"), not for the client.
- Collect structured feedback while the room is still warm. A feedback card on the table (part 3's QR card, one action, no login) for the two-minute in-room version, and a structured follow-up survey for the next morning — the workshop feedback form template from part 6 is the one I use, because the responses come back scored rather than as paragraphs to decode.
- Follow up within 48 hours. One email: the commitments people wrote at the close (part 1's beat four), the slides or materials, the one thing you'd change next time. Wait a week and you're just another inbox item; within 48 hours, you're still the room they were in.
The debrief of the debrief
The step almost everyone skips: ten minutes after the room empties, before you pack the props. Three questions, written in the margin of the run sheet:
- Which block ran over, and what did I cut? (If the answer is "the debrief," fix the timing, not the debrief.)
- Which debrief question produced silence, and what will I replace it with?
- What did the wall say that nobody said out loud?
That margin note is the difference between a workshop you run once and a workshop you get better at. It's also, incidentally, the raw material for part 9 — because the notes, the measured deltas and the feedback all feed the thing that turns a one-off workshop into a recurring engagement: reporting.
Next in the series: the monthly report clients actually read — and how to produce it in fifteen minutes instead of an afternoon.
Tools in this post:
- WorkshopSkill — folders with scripted debriefs and exit tickets: Blind Portrait (8-question debrief), Exit Ticket, Four Styles Debrief
- QRCard AI — the live message wall for anonymous, scan-to-post reflections
- FormLM — the workshop feedback form template for structured, scored post-session feedback
- Otter.ai — consent-on-the-record transcripts for your own review
*Disclosure: I'm one of the makers — the tools from my own shop named across this series. *
Top comments (0)