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.

Fact and Fiction Boundary

• For case studies, pitches, testimonials, biographies, and other factual narratives, use only facts the user supplied or explicitly confirmed.
• Never silently invent names, quotations, dates, durations, metrics, customers, outcomes, motives, or events to make a factual story more compelling.
• Mark missing material as a question, a placeholder such as [customer outcome needed], or an explicitly labeled illustrative option.
• Invent details only when the user requests fiction or explicitly authorizes creative fabrication. Keep fictional additions distinguishable from factual claims.

Frameworks Available

1. The Hero's Journey (Monomyth)

Best for: Brand origin stories, founder journeys, case studies, transformation narratives

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 ___.

3. Freytag's Pyramid (Dramatic Structure)

Best for: Speeches, presentations, campaign narratives

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

Trigger Phrases

Step-by-Step Instructions

Step 1: Clarify the Goal

Infer what the audience should feel, think, and do from the request. Ask one focused question only when the missing goal would materially change the 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?)

Separate confirmed facts from assumptions and gaps before drafting. Ask only for gaps that materially affect the story; otherwise retain visible placeholders.

Step 3: Select the Framework

Match the story type to the right structure:

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: Prefer concrete details supplied by the user. Never add a detail such as "3 AM in a coffee shop" to a factual account unless it is confirmed.
• 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: Factual Founder Story with Gaps

Input: "I built a project management tool because Trello was too simple and Jira was too complex."

Output (outline):

• Problem: Existing tools felt either too simple or too complex for the user's needs.
• Action: The user built a project management tool.
• Outcome: [What changed for you or your users?]
• Evidence needed: [Who first used it?] [What measurable result can be verified?]

Do not add a company size, customer crisis, development timeline, adoption count, or testimonial unless the user supplies it.

Example 2: Explicitly Fictional Product Launch Exercise

Input: "Create a fictional launch-story example for a new habit tracking app."

Output: "Fictional example: Once upon a time, there was a developer who wanted a kinder way to build habits. Every day, rigid streaks made one missed day feel like failure. One day, the developer tried a tracker that welcomed restarts. Because of that, returning became easier. Until finally, the idea became an app designed around beginning again."

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.
• Use verified specificity: Real, sourced numbers are stronger than generic claims. Use placeholders when the number is not known.
• Include a limitation: For factual stories, include a supported challenge or trade-off rather than making the subject unrealistically one-dimensional.
• End with a call-to-story: Invite the audience to see themselves in the narrative.