szoloth/strategic-storytelling

Strategic Storytelling

Overview

Transform product ideas into compelling narratives that move stakeholders to action. This skill applies narrative structure to create emotional resonance while maintaining logical rigor—essential for exec presentations, stakeholder buy-in, and product positioning.

When to use this skill:

• Presenting to executives or leadership
• Building stakeholder coalition for a new initiative
• Positioning a product or feature
• Pitching internally for resources
• Creating compelling product demos
• Scout investor decks and commercialization pitches

When NOT to use this skill:

• Daily stakeholder updates (use communication-optimizer for conciseness)
• Technical documentation
• Research summaries (use research-expert)

Core Framework: Andy Raskin's 5-Act Strategic Narrative

The principle: Don't lead with your product. Lead with the world your audience lives in—and show them how it's changing.

The 5 Acts

Act 1: Old World (The Before)
        ↓
Act 2: Insight (The Shift)
        ↓
Act 3: New World (The Opportunity)
        ↓
Act 4: Stakes (Win Big or Lose)
        ↓
Act 5: Your Role (How You Help Them Win)

Act 1: Old World

Purpose: Establish shared reality. Get heads nodding.

What to include:

• How things used to work (or currently work)
• What was considered "normal" or "acceptable"
• The status quo that feels familiar

Key question: "What does my audience already believe is true?"

Example (DWA context):

"For years, Story artists managed reference collections in personal folders. Every artist had their system. It worked because productions were smaller and teams rarely overlapped."

Example (Scout context):

"Animation studios have always treated digital assets as production-specific resources. Each show builds its library from scratch. Cross-pollination is informal, accidental."

Act 2: Insight (The Shift)

Purpose: Create tension. Something has changed that makes the old world untenable.

What to include:

• What changed externally (market, technology, customer behavior)
• Why the old approach no longer works
• The "aha" moment that explains why this matters now

Key question: "What's the undeniable shift that my audience can't ignore?"

Example (DWA context):

"But productions scaled from 3 to 7 simultaneous shows. Reference libraries grew from terabytes to 500+ TB. And artists started working across multiple productions—but their reference stayed siloed in personal folders."

Example (Scout context):

"AI is changing what's possible. Studios that unlock their asset libraries will have competitive advantage in training generation models. But most studios have 15+ years of assets locked in silos they can't even search."

Act 3: New World (The Opportunity)

Purpose: Paint the vision. Show what's now possible.

What to include:

• How winners will operate in this new reality
• The opportunity for those who adapt
• Concrete outcomes, not features

Key question: "What does winning look like in the new world?"

Example (DWA context):

"The studios that figure this out will have artists who find the perfect reference in seconds instead of hours—and can build on work from any production. Institutional knowledge becomes a competitive advantage, not tribal memory."

Example (Scout context):

"Studios that organize their asset libraries now will be able to: train proprietary AI models on 15 years of house style, onboard artists in days instead of weeks, and license IP-compliant assets to partners. The asset library becomes a strategic moat."

Act 4: Stakes (Win Big or Lose)

Purpose: Create urgency. Make the cost of inaction concrete.

What to include:

• What happens if they embrace the new world (positive)
• What happens if they don't (negative)
• Why timing matters

Key question: "What does my audience risk by not acting?"

Example (DWA context):

"Artists who can find and remix existing work will ship faster and at higher quality. Studios that don't solve this will keep losing experienced artists who are frustrated by broken workflows—and lose institutional knowledge when they leave."

Example (Scout context):

"Studios that organize now will have 2-3 years of competitive advantage before others catch up. Those that wait will face higher costs, longer timelines, and the risk of having AI trained on poorly-organized data that perpetuates mistakes."

Act 5: Your Role (How You Help Them Win)

Purpose: Position your solution as the path to winning.

What to include:

• How your product/initiative helps them succeed
• Proof points (credibility, traction, testimonials)
• Clear next step

Key question: "How do we help them win in the new world?"

Note: This is the ONLY place you talk about your product. Acts 1-4 should be true regardless of whether your product exists.

Example (DWA context):

"That's what Rico Collections enables—a way for artists to organize, discover, and share reference across productions without leaving their existing workflow. We've piloted with Story department: artists report 30-40% time savings on reference retrieval."

Example (Scout context):

"Scout provides the infrastructure to organize, search, and govern digital assets at scale. We've built it from the ground up for animation studios, informed by 12 months embedded with a major studio. Our first customer is already seeing [specific proof point]."

---

Application Templates

Template: Executive Presentation

# [Title]: [One-line hook]

## Slide 1: The Old World
[1-2 sentences: How things used to work]
[Optional: image/visual of "before" state]

## Slide 2: The Shift
[What changed externally that makes old approach untenable]
[Data point or undeniable trend if available]

## Slide 3: The New World
[Vision of how winners will operate]
[Focus on outcomes, not features]

## Slide 4: The Stakes
[What they win by acting / What they lose by not acting]
[Make urgency concrete]

## Slide 5: Our Approach
[How you help them win]
[1-3 key capabilities—keep it simple]

## Slide 6: Proof
[Evidence this works: pilot results, testimonials, metrics]

## Slide 7: Ask
[Specific next step you want them to take]

Template: Stakeholder Buy-In Pitch

Use this for internal pitches (e.g., getting Charles to support a new initiative):

# [Initiative]: The Case for [Outcome]

## Context (Old World)
[Current state - get agreement on shared reality]

## What's Changed (Insight)
[The shift that makes action necessary now]
[Evidence: data, user quotes, external trends]

## The Opportunity (New World)
[What becomes possible if we act]
[Concrete outcomes, not features]

## The Risk of Inaction (Stakes)
[What we lose by waiting]
[Make the cost concrete and time-bound]

## Proposal (Our Role)
[Specific initiative and what it enables]
[How it positions us to win]

## Evidence
- [Proof point 1: user research, pilot data]
- [Proof point 2: competitive analysis]
- [Proof point 3: expert endorsement]

## Ask
[Specific decision or resource needed]
[Next step and timeline]

Template: Product Positioning Narrative

# [Product Name]: [Positioning Statement]

## The Old World
For years, [target audience] has [old behavior].
This made sense because [context].

## The Shift
But [external change] has changed everything.
[Old approach] no longer works because [specific reason].

## The New World
Now, [target audience] can [new capability/outcome].
The best [companies/teams/users] are already [new behavior].

## The Stakes
Those who [adopt new approach] will [positive outcome].
Those who don't will [negative consequence].

## [Product Name]
We help [target audience] [achieve outcome] by [core capability].

Unlike [alternatives], we [differentiation].

## Proof
- [Customer/user evidence]
- [Metric or outcome]
- [Credibility marker]

---

Nancy Duarte: Presentation Structure

Complement the 5-act narrative with Duarte's presentation rhythm.

The "What Is" / "What Could Be" Pattern

Alternate between:

• What is: Current reality, problems, pain (creates tension)
• What could be: Vision, possibility, solution (releases tension)

Application:

What is: "Artists spend 30% of time searching for assets"
What could be: "Imagine finding the perfect reference in seconds"
What is: "Tribal knowledge leaves when people leave"
What could be: "Imagine onboarding an artist with the studio's entire creative history"
What is: "Current search only finds exact keywords"
What could be: "Imagine searching by concept, style, or visual similarity"

The "Sparkline" Structure

Build presentations that move between analytical and emotional:

Opening hook (emotional)
    ↓
Context/problem (analytical)
    ↓
Vision/opportunity (emotional)
    ↓
Evidence/data (analytical)
    ↓
Stakes/urgency (emotional)
    ↓
Call to action (both)

---

Adaptation for DWA Context

Charles-specific considerations

His communication preferences:

• Peer tone, minimal formatting
• Concrete deliverables, not theoretical frameworks
• Outcome-focused, questions ROI of methodology

Adaptation:

• Skip elaborate slide decks—use conversational narrative
• Lead with pilot data and artist quotes, not frameworks
• Frame as "here's what I'm seeing" not "based on my analysis"
• Hide the 5-act structure—just tell the story naturally

Example (casual version for Charles):

"Quick thought on the collections thing. Story artists have been managing refs in personal folders forever, which worked when we had 3 shows. Now we've got 7 simultaneous productions and 500TB of refs scattered everywhere.

The artists I talked to are spending 30-40% of time just searching for stuff they know exists. Heidi mentioned she recreated a character study last month that turned out to already exist in Wild Robot archives.

What I'm thinking: if we nail collections in Rico, artists could find existing work in seconds instead of hours. The pilot feedback suggests this is the highest-impact thing we could ship.

Does that match what you're hearing from the Story leads?"

Scout/commercialization context

For external pitches, use the full 5-act structure more formally:

• Investor decks need clear narrative arc
• Competitive positioning needs crisp differentiation
• Go-to-market needs compelling "why now"

---

Common Pitfalls

❌ Leading with product features

Problem: Audience doesn't care about features until they feel the problem Fix: Make sure Acts 1-4 would be true even without your product

❌ Skipping the "shift" (Act 2)

Problem: Without explaining what changed, there's no urgency Fix: Always answer "why now?" with an external change

❌ Making yourself the hero

Problem: Audience should see themselves as the hero Fix: Your product helps them win—you're the guide, not the protagonist

❌ Too many proof points in Act 5

Problem: Drowning the ask in data Fix: 1-3 proof points max, then clear call to action

❌ No concrete stakes

Problem: Vague "this is important" doesn't create urgency Fix: Make the cost of inaction specific and time-bound

---

Key Quotes

Andy Raskin:

"The best product stories make the customer the hero, not your product."

Nancy Duarte:

"The audience doesn't need to tune themselves to you—you need to tune your message to them."

"Don't deliver a presentation. Take the audience on a journey."

On framing:

"Before you can show people why they should care about your solution, you have to make them care about the problem."

---

Quality Checklist

Before delivering a narrative pitch:

• [ ] Acts 1-4 are true regardless of whether my product exists
• [ ] The "shift" (Act 2) answers "why now?" with an external change
• [ ] Stakes are concrete and time-bound, not vague
• [ ] Audience is positioned as hero, not my product
• [ ] I have 1-3 proof points, not a data dump
• [ ] Clear, specific call to action at the end
• [ ] Adapted to audience's communication preferences

---

Related Skills

• communication-optimizer — For concise stakeholder updates (not narrative pitches)
• stakeholder-analyst — For understanding audience psychology before crafting narrative
• marty-cagan-coach — For framing product pitches around outcomes, not features
• product-strategy-coach — For broader positioning and go-to-market strategy