A workshop presentation is a working surface for a group. Participants need to know why an activity matters, what to do next, how long it will take and what they will leave with. Start with a clear outcome and use an education presentation structure when you need a reliable rhythm between explanation and practice.
Write the participant outcome
Describe the observable result: draft a one-page plan, identify three risks, or practice a conversation. “Understand the topic” is too vague to guide an activity. The outcome determines what belongs on the slides and what should stay in the facilitator notes.
List the assumed knowledge and the group size. A workshop for eight specialists can use different prompts from one for forty new starters. Include an access or materials note early so people are not surprised when an exercise begins.
A finished brief for a sixty-minute workshop
Use this fictional session: eight service-team members must choose next week’s improvement work from six requests. They have five person-days available. By the end, they will produce a short backlog showing what is selected, what is deferred, why and who takes the next action. This is a prioritization exercise, not permission to override a mandatory safety or legal requirement.
Prepare six request cards, the capacity constraint, a shared decision sheet and a way to contribute in writing. Participants work in two groups of four. The facilitator demonstrates with a spare example before they start, so the first exercise does not become a debate about the instructions.
The CDC’s Quality Training Standards, developed for public-health training, connect objectives, relevant practice and learner assessment. The transferable principle is alignment: if the outcome is a defensible work plan, people must practice making and explaining one, not just listen to a lecture about prioritization.
Build a timed rhythm
Alternate short input with action. A useful pattern is orient → demonstrate → practice → compare → apply. Put the minutes on the agenda, and show the current step on activity slides. If a discussion runs long, identify the part that can be shortened without losing the outcome.
Do not make the agenda a promise that no one can follow. Add a visible break or reset point for longer sessions. A facilitator can move faster when the group is ready, but participants still need a map of where the work is going.
The sixty-minute run sheet
| Time | What the group does | Material | Output |
|---|---|---|---|
| 0–5 min | Hear the outcome and five-day constraint. | Opening slide. | A shared task definition. |
| 5–12 min | Read six cards; ask factual questions. | Request cards. | Unknowns separated from assumptions. |
| 12–17 min | Watch an example decision. | A completed spare card. | A model explanation. |
| 17–32 min | Select work and explain deferrals in two groups. | Activity slide and decision sheet. | Two proposed backlogs. |
| 32–42 min | Each group shares its choice and hardest trade-off. | Groups’ sheets. | Differences made explicit. |
| 42–53 min | Discuss differences; agree a proposal or record dissent. | Combined decision log. | One proposal with unresolved issues visible. |
| 53–60 min | Name owners and explain the next action. | Take-away slide. | A dated action record. |
The timings total sixty minutes, including the debrief. If introductions take three extra minutes, shorten the factual-question round and collect outstanding questions on the sheet; do not silently remove the final ownership step. For a thirty-minute version, reduce the input to three cards and use one group decision. Running the full exercise at twice the speed changes the task into rushed voting.
Make instructions doable on one slide
An activity slide should answer: work alone or together, use what input, produce what artifact, and stop when? Put an example of the expected output next to the instructions. Long paragraphs belong in a handout, not in the moment when people are trying to start.
Use a timer or checkpoint that the facilitator can see. When groups need different amounts of support, add a prompt for the facilitator rather than adding five competing instructions to the participant slide. A business continuity tabletop exercise shows how to separate participant scenarios from facilitator follow-ups and observer notes when the workshop rehearses decisions rather than operates a live system.
The activity slide, written out
Choose next week’s improvement work — 15 minutes. “Work in your group of four. Read the six request cards. Select a package that uses no more than five person-days. For each selected request, name the benefit and the evidence on the card. For each deferred request, record the reason and what would make you reconsider. Do not invent missing evidence. Choose one speaker to explain your hardest trade-off.”
The six fictional cards contain: A, correct a broken confirmation link, one day, ten recorded failures; B, rewrite an ambiguous confirmation message, two days, twelve recorded questions; C, add a manager dashboard, four days, one request but no agreed measure; D, change page colors, two days, no reported task failure; E, make the request form usable by keyboard, two days, a blocked keyboard-only task in this scenario; F, interview requesters about a suspected issue, one day, cause unknown. Effort and evidence are invented for this exercise, not general estimates.
Assign a reader, recorder, timekeeper and challenger within each group. At minute ten, ask, “Does your package fit five days, and have you recorded the cost of what you left out?” Early finishers should test a changed assumption, such as one item taking an extra day, rather than add work just to fill the slide.
Design the share-back and debrief
Reserve time for groups to compare outputs. Tell them what to share: a decision, a pattern, a question or a next action. The debrief is where the activity becomes reusable knowledge, so do not treat it as optional if the schedule slips.
Capture the group’s words without claiming consensus. A parking-lot slide can hold questions that need follow-up. A simple decision or action log turns a good conversation into something the team can continue after the workshop.
What a participant output can look like
| Decision | Reason | Follow-up |
|---|---|---|
| Select A, B and E: 5 days total. | Address three described task failures within the capacity limit. | Assign owners and confirm effort assumptions before scheduling. |
| Defer C and D. | C lacks a defined decision the dashboard would support; D lacks an identified task problem. | Ask requesters for the missing purpose or evidence. |
| Defer F from this package, but keep the question open. | Research may be valuable, but the package uses all capacity. | Reconsider if one item is smaller than estimated or the unknown threatens the plan. |
This is one defensible answer to the fictional brief, not the answer every group must reach. Another group may choose A, E and F with a day unallocated, explaining why it prefers research before using the remaining capacity. Ask what evidence would change each decision. Do not award points simply for agreeing with the facilitator.
During share-back, give each group two minutes for its package and three minutes for questions. Capture disagreement as “unresolved,” with the person who can decide it. A show of hands does not give a group authority it does not possess.
Finish with a usable take-away
End with the artifact participants created, the next action and the owner. Link to a template or export a handout if the group needs to use the result later. Ask one person to explain the next step without looking at the facilitator notes.
After the session, record what took longer than planned and which instruction caused questions. Update the next version from those observations rather than adding more decorative slides. A workshop deck improves when it helps people do the work with less explanation.
Close with a record people can use next week
The final sheet should say: “Proposed package: A, B, E. Capacity assumption: five person-days. Next action: the service lead confirms effort and owners before scheduling. Open point: whether F should replace part of the package if the unknown affects delivery. Review trigger: a material change in effort, evidence or a mandatory requirement.” Replace role labels with actual owners in the internal copy.
Ask someone who did not present to explain what is selected and what still needs a decision. Their answer reveals whether the session produced a usable plan. Save the group’s artifact, not only the facilitator’s slides. Next time, reuse the structure but refresh the cards: the point is practicing judgment, not remembering a preferred combination of letters.
