Turn a personal experience into a persuasive keynote arc

Transform raw autobiographical notes into a compelling, universal keynote narrative. Ideal for TEDx talks, executive keynotes, and founder presentations.

Prompt

Prompt
Act as an executive speechwriter and storytelling strategist. Ask me 3 questions in one message: 1. What specific personal incident or turning point do you want to share? 2. What universal lesson or paradigm shift does this experience reveal? 3. Who is your audience, and what practical behavior do you want them to adopt? After I answer, transform my raw story into a structured five-stage keynote narrative. Avoid melodramatic clichés. Ensure the personal experience functions as evidence for a broader thesis, not self-serving autobiography. Output format: 1. The Core Idea in one memorable sentence. 2. A 5-part narrative breakdown (Inciting Moment, Complication & Stasis, Turning Point, Universal Insight, Call to Action) with talking points for each. 3. Two potential opening hooks and one closing line.

Example output

Example for: an engineering director who learned leadership after a failed production outage

1. The Core Idea

True operational resilience is not built by eliminating human error, but by designing systems where failure is safe to discuss.

2. Five-Part Narrative Breakdown

1. Inciting Moment (The Flashpoint)

  • Describe the exact physical setting: 2:14 AM on a Tuesday, an amber terminal alert, and 40,000 active users suddenly dropped.
  • Detail your immediate emotional response: panic, followed by the instinct to find who pushed the bad commit.

2. Complication & Stasis (The Mistaken Belief)

  • Outline the standard industry playbook you executed: finding the offending engineer, enforcing stricter approval gates, and adding three layers of sign-offs.
  • Explain the hidden cost: for the next six months, software releases slowed to a crawl, and engineers hid minor anomalies out of fear.

3. Turning Point (The Shift in Perspective)

  • Detail the second incident: a preventable bug slipped past all six sign-offs because everyone assumed someone else checked it.
  • Contrast the realization: accountability cannot be created through process layers that hide personal ownership.

4. Universal Insight (The Shared Truth)

  • Connect the specific coding incident to team dynamics at large: when organizations punish mistakes, they do not prevent errors; they simply prevent discovery.
  • Define the alternative: blameless post-mortems and psychological safety as hard operational assets.

5. Call to Action (The Practical Step)

  • Urge leaders to stop asking "Who caused this?" during their next breakdown and instead ask "What system made this error easy to commit?"
3. Hooks and Closing
  • Opening Hook A: "At 2:14 AM on a Tuesday, my team cost our company $180,000 in six minutes—and my first instinct was to find a person to blame."
  • Opening Hook B: "Most leaders think their biggest threat is incompetence. It isn't. It is fear dressed up as caution."
  • Closing Line: "If your team cannot afford to make a mistake in daylight, they will simply bury them in the dark."
Written by AI from this prompt. Your results will vary.

Works in ChatGPT, Claude, and Gemini. Provide direct answers to the model's 3 questions to establish your story's stakes. Follow up by asking the model to trim the draft down to a specific target speaking time, such as five or eight minutes.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Presentations & Public Speaking
Presentations & Public Speaking

Draft a warm milestone tribute speech from notes

Turn bulleted memories and achievements into a polished two-minute tribute speech. Ideal for team leads honoring retiring peers or celebrating major project launches.

Presentations & Public Speaking

Outline a five-minute lightning talk

Turn a single idea into a focused five-minute lightning talk structure that hooks listeners and stays strictly on time.