Plan my session
Plan a concrete work block with agenda, roles, preparation, and a copyable result artifact.
Session: Storytelling
The plan translates the method into a concrete facilitated work block. Your inputs flow directly into the session brief and work artifact.
Method session with 1-6. The plan uses the existing method logic and the runsheet.
RunsheetUse the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.
The session works directly toward Narrative Outline. After the session, the artifact should be shareable, reviewable, or reusable.
- 1
Section 1: Audience and goal
10-15 minDescribe audience precisely (role, prior knowledge, concerns, what they believe today). Formulate goal of story: what should they understand, believe, do. Hint: "Stakeholder" is not an audience. Name concrete role ("board member with finance focus"). If three audiences at once: three story variants, not one.
FacilitatorNarrative Outline - 2
Section 2: Context and status quo
10-15 minWhat world does audience experience today? What works, what does not, what do they take for granted. Context in 2-3 sentences. Hint: Context too long kills story. Only setup needed to introduce conflict. Anyone telling background longer than conflict loses audience.
FacilitatorKey Message - 3
Section 3: Conflict or tension
15-25 minWhat breaks the status quo? Conflict as concrete event, data point, insight or tension line. One conflict per story, not three. Hint: Without conflict, it is not storytelling, but report. If audience does not think "and then?" after this step, conflict is too weak.
FacilitatorStory Arc - 4
Section 4: Turning point and evidence
15-25 minWhat changed or must change? Turning point as insight, decision, data, user voice. 1-2 solid pieces of evidence. Hint: Evidence must be checkable. Storytelling without verifiable anchor is perceived as manipulative, especially with skeptical audience (for example engineering).
FacilitatorNarrative Outline - 5
Section 5: Consequence and call to action
10-20 minWhat follows from turning point for audience? Concrete everyday consequence. Clear call to action: what audience should do or decide after story. Hint: Vague calls to action ("we should look at this") win no decision. "Approve EUR 200k budget for pilot X by 06/30" is one.
FacilitatorKey Message - 6
Section 6: Dry run and iteration
15-30 minTell story aloud or share as 1-pager. Sparring partners play audience and give feedback on clarity, credibility, effect. At least one iteration. Hint: 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.
OwnerStory Arc - 7
Publish artifact
10 minCheck the artifact for completeness, define location, set version or status, and name review recipients.
OwnerNarrative Outline
Session Brief
For invitations, boards, tickets, PR descriptions, or workshop notes.
session-brief.md
Session Brief: Storytelling
Goal
Artifact: Narrative Outline
Working Question
Which narrative leads the defined target group from starting state to the reaction the message needs?
Context
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).
Setup
- Format: Method session
- Duration: 45-120 min
- Mode: Workshop or async
- Participants: One story owner (author of final message); one to five sparring partners close to target group or communication; optional external reviewer for audience test.
- Owner: One story owner (author of final message)
- Participation mode: Team round, shared work and alignment
- Outcome logic: Finish artifact
Participation Logic
Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.
Outcome Logic
The session works directly toward Narrative Outline. After the session, the artifact should be shareable, reviewable, or reusable.
Input
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.
Preparation
Canvas on wall. Header with message and audience. Examples of good stories from own context or classic cases visible. Timer on first section.
Agenda
-
Section 1: Audience and goal (10-15 min) Owner: Facilitator Action: Describe audience precisely (role, prior knowledge, concerns, what they believe today). Formulate goal of story: what should they understand, believe, do. Hint: "Stakeholder" is not an audience. Name concrete role ("board member with finance focus"). If three audiences at once: three story variants, not one. Output: Narrative Outline
-
Section 2: Context and status quo (10-15 min) Owner: Facilitator Action: What world does audience experience today? What works, what does not, what do they take for granted. Context in 2-3 sentences. Hint: Context too long kills story. Only setup needed to introduce conflict. Anyone telling background longer than conflict loses audience. Output: Key Message
-
Section 3: Conflict or tension (15-25 min) Owner: Facilitator Action: What breaks the status quo? Conflict as concrete event, data point, insight or tension line. One conflict per story, not three. Hint: Without conflict, it is not storytelling, but report. If audience does not think "and then?" after this step, conflict is too weak. Output: Story Arc
-
Section 4: Turning point and evidence (15-25 min) Owner: Facilitator Action: What changed or must change? Turning point as insight, decision, data, user voice. 1-2 solid pieces of evidence. Hint: Evidence must be checkable. Storytelling without verifiable anchor is perceived as manipulative, especially with skeptical audience (for example engineering). Output: Narrative Outline
-
Section 5: Consequence and call to action (10-20 min) Owner: Facilitator Action: What follows from turning point for audience? Concrete everyday consequence. Clear call to action: what audience should do or decide after story. Hint: Vague calls to action ("we should look at this") win no decision. "Approve EUR 200k budget for pilot X by 06/30" is one. Output: Key Message
-
Section 6: Dry run and iteration (15-30 min) Owner: Owner Action: Tell story aloud or share as 1-pager. Sparring partners play audience and give feedback on clarity, credibility, effect. At least one iteration. Hint: 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. Output: Story Arc
-
Publish artifact (10 min) Owner: Owner Action: Check the artifact for completeness, define location, set version or status, and name review recipients. Output: Narrative Outline
Closeout
- Update result artifact: Narrative Outline
- Define location, version, and review recipients.
- Define owner, next step, and review date.
Work artifact
Pre-filled starting point based on the matching template.
work-artifact.md
Narrative Outline: Storytelling
Working Question
Which narrative leads the defined target group from starting state to the reaction the message needs?
Context
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).
Participants
- Owner: One story owner (author of final message)
- Participants: One story owner (author of final message); one to five sparring partners close to target group or communication; optional external reviewer for audience test.
Input
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.
Template
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.
Completion Check
- Narrative Outline is complete enough for review:
- Location:
- Version / status:
- Review by:
- Next step:
Next Step
- Review result
- Mark open questions
- Schedule review or decision
Storytelling Working Template
View templateCompact working template for Storytelling with context, input, output artifacts, and next step.markdown
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.
- Working question, owner, and target artifact are visible.
- The result fits Narrative Outline.
- 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.
- Open questions are noted as follow-ups.
- The next review or decision point is scheduled.