Data persuades the rational mind; stories move people to act. Transform analytical output into structured stories that engage emotionally and drive action.
When to Use
- Analysis or recommendations need to reach a broader audience
- Content creation: blog posts, case studies, talks, product narratives, thought leadership
- argument-craft output needs story-wrapping for impact
- Technically sound message that fails to engage
- Presentations needing attention beyond slide one
Core Methodology
Step 1: Define the Narrative Brief
- Audience: who, what they know, what they care about
- Purpose: what should they think, feel, or do after?
- Core message: one sentence — if you can't, the narrative lacks focus
- Medium: blog, deck, case study, video script, memo, talk — each has distinct pacing
- Constraints: word count, tone, brand voice, technical depth ceiling
Step 2: Identify Character and Stakes
Every narrative needs a protagonist with something at risk.
- Protagonist: person, team, company, or idea — audience must identify with or root for them
- Stakes: what happens if they fail? Higher stakes = more engagement
- Antagonist/obstacle: competitor, systemic problem, misconception, status quo, time pressure
Don't skip this for "dry" topics. A financial analysis becomes a story when the protagonist is a CFO choosing between two paths with the company's future at stake.
Step 3: Select the Narrative Arc
| Arc | Structure | Best for |
|---|---|---|
| Problem-Solution | Setup pain, escalate, deliver solution | Product narratives, case studies |
| Before-After-Bridge | Old world, new world, how to get there | Transformation stories |
| Hero's Journey | Ordinary world → call → trials → transformation → return with insight | Thought leadership, keynotes |
| Mystery-Reveal | Puzzle → tension via investigation → insight | Blog posts, talks |
| In Medias Res | Start mid-action, fill in context | Crowded channels, attention grabs |
Match arc to medium and audience patience. A Slack post = Problem-Solution. A 20-min talk can sustain Hero's Journey.
Step 4: Design the Hook
First 30 seconds — or first paragraph — determines whether they stay.
Patterns:
- Surprising fact: violates expectations ("98% of strategies fail before execution")
- Question: poses a mystery ("Why did the best-funded team lose?")
- Vivid scene: drops reader into a moment ("It's 2am and the pager fires for the third time")
- Counterintuitive claim: "The most dangerous risk is the one everyone agrees on"
- Stakes declaration: "This decision determines whether the product ships or dies"
Generate 2-3 options. The strongest one creates a question only the rest of the narrative can answer.
Step 5: Build the Beat-by-Beat Outline
Each beat = unit of information or emotion advancing the story.
For each beat: what happens, what audience feels, transition to next.
Tension rules:
- Escalate before resolving — premature resolution kills engagement
- Complicate the problem at least once after introducing it
- Place the most important insight at peak tension, not after resolution
- End with transformation, not summary
Step 6: Anchor in Concrete Details
Replace abstractions with specific, sensory details.
| Abstract (weak) | Concrete (strong) |
|---|---|
| "Significant cost savings" | "Saved $2.3M in the first quarter" |
| "The team struggled" | "Three engineers quit in the same week" |
| "Improved performance" | "Response time dropped from 4s to 200ms" |
| "A large company" | "A 10,000-person logistics company in Rotterdam" |
Identify 3-5 key moments where a concrete detail anchors the story. These are what audiences remember and retell.
Output Format
🎯 Narrative Brief
- Audience: [who, what they know, what they care about]
- Purpose: [think / feel / do outcome]
- Core message: [one sentence]
- Medium: [format and channel]
👥 Character & Stakes
- Protagonist: [who the audience roots for]
- Stakes: [what's at risk]
- Obstacle: [what stands in the way]
📋 Story Spine
| Beat | Arc phase | What happens | Audience feels | Transition |
|---|---|---|---|---|
| 1 | [Setup/Tension/Resolution/Transformation] | [event] | [emotion] | [link to next] |
| 2 | ... | ... | ... | ... |
🎣 Hook Options
- [Option A — type: surprising fact / question / scene / counterintuitive / stakes]
- [Option B — type]
- [Option C — type]
Recommended: [which and why]
🏆 Arc Selection
- Arc: [Problem-Solution / Before-After / Hero's Journey / Mystery-Reveal / In Medias Res]
- Rationale: [why this fits audience, medium, message]
📝 Key Concrete Details
- Beat [N]: [specific detail and why it anchors]
- Beat [N]: [specific detail]
- Beat [N]: [specific detail]
Thinking Triggers
- "If they remember only one thing, what should it be?"
- "Where does tension peak — am I resolving too early?"
- "Who's the protagonist, and would the audience root for them?"
- "Can I replace this abstraction with a number, name, or scene?"
- "What question does my hook plant that only the full narrative answers?"
- "Would I keep reading after the first paragraph?"
Common Traps
| Trap | What goes wrong |
|---|---|
| Data dump with a title | Listing facts without structure. Information is not a story. |
| Premature resolution | Solution before audience feels the problem. No tension = no engagement. |
| Missing protagonist | Abstract narratives about "the industry" with no character to root for. |
| Abstract language | Generalizations ("significant impact") instead of concrete details ("saved 14 hours/week"). |
| Burying the hook | Background context before the moment that grabs attention. |
| Tension without resolution | Build-up without satisfying answer leaves audience frustrated. |
| Narrative as evidence | A compelling story is not proof. If analysis is weak, a strong narrative makes it harder to challenge — a bug, not a feature. Verify substance before polishing delivery. |
| Selective detail | Cherry-picking concrete details that support the conclusion while omitting inconvenient ones. Anchors should be representative. |