ThemeCapture & close
CardCard 11 of 60
Questions5 to explore

Deliverables

Will participants produce or present something?

Deciding upfront what participants will actually produce changes how you design every activity before it.

A deliverable is something that comes out of the workshop: a decision, a prototype, a ranked list, a written plan, a commitment, a visual map. Not every workshop needs one, but if yours does, name it before you design the day. The clearer the output, the easier it is to work backward to the activities that will generate it.

Deliverables also set expectations for participants. People work differently when they know the session ends with something they have to stand behind. Make sure the deliverable is realistic for the time, the group, and the energy you will have at the point in the day when it is produced.

Easy to missDecide whether the deliverable will be taken away by participants, left behind for the organizers, or handed to a specific person, because that one detail affects format, file type, and what happens in the last 20 minutes of the session.

How experienced facilitators handle it

The same building block, handled by people who have run a lot of workshops. Patterns and illustrations to react to, not rules to follow.

Name the output early

Experienced facilitators write the deliverable down and share it with participants before the session, so everyone arrives already understanding what they are working toward.

Match output to time

They check whether the group can realistically produce the deliverable in the time available, then scale either the ambition or the time accordingly, rather than leaving it to chance.

Build toward it visibly

They design the final activity to feed directly into the deliverable, so participants experience the last step as natural completion rather than a sudden demand.

Agree on ownership

They settle in advance who owns the deliverable after the session ends, who writes it up, and who is responsible for acting on it.

Questions to plan around

Use these on your own or in a group. There are no right answers, only better conversations.

What will participants have made, decided, or produced by the time they leave?
Is the deliverable shared output for the group, or does each person take something individual away?
Who owns the deliverable after the session, and what happens to it next?
Is what you are asking people to produce realistic given the time, number of participants, and energy level at that point in the day?
Have you told participants in advance that they will produce this, so they can prepare?

Watch for

A vague deliverable ('some ideas', 'a conversation') gives participants nothing to build toward and often results in a session that feels like it ended before it finished.
Setting a deliverable that requires work the group cannot do in the room, such as verifying data or getting sign-off from absent stakeholders, creates frustration and unfinished output.
The deliverable you planned at the start may need to be adjusted mid-session based on how discussions actually go; experienced facilitators build in a moment near the end to check whether the original output still makes sense.