Each week, we share a practical technique to become a more effective storyteller and analyze a video that demonstrates its use in the real-world.
Quote of the week
“If you would persuade, you must appeal to interest rather than intellect.” Benjamin Franklin

photo: campaign creators via unsplash
Have you ever walked into a stakeholder meeting armed with compelling data, detailed user research, and a brilliant product strategy, only to leave feeling like you spoke different languages? You know your solution works, but somehow your pitch fell flat.
You're not alone. According to the Product Management Festival Survey 2024, a majority of product managers say stakeholder buy-in is their biggest challenge. Harvard Business Review found nearly half of failed product pitches don't articulate the problem clearly, while McKinsey reported that a third fail because the narrative doesn't resonate.
The issue isn't your solution - it's how you're presenting it.
Why Features Don't Sell, But Stories Do
Two years ago, I watched a product manager deliver what should have been a winning pitch. She had impressive metrics, competitive analysis, and a roadmap that addressed every stakeholder concern. Yet the room remained skeptical. Her problem? She led with features instead of stories.
Stories have the ability to connect with people at an emotional level, creating the foundation for logical buy-in.
The Three-Sentence Story Framework
Building on insights from Pixar's storytelling approach, here's a simple framework that transforms abstract product concepts into compelling narratives:
Context: "Once upon a time..." Set the stage by introducing your characters and explaining the current situation. This isn't just background - it's about making your audience care about the people affected by the problem.
Example: "Our users wasted 3 hours per week on manual data entry."
Conflict: "But then..." Introduce the tension that makes your audience lean in. This is where you highlight the gap between what users need and what currently exists.
Example: "But no-code tools were too complex for non-technical teams."
Resolution: "So now..." Present your solution and demonstrate how it addresses the problem in measurable ways. This is where your features finally get their moment, but now they're positioned as the hero's tools, not the hero itself.
Example: "So we built a drag-and-drop solution. User adoption jumped 200%."
The power of this structure lies in its simplicity. In three sentences, you can transform a feature-heavy pitch into an engaging narrative that stakeholders can visualize and remember.
Video
This week, we analyze Jessica Huang's 45-second story from the Husky Startup Challenge that we've featured before. Notice how she uses this exact framework - context (friend Sally's online shopping), conflict (poor fit expectations), and resolution (MODE's solution) - to create immediate stakeholder engagement.
Watch how Jessica doesn't lead with features or technical specifications. Instead, she creates a relatable scenario that makes her audience immediately understand both the problem and why her solution matters. Her three-sentence structure turns a potential technology demo into a compelling human story.
As you prepare your next stakeholder presentation, remember: people don't buy products, they buy better versions of themselves. Your three-sentence story should help them see not just what you're building, but why it matters to the people who will use it.
This newsletter was inspired by concepts from Pixar's storytelling approach and insights from product management research.