AI Prompt for Turning Facts Into Stories

What it does

You have facts, data, or results that need to land with an audience — but a bulleted list won’t cut it. This prompt transforms raw material into a narrative with tension, structure, and a clear takeaway. Three modes: Draft (produce the narrative), Analyze (deconstruct the story potential without writing), or Coach (produce the narrative and explain the structural choices). Default is Coach. Works for presentations, blog posts, case studies, investor updates, or any situation where you need people to care about information, not just receive it.

The Prompt

I need to turn raw material into a compelling narrative.

The facts/data:
[PASTE YOUR FACTS, NUMBERS, RESULTS, OR KEY POINTS]

Audience: [WHO WILL READ/HEAR THIS — role, expertise level, what they care about, what decisions they're making]

Format: [PRESENTATION / BLOG POST / CASE STUDY / EMAIL / INTERNAL MEMO / OTHER]

Desired length: [APPROXIMATE — e.g., "5-minute talk", "800 words", "one page"]

Mode: [DRAFT / ANALYZE / COACH — default is COACH]
- Draft: produce the narrative
- Analyze: deconstruct the material's story potential without writing
- Coach: produce the narrative and explain the structural choices

---

Please follow these steps:

1. IDENTIFY THE STORY TYPE

Not all material fits the same arc. Evaluate which type best serves this material:
- **Transformation:** a clear before/after — something changed and the change matters
- **Discovery:** something unexpected was found — the surprise IS the story
- **Contrast:** two things that seem similar are different (or vice versa) — the gap creates insight
- **Origin:** how something came to exist, often told backward from the result
- **Mystery:** start with the surprising outcome, then reveal the path that led there

Output this step as a required structured block:

Story type: [chosen type]
Evidence that supports this type: [2-3 specific items from the material]
Evidence that would support a different type: [name the strongest alternative type and cite evidence for it]
Why this type wins for this audience: [one sentence — the tie-break]

If the material genuinely doesn't contain a story — it's just information — say so directly. An honest "this works better as a structured summary" is more useful than a forced narrative.

2. STATE THE RED THREAD (REQUIRED OUTPUT FIELD)

At the top of every mode, state it as a named output slot — do not bury it in prose:

Red thread: [one sentence]

This is the single connecting idea every section must serve. Every paragraph either advances or enriches this thread. Anything that doesn't, cut — no matter how interesting it is on its own. If you cannot state the red thread in one sentence, the story isn't ready yet.

3. BUILD THE STRUCTURE

Adapt these elements to your chosen story type:

- **Hook:** One sentence or image that earns the next 30 seconds of attention. No preamble. No throat-clearing.
- **Context:** Minimum background needed — and nothing more. The audience should feel slightly impatient for the main point. That's the right amount of context.
- **Tension:** What was at stake, uncertain, broken, or surprising. Calibrate to the audience — a board cares about strategic risk, a dev team cares about technical uncertainty, a customer cares about their own problem.
- **Turn:** The key insight, decision, or result. This is the structural peak — the moment the red thread pulls taut.
- **Landing:** What this means for THIS audience, specifically. Not a generic conclusion. Not "and so we learned that teamwork matters." What should they think, feel, or do differently?
- **Sensory anchor:** Identify one concrete, specific detail that will make this story stick. A number with context, a quote, a moment. The audience will forget your argument but remember this detail. Place it at or near the turn.

4. DRAFT THE NARRATIVE (skip in Analyze mode)

Write the full narrative in the requested format and length. Follow the structure from step 3.

Rules:
- Match tone to audience and format. A board presentation sounds different from a dev blog.
- Use one strong example instead of three weak ones. Story is about focus, not coverage.
- Every sentence must earn its place. If you can cut it without losing meaning, cut it.

5. STRUCTURAL CHOICES

Show the alternatives you considered:
- Which other story type(s) could have worked? Why is your choice stronger for this audience? (Reference your falsification evidence from step 1.)
- One alternative hook you rejected, with reasoning.
- If you cut material that was interesting but didn't serve the red thread, name it — the author may want it elsewhere.

In Coach mode: for each choice, explain the storytelling principle behind it.

---

IMPORTANT — do NOT:
- Default to the transformation arc. Transformation is the most familiar type and the one generic prompts reach for by habit. If the material best fits origin, discovery, contrast, or mystery, choose that type and defend the choice in Structural Choices. A defended non-transformation pick is almost always stronger than an undefended transformation one.
- Use "journey," "game-changer," "in today's fast-paced world," "imagine a world where," or other narrative clichés. If you catch yourself reaching for one, find the specific, concrete version instead.
- Add dramatic tension that isn't in the source material. Manufactured drama is the fastest way to lose a sophisticated audience. If the stakes are modest, let them be modest.
- Front-load context before the hook. Background is earned after you've made the audience care. If your first paragraph is setup, restructure.
- Resolve tension too quickly. Sit in the uncertainty, the problem, the gap — let the audience feel it before delivering the turn. A story that rushes to its conclusion teaches nothing.
- Write a generic landing. "And that's why innovation matters" is not a landing. The landing must connect to a specific decision, feeling, or action for THIS audience.
- Summarize the whole story in the hook. A hook is a door, not a window — it should pull people through, not show them everything from outside.

---

STORYTELLING INSTINCT — mode-specific timing:

- **Draft mode:** omit entirely. Draft is output-only; ship the narrative and stop.
- **Analyze mode:** surface at the END, after the structural deconstruction. The instinct is earned through the analysis — name the one transferable principle the material revealed.
- **Coach mode:** front-load a one-sentence principle BEFORE the draft ("The principle at work here: [X]"), then demonstrate it through the structural choices in steps 3 and 5. A reader should be able to see the principle operating in the draft itself, not just hear it announced.

Frame it as: "The principle at work here: [X]. Next time you have [similar material], [specific guidance]." Not generic writing advice — a principle the author can apply to their next story.

Usage Notes

• The biggest differentiator vs. generic storytelling prompts is type identification — this prompt makes you pick between five story types (transformation, discovery, contrast, origin, mystery) with falsification evidence, instead of assuming everything is a tension→resolution arc.
• Mode selection matters. Use Analyze before you commit to writing — especially when you’re not sure the material contains a story at all. Use Draft when you already know the shape and just want output. Default to Coach when you want both narrative and the craft behind it.
• The red thread is stated as a required output field for a reason: if you can’t say the connecting idea in one sentence, the story isn’t ready. Use the red thread as a cutting tool — anything that doesn’t serve it goes, no matter how nice the sentence.
• For data-heavy material, pick one number that tells the whole story and build around it. “Revenue grew 34% in Q2” is a story seed. A table of 12 metrics is not.
• Works especially well as a second pass — write your draft first, then use this prompt to find the narrative you missed.