Storytelling Advisor
What It Does
Transforms raw ideas, experiences, or messages into structured narratives using proven storytelling frameworks. Whether you're writing a brand story, a keynote, a pitch deck, or a social media thread, this skill helps you find the right structure, emotional arc, and narrative tension.
Frameworks Available
1. The Hero's Journey (Monomyth)
Best for: Brand origin stories, founder journeys, case studies, transformation narratives
| Stage | Description | Prompting Question |
|---|---|---|
| Ordinary World | The hero's normal life before the adventure | What was life like before the problem was solved? |
| Call to Adventure | An event disrupts the status quo | What changed? What forced action? |
| Refusal of the Call | Doubt, hesitation, fear | What almost stopped you from taking action? |
| Meeting the Mentor | A guide provides wisdom or tools | Who or what showed the way? |
| Crossing the Threshold | Commitment to the journey | What was the point of no return? |
| Tests, Allies, Enemies | Challenges, support, obstacles | What went wrong along the way? Who helped? |
| Approach to the Inmost Cave | Preparing for the biggest challenge | What was the hardest obstacle you faced? |
| Ordeal | The central crisis | What was make-or-break moment? |
| Reward | The prize for surviving the ordeal | What did you gain? |
| The Road Back | Returning to normal life with new wisdom | How did things change after? |
| Resurrection | Final test — applying the lesson | How did you prove the transformation was real? |
| Return with Elixir | Sharing the lesson with the world | What can others learn from this journey? |
2. Pixar Storytelling Formula
Best for: Short-form narratives, social media stories, email sequences, product launches
Structure: Once upon a time there was ___. Every day, ___. One day ___. Because of that, ___. Because of that, ___. Until finally ___.
| Element | Role | Example (Brand Story) |
|---|---|---|
| Once upon a time... | Setup — who, where, when | "Once upon a time, a designer couldn't find a simple prototyping tool." |
| Every day... | Status quo — the routine struggle | "Every day, she wasted hours on complex software that kept crashing." |
| One day... | Inciting incident | "One day, she decided to build her own tool." |
| Because of that... | Consequence 1 | "Because of that, her friends asked to use it too." |
| Because of that... | Consequence 2 | "Because of that, she realized others had the same problem." |
| Until finally... | Resolution | "Until finally, Figma was born." |
3. Freytag's Pyramid (Dramatic Structure)
Best for: Speeches, presentations, campaign narratives
| Element | Purpose |
|---|---|
| Exposition | Context — what's the situation? |
| Rising Action | Tension builds — what's at stake? |
| Climax | The turning point — the big reveal or decision |
| Falling Action | Consequences unfold |
| Denouement | Resolution and takeaway |
4. The Story Spine
Best for: Team storytelling, collaborative narrative building
Once upon a time... And every day... But one day... And because of that... And because of that... And because of that... Until finally... And ever since that day... The moral of the story is...
5. The Inverted Pyramid
Best for: Newsletters, blog posts, executive summaries
| Layer | Content |
|---|---|
| Lead | The most critical information (who, what, when, where, why) |
| Body | Supporting details, context, evidence |
| Tail | Background, nuance, optional reading |
Trigger Phrases
| Phrase | Action |
|---|---|
| "Help me tell a story about..." | Guides you through selecting the best framework |
| "Turn this into a narrative..." | Structures raw info into a story arc |
| "Make this more compelling..." | Suggests adding stakes, tension, or emotional beats |
| "Tell my brand story..." | Applies Hero's Journey to brand/founder narrative |
| "Pixar this for me..." | Forces content into the Pixar formula |
| "What framework should I use for..." | Recommends the best framework for your context |
| "Pitch this as a story..." | Converts a pitch into narrative form |
Step-by-Step Instructions
Step 1: Clarify the Goal
Ask: What do you want the audience to feel, think, and do after hearing this story?
Step 2: Harvest the Raw Material
Collect:
- Characters (who is the hero? who is the mentor? who is the antagonist?)
- Setting (where and when does this happen?)
- Conflict (what was the problem or challenge?)
- Stakes (what was at risk?)
- Transformation (how did things change?)
- Lesson (what can be learned?)
Step 3: Select the Framework
Match the story type to the right structure:
| If you're telling... | Use... |
|---|---|
| A founder origin story | Hero's Journey |
| A product value prop | Pixar Formula |
| A keynote or speech | Freytag's Pyramid |
| A social media thread | Story Spine |
| A newsletter or article | Inverted Pyramid |
Step 4: Map Content to Structure
Fill each framework slot with your raw material. Identify gaps and missing beats.
Step 5: Add Narrative Devices
- Emotional hook: Start with a relatable moment or surprise
- Specific details: Concrete beats (e.g., "3 AM in a coffee shop") beat abstractions ("working hard")
- Tension: What was almost lost? What was uncertain?
- Pacing: Short sentences for action, longer ones for reflection
Step 6: Refine and Cut
- Remove everything that doesn't serve the goal
- Read aloud to test rhythm
- Tighten: Can you say it in half the words?
Step 7: End with a Punch
The last line should be memorable — a lesson learned, a question posed, an invitation extended.
Examples
Example 1: SaaS Founder Story (Hero's Journey)
Input: "I built a project management tool because Trello was too simple and Jira was too complex."
Output (condensed): "As a designer at a 50-person agency, Sarah lived in spreadsheet chaos — every day, tasks slipped through the cracks (Ordinary World). When a client threatened to leave over a missed deadline, she knew something had to change (Call to Adventure). She almost bought another tool, but none fit (Refusal). Her partner suggested building something just for their team (Mentor). So she spent three weekends coding a prototype (Crossing the Threshold). Early users hated the first version — too many bugs (Tests)... until finally, she stripped it down to one feature: a clean Kanban board that actually worked. That became Trello 2.0. The client stayed. And 10,000 teams later, the lesson is clear: simple beats feature-rich when execution matters. (The Elixir)."
Example 2: Product Launch Email (Pixar)
Input: "Launching a new habit tracking app"
Output: "Once upon a time, there was a developer who wanted to build better habits. Every day, he downloaded habit trackers, used them for three days, and abandoned them. One day, he realized the problem: they all punished you for missing a day. Because of that, he designed an app that celebrates streaks without shaming gaps. Because of that, his own habits stuck for the first time. Until finally — after 18 months of building — Streakful was ready for the world. The first 500 beta users are in. Want to join them?"
Pro Tips
- Start in the middle: The most interesting story doesn't always start at the beginning. Open with the crisis, then flash back.
- Use contrast: Before/after, then/now, almost lost/eventually won.
- Be specific with numbers: "3 weeks of sleepless nights" > "a challenging period."
- Include a weakness: Vulnerable stories build trust. Don't be the flawless hero.
- End with a call-to-story: Invite the audience to see themselves in the narrative.
