Five questions a facilitator should answer after every session

Written by the IdeaHone Editorial Team · · updated 11 November 2026 · 6 min read

Hand writing on a whiteboard with a black marker

After 30 workshops most facilitators have not run 30 workshops. They have run the same workshop 30 times. The difference is ten minutes the same evening, alone, in writing: five questions that turn one session into a lesson for the next.

Why the same evening, and why in writing

By the next morning you remember that the session went well or badly, not the minute the energy dropped or who said nothing after the break. And "the room was tired" is hard to write next to "I skipped the break to catch up".

The five questions

1. Did we get the decision the brief asked for?

A workshop exists to produce the decision, shortlist or plan named in the workshop brief. Everything else is a pleasant afternoon.

Answer yes, partly or no. If not yes, trace where the time went: a long warm-up, the group reopening the problem at minute 40, scoring that started too late.

If the time went to a planned step, shorten it next time. If it went to something unplanned, write down the sentence you will say the moment it starts again.

2. Who spoke, who did not, and did the record show it?

Three loud people shape most workshops. The ideas you lose are the ones said once, quietly, by someone who did not repeat them.

Name three people who said little and note whether there was a reason (new in the team, their manager in the room, remote while the others sat together). Then open the record: are their remarks in it, or only what was repeated at the wall? A capture that shows who said what answers this in a minute; tools like IdeaHone capture it live, with names where people have agreed.

Choose one method for next time that gives quiet people a channel before the group talks, such as silent writing.

3. Which idea surprised me?

If nothing surprised you, the group produced what you already knew. Either the question was too narrow or the room was too uniform.

Write the idea in one line, then where it came from: which person, which method, which minute. Surprise usually has an address.

If a method produced it, give that method more time next round. If nothing surprised you, change the question or the invitation list before anything else.

4. Where did energy drop and what did I do?

Every session has a low point. Your job is to notice it within two minutes, not on the drive home.

Write the minute, the cause and your reaction: "Minute 55, after the third presentation in a row, I asked for a fourth." Then say whether the fix worked. The uncomfortable answers are the most useful lines in the file.

Move the break, change the format at that point, or cut the block. Decide now, while you still remember the feeling.

5. What will the participants see within 24 hours?

A workshop that produces nothing visible the next day is, for the participants, a workshop that produced nothing.

Name the record, who sends it and when. Check that it is one line per idea with an owner, not a photo of the wall. The follow-up checklist covers the rest.

If the answer is "nothing yet", the workshop is not finished. Finish it before you answer the other four questions.

The routine

  1. Block the time before the workshop. Put 15 minutes in your calendar directly after the session, while you are still planning the agenda. On the day, something else takes the slot.
  2. Answer in writing. One or two sentences per question. The limit keeps you honest and the file readable.
  3. Keep one file per facilitator. Date, workshop, five answers. Not a scored template, not a shared document. A plain file you will actually open.
  4. Read the last three before planning the next workshop. Patterns show up at three. If the energy dropped at minute 55 three times, it is not the room.
  5. Share one insight with the sponsor. One sentence, not the file: "Next time I will seat the two team leads apart." It shows that you learn, and it improves the next brief.

Good signs and warning signs

QuestionGood signWarning sign
DecisionOne sentence, and it matches the brief"We had a great discussion"
Who spokeThe quiet people's remarks are in the recordYou cannot name three quiet people
SurpriseOne idea you could not have written beforehand"The usual suspects, well structured"
EnergyYou noticed within two minutes and changed somethingYou noticed on the drive home
24 hoursOwner, time and format are decided"Someone will type up the notes"

Ask one participant the same five questions a week later. The gap between your answers and theirs is the real learning; your own answers only tell you what you noticed.

Do not turn the questions into a survey for the participants. A feedback form measures satisfaction. This is the facilitator's own work, and it only works when nobody else grades it.

Habits that stop you learning from workshops

  • Skipping it after a good workshop. Good sessions hide the most useful questions, because nobody asks why they worked.
  • Answering in your head. You keep the verdict and lose the detail. Unwritten is unlearned.
  • Blaming the room. "They were tired" answers question four and teaches you nothing. Write what you did.
  • Keeping the answers private forever. The file is yours, but one insight per workshop belongs to the sponsor or the team.

Never lose an idea between sessions

IdeaHone follows every idea from first mention to decision, across all your workshops and teams.

Request a demo

How do facilitators improve?

By reviewing workshops, not by running more of them. A short written retrospective after each session, read back before the next one, turns repetition into practice.

What should a facilitator reflect on after a workshop?

Five things: whether the decision in the brief was reached, who spoke and who did not, which idea surprised you, where the energy dropped and what you did, and what the participants will see within 24 hours.

How long should a facilitator retrospective take?

Ten to 15 minutes, the same evening, in writing. Longer turns it into a report nobody reads; later turns it into a memory nobody trusts.

All resources