Storytelling for business
How do I use storytelling to make my presentations and pitches more compelling?
Projekt-Plan
Why: In business storytelling, your brand or product is not the hero; your customer is. If you position yourself as the hero, the audience remains distant.
How:
- Identify one specific 'Hero' persona for your next pitch.
- List their primary external problem (tangible), internal problem (frustration), and philosophical problem (why it's just plain wrong).
- Write down what the hero wants most in relation to your offer.
Done when: You have a one-page 'Hero Profile' detailing their needs and frustrations.
Why: Every hero needs a guide (like Yoda or Obi-Wan) to help them overcome obstacles. Your role is to provide empathy and authority.
How:
- Draft two sentences of empathy: 'We understand how frustrating it is to [Problem]...'
- Draft two sentences of authority: Mention a brief statistic or a past success that proves you can solve the problem.
- Ensure these are ready to be integrated into your presentation intro.
Done when: You have a written 'Guide Statement' that balances empathy and authority.
Why: A presentation without a central theme is forgettable. You need a single, clear message that anchors everything.
How:
- Use the Duarte 'Big Idea' formula: [Your Point of View] + [What's at Stake].
- Example: 'Switching to decentralized servers (POV) will prevent the $2M annual loss from downtime (Stakes).'
- Keep it under 140 characters.
Done when: Your 'Big Idea' is written in a single, punchy sentence.
Why: The 'And, But, Therefore' (ABT) framework is the DNA of story. It creates immediate tension and resolution.
How:
- And: State a shared context (e.g., 'We want to scale AND maintain quality').
- But: Introduce the conflict (e.g., 'BUT our current tools are too slow').
- Therefore: Offer the solution (e.g., 'THEREFORE, we developed X').
- Practice saying this in under 30 seconds.
Done when: You have a 3-sentence ABT pitch that you can recite from memory.
Why: Great presentations alternate between 'What is' (the current reality) and 'What could be' (the future vision) to build emotional tension.
How:
- Draw a horizontal line. The bottom is 'What is' (pain points), the top is 'What could be' (solutions).
- Map your slides to jump between these two states at least 3-4 times.
- End with the 'New Bliss'—the final state of success for your hero.
Done when: You have a visual storyboard showing the 'What is' vs. 'What could be' transitions.
Why: Starting in the middle of the action (In Medias Res) hooks the audience instantly compared to a boring 'About Us' slide.
How:
- Identify the moment of highest tension in your hero's journey.
- Start your presentation with: 'It was 2 AM on a Tuesday when the servers finally gave up...'
- Skip the introductions until after this hook.
Done when: Your presentation script starts with a high-stakes opening scene.
Why: You shouldn't have to invent stories every time. A story bank is a vault of anecdotes ready for use.
How:
- Create a database with columns: Title, Theme (e.g., Failure, Innovation), and The Lesson.
- Add 5 stories: 1 Origin story, 2 Customer success stories, 1 'Failure' story, and 1 'Aha!' moment.
- Keep them brief—just the core facts and the emotional 'turn'.
Done when: You have a digital database with at least 5 categorized stories.
Why: Abstract facts are boring; sensory details are memorable.
How:
- Take a customer success story from your bank.
- Instead of 'They were happy,' describe the 'sigh of relief' or the 'silence in the room' when the problem was solved.
- Use specific numbers (e.g., '14 missed calls' instead of 'many calls').
Done when: One key anecdote is rewritten with at least three specific sensory details.
Why: Slides should be visual aids, not teleprompters. Too much text kills the story.
How:
- Limit each slide to ONE idea, ONE image, and less than 10 words.
- Use high-quality, generic imagery that evokes the emotion of the current 'Sparkline' state.
- Remove all bullet points; tell the story verbally instead.
Done when: Your slide deck is minimalist, with no more than 10 words per slide.
Why: Silence is a storytelling tool. It allows the audience to process the 'But' (conflict) or the 'Therefore' (resolution).
How:
- Identify three moments in your script where you introduce a major conflict or a solution.
- Mark these with a [PAUSE] tag.
- Practice standing still and remaining silent for a full 3 seconds at these marks.
Done when: You can deliver your pitch with intentional 3-second pauses at key moments.
Why: You cannot improve what you cannot see. Watching yourself reveals filler words and flat energy.
How:
- Set up your phone or webcam.
- Deliver your ABT-structured pitch with your 'In Medias Res' opening.
- Watch it back once to check for 'ums' and once to check for facial expressions.
Done when: You have a video recording of your pitch and a list of 3 areas for improvement.
Why: A story without a clear ending leaves the audience hanging. They need to know exactly what to do next to avoid failure.
How:
- Define one clear action (e.g., 'Schedule a 15-min demo').
- Remind them of the stakes: 'Don't let another quarter pass with [Problem].'
- Make the CTA button or slide the most visually distinct part of the deck.
Done when: Your final slide has a single, clear, and urgent Call to Action.
Why: External feedback catches logic gaps that you are too close to see.
How:
- Schedule a 15-minute call with a colleague or friend this Friday.
- Present your pitch without slides first to see if the story holds up on its own.
- Ask them: 'What was the conflict?' and 'What is the one thing I want you to do?'
Done when: You have received and documented feedback from at least one person.
Why: Confidence comes from repetition. A final run-through ensures you stay within time limits.
How:
- Wear what you plan to wear for the actual pitch.
- Use a clicker or keyboard to advance slides.
- Time the presentation to ensure it is 10% shorter than your allotted slot (to allow for Q&A).
Done when: You have completed a full rehearsal that meets the time requirements.