---
name: storytelling-frameworks
description: Structure narratives for pitches, content, and communication using Hero's Journey, Before-After-Bridge, and Pixar pitch templates.
domain: mindset
---

# Storytelling Frameworks

Proven narrative structures for business communication: pitches, presentations, content marketing, sales copy. Covers 5 core frameworks with concrete templates.

## When to Use

- Crafting pitch decks, keynote presentations, or sales narratives
- Writing marketing copy, case studies, or content
- Structuring product demos or explainer videos
- Making ideas memorable and emotionally resonant
- **When NOT to use**: Dense technical documentation, legal writing, or situations requiring pure data presentation

## 5 Core Frameworks

### 1. Hero's Journey (Joseph Campbell)

**Structure**: Ordinary World → Call to Adventure → Trials → Transformation → Return

**Business Application**: Customer is the hero (not your product). Your product is the guide.

**Template**:
1. **Ordinary World**: Customer's status quo (with pain)
2. **Call**: Problem becomes urgent
3. **Trials**: Attempts to solve it fail
4. **Guide appears**: Your solution
5. **Transformation**: Customer succeeds
6. **Return**: They share their success

**Example** (SaaS pitch):
> "Marketing teams drown in manual reporting (Ordinary World). When the board demands real-time ROI visibility (Call), spreadsheets break (Trials). Our dashboard aggregates data automatically (Guide). Now they present insights in minutes, not days (Transformation). The CMO got promoted and recommended us to 5 peers (Return)."

### 2. Before-After-Bridge (BAB)

**Structure**: Before (pain) → After (vision) → Bridge (how to get there)

**Best for**: Landing pages, ads, cold emails

**Template**:
1. **Before**: Current painful state
2. **After**: Desired future state
3. **Bridge**: How your solution gets them there

**Example**:
> **Before**: "You're losing 30% of leads because follow-ups are manual and slow."  
> **After**: "Imagine every lead gets a personalized reply in under 60 seconds."  
> **Bridge**: "Our AI assistant handles first responses automatically. Setup takes 10 minutes."

### 3. Pixar Pitch (Pixar Story Formula)

**Structure**: 22-word template for any story

**Template**:
> "Once upon a time, ___. Every day, ___. One day, ___. Because of that, ___. Because of that, ___. Until finally, ___."

**Example** (Startup pitch):
> "Once upon a time, developers wasted hours on deploy config. Every day, they copy-pasted YAML and broke production. One day, we built a deploy UI that generates safe configs. Because of that, deploy time dropped 80%. Because of that, teams ship 3x faster. Until finally, 500 companies adopted it and Microsoft acquired us."

### 4. Problem-Agitate-Solve (PAS)

**Structure**: Problem → Agitate (make pain vivid) → Solve

**Best for**: Sales copy, urgent pitches

**Template**:
1. **Problem**: Identify the pain
2. **Agitate**: Make it worse (consequences, urgency, emotion)
3. **Solve**: Present your solution

**Example**:
> **Problem**: "Your API has no rate limiting."  
> **Agitate**: "A single bad actor can take down your entire service. Last quarter, 3 competitors suffered multi-hour outages from DDoS attacks. Customers churned. Revenue lost. Trust gone."  
> **Solve**: "Our rate limiter deploys in 5 minutes and scales automatically. $49/month for peace of mind."

### 5. Star-Moment-Success (SMS)

**Structure**: Star (character) → Moment (challenge) → Success (outcome)

**Best for**: Case studies, testimonials, customer stories

**Template**:
1. **Star**: Who is the customer? (role, company, context)
2. **Moment**: What challenge did they face? (specific, relatable)
3. **Success**: How did they win? (quantified outcome)

**Example**:
> **Star**: "Jane, VP of Ops at a 200-person SaaS company."  
> **Moment**: "She was manually tracking 40 vendor contracts in spreadsheets. Renewals were missed. Budget overruns."  
> **Success**: "With our contract platform, she automated alerts, cut SaaS spend by 18%, and freed 10 hours/week. Her CEO promoted her to COO."

## Story Elements That Hook

| Element | Why It Works | Example |
|---------|--------------|---------|
| **Specificity** | Concrete details are believable | "Lost $47K in Q2" not "Lost money" |
| **Conflict** | Tension creates engagement | "The board wanted to fire him" |
| **Transformation** | People love before/after | "From $0 to $10M ARR in 18 months" |
| **Emotion** | Logic convinces, emotion converts | "She cried when she saw the NPS score" |
| **Stakes** | What's at risk? | "If we didn't ship by Friday, we'd lose the client" |

## Common Rationalizations

| Rationalization | Reality |
|-----------------|---------|
| "Just give them the facts" | Data informs, but stories persuade. Use both. |
| "Storytelling is fluff" | Stories make ideas memorable (63% recall vs 5% for stats alone). |
| "I'm not creative" | Storytelling is structure, not fiction. Follow templates. |
| "This is too serious for stories" | Even enterprise B2B and technical audiences respond to narrative. |

## Red Flags

- Your "story" is just feature lists disguised as narrative
- The customer isn't the hero (you are)
- You use story frameworks to obscure facts or manipulate
- Your narrative has no conflict or stakes (boring)
- You over-dramatize to the point of incredibility

## Verification

- [ ] Framework chosen matches context (BAB for landing page, Hero's Journey for keynote, etc.)
- [ ] Customer is the hero (not your product/company)
- [ ] Specific details included (names, numbers, moments)
- [ ] Conflict and stakes are clear
- [ ] Transformation or outcome is quantified
- [ ] Story is true and ethical (not fabricated or exaggerated)