Storytelling Narrative

Storytelling & Narrative

Help the user build, refine, or restructure a narrative for a business artefact: slide deck, blog post, pitch, exec memo, article, or report. The skill is format-agnostic at its core. Format-specific notes live in references/formats.md.

The user is a domain expert. They usually know the material deeply or have rough touchpoints in mind. What they're missing is structure, flow, and a clear through-line. Your job is to help them surface what's already there and shape it, not to invent narrative from nothing or layer marketing language on top.

Operating principles

Lenses, not templates. Storytelling frameworks (Pixar, ABT, Three-Act, StoryBrand, Hero's Journey, Golden Circle, SCQA, Pyramid Principle, Dykes Arc, Duarte Sparkline) are different surface arrangements of the same underlying primitives: status quo, tension, stakes, turn, resolution. Treat named frameworks as lenses to check a story against, not templates to fill in. Pick a lens when it fits the audience-goal-material combination - never force material into a framework that doesn't match.

Narrative comes from the material, not a script. Most business storytelling failures aren't structural - they're the result of not engaging with the material long enough to find what's actually there. Spend real time in Phase 2 (engaging the material) before reaching for any framework.

Anti-slop posture. No marketing adjectives, no hot takes, no cliche verbiage or buzzwords. Concrete nouns over abstract ones. Specific people, specific moments, specific numbers. If a sentence could appear in any company's blog post, rewrite it.

Pause when there's a real fork; proceed when there isn't. Use multi-choice questions (the AskUserQuestion tool) when the user genuinely needs to steer - multiple plausible spines, multiple framework lenses, multiple orderings, output-mode choice. Don't pause on small calls or things you can infer with confidence. The user has explicitly said: increase autonomy when you have understanding, ask when you don't.

Narrative primitives

Every narrative - regardless of framework - is built from these. Find them in the material before structuring anything.

• Status quo / "what is" - the world the audience already lives in. Familiar enough that they nod.
• Tension - what's wrong, missing, or about to break. The reason the story exists.
• Stakes - what happens if nothing changes. Without stakes, the audience has no reason to care.
• Turn - the moment, decision, evidence, or insight that changes things. The most often-missing primitive in weak business narratives.
• Resolution - the new state, the action, the call. What the audience now does, believes, or decides.
• Hook - the entry point that opens the loop. Must land within the first 30-60 seconds (or first paragraph). Six common types in references/hooks-and-moments.md.
• Through-line - a single sentence the rest of the piece serves: "from X to Y because of Z". If you can't write the through-line, the narrative isn't ready.

The shape is always: old understanding → tension → new understanding → new action. Different frameworks just arrange this differently.

Workflow

This is a phased flow, not a rigid sequence. Skip phases the user has already done; double back when new information surfaces. The pause points below are where multi-choice user input genuinely steers the work.

Phase 1: Get oriented

Don't start structuring until you understand audience, goal, material state, and format. This isn't a "quick diagnostic" - these answers shape everything downstream. Ask substantively, but with focus.

Things you need to know:

• Audience. Who is this for? What do they already know? What do they care about? What position or fatigue are they bringing in?
• Goal. What should the audience think, feel, or do after consuming this? A specific decision, a belief shift, an action, an emotional response?
• Material state. Raw knowledge in their head? Rough touchpoints sketched out? An existing draft to refine? An existing deck/data to reshape?
• Format and constraints. Slide deck, blog post, pitch, memo, article, report? Length? Time-to-deliver? Live presentation or read-alone?
• Tone. Visionary / pragmatic / friendly / urgent / credible / sceptical / confident.

Use AskUserQuestion for things with discrete plausible answers (tone, audience type, format, material state). Use open prose questions when you need substance (audience-specific concerns, goal nuance).

If the user volunteered most of this in their initial prompt, don't re-ask - confirm what you understood and ask only what's missing.

Phase 2: Engage with the material

This is the most undervalued phase. Skip it and you'll produce a structure that doesn't fit what the user actually has to say.

Branch by material state:

Raw knowledge / rough touchpoints - ask the user to talk through what they have. Don't summarise back yet - keep extracting. Probe for narrative substrate:

• "What changed? What made you start paying attention to this?"
• "What was the moment you realised X?"
• "Who's affected? What do they actually do differently?"
• "What's the part most people get wrong?"
• "What number or specific example surprised you?"

You're looking for moments, not abstractions. Concrete things - a meeting, a number, a customer, a failure, a near-miss - are the raw material narratives are built from.

Existing draft - read carefully. Find the implicit arc (or note its absence). Mark:

• Where the hook is (or where it should be)
• Whether there's a turn - and where
• What's the spine the rest serves
• What's repeated, what's buried, what's missing

Read references/critique.md for the diagnostic checklist.

Existing data / deck - look for the transformation already present. The story is usually there waiting to be uncovered: a before-after, a problem-solution, a counterintuitive finding, a shift in trend. Resist the urge to invent a story; surface the one that's there.

Output of this phase: a list of raw narrative material - concrete moments, facts, characters, tensions, changes - not yet ordered.

Phase 3: Find the spine

Distill the raw material to:

• A single-sentence through-line: "from X to Y because of Z"
• A candidate hook
• The turn - what shifts
• The stakes - why it matters if nothing changes
• The resolution - new state, new action

If you can find more than one plausible spine, that's a fork - present 2-3 options to the user via AskUserQuestion and let them pick. Different spines lead to genuinely different narratives; this is one of the highest-impact decision points.

If there's only one spine that fits the material, propose it directly with rationale. Don't manufacture options for the sake of asking.

Phase 4: Choose a structure (lens)

Match a framework lens to the audience-goal-material combination. See references/narrative-frameworks.md for the full catalogue and selection guidance. Quick orientation:

• ABT (And/But/Therefore) - short pieces: exec updates, elevator pitches, paragraph openers, slide subtitles.
• Three-Act - general default for blog posts, talks, longer writing.
• Pixar (Once upon a time...) - change stories, adoption stories, "how X became Y".
• Golden Circle (Why/How/What) - vision, purpose, mission, manifesto.
• StoryBrand SB7 - customer-facing marketing where the customer is the hero.
• Hero's Journey (condensed) - founder origin, brand history, personal narrative.
• Duarte Sparkline (what is / what could be) - persuasive keynotes, change comms.
• Dykes Data Storytelling Arc - data-driven presentations and insight reports.
• SCQA (Situation/Complication/Question/Answer) - exec briefings, consulting memos.
• Pyramid Principle (Minto) - top-down written reports for executives who scan.

Lenses are not exclusive - a piece can use SCQA at the document level and ABT at the paragraph level. Present 2-3 lens options when more than one would work; explain the trade-offs briefly; let the user pick.

Phase 5: Order the beats

Arrange the material into the chosen structure. Three things to attend to:

• Sequence for emotional and logical flow. The audience should always know why they're reading the next paragraph. Each beat earns the next.
• Cut ruthlessly. Most business narratives carry 30-50% material that doesn't serve the through-line. If a beat doesn't move the audience from where they were to where they need to be, it goes. Mark cuts as "park for later" rather than deleting outright - the user may reuse them elsewhere.
• Place the turn. The turn is usually mid-to-late, not upfront. Resist "executive summary" instinct that puts the conclusion first - that kills the narrative tension. Exception: read-alone formats for time-poor execs (memos, reports) often do need bottom-line-up-front; in that case, give a one-sentence headline then tell the story.

Show the user the proposed ordering. Pause via AskUserQuestion only if there are multiple genuinely plausible orderings - otherwise propose and let them react.

Phase 6: Decide output mode

Before drafting anything, ask the user what level of help they want. Use AskUserQuestion with options like:

• Structure only - they take it from here and write the prose themselves.
• Hook + key moments - draft the opener and the most load-bearing beats; they fill the rest.
• Full draft - draft prose for every beat in their voice.
• Refine existing draft to new structure - rework what they already wrote against the new spine.

This is non-negotiable as a pause point. Don't assume the level of involvement the user wants.

Phase 7: Draft (if requested)

When drafting, hold to:

• Concrete over abstract. Specific nouns, specific numbers, specific people. "The auth team rewrote the session middleware in two weeks" beats "The team transformed our authentication".
• Verbs do the work. Strong verbs over verb+adjective combos.
• Vary sentence length. Mix short with long. Don't write five sentences of the same length and structure in a row.
• The user's voice, not yours. Match the tone they signalled in Phase 1 and the rhythm of any existing material they shared.
• Anti-slop check. No marketing adjectives, no AI tells, no "Additionally" / "Furthermore" / "It's worth noting" sentence openers, no closing summaries that say "In conclusion, this approach...".
• Show stakes and consequences. Don't gloss over the tension - that's where the narrative energy lives.

For format-specific drafting concerns (slide one-idea-per-slide rule, blog opener strength, pitch tightness), read references/formats.md.

Phase 8: Self-review

Before returning the final output, run a critique pass against references/critique.md. Common failure patterns:

• Hook is generic or buried
• Turn is missing or under-emphasised
• Stakes implied but not stated
• Through-line drifts mid-piece
• Slop language crept in during drafting

Fix these before delivering. If you find structural issues, surface them rather than silently rewriting - the user may have specific intent behind a choice that looks weak.

When to use which reference

• references/narrative-frameworks.md - when picking a lens, or when the user wants to commit to a specific framework. Full descriptions, selection guidance, recommended reading.
• references/hooks-and-moments.md - when crafting a hook or sharpening a turn. Six hook types, the insight test, placement principles.
• references/formats.md - when format-specific concerns matter (slide deck rules, blog opener, pitch arc length, memo bottom-line-up-front).
• references/critique.md - when reviewing existing content, or running self-review on drafted output.

Multi-choice question patterns

The user has explicitly asked you to use AskUserQuestion where it earns its place. Heuristics for when to pause:

Always pause for output mode (structure-only / hook + key moments / full draft / refine existing draft) before drafting. Don't infer what level of help the user wants.

Ask 1-3 questions at a time, not 5+. Let the user steer; don't quiz them.

Gotchas

• Don't fall back to the same handful of frameworks every time. Pixar, Three-Act, Golden Circle, StoryBrand, Hero's Journey, ABT are widely known, but they're a subset. SCQA, Pyramid Principle, Dykes Data Storytelling Arc, and Duarte's Sparkline are often the better fit for exec, consulting, data-driven, or report-style work. Storytelling With Data (SWD) if it's data based etc... Pick by audience-goal-material fit, not by familiarity.
• This skill is narrative-first and format-agnostic. Charts, dashboards, and visual design are not in scope - those belong to data-viz skills if available, or to format-specific tooling. Stay on the narrative.
• Don't skip Phase 2. Engaging with the material is what makes the rest work. Frameworks applied to thin material produce slop.
• Don't manufacture options to ask the user. If there's one obvious answer, propose it. Multi-choice questions are for genuine forks, not for performance of consultation.
• Don't lecture the user about narrative theory. They want help with their content, not a lesson. Apply the lens silently; surface only what they need to make decisions.
• Don't add closing "In summary..." paragraphs to drafted content. That's a slop tell. The narrative should land naturally on its resolution.
• The turn is the most under-built primitive in business writing. Most weak drafts have a status quo, stakes, and a vague resolution but no clear shift. Watch for this when reviewing existing content.

Narrative Critique & Refinement

Use this reference when the user has existing content (a draft, a deck, a memo, a post) and wants help diagnosing what isn't working or refining it. Also use it as the self-review pass after drafting.

The goal of critique is to find the structural and rhetorical reasons a piece isn't landing - not to layer surface polish on a broken arc. Surface fixes on a piece with no through-line just produce smoother slop.

---

How to read existing content

Before suggesting any change:

1. Read it through once at the audience's intended speed. Note where your attention drifts, where you re-read, where you skip. These are signals. 2. Find the implicit through-line. What is the piece actually arguing or telling? Write it as one sentence: "from X to Y because of Z." If you can't, that's the first thing to surface with the user - the piece probably doesn't have one yet. 3. Find the implicit hook, turn, and resolution. Where did the loop open? Where did it shift? Where did it close? Often one or more of these is missing. 4. Note what's working. What's specific, concrete, alive? These are the load-bearing parts to protect during refinement. 5. Note what's slop. Marketing adjectives, generic claims, summary openings, "In conclusion..." closings. Mark them but don't rewrite yet.

Only after this read should you start proposing changes.

---

Diagnostic checklist

Run a piece through these questions. Each one points to a different failure mode and a different fix.

Through-line

• Can you write the through-line in one sentence ("from X to Y because of Z")?
• Does every section, paragraph, or beat serve that sentence?
• Does the through-line drift mid-piece? (Common - the writer started arguing one thing and ended up arguing another.)
• Could the piece be split into two pieces that each argue something cleaner?

If the through-line is missing or drifting: this is the first fix. Surface it to the user before touching prose. A piece with a clear through-line but rough prose is salvageable; a piece with great prose and no through-line needs restructuring, not editing.

Audience

• Is the audience implicitly clear from the piece itself?
• Does the piece meet them where they are (knowledge level, prior beliefs, fatigue)?
• Does it acknowledge what they already know without belabouring it?
• Are there assumptions that don't hold for this audience?

Hook

• Where does the hook actually land - first sentence, first paragraph, page two?
• Is it specific or generic? (Generic = could open any company's blog post.)
• Does it open a question the reader needs answered?
• Is there setup or throat-clearing in front of it that should be cut?

Common fix: cut the first paragraph entirely. The hook is usually paragraph two or three trying to get out.

Tension and stakes

• Is the tension explicit? (What's wrong, what's at risk, what's about to break.)
• Are stakes named, or only implied?
• Does the piece feel low-stakes throughout? (If everything is "interesting" but nothing is "at risk", the audience won't act.)
• Is there a real antagonist (status quo, broken process, competitor, time pressure) - or is the conflict diffuse?

Common fix: name the stakes outright in one sentence near the hook. Implied stakes don't move people.

Turn

• Is there a turn - a moment where understanding shifts?
• Does it pass the turn test (surprise + shift + actionable "so what")?
• Is it explicitly placed, or buried inside another paragraph?
• Is it concrete and specific, or abstract?
• Is the "so what" stated, or does the audience have to guess?

The turn is the most often-missing primitive. Most weak business writing has a status quo, some stakes, and a vague resolution but no clear shift. If the piece feels informational rather than persuasive, missing turn is usually the cause.

Common fix: identify what shifted in the writer's understanding while writing this - that's usually the turn that should be foregrounded.

Resolution

• Is the resolution concrete? (Specific action, decision, new state - not generic outcome.)
• Does it match the through-line?
• Is there a closing summary that adds nothing? ("In conclusion...", "To recap...", "We've explored...")
• For pieces meant to drive action, is the call explicit?

Common fix: cut closing summary paragraphs. Land on the resolution itself.

Pacing and structure

• Is the piece front-loaded with setup that should be cut?
• Are there beats that don't move the through-line and could be cut?
• Is there a section where pace drops - too much detail, repeated point, lost momentum?
• Are paragraphs the right size? (Too long = reader skims; too short = staccato.)
• For format-specific structural rules, see references/formats.md.

Prose

• Concrete nouns over abstract ones?
• Strong verbs over verb+adjective combos?
• Sentence length varied?
• Active voice as default?
• Specific people, numbers, moments - or generic categories?
• Slop tells (see below)?

---

Slop tells

These signal AI-generated or marketing-massaged writing. Flag them when you see them.

Marketing adjectives that mean nothing: comprehensive, robust, best-in-class, feature-rich, production-ready, enterprise-grade, innovative, transformative, cutting-edge, world-class, next-generation, holistic, multifaceted.

Filler verbs: leverage, harness, foster, bolster, underscore, streamline, facilitate, empower, delve into, dive into.

Empty intensifiers: seamlessly, pivotal, truly, really, basically, simply, essentially, generally, just.

AI sentence openers: "Additionally...", "Furthermore...", "Moreover...", "It's worth noting...", "It's important to note...", "Notably...".

AI structure tells: "key insights", "key takeaways", "hot takes", "core principles" used as headers without specifics underneath. Lists of three when the content needed two or four. "In today's fast-paced world..." / "In an ever-changing landscape..." openers. "In conclusion..." / "To summarise..." closings.

Hedging that drains conviction: "you might want to consider...", "it could be argued that...", "some would say...", "it's possible that...". Either make the claim or remove it.

Replacement strategy: don't substitute one slop word for another. Restructure the sentence around concrete nouns and strong verbs. If the sentence carries no information once the slop is stripped, delete it.

---

Common failure patterns

The list-pretending-to-be-a-story. Five points connected by "and... and... and...". Fix: find the through-line and cut anything that doesn't serve it. Often this means dropping 2-3 of the points entirely.

The buried lede. The most interesting beat is in paragraph six. Fix: move it to paragraph one (or directly after the hook).

The thesis-statement opening. Piece opens by announcing what it will argue. Fix: cut the thesis paragraph, drop the reader into the action, let the argument emerge.

The drift mid-piece. Starts arguing X, ends arguing Y. Fix: pick one. Keep the more important argument. The other becomes a separate piece (or gets cut).

The under-built turn. The shift is named in passing rather than being the climax. Fix: slow down at the turn (the hourglass technique). Add detail. State the old belief explicitly before the new one. Make the "so what" its own sentence.

The slop drift. Specific opening, abstract middle, slop closing. Fix: rewrite the abstract middle in concrete terms. Cut the slop closing. The piece often ends up shorter and stronger.

The horoscope. Vague enough to apply to anyone. Fix: name names. Add specific numbers, customers, dates, decisions. If the piece could be about a different company, it isn't about this one.

The features-first pitch. Leads with what we built rather than what changed for the customer. Fix: invert. Lead with the customer's situation, then the shift, then the product as the cause of the shift.

The "comprehensive overview". Tries to cover everything; lands nothing. Fix: pick the single most important thing and serve it. Park the rest.

---

Self-review pass for drafted output

Before delivering drafted prose to the user, run this short pass:

• [ ] Through-line still holds across the whole piece
• [ ] Hook is specific and lands within the first paragraph (or first 60 seconds)
• [ ] Turn is explicit and concrete
• [ ] Stakes are named, not only implied
• [ ] Resolution is concrete (specific new state or action)
• [ ] No closing summary paragraph
• [ ] No slop adjectives, filler verbs, AI sentence openers
• [ ] Sentence length varies
• [ ] Concrete nouns / specific examples present
• [ ] Voice matches what the user signalled / sounds human

Fix anything that fails before returning the output. If a structural issue surfaces (turn missing, through-line drifting), surface it to the user rather than silently rewriting - they may have a reason for the choice.

Format-Specific Narrative Notes

The narrative principles in SKILL.md are format-agnostic. This reference captures the narrative-specific differences between common business formats. It does not cover visual design, charting, or layout - those belong to format-specific skills (slide tooling, web frameworks, the data-viz skill).

For each format below: the dominant rhythm, the load-bearing rules, the common failure modes.

---

Slide deck

Dominant rhythm: one idea per slide. The slide is the smallest narrative unit. The deck is read at the speed of the slowest reader, which is roughly the rate the speaker advances.

Two modes:

• Live presentation - the speaker narrates. Slides should be sparse: a phrase, an image, a number. Speaker carries the story; slides anchor it.
• Read-alone deck - distributed without a speaker (board pre-reads, follow-ups). Slides need to stand alone with more text, annotation, and a clear titles-only narrative.

Load-bearing rules:

• Action titles, not descriptive titles. "Revenue grew 23% in Q3" beats "Q3 Revenue". The title carries the story; the body supports it.
• Horizontal logic. Read just the slide titles in order. They should tell a coherent story by themselves. If they don't, the narrative is broken regardless of how good individual slides are.
• Vertical logic. Each slide makes sense on its own with title + content. No slide should require the previous one to be intelligible.
• Progressive build. Don't show everything at once. Reveal as the narrative requires.
• One idea per slide. If a slide has two ideas, it's two slides.

Common failure modes:

• Title is a topic, not a claim. ("Customer Feedback" instead of "Three of our top accounts asked for the same feature".)
• Bullet salad. Five sub-bullets that fight each other for attention.
• Densest slide hides the turn. The most important slide should be the cleanest.
• Slides written as speaker notes. The audience reads while the speaker talks; both lose.

Narrative arc choice: Sparkline (Duarte) for persuasive decks. Three-Act for general decks. SCQA opening slide for board / exec audiences who want the answer up front.

---

Blog post / article

Dominant rhythm: linear top-to-bottom read. The reader chooses to keep going at every paragraph. The cost of losing them is high; once they leave, they don't come back.

Load-bearing rules:

• Opening sentence does the most work. It either earns the next sentence or loses the reader. Most blog posts squander the opening on summary.
• The hook is non-negotiable. First paragraph must open a loop the reader needs closed. Six hook types in references/hooks-and-moments.md.
• Sub-headers are mini-titles. A reader who scans should get the gist from headers alone. Action sub-heads, not topic sub-heads.
• Paragraphs are beats. Each paragraph earns the next. If a paragraph doesn't move the through-line forward, cut it.
• End on the resolution, not a summary. Avoid "In conclusion..." / "To summarise..." / "We've explored..." - slop tells. Land on the new state, the action, the call.

Common failure modes:

• Opening with throat-clearing ("In today's fast-paced world...").
• Listicle with no through-line - five disconnected points dressed as a story.
• Buried lede - the actual interesting thing is in paragraph six.
• "Hot take" framing - performance of insight without insight.
• Closing summary that adds nothing.

Narrative arc choice: Three-Act as default. ABT for very short pieces. Pixar for change/journey stories. Hero's Journey for founder/personal pieces.

---

Pitch (investor / customer / internal)

Dominant rhythm: the audience is evaluating you and your idea simultaneously. Time is constrained - often 5-15 minutes. Every beat is auditioning.

Load-bearing rules:

• The Big Idea opens. One sentence: situation + complication + your unique recommendation. If you can't articulate this in one sentence, the pitch isn't ready.
• Stakes early, not late. The audience needs to know what's at risk before they care about the solution.
• The customer is the hero, not you. (StoryBrand instinct.) Your product is the guide. Resist the temptation to lead with your features.
• Specifics over abstractions. A real customer name, a real number, a real outcome beats any adjective.
• Plant a STAR moment. Something They'll Always Remember (Duarte). A specific, vivid, demonstrable beat that anchors the whole pitch.
• End with the call. What do you want from this audience, exactly? Investment? Pilot? Approval? Make it explicit.

Common failure modes:

• Product-first ordering. Features before problem.
• Generic problem statement. "Companies struggle with X" - which companies? what does struggling look like?
• No villain. Without a clear antagonist (status quo, competitor, broken process), the conflict is fuzzy.
• Closing slide that says "Questions?" instead of an explicit ask.

Narrative arc choice: Sparkline (Duarte) + StoryBrand SB7 for outward-facing pitches. Golden Circle for vision-heavy pitches. SCQA for short internal/exec pitches.

---

Exec memo / status update / 1-pager

Dominant rhythm: scanned, not read. The reader's question is "what do I need to do or know about this?" - and they want the answer in the first 30 seconds.

Load-bearing rules:

• Bottom line up front (BLUF). Lead with the recommendation, decision, or finding. Then justify it.
• SCQA at the top. Situation → Complication → Question → Answer is the natural shape.
• One screen rule. A status update or memo that scrolls past one screen has lost the executive.
• Numbered or bulleted scaffolding. Exec readers parse structure faster than prose. Use it deliberately.
• No throat-clearing. No "I wanted to share..." / "As discussed..." / "Just following up..." openers. Get to the substance.
• Ask is explicit and isolated. If you want a decision, isolate the ask in a single sentence near the top: "Decision needed: approve $X for Y by Friday."

Common failure modes:

• Reverse-chronological structure (telling the story of how you got here before the headline).
• Hedged ask. "We might want to consider whether..." - make the recommendation, attach the uncertainty separately.
• Buried numbers. The most decision-relevant figure should be visible without scrolling.
• Memo that's actually a draft of a longer document. If it doesn't serve the scanning reader, it's the wrong format.

Narrative arc choice: SCQA always. ABT inside individual sections.

---

Long report / strategy document / board paper

Dominant rhythm: scanned at multiple levels. Some readers will only read the executive summary. Some will scan headings and stop where their interest fires. Few will read linearly.

Load-bearing rules:

• Pyramid Principle. Lead with the answer; group supporting arguments below; each group has its own evidence underneath. Reader can stop at any level and have the gist.
• Executive summary stands alone. Often re-read separately. Must contain the through-line, the recommendation, and the rationale in one page.
• Section openers are mini-SCQAs. Each section starts with situation/complication/question/answer for that section's topic.
• Headings are claims, not topics. "Our cloud spend is growing faster than revenue" beats "Cloud Spend Analysis".
• Appendix what would otherwise interrupt. Detailed methodology, raw data, supporting evidence - appendix it. Don't let it slow the main narrative.

Common failure modes:

• Bottom-up writing. Building to a conclusion the time-poor reader will never reach.
• Buried recommendation in section 4 of 7.
• Methodology before findings. Readers don't care how you got there until they care that you got there.
• Throat-clearing introduction ("This document aims to...").

Narrative arc choice: Pyramid Principle as the structural backbone. SCQA at section level. Inside paragraphs, ABT.

---

Conference talk / keynote

Dominant rhythm: live audience, time-bounded, often recorded. Memory is selective - audiences remember moments, not arguments.

Load-bearing rules:

• Open with a moment, not an agenda. No "Today I'll cover three things". Drop straight into the hook.
• One single Big Idea. A talk about three things is a talk about nothing. Pick one and serve it.
• At least one S.T.A.R. moment. A specific, tangible, dramatic beat that crystallises the idea (Duarte).
• Personal beats earn trust. A vulnerability hook or Five-Second Moment near the start changes the audience's relationship to the speaker.
• Land the resolution. The last sentence is what they'll quote. Write it first; everything else serves it.
• Soundbites travel. Build 1-2 short, repeatable phrases the audience can carry out the door.

Common failure modes:

• The "comprehensive overview" instinct. Tries to cover everything; the audience remembers nothing.
• Reading slides aloud.
• No personal stake. Generic talks read as generic.
• Anticlimactic ending. The ending is the part the audience remembers - don't waste it on "thanks for listening".

Narrative arc choice: Sparkline + Five-Second Moment. Golden Circle for vision-heavy keynotes.

---

When the format isn't decided yet

If the user hasn't picked a format, the format choice itself is a narrative decision. Ask:

• Who is reading or watching, and how much of their attention do they have?
• Live or async?
• One reader or many?
• How long is the journey: a 30-second decision or a 30-minute talk?
• Does the audience need to act, decide, or simply understand?

These answers shape format. A persuasive case to a single decision-maker may be better as a 1-page memo than a 20-slide deck. A change story that needs to spread may be better as a blog post than a board paper. The format is downstream of the audience and the goal.

Hooks & Turns: The Engine of Narrative

Hooks open attention loops. Turns close them. Together they power every compelling narrative - pitch, post, talk, memo, or report. Most weak business writing fails at one of these two points: the hook is generic and buried, or the turn is missing.

---

What makes a hook work

The brain is a prediction machine. A hook works by creating a knowledge gap - a space between what the audience knows and what they want to know. This gap triggers dopamine release (Lisa Cron), which says "pay attention, this matters."

A working hook does two things: 1. Signals that something unexpected, important, or threatening is happening 2. Creates an open question the audience needs answered

Why hooks fail:

• No stakes. "Here's our Q3 update" - who cares?
• No gap. The answer is obvious or already known.
• Too abstract. The brain needs specifics to engage. We think in images, not abstractions.
• Buried. The setup goes on too long before the hook lands.
• Generic. A hook that could open any company's blog post about anything is not a hook.

Hook placement:

• Live presentation: within the first 30-60 seconds.
• Blog post / article: in the first paragraph, ideally the first sentence.
• Pitch / memo: before the recipient decides whether to keep reading. For exec audiences, often the very first line.

---

Six hook types

1. The anomaly hook

Present a data point, observation, or situation that breaks an expected pattern. The audience's brain registers "that doesn't fit" and demands resolution.

Pattern: "Everything looked normal - until [unexpected observation]."

Examples:

• "Revenue grew 12% last quarter across every region - except Southeast, which dropped 23%."
• "We've shipped on schedule for eight straight quarters. Then in March, three releases slipped at once."
• "Most of our churn happens in month one. The customers who churned this quarter had been with us for over two years."

Why it works: the brain hates unexplained pattern breaks. It wants resolution.

2. The stakes hook

Open with what's at risk: financial, operational, reputational, human, or strategic.

Pattern: "If we don't [act], [consequence]."

Examples:

• "At current churn rates, we'll lose $4.2M in recurring revenue by Q4."
• "We have nine months before our biggest competitor ships the equivalent feature."
• "Every week we delay this migration, the rollback window gets harder to recover."

Why it works: the brain prioritises survival-relevant information. Stakes activate attention systems faster than information does.

3. The contrast hook (Duarte's "what is / what could be")

Juxtapose the current state against a possible future to create tension between them.

Pattern: "Right now [what is]. But imagine [what could be]."

Examples:

• "Right now, our reviewers spend six hours per document. With the right system, that could be 45 minutes."
• "Today, our customers wait three weeks for an answer. We can get that to three minutes."
• "Today every team writes its own auth middleware. By December, no team should have to."

Why it works: contrast creates cognitive dissonance. The gap between "what is" and "what could be" generates desire for resolution.

4. The question hook

Pose a question the audience can't help but try to answer.

Pattern: "What if...?" or "Why does...?" or "How is it that...?"

Examples:

• "Why do 40% of our highest-value customers leave within 90 days of onboarding?"
• "What would change if we could deploy to production in five minutes instead of fifty?"
• "How is it that our smallest customers generate the most support load?"

Why it works: the brain is goal-directed. A question gives it a goal. It cannot not try to answer.

5. The confession / vulnerability hook

Start with a personal moment of failure, surprise, or realisation. Most business writing avoids this; that's why it works when used.

Pattern: "I was wrong about..." or "I didn't expect..." or "We thought we knew X. We didn't."

Examples:

• "When I first saw the support data, I assumed the new product was failing. I was wrong."
• "Three months ago, I would have told you we were on track. The numbers said otherwise."
• "We launched what we thought was the obvious feature. Nobody used it."

Why it works: vulnerability builds trust instantly. Audiences lean in because authenticity is rare. The brain attends to characters who have something at stake - including the speaker.

6. The "in medias res" hook

Start in the middle of the action. Skip all preamble. Drop the audience into a specific moment and let the setup come later.

Pattern: a concrete, specific moment with sensory or situational detail.

Examples:

• "The alert fired at 2:47am. The system was about to breach its safety threshold."
• "Slide 47 - that's where the presentation fell apart in front of the executive team."
• "The customer's email was three lines long. The third line was 'we're switching to your competitor on Monday'."

Why it works: specificity creates mental imagery. Action creates momentum. The audience is instantly inside the scene rather than being walked into it.

---

What makes a turn work

The turn is the moment, finding, decision, or argument that shifts the audience from their old understanding to a new one. It is the load-bearing primitive of narrative - and the one most often missing or under-built in business writing.

A working turn combines: 1. A shift in understanding - something the audience now sees differently. 2. An explicit "so what" - why the shift matters.

A finding without a "so what" is an observation, not a turn. An interesting fact is not a turn unless it changes how the audience should act, decide, or believe.

The turn test

For any candidate turn, ask three questions:

• Surprise? Does it challenge what the audience believed coming in? (If a dog bites a mailman, that's not a story. If a mailman bites a dog, it is.)
• Shift understanding? Does it change how the audience thinks about the problem, not just add a new fact?
• Inspire action? Does it create a reason to do something - decide, choose, change?

If it doesn't pass all three, it's a beat, not a turn.

Placement

The turn usually lands mid-to-late, not upfront. The "executive summary" instinct that puts conclusions first kills the narrative tension that makes the turn land. Setup → tension → turn → resolution is the shape that works.

Exception: written documents read by people who scan (board papers, exec memos, consulting reports) often need bottom-line-up-front. In that case, give a one-sentence headline up top, then tell the story underneath. The reader who scans gets the answer; the reader who keeps reading gets the narrative.

Making the turn land

Techniques drawn from across frameworks:

• The hourglass (Dicks) - slow down right before the turn. Add detail, a beat, a pause. This signals "this is important" and lets the audience catch up emotionally.
• Contrast framing (Duarte) - state the old belief explicitly before revealing the new understanding. "We assumed X. The data shows Y." The contrast amplifies the shift.
• Concrete specificity (Heath) - the turn must be tangible, not abstract. Not "customer behaviour is changing" but "customers who don't get a response within 48 hours churn three times more often within 90 days."
• Emotional connection (Cron) - connect the turn to people, not categories. Real customers, real teams, real names where possible.
• The "so what" bridge (Dykes) - immediately after the turn, name why it matters. Don't make the audience guess.

---

The transformation arc

Every story, at every scale, follows the same shape:

Old understanding → tension / evidence → new understanding → new action

Different frameworks dress it differently:

They are all the same shape. The hook opens the loop. The turn closes it. Everything else is the bridge between.

---

Quick checklists

Hook check

• [ ] Lands within the first 30-60 seconds (or first paragraph for written work)
• [ ] Creates a specific, unanswered question
• [ ] Concrete, not abstract
• [ ] Stakes are signalled (not necessarily stated outright)
• [ ] Would pass the Dinner Test - would you open with this telling a friend?
• [ ] Could not appear in a generic blog post about a different company

Turn check

• [ ] Genuinely surprising - challenges assumptions the audience came in with
• [ ] Shifts understanding, not just adds a fact
• [ ] The "so what" is explicit, not implied
• [ ] Placed at the climax, not the beginning (or paired with a one-line headline if BLUF is required)
• [ ] Concrete and specific, not abstract
• [ ] Connects to real people the audience cares about
• [ ] Naturally leads to a clear action or recommendation

Narrative Frameworks (Lenses, Not Templates)

These frameworks are different surface arrangements of the same underlying primitives: status quo → tension → stakes → turn → resolution. Treat them as lenses to check material against, not templates to fill in. The right lens for a piece depends on audience, goal, length, and material - not on which framework is "best".

Most strong business narratives use a coarse-grained lens at the document level (e.g. SCQA for an exec memo, Three-Act for a blog post) and a fine-grained lens at the paragraph or beat level (e.g. ABT for a single update or section opener).

Selection guidance

---

Short-form lenses

ABT (And/But/Therefore) - Randy Olson

The shortest workable narrative shape. Three beats:

• And - establish the shared context. ("We've grown the platform 40% YoY AND demand is still climbing.")
• But - introduce the tension. ("BUT the underlying database can't sustain another doubling in load.")
• Therefore - propose the action. ("THEREFORE we need to commit to the migration in Q3.")

When to use: exec updates, project status posts, paragraph-level structuring inside a longer piece, elevator pitches, slide subtitles, Slack posts. Anywhere you need clear thinking in 3-5 sentences.

Why it works: forces you to identify the actual tension (the "but") rather than chaining facts with "and... and... and...". The "and" → "but" → "therefore" transition is the smallest unit of narrative.

Failure mode: "AND... AND... therefore" - no real tension. If your "but" is weak, the whole thing is informational, not narrative.

SCQA (Situation / Complication / Question / Answer) - Barbara Minto

The Minto-school standard for executive briefings. Four beats:

• Situation - the stable backdrop the reader already accepts.
• Complication - what changed or is changing that disturbs the situation.
• Question - the question the complication raises in the reader's mind.
• Answer - your recommendation or finding.

When to use: consulting memos, exec briefings, 1-pagers, decision documents, opening paragraphs of formal reports.

Why it works: meets executives where they are - they want to know what's at stake and what you recommend, in that order. SCQA naturally surfaces both. The "question" beat is the connector that prevents the answer feeling unmoored.

Failure mode: skipping the complication or making it generic. A vague "the market is changing" complication produces a vague answer.

Pyramid Principle - Barbara Minto

A structural principle for written documents read by people who skim. Top-down rule:

• Lead with the answer (the single governing thesis).
• Group supporting arguments in 2-4 buckets directly underneath.
• Each bucket has its own supporting facts/evidence.
• Reader can stop at any level and still have the gist.

When to use: long written reports, board papers, strategy documents, exec-facing PRDs, consulting deliverables. Anywhere the reader will not read linearly.

Why it works: time-poor readers can scan headers and section openers and still leave with the conclusion and reasoning.

Failure mode: bottom-up writing. If your document builds to its conclusion, it'll fight every reader who scans. Restructure top-down.

Note: Pyramid Principle is structural, not narrative. Combine it with SCQA at the section openings to add narrative tension.

---

General-purpose arcs

Three-Act Structure

The default narrative shape for most longer business writing. Three acts:

• Act I - Setup. Context, characters (in business: people, teams, market), the world as it is. Ends with an inciting incident - something that disturbs the status quo.
• Act II - Confrontation. Rising tension, obstacles, attempts that don't fully work, the turning point. Most of the running time lives here.
• Act III - Resolution. The decision, the action, the new equilibrium. Short - once the turn has happened, end soon.

When to use: blog posts, articles, general talks, longer narratives where you have room to breathe.

Why it works: matches the audience's pattern-prediction machinery. The brain expects setup-conflict-resolution and stays engaged because each act sets up the next.

Failure mode: bloated Act I. Most weak business writing spends too long on setup before the inciting incident. Cut setup ruthlessly - get to the turn.

Pixar's "Once upon a time..."

Pixar's six-beat structure for stories about change:

• Once upon a time... - the ordinary world.
• Every day... - the routine, the way things normally are.
• One day... - the disruption, the change, the new arrival.
• Because of that... - first-order consequence.
• Because of that... - second-order consequence (the chain reaction).
• Until finally... - the resolution, the new equilibrium.

When to use: change stories, adoption stories ("how we moved from X to Y"), case studies, customer journey stories, transformation narratives.

Why it works: the doubled "because of that..." forces causal storytelling - each beat must follow from the previous one. This is what separates a story from a list of events.

Failure mode: the chain breaks. If your second "because of that" doesn't actually follow from the first, you don't have a story - you have two adjacent things.

Hero's Journey (condensed) - Joseph Campbell

A condensed business-friendly version of Campbell's monomyth, useful for founder, brand-origin, and personal narratives:

• Call to adventure - the catalyst, the moment of recognition.
• Crossing the threshold - the commitment (quitting the job, taking the leap, raising the round).
• Trials, allies, enemies - the challenges, mentors, competitors along the way.
• Ordeal - the near-failure, the dark moment.
• Reward - the breakthrough, the win, the lesson.
• Return with the elixir - coming back changed, with something to share.

When to use: founder stories, company origin narratives, personal brand pieces, "lessons learned" pieces, conference keynotes that are partly autobiographical.

Why it works: structurally familiar to any audience that's seen a film in the last fifty years. The vulnerability of the ordeal is what builds trust.

Failure mode: skipping the ordeal. Founder stories without a real near-failure read as humblebrag. The ordeal is what makes the journey relatable.

---

Persuasion & vision lenses

Golden Circle (Why / How / What) - Simon Sinek

Three concentric rings, communicated outward-in:

• Why - the belief, the purpose, the reason the work exists. ("We believe...")
• How - the unique approach or principle that follows from the why.
• What - the actual product, service, or output.

When to use: vision and mission communication, manifestos, all-hands talks, investor pitches that need to land purpose before product, brand-level pieces.

Why it works: leads with belief, which the audience either shares or doesn't - and that filtering creates resonance with the right people. Product features are forgettable; reasons to believe stick.

Failure mode: a vague or unfalsifiable why. "We believe in helping people" is too generic. The why must be specific enough that someone could reasonably disagree.

Sparkline - Nancy Duarte (from "Resonate")

A persuasive presentation oscillates between current state and possible future:

What Is → What Could Be → What Is → What Could Be → ... → New Bliss

Three contrasts to use:

• Content contrast - your view vs. the audience's prior view.
• Emotion contrast - analytical content followed by emotional content.
• Delivery contrast - traditional vs. nontraditional delivery moments.

End with new bliss - a vivid picture of the world if the idea is adopted, plus a clear call to action.

When to use: persuasive keynotes, change-management talks, big-vision pitch decks, town halls that need to move people to action.

Why it works: the gap between "what is" and "what could be" is where the audience's energy lives. Each oscillation widens the gap and pulls them toward the future.

Key supporting concepts:

• The Big Idea - one sentence: situation + complication leading to your unique recommendation.
• S.T.A.R. moment - Something They'll Always Remember: a dramatic, tangible demonstration of the idea (Jobs pulling MacBook Air out of an envelope).
• Audience as hero - the audience is the protagonist; the speaker is the mentor.
• Sound bites - small, repeatable phrases that travel.

Failure mode: only one oscillation, or weak "what could be". The future state has to be vivid and specific.

StoryBrand SB7 - Donald Miller

Seven-element framework for customer-facing brand messaging. The customer is the hero; the brand is the guide.

1. A character (the customer) - wants something specific. 2. Has a problem - at three levels:

• External - the tangible problem.
• Internal - the emotional frustration. (Customers buy solutions to internal problems.)
• Philosophical - why it's wrong that this problem exists.

3. And meets a guide (the brand) - who shows empathy ("I understand") + authority ("I've solved this before"). 4. Who has a plan - clear steps (3-4 max), reducing perceived risk. 5. And calls them to action - direct ("Buy now") and transitional ("Download the guide"). 6. That helps them avoid failure - explicit negative stakes. 7. And ends in success - the after-state, the transformation.

When to use: website copy, marketing pages, sales decks, product positioning, brand messaging, customer-facing pitches.

Why it works: positions the brand correctly (guide, not hero) which is counter to most companies' instinct. Names the internal problem, which is what actually drives buying decisions.

Failure mode: positioning the brand as the hero. The audience is not interested in your journey; they're interested in theirs.

---

Data & insight lenses

Data Storytelling Arc - Brent Dykes

Based on Freytag's Pyramid, optimised for fact-based stories. Four beats:

• Setting & hook - just enough context, then a notable observation that opens a question (the hook).
• Rising points - focused supporting evidence that builds tension. Not a data dump.
• Aha moment - the central insight: an unexpected shift in understanding plus an explicit "so what". This is the climax. Don't put it upfront.
• Solution & next steps - options and a recommendation.

Dykes' core formula: Data + Narrative + Visuals - all three required. Eye-appealing charts without strong narrative are weak data stories. Reporting is not storytelling.

The insight test (an aha moment must do all three):

• Surprise - does it challenge what we believed?
• Shift understanding - does it change how the audience thinks about the problem?
• Inspire action - does it create urgency to do something differently?

When to use: data-driven presentations, insight reports, stakeholder briefings about findings.

Failure mode: putting the insight first ("executive summary" instinct). That kills the suspense the rising points are meant to build.

---

Performance storytelling

Five-Second Moment - Matthew Dicks

A performance-storytelling framework from a 61-time Moth StorySLAM champion. Useful in business when you need to drop in a personal anecdote.

Core concept: every story is about a single moment of transformation that takes no more than five seconds. Without it, you have an anecdote, not a story.

Construction rules:

• Start at the end - know your moment first, build backward.
• Begin as close to the end as possible - strip setup that doesn't serve the moment.
• Begin in the opposite - open in the emotional or situational opposite of where you'll land.
• The Dinner Test - if you wouldn't tell it this way to a friend at dinner, don't tell it that way at all.
• Stories can never be about two things - one five-second moment per story.
• Use "but" and "therefore"; never "and" - "and" provides no momentum.

Engagement devices: stakes, surprise, suspense, backpacks (info loaded in advance), hourglasses (slowing down right before the moment), breadcrumbs, crystal balls (false predictions).

When to use: opening anecdotes in talks, vulnerability moments in keynotes, conference talks, leadership comms with a personal beat.

Failure mode: a story about two things. If you can't say what the single moment of change is, the story isn't ready.

---

Diagnostic / cognitive lenses

Brain Science of Story - Lisa Cron ("Wired for Story")

Why stories work neurologically. Use as a diagnostic when something isn't landing.

When to use: diagnostic - when a piece isn't landing, walk through these and find the missing primitive.

SUCCESs - Chip & Dan Heath ("Made to Stick")

A diagnostic checklist for sticky messages. Run a piece through each letter:

The Curse of Knowledge: once you know something, you can't imagine not knowing it. This is the single biggest barrier to sticky communication. Combat it with concrete language and the Dinner Test.

When to use: final review pass on any piece. If a letter scores weak, the piece needs work there.

---

Recommended reading

For agents and users who want to go deeper:

1. Effective Data Storytelling - Brent Dykes (Data Storytelling Arc; Data + Narrative + Visuals) 2. Resonate / DataStory - Nancy Duarte (Sparkline; Big Idea; STAR moment) 3. Building a StoryBrand - Donald Miller (SB7; customer-as-hero; brand-as-guide) 4. Storyworthy - Matthew Dicks (Five-Second Moment; Homework for Life; performance storytelling) 5. Made to Stick - Chip & Dan Heath (SUCCESs; Curse of Knowledge) 6. Wired for Story - Lisa Cron (cognitive-story pairs; why hooks work) 7. The Pyramid Principle - Barbara Minto (top-down structuring; SCQA) 8. Start With Why - Simon Sinek (Golden Circle) 9. The Hero with a Thousand Faces - Joseph Campbell (monomyth; original source) 10. Houston, We Have a Narrative - Randy Olson (ABT)