Storytelling Frameworks (스토리텔링 프레임워크)

"The universe is made of stories, not atoms." — Muriel Rukeyser

"Stories are just data with a soul." — Brene Brown

Why Storytelling Matters (왜 스토리텔링인가)

• Facts inform; stories transform (사실은 알리고, 이야기는 변화시킨다)
• People retain 65-70% of information shared through stories vs 5-10% of statistics
• Stories activate the brain's motor cortex, sensory cortex, and frontal cortex — facts activate only Broca's and Wernicke's areas
• Every great leader, salesperson, and teacher is a storyteller

Framework 1: The Hero's Journey (영웅의 여정)

Origin

Joseph Campbell's The Hero with a Thousand Faces (1949), refined by Christopher Vogler for Hollywood in The Writer's Journey (1992).

The 12 Stages

    ORDINARY WORLD                    SPECIAL WORLD
         |                                 |
    1. Ordinary World             7. Approach to Inmost Cave
    2. Call to Adventure          8. Ordeal (Supreme Test)
    3. Refusal of the Call        9. Reward (Seizing the Sword)
    4. Meeting the Mentor        10. The Road Back
    5. Crossing the Threshold    11. Resurrection
    6. Tests, Allies, Enemies    12. Return with the Elixir

Business Shortcut: 5-Stage Hero's Journey

For presentations and pitches, condense to 5 stages:

1. Status Quo — Here's how things are
2. Disruption — Something changes/threatens
3. Quest — The journey to solve it
4. Transformation — What was learned/built
5. New Normal — The better future

Framework 2: STAR Method (STAR 기법)

Origin

Developed for behavioral interview questions. Now used broadly for structured storytelling.

Structure

STAR+ Enhancement

Add these to make STAR stories memorable:

• Stakes: What would have happened if you failed? (위험)
• Tension: What moment was most uncertain? (긴장)
• Insight: What did you learn that you still use today? (통찰)

Example Structure

S: "In Q3 2024, our largest client threatened to leave after a failed deployment." T: "As the account lead, I had 2 weeks to prevent a $2M annual revenue loss." A: "I flew to their office, conducted root-cause analysis with their engineering team, rebuilt the deployment pipeline myself over a weekend, and created a 30-day stabilization plan." R: "Not only did they stay, but they expanded the contract by 40%. I learned that showing up in person during a crisis builds more trust than any slide deck."

Framework 3: PAS (Problem-Agitate-Solution)

Origin

Classic direct-response copywriting framework. Used in sales, marketing, and persuasive presentations.

Structure

Agitation Techniques

The "Agitate" step is what separates mediocre from great persuasion:

1. Consequences (결과): "If this continues for 6 more months..."
2. Comparison (비교): "Your competitors have already solved this..."
3. Hidden costs (숨겨진 비용): "The real cost isn't the tool — it's the 4 hours/week your team wastes on..."
4. Emotional cost (감정적 비용): "Every Sunday night, that pit in your stomach..."
5. Social proof of pain (고통의 사회적 증거): "73% of teams report this exact frustration..."

PAS vs PASO

Extended version adds Outcome (결과):

• Problem → Agitate → Solution → Outcome
• Outcome = concrete vision of life after the solution

Framework 4: Pixar Story Spine (픽사 스토리 스파인)

Origin

Created by Kenn Adams for improvisational theater. Adopted by Pixar as a story development tool.

The Spine

Once upon a time, there was ___.          (옛날에 ___가 있었다)
Every day, ___.                           (매일 ___했다)
One day, ___.                             (어느 날 ___가 일어났다)
Because of that, ___.                     (그 때문에 ___)
Because of that, ___.                     (그 때문에 ___)
Because of that, ___.                     (그 때문에 ___)
Until finally, ___.                       (마침내 ___)
And ever since then, ___.                 (그 이후로 ___)
The moral is: ___.                        (교훈은 ___)

Business Example

Once upon a time, there was a factory that ran maintenance by gut feeling. Every day, machines broke unexpectedly, costing $50K in downtime. One day, they installed IoT sensors on every critical asset. Because of that, they could predict failures 72 hours ahead. Because of that, maintenance became proactive instead of reactive. Because of that, downtime dropped 80% in 6 months. Until finally, they became the benchmark plant in the company. And ever since then, every new factory starts with predictive maintenance. The moral is: The most expensive maintenance is the kind you didn't plan for.

Why It Works

• "Once upon a time" establishes normalcy — the audience relaxes
• "Every day" creates rhythm and expectations
• "One day" breaks the pattern — attention spikes
• "Because of that" (x3) creates causality — the brain craves cause-and-effect
• "Until finally" delivers resolution — satisfaction

Framework 5: Nancy Duarte's Sparkline (낸시 두아르떼의 스파크라인)

Origin

Nancy Duarte's Resonate (2010). Analyzed hundreds of great speeches (MLK, Steve Jobs) and found a common structure.

The Pattern: What Is vs What Could Be (현재 vs 가능한 미래)

  What Could Be ─────╮    ╭────╮    ╭──── NEW BLISS
                      │    │    │    │
                      ╰────╯    ╰────╯
  ────────────────────────────────────────
  What Is ────────────╮    ╭────╮
                      │    │    │
                      ╰────╯    ╰────────
  ← Beginning                    End →

The speaker oscillates between:

• What Is (현재 상태): The current reality, the problem, the pain
• What Could Be (가능한 미래): The vision, the possibility, the promise

Each swing creates contrast and tension. The audience is pulled between dissatisfaction and hope.

Structure

1. What Is — Start with the audience's current reality
2. What Could Be — Paint the alternative
3. What Is — Back to reality (the gap stings more now)
4. What Could Be — Expand the vision further
5. What Is — Final contrast
6. New Bliss — End with the transformed future (the call to action)

Steve Jobs iPhone Launch (2007) — Sparkline

Key Principles

• Contrast creates energy (대비가 에너지를 만든다) — Without "What Is", "What Could Be" has no weight
• End on "What Could Be" — Always leave the audience in the aspirational state
• The audience is the hero — You are the mentor. The sparkline shows THEIR journey, not yours.
• STAR moment — Every great presentation needs one "Something They'll Always Remember" moment

Framework 6: 기승전결 (起承轉結) — Korean/East Asian Narrative

The traditional Korean 4-act structure:

When to use: Korean business presentations, writing for Korean audiences, any situation where the audience expects gradual build-up before the point.

Framework 7: 두괄식 (頭括式) — Conclusion-First

Korean business standard: State the conclusion/recommendation FIRST, then support with evidence.

• Opposite of Hero's Journey (which builds to climax)
• Used in: Korean corporate reports, military briefings, executive summaries
• Structure: Bottom Line → Supporting Point 1 → Supporting Point 2 → Restatement

Sub-commands

/story

Analyze a communication need and recommend the best framework.

/story:korean

Apply 기승전결 or 두괄식 to your content. Analyzes whether your audience/context calls for gradual build-up (기승전결) or conclusion-first (두괄식).

Input: Your topic, audience, and context (Korean business? presentation? report?).

Output: Structured narrative using the appropriate Korean framework.

Input: What you need to communicate, to whom, and for what purpose.

Output:

## Storytelling Recommendation

**Best Framework**: [Hero's Journey / STAR / PAS / Story Spine / Sparkline]
**Why**: [rationale]

### Draft Structure
[framework applied to your specific content]

### Key Moments to Emphasize
- ...

### Alternative Framework
[second-best option with brief outline]

/story:hero

Apply the Hero's Journey to your content. Full 12-stage or condensed 5-stage.

Input: Your topic, audience, and desired outcome.

Output: Stage-by-stage narrative outline.

/story:star

Build a STAR story for interviews, presentations, or case studies.

Input: The situation or achievement you want to describe.

Output: STAR structure with stakes, tension, and insight.

/story:pitch

Build a pitch using PAS or PASO.

Input: What you're selling/proposing and to whom.

Output: Problem statement, agitation angles, solution framing, and outcome vision.

/story:sparkline

Create a Sparkline presentation structure.

Input: Your topic and call to action.

Output: Alternating What Is / What Could Be beats, with STAR moment recommendation.

Anti-patterns (하지 말아야 할 것들)

1. Data Dump Disguised as Story (데이터 덤프를 이야기로 위장) — Adding "Once upon a time" to a spreadsheet doesn't make it a story. Stories need character, conflict, and change.
2. The Hero Is Always You (주인공이 항상 나) — In business storytelling, the customer/audience is the hero. You are the mentor/guide.
3. No Stakes (위험 없음) — Without risk of failure, there's no tension. No tension, no attention.
4. Burying the Lead (핵심을 묻어버리기) — Don't save the payoff for minute 30 of a 30-minute talk. Hook them in 30 seconds.
5. Generic Stories (일반적인 이야기) — "A company had a problem and solved it" convinces no one. Specific details create belief.
6. Forcing a Framework (프레임워크 강제 적용) — Not every situation needs the full Hero's Journey. A 2-minute update needs STAR, not 12 stages.
7. Neglecting Emotion (감정 무시) — Logic makes people think; emotion makes people act. Every story needs an emotional beat.
8. Happy Endings Without Struggle (고생 없는 해피엔딩) — Transformation without difficulty is unbelievable. Show the mess.

Framework Selection Guide (프레임워크 선택 가이드)

References

• Joseph Campbell, The Hero with a Thousand Faces (1949)
• Christopher Vogler, The Writer's Journey (1992, 3rd ed. 2007)
• Nancy Duarte, Resonate: Present Visual Stories that Transform Audiences (2010)
• Nancy Duarte, slide:ology (2008)
• Kenn Adams, How to Improvise a Full-Length Play: The Art of Spontaneous Theater (1990)
• Robert McKee, Story: Substance, Structure, Style, and the Principles of Screenwriting (1997)
• See: references/frameworks-detail.md