Form
Story document or slide deck with sections Audience, goal, context, conflict, turning point, evidence, consequence, call to action; plus script or bullet notes for oral variant and feedback notes from dry run.
RunsheetFacilitation
Storytelling
ComplexityMedium
Time45-120 min
Participants1-6
FormatWorkshop + async
MaturityEstablished
01
Preparation
What needs to be ready before start
Materials
Storytelling canvas with sections Audience, goal, context, conflict, turning point, consequence, call to action; notes from research, data or strategy; examples of good and bad stories as anchors; timer.
People / roles
One story owner (author of final message); one to five sparring partners close to target group or communication; optional external reviewer for audience test.
Pre-read
Concrete message as one sentence; desired effect on audience (understand, believe, decide, act); 3-5 pieces of evidence or data; list of non-goals (what story should not attempt).
Time needed
45-120 min
Setup
Canvas on wall. Header with message and audience. Examples of good stories from own context or classic cases visible. Timer on first section.
02
Core question
The one question this method answers
Which narrative leads the defined target group from starting state to the reaction the message needs?
03
Flow
Marker: Sektion
| Step | Duration | Action | Hint |
|---|---|---|---|
1Section 1: Audience and goal | 10-15 min | Describe audience precisely (role, prior knowledge, concerns, what they believe today). Formulate goal of story: what should they understand, believe, do. | "Stakeholder" is not an audience. Name concrete role ("board member with finance focus"). If three audiences at once: three story variants, not one. |
2Section 2: Context and status quo | 10-15 min | What world does audience experience today? What works, what does not, what do they take for granted. Context in 2-3 sentences. | Context too long kills story. Only setup needed to introduce conflict. Anyone telling background longer than conflict loses audience. |
3Section 3: Conflict or tension | 15-25 min | What breaks the status quo? Conflict as concrete event, data point, insight or tension line. One conflict per story, not three. | Without conflict, it is not storytelling, but report. If audience does not think "and then?" after this step, conflict is too weak. |
4Section 4: Turning point and evidence | 15-25 min | What changed or must change? Turning point as insight, decision, data, user voice. 1-2 solid pieces of evidence. | Evidence must be checkable. Storytelling without verifiable anchor is perceived as manipulative, especially with skeptical audience (for example engineering). |
5Section 5: Consequence and call to action | 10-20 min | What follows from turning point for audience? Concrete everyday consequence. Clear call to action: what audience should do or decide after story. | Vague calls to action ("we should look at this") win no decision. "Approve EUR 200k budget for pilot X by 06/30" is one. |
6Section 6: Dry run and iteration | 15-30 min | Tell story aloud or share as 1-pager. Sparring partners play audience and give feedback on clarity, credibility, effect. At least one iteration. | Dry run is mandatory, not bonus. Anyone entering real meeting without rehearsal learns there where story does not carry. At least one sparring before real appointment. |
04
Artifact
What comes out at the end
Versioning / ownership
One entry per story with date and audience in title. After real presentation, add feedback and observed effect; create follow-up versions for iterations or other audiences as copies.
Tool alternatives
- Google Slides or Pitch for slide deck
- Notion or Confluence page for asynchronous stories
- Loom video as spoken story
- 1-pager memo in Amazon style (PR-FAQ)
storytelling-working-template.md
Compact working template for Storytelling with context, input, output artifacts, and next step.
Storytelling Working Template
Goal
Structures information as a coherent story with context, tension, and resolution.
Context
When and for what do we use this method?
Input
Which data, observations, decisions, or materials are available?
Execution
Short notes along the runsheet.
Output artifacts
- Narrative Outline:
- Key Message:
- Story Arc:
Assumptions and open questions
- ...
Decision / Next step
Owner, date, and success signal.
05
Example output
Concrete filled scenario, fictional example
storytelling-beispiel.md
Concrete filled scenario, fictional example
Story — Board: platform investment now, not in 12 months (2026-05-18)
Audience: 5-person board, finance focus, currently believes platform team creates no customer impact. Goal: Approval of EUR 2.8M additional budget for platform team 2026.
Context: We have 11 product teams. Each team builds auth, logging and CI itself. Per team this costs on average 18% of engineering capacity.
Conflict: Last quarter, three teams fixed the same authentication bug separately. A critical compliance gap was discovered only after 6 weeks because nobody was centrally responsible. Sabine, solo tax advisor and our long-term customer, wrote on 2026-05-02: "I trust you with my client data. But when I hear that you solve security questions in a distributed way, I get nervous."
Turning point: We evaluated the pilot. The platform team set up in Q4/2025 standardized the auth module. Three teams use it now. Auth-related bugs in these teams fell by 71% (data: Linear, Q1 comparison). Setup time for new services: from 9 to 1.5 days.
Consequence: If we scale platform team to 8 FTE, we cover logging, CI and observability by Q4. Engineering efficiency increases by estimated 14% (assumption: trend from auth pilot, sensitivity table attached). ROI after 14 months.
Call to Action: Request approval of EUR 2.8M (6 additional FTE) in today's decision, start 2026-07-01.
06
Pitfalls
Recognize symptoms and steer against them
Trap
Story without conflict
Symptom
Contribution is a report: status, data, recommendation. Audience checks out after 90 s.
What to do
Name conflict explicitly: what changes or must change. One tension element is enough and mandatory.
Trap
Wrong audience
Symptom
Story was written for engineering but told to board; technical detail loses audience.
What to do
Fill audience section before writing. For several target groups, create separate versions, not one universal story.
Trap
Data without story
Symptom
Slide deck with 12 charts and data points, without narrative arc.
What to do
Formulate meaning per data point: what does this mean for audience. Data is evidence, not plot.
Trap
Vague call to action
Symptom
Story ends with "we should keep discussing" or "more investment would be useful".
What to do
Call to action with verb, amount/timeframe, date, decider. If audience does not know what to do next, story had no purpose.
Trap
No dry run
Symptom
Story tested first time live in real meeting, reaction differs from expected.
What to do
At least one sparring with audience-near person before real presentation. Incorporate feedback. Several iterations normal.
07
Stop criteria
Done signals checkable in under a minute
Audience unclear or scattered across several contradictory target groups, one story impossible.
Message unclear or not decision-ready, storytelling does not replace strategy work.
No evidence for turning point available, story would be empty or manipulative.
Format wrong (for example oral story for audience that only reads text), effort fizzles.
Time window in real meeting too short (for example 2 min), report format is more efficient.
Audience is hostile and needs negotiation rather than narrative, storytelling deepens distrust.
Finished the runsheet?
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.