In this guide
Give the story a meeting job
Decide whether the story must open a discussion, explain a result, support a decision, teach a lesson or align people around change. Write the action you want from the group. Without that job, a story can consume time while leaving the meeting unchanged.
Check who is present and what they already know. A story for senior leaders may begin with the decision; a frontline group may need more operational context.
Collect only relevant and shareable evidence
Gather verified facts, dates, observations and outcomes. Separate them from interpretations. Protect confidential information and obtain permission before identifying customers, employees or partners.
Choose one example that represents the issue fairly. Do not use an exceptional case as proof of a general pattern. If the evidence is incomplete, make the uncertainty part of the story.
Use situation, change and next step
Situation explains the starting point and stakes. Change shows the decision, action or evidence that altered the position. Next step names what the group must decide or do. In most meetings, each part can be brief.
Draft the spine in three sentences. If the next step does not follow from the change, more context will not repair the logic. Revisit the evidence or the request.
Make the human detail earn its place
A specific moment can help the group understand impact: a customer question, a manager’s workaround or the instant a process failed. Use it when it clarifies the problem, not simply to create emotion.
Keep the person’s dignity and privacy intact. Composite or fictional examples must be labelled. Return quickly from the example to the evidence and meeting decision.
Fictional meeting story
Situation: Each store reported availability differently, so the regional call spent twenty minutes reconciling definitions.
Change: Three managers tested one exception template and completed the review before the call.
Next step: Agree the five shared definitions and appoint an owner for the two-week trial.
Place the story where it changes the conversation
Use a short story at the opening when it establishes the problem, after data when it explains practical meaning, or before a decision when it clarifies the trade-off. Do not force stories into every agenda item.
Signal the transition: ‘Here is one example of what this looks like in practice.’ This helps the group understand the relationship between the story, evidence and discussion.
Invite examination rather than applause
End with a focused question or decision. Ask what the group sees differently, which assumption needs testing or what action they can support. Be ready for another participant’s evidence to complicate the story.
Use plain language and keep the contribution concise. Digital.gov’s guidance emphasises writing for the audience and structuring information around what people need to know. The same discipline helps spoken communication.
Record action and improve the story bank
Close the agenda item with owner, action and review point. A compelling story without follow-through is entertainment. Send a short record that distinguishes the example from the decision actually made.
Afterwards, ask whether the group understood the intended point and whether the story shortened or lengthened the route to action. Save appropriate examples in a private story bank with evidence, permissions and possible uses.
Before you move on
- The story has a specific job in the meeting.
- Its facts are verified and appropriate to share.
- The structure moves from situation to change to next step.
- Human detail clarifies impact without exploiting a person.
- The story appears where it supports the agenda decision.
- The ending invites examination and a focused response.
- Action, ownership and the lesson are recorded afterwards.
Sources and further reading
These official resources informed the guardrails and practical method in this guide.
This preview uses fictional examples where indicated. Read our editorial approach.