Storytelling

Storytelling

When to Use

• Shape a story spine (setup → tension → resolution) for a decision, launch, or change
• Tailor the same facts into executive, board, customer, or team narratives
• Build a data story with honest framing, context, and uncertainty
• Draft product or strategy narratives that connect problem, choice, and proof
• Turn incidents or postmortems into blameless, actionable stories
• Explain actuarial or insurance risk to non-technical stakeholders without diluting rigor
• Outline slide or visual narrative flow (section purpose, not final design)
• Distill key messages (3–5 MECE bullets) aligned to one audience and one ask

When NOT to Use

• Reframe jargon or produce dual-audience briefs without building narrative arc → cross-department-translation
• Org-wide messaging hierarchy, launch/crisis wording packs, or comms cadence → communication-lead
• Issue trees, business cases, or steerCo analysis as the primary deliverable → business-consultant
• API docs, runbooks, tutorials, or information architecture → tech-writer-researcher
• Long-form creative fiction, screenplays, or character-driven prose
• Brand voice, campaign creative, or marketing copy without strategic narrative framing → route to marketing or brand skills if present; pair with communication-lead for approved external lines
• Legal contract language, regulatory filings, or compliance attestation narratives → commercial-counsel, compliance-engineer, actuarial-consulting as appropriate

Related skills

Core Workflows

1. Clarify audience, ask, and proof

Before drafting, lock:

If the task is only vocabulary translation, route to cross-department-translation.

See `references/storytelling_scope_and_principles.md`.

2. Build the story spine

Use a single through-line:

1. Setup — context the audience already accepts 2. Tension — gap, risk, or opportunity (named clearly) 3. Turn — insight, decision, or intervention 4. Resolution — outcome, next step, or open question (honest)

Derive 3–5 key messages from the spine; each message needs one proof point.

See `references/narrative_structure_and_arcs.md`.

3. Tune register and channel

Match depth, jargon, and tone to audience and medium (live talk, memo, deck, status page).

See `references/audience_and_register.md`.

4. Tell the data story

Lead with the so what; show trend and comparison; state uncertainty; avoid chartjunk narratives.

See `references/data_and_metrics_storytelling.md`.

5. Executive, board, and strategy stories

Pyramid the recommendation; separate decision from appendix; pre-empt predictable objections.

See `references/executive_board_and_strategy_stories.md`.

6. Incident, change, and actuarial narratives

Blameless incident arcs; change stories with empathy and timeline; risk stories with ranges and drivers—not false precision.

See `references/incident_change_and_actuarial_narratives.md`.

Output standards

• One primary ask per story; secondary asks subordinate
• Plain language; define acronyms once per artifact
• No fabricated quotes, metrics, or causation
• Label estimates, scenarios, and confidence explicitly
• For slides: section intent + headline + 1–2 supporting bullets (not full visual design)
• Version and timestamp incident or crisis story drafts

When to load references

• Scope, ethics, boundaries → references/storytelling_scope_and_principles.md
• Arcs, spine, key messages → references/narrative_structure_and_arcs.md
• Audience and register → references/audience_and_register.md
• Metrics and charts as narrative → references/data_and_metrics_storytelling.md
• Exec, board, strategy, pitch → references/executive_board_and_strategy_stories.md
• Incident, change, actuarial risk → references/incident_change_and_actuarial_narratives.md

Audience and register

Table of contents

1. Audience dimensions 2. Executive register 3. Board register 4. Customer and partner register 5. Team and practitioner register 6. Channel constraints 7. Variant workflow

Audience dimensions

Tune narratives on four axes:

Document the profile in one line before drafting: e.g., “CFO, informed generalist, cares about cash and audit risk.”

Executive register

Goals: Fast decision, clear trade-offs, minimal detail unless asked.

Structure: Pyramid — answer → supporting KMs → appendix.

Pair with business-consultant when the pack is primarily analytical; storyteller owns sequence and emphasis.

Board register

Goals: Fiduciary clarity, strategic choice, oversight—not operations.

Align with communication-lead for approved external/board communications.

Customer and partner register

Goals: Trust, clarity, empathy, truthful product claims.

Route contractual or SLA language to commercial-counsel; storyteller drafts narrative around approved facts.

Team and practitioner register

Goals: Shared mental model, actionable detail, psychological safety.

For cross-functional vocabulary alignment without full story arc, use cross-department-translation.

Channel constraints

Variant workflow

When one story must serve multiple audiences:

1. Write master spine once (facts + proof only). 2. Derive audience variants by changing:

• Opening (what they already believe)
• Depth of proof (summary vs appendix)
• Ask (approve vs inform vs execute)

3. Keep facts identical across variants; never different numbers. 4. Log variant table:

Data and metrics storytelling

Table of contents

1. Data story anatomy 2. Honest framing rules 3. Chart and slide narrative 4. Comparisons and baselines 5. Uncertainty and scenarios 6. Metric definitions 7. Common pitfalls 8. Worked example skeleton

Data story anatomy

A data story is not a dashboard export. Minimum structure:

INSIGHT   — One sentence: what changed and why it matters
EVIDENCE  — Chart or table with labeled comparison
CONTEXT   — Definition, period, population, caveats
ACTION    — Decision, investigation, or communication next step

Order: Insight first (pyramid), then evidence—never reverse for executive audiences.

Honest framing rules

Flag data quality issues (late-arriving data, definition changes) in one line.

Chart and slide narrative

Each visual needs a headline insight, not a chart title:

Slide annotation pattern:

1. Headline (insight) 2. Visual (one message) 3. Footnote (definition + source + date) 4. Optional callout (one number)

Prefer small multiples or one comparison over dense dashboards in narrative decks.

Comparisons and baselines

Always answer: Compared to what?

When metrics redefine, show bridge or restate prior periods—do not blend incompatible series silently.

Uncertainty and scenarios

Scenario framing:

• Base: most likely assumptions
• Downside: material risk case
• Upside: only if decision-relevant (avoid false optimism)

Metric definitions

Include a metric contract in appendix or footnote:

Align definitions with analytics or actuarial owners before board or customer narratives.

Common pitfalls

Worked example skeleton

Prompt: “Tell the data story for Q3 retention.”

INSIGHT: Net revenue retention fell from 112% to 104% driven by mid-market downgrades, not new-logo churn.

EVIDENCE: [Chart: NRR by segment, Q1–Q3] Mid-market −9pp; enterprise stable.

CONTEXT: NRR = (starting ARR + expansion − contraction − churn) / starting ARR; excludes one-time services.

CAVEAT: July price increase may have accelerated Q3 downgrades; cohort still maturing.

ACTION: Approve CS playbook pilot for mid-market; revisit packaging in Q4 planning.

Pair with business-consultant for driver analysis depth; storyteller owns sequence and headline honesty.

Executive, board, and strategy stories

Table of contents

1. Purpose and boundaries 2. Pyramid structure 3. Strategy narrative arc 4. Pitch and investment stories 5. Product narrative 6. Objection handling 7. Pre-read and live delivery 8. Slide narrative outline template

Purpose and boundaries

Executive and board stories drive decisions under uncertainty. They are not:

• Full financial models (attach or hand off to FP&A / business-consultant)
• Legal disclosures (counsel-owned)
• Operational runbooks (tech-writer-researcher)

Success = audience knows what you recommend, why, risks, and what you need from them.

Pyramid structure

APEX     — Recommendation + ask (one sentence)
TIER 2   — 3 key messages (why now, why us, why this option)
TIER 3   — Evidence per KM (metrics, cases, benchmarks)
BASE     — Appendix (methods, detail, sensitivity)

Time-box:

Strategy narrative arc

For portfolio, market entry, or transformation choices:

1. Where we play — market, segment, capability (shared context) 2. Why change — external shift or performance gap (tension) 3. Strategic choice — explicit option selected (turn) 4. How we win — moat, capabilities, investments (resolution path) 5. What we need — capital, hires, partnerships (ask)

Show rejected options briefly to prove rigor—one line each with kill reason.

Pitch and investment stories

Pitch story (internal or external) follows:

Avoid hype adjectives; every claim needs evidence or labeled assumption.

Pair with business-model-researcher or business-consultant for market sizing depth.

Product narrative

Connect user problem → product choice → measurable outcome:

For [user], who [job-to-be-done],
[product] provides [outcome]
unlike [alternative]
because [differentiator].

Roadmap stories: now / next / later with outcomes per horizon—not feature laundry lists.

Coordinate ship dates with engineering and communication-lead for external promises.

Objection handling

Pre-write top 5 objections for exec/board:

Place objections in appendix Q&A, not main spine—unless one objection blocks the decision.

Pre-read and live delivery

Slide narrative outline template

Storyteller supplies intent + headlines; analyst supplies charts; designer owns layout.

Incident, change, and actuarial narratives

Table of contents

1. Incident story principles 2. Incident timeline arc 3. Customer and internal incident messages 4. Postmortem narrative 5. Change and transformation stories 6. Actuarial and insurance risk stories 7. Regulatory and sensitive audiences 8. Handoffs

Incident story principles

Separate process (incident-management-engineer) from narrative (this skill):

Rules:

• No speculation on root cause until confirmed
• No naming individuals as villains
• Timestamp updates; version messages
• Single source of truth for facts

Incident timeline arc

In medias res works well:

1. Impact now — who is affected, what is broken, workaround 2. Timeline — detection → response → mitigation → recovery (UTC) 3. Current status — monitoring, ETA if known (or “investigating”) 4. Next update — when and where 5. Learning preview — postmortem timing (no premature blame)

[TIME] — [Observable event]
[TIME] — [Action taken]
[TIME] — [Customer-visible change]

Gap markers: “Unknown between X and Y—under investigation.”

Customer and internal incident messages

Holding line pattern:

We are investigating [symptom] affecting [scope].
Impact: [user-visible effect].
Workaround: [if any].
Next update: [time] via [channel].

Route legal/security review per severity with communication-lead.

Postmortem narrative

Blameless postmortem story arc:

1. Summary — impact, duration, customer effect (facts) 2. Timeline — detailed, linked to artifacts 3. Root cause — technical + contributing factors (systems) 4. What went well — detection, collaboration 5. What went wrong — gaps without personal attack 6. Action items — owner, due date, verification method 7. Lessons — durable policy or design change

Learning story test: Could a new engineer understand how the system failed and what we changed?

Change and transformation stories

Organizational change needs empathy + clarity:

Manager cascade: Same spine; managers add team-specific examples.

Pair with communication-lead for company-wide rollout wording.

Actuarial and insurance risk stories

Translate technical actuarial work for non-technical listeners without losing integrity:

Structure:

1. Question — what decision the audience must make 2. Answer headline — central estimate or direction 3. Drivers — 2–3 factors in plain language 4. Uncertainty — range or sensitivity (“if X, then Y”) 5. Actions — pricing, reinsurance, capital, or monitoring

Do not simplify away material limitations—state them in one sentence.

Deep modeling stays with actuary / actuarial-consulting; storyteller shapes explanation.

Regulatory and sensitive audiences

Never promise outcomes regulators must approve.

Handoffs

Narrative structure and arcs

Table of contents

1. Story spine (default) 2. Classic arcs for business 3. Key messages from spine 4. Tension without manipulation 5. Openings and closings 6. Parallel structure and repetition 7. Templates

Story spine (default)

Use for most internal and customer narratives:

SETUP     — Shared context the audience accepts
TENSION   — Problem, risk, gap, or opportunity (specific)
TURN      — Insight, decision, or intervention
RESOLUTION — Outcome, path forward, or honest open question

Example (product launch):

• Setup: Customers lose time reconciling exports manually.
• Tension: Error rate rises as volume grows; support tickets up 40%.
• Turn: Shipped automated reconciliation with audit trail.
• Resolution: Pilot customers cut close time by 2 days; GA next month with training plan.

Classic arcs for business

Pick one arc per artifact; do not stack metaphors.

Key messages from spine

Derive 3–5 key messages (KM):

1. Map each KM to one spine beat (usually TENSION or TURN). 2. Attach one proof point per KM (metric, example, quote). 3. Check MECE: no overlap; together they support the ask. 4. Order for audience: execs often want recommendation KM first (pyramid).

KM template:

KM[n]: [Claim in plain language]
Proof: [Metric, example, or exhibit]
So what: [Link to ask]

Tension without manipulation

Effective tension names a real constraint:

• Market, regulatory, or competitive shift
• Customer pain with evidence
• Technical debt or reliability trend
• Financial or capacity limit

Avoid:

• Vague fear (“we might fall behind”)
• Inflated deadlines without source
• Straw-man alternatives

For data stories, tension is often “metric moved; here is plausible driver set” not “disaster.”

Openings and closings

Openings (pick one):

• Headline first — “We recommend X because Y.”
• Concrete scene — One sentence of customer or operator reality.
• Contrast — “Last quarter … This quarter …”

Closings (pick one):

• Ask — Decision, budget, or approval with owner and date.
• Commitment — What we will do by when.
• Learning — What we know now that we did not before (postmortems).

Never end on “questions?” without restating the ask.

Parallel structure and repetition

Use parallel bullets for comparisons:

• Option A: cost, risk, time
• Option B: cost, risk, time

Use anaphora sparingly in talks (“We will measure. We will publish. We will iterate.”).

Limit rule of three to three items when listing priorities—more than three dilutes memory.

Templates

One-paragraph spine

[Audience] needs [outcome]. Today, [tension with proof]. We [turn/decision].
By [date], [resolution]. The ask is [single CTA].

Five-slide narrative outline

Story ↔ key message map

Storytelling scope and principles

Table of contents

1. Role boundary 2. What storytelling adds 3. Ethics and honesty 4. Story vs slide vs memo 5. Collaboration handoffs 6. Quality checklist 7. Anti-patterns

Role boundary

Storytelling (this skill) designs narrative structure and audience-specific through-lines for organizational and business communication. It is not:

What storytelling adds

Storytelling answers: Why should this audience care, in what order, and what should they do next?

Deliverables typically include:

• Story spine — setup, tension, turn, resolution (1 paragraph or 4 beats)
• Key messages — 3–5 MECE bullets tied to proof
• Audience variant — same facts, different emphasis (exec vs engineer vs customer)
• Narrative outline — slide or section flow with intent per block
• Talk track — spoken arc for meetings (not a full script unless requested)

It does not replace analysis, legal review, or program management.

Ethics and honesty

When stakes are high (board, regulators, public incident), pair narrative work with communication-lead or counsel approval paths.

Story vs slide vs memo

Default: one primary medium per request; adapt spine once, then reshape for secondary channels.

Collaboration handoffs

Quality checklist

Before delivery, verify:

• [ ] Single audience and ask identified
• [ ] Spine present; every section advances the arc
• [ ] Key messages are MECE and evidenced
• [ ] No unsupported superlatives (“best”, “only”, “guaranteed”)
• [ ] Jargon defined or removed for this audience
• [ ] Next step is explicit and owned
• [ ] Sensitive claims flagged for review where needed

Anti-patterns

Engagement intake (quick)

Capture before drafting:

If intake reveals no clear ask, resolve with the requester before writing prose.

Sensitivity tiers

Escalate tier when reputational, legal, or safety stakes apply.