Storytelling > Specs
Product management is hard. You’re pulled in all directions by the needs and priorities of users, engineers, designers, stakeholders, and more. You find yourself having to justify the ‘why’ of your roadmap, the ‘how’ of your strategy, and the ‘what’ of every release.
If you’re a product manager, I’m sure you’ve seen this famous quote by David Henry Thoreau:
“Facts do not speak for themselves.”
But here’s the thing about facts. On their own, they can tell you what’s happening. They can’t tell you what to do about it. Facts can inform decisions, but they can’t inspire people to act on them. The one thing that can do both?
A good story.
Why it Matters
You might not think of yourself as a storyteller, but in product management, it’s one of your most important jobs. Why?
- Stories bring people together and guide them.
Say you’ve got a complex product decision to explain to five different teams. Chances are, they won’t leave with the same understanding of the what/why/how. Without a clear narrative, work will be siloed. People will make assumptions, and initiatives will fall by the wayside.
But a good story creates alignment. A good story will connect the dots between the customer problem, the business value, and the product decision.
Instead of stating bluntly, “We need to build this feature because it will drive engagement”, you can weave a story. “Let me tell you about Priya, one of our customers who signed up but never returned. Let me show you why that happened and what we can do about it.”
- Stories evoke emotions and encourage empathy.
Data tells, stories sell.
Stakeholders won’t be moved by a graph showing a 2% drop in user retention month-over-month. They don’t care about percentages, engagement scores, or numbers that end in .03. They care about real people. They care about stories.
A well-told story puts empathy front and centre. It goes beyond facts and data, helping people see things from the user’s perspective. It’s the difference between someone just nodding along and someone actually caring.
When people care, they become engaged. They start to think. And once you’ve got people thinking, they’ll act.
- Stories make things stand out.
We all live in a world drowning in slide decks, dashboards, and Jira tickets. Everyone gets bombarded by dozens of meetings, calls, and Slack messages every day. It’s noise. A lot of noise.
The product manager’s job is to cut through that noise. You’re fighting for people’s attention. Your job is to grab that attention and not let go. How do you do that? With a good story.
A compelling story is memorable. It sticks. And it will help your message rise to the top of that pile of other, less interesting stuff your audience gets from other teams, other products, other initiatives. If they remember your story, they’ll remember the value of your product.
A Real World Example
The following example will clarify why framing your use case or value proposition as a story is beneficial.
Angela’s Cart
A PM at a mid-sized e-commerce startup was trying to get buy-in for prioritising a checkout flow improvement in her roadmap. Sure, they could see cart abandonment in their funnel reports, but leadership didn’t see it as a priority.
The numbers were telling, but they weren’t inspiring anyone to action. So, the PM tried to do things differently. She showed up to her next executive sync with a similar set of slide decks as before. But one key slide was different.
Instead of opening with data, she opened with a story.
Meet Angela
She’s a busy mum of two who shops on her phone while she commutes. Last week, she found the perfect birthday gift for her daughter on ShopEasy. She added it to her cart. She even checked out the reviews and decided she should buy it.
Right at the moment she hit the pay button, she got asked to log in again. The page reloaded. The cart was empty. She got frustrated and gave up. She didn’t come back. That gift? She bought it elsewhere.
She followed up with data. The cart abandonment rate was 70% of returning mobile users who were logged out. Execs were now seeing the human cost behind that metric, and the budget to fix the session handling was approved that week.
That’s storytelling in action.
The How
Remember the following points when preparing for a storytelling session.
- The user first
Make it personal.
Describe a user in vivid detail. Give them a name. A backstory. A problem that’s keeping them up at night. “John, a 37-year-old self-employed small business owner, who currently spends 2 hours every night manually reconciling invoices…” is much more compelling than “Our SME customers struggle with manual billing reconciliation”.
- Structure it right
Stories can be simple. Just three pieces of information in the right order, and your audience will remember.
Problem: What’s broken, what’s missing, what’s hard, what’s painful?
Urgency: Why does this matter? Why is it important now? What workarounds has the user explored or tried?
Solution: What are we doing to address the problem? What are we building, releasing, or shipping?
Outcome: How does the user’s life, job, or business get better? What’s the quantifiable business value?
Problem-Urgency-Solution lets you share everything your audience needs to hear.
The full picture.
- Keep it real
Storytelling isn’t a performance art. Don’t over-dramatise. Be authentic. The point isn’t to wow people. It’s to help them understand, to help them feel connected to your product, to help them take action.
- Customise for your audience
The same story needs to be structured differently depending on who’s listening. The engineers will care about the problem’s complexity and edge cases. Leadership execs will want to hear the strategic impact.
The same story arc, but viewed through a different lens depending on who’s listening.
- Practice storytelling everywhere
You don’t need a stage or a PowerPoint deck to be a storyteller. You can do it in daily stand-ups, sprint reviews, product demos, hallway conversations, or during a meeting prep.
Storytelling can work anywhere, anytime you need to help someone understand your ‘why’. Don’t limit it to ‘official’ meetings only.
The Pitfalls
Let’s go over some of the pitfalls you need to avoid.
- Inflated fluff
If a story lacks a clear focus on what you’re doing and why, it risks becoming meaningless rambling.
- Neglecting data
Stories don’t just replace data; they leverage it.
Similar to Angela’s story, a data point or two can help you build context for your narrative. It also helps provide support and backup for the claims you’re making. Data, in storytelling, is the evidence for your claims. It can be the supporting character that makes your narrative bulletproof.
- Misplaced focus
Your story should not be about your product. It’s about the user. The hero of your narrative is a user, not a feature.
- Failure to show
Whenever possible, use visual evidence of the problem. Screenshots, real quotes, or short user videos.
Stories are far more powerful when they can be seen, not just heard.
Final Thought
Storytelling for product managers is more than just a presentation skill. It’s a leadership practice. It’s one of the best ways to inspire, motivate, and get buy-in from people and teams around you.
The next time you prepare for your presentation, meeting, product demo, or sync, ask yourself first: What’s the story I want people to walk away with? Because in the end, the best product managers aren’t the ones who explain features best.
They’re the storytellers.
