The most expensive meeting of my career was one where I had the better evidence and lost anyway. The other PM had a thinner analysis and a cleaner story. The room went with the story. It took me years to stop being bitter about that and start learning from it.
Here is what I eventually understood: the room did not choose worse evidence. The room chose the evidence it could carry out the door. Storytelling for product managers is not presentation polish. It is a compression algorithm for decisions, and the PMs losing influence right now are mostly not worse analysts than their peers. They are worse narrators of equal analysis.
The short version
Decisions propagate through retellings, so your argument has to survive being repeated by someone else when you are not in the room. Three frameworks cover 90% of PM situations: SCQA and the Minto pyramid for memos and readouts, the working-backwards PR/FAQ for new bets, and the premortem narrative for risk conversations. Verbatim customer quotes are your load-bearing beams because they are data already wearing narrative. This post is the deep dive on the storytelling skill from The Skill Stack: What PMs and CPOs Must Learn Now, with worked examples, a 4-week practice plan, and an opinionated resource list. The companion craft for product proof is in show, don't tell.
The retelling test
Every decision in an org bigger than ten people gets made at least partly in rooms you are not in. Your VP carries your case to the exec team. An engineer carries the why to their standup. A board member carries the product story to the next board.
So the real unit of PM communication is not the memo. It is the retelling of the memo.
The test: hand your last strategy memo to someone outside your team. An hour later, ask them to repeat the argument. Not the topic, the argument. The claim, the reason, the ask. If what comes back is "it was about the onboarding funnel," you wrote a report. If what comes back is "we should kill the trial flow because activated users all skip it, and they want two engineers for a quarter," you wrote a story.
Reports inform. Stories travel. Only things that travel get decided in your favor.
I run this test on my own writing constantly, and the failure rate is humbling. Structure is the fix, and three structures cover almost everything.
Framework one: SCQA, for memos and readouts
Barbara Minto built the Pyramid Principle at McKinsey, and the consulting world has run on it for fifty years. The core move: answer first, then grouped arguments below it, each group summarized by its own claim.
SCQA is the opening sequence. Situation: ground the reader in what they already accept. Complication: what changed or broke. Question: the decision this raises. Answer: your recommendation, stated plainly, before any evidence.
A worked product example. Status update, old way: "This sprint we shipped the export improvements, ran six customer calls, and started investigating the latency spike." Topic, no argument. Same update, SCQA:
Situation: Enterprise renewals depend on the reporting workflow. Complication: Latency on large reports doubled in the last month and two renewal accounts have flagged it. Question: Do we pause the export roadmap to fix it? Answer: Yes, for two weeks. Here are the three reasons and the cost.
The second version survives retelling. Someone can carry "we are pausing exports for two weeks to protect two renewals" up two levels intact. Nobody can carry a sprint inventory anywhere.
The pyramid part matters too: under the answer, group your support into three buckets at most, each with its own one-line claim. Readers remember groups, not lists. The strategy memo template on this site is built on exactly this shape.
Framework two: the PR/FAQ, for new bets
Amazon's working-backwards process, documented by Bryar and Carr in Working Backwards, inverts the proposal. Instead of arguing toward a thing, you write the press release for the finished thing, dated launch day, in customer language. Then you write the FAQ: the hard questions a skeptic would ask, answered before anyone builds anything.
Why it works as storytelling: the press release forces you to find the customer-visible story of the bet. If you cannot write a compelling paragraph about what changed for the customer, the bet has no story, which usually means it has no point. I have killed more of my own ideas at the press-release stage than any review process ever killed. That is the cheapest kill available, per the cost of being wrong.
The FAQ is the steel-manning. "Why will customers switch from their current workaround?" "What does this cost to run per user?" If the FAQ answers are mushy, the room will find the mush anyway. Better you find it first. Use the PR/FAQ template when you write your first one; the format discipline matters more than it looks.
Framework three: the premortem narrative, for risk
Gary Klein's premortem is prospective hindsight: assume the project shipped and failed, then have everyone write the story of why. Klein's research found that imagining an outcome as certain dramatically improves people's ability to find its causes.
The PM craft is in the narrative half. A risk register ("dependency on platform team, medium likelihood") gets skimmed. A premortem story ("it is March, adoption stalled at 4% because the platform migration slipped and we shipped on the old stack with double the latency") gets felt. Same risk, but the story version produces a mitigation conversation and the register version produces a nod.
Write the premortem as a half-page story, in past tense, with a date. Read it aloud at the kickoff. It is the only risk format I have seen change behavior in a room.
Quotes are data wearing narrative
A debate I have refereed a hundred times: story versus data. It is a false split. A verbatim customer quote is both. It carries the evidence (a real person said this) and the narrative (a human voice, a specific frustration) in one unit, which is why quotes survive retelling better than any chart.
The craft: two or three load-bearing verbatim quotes per memo. Verbatim, with role and context, never paraphrased, because a paraphrased quote is just your opinion in costume. Let aggregate numbers sit behind the quotes as proof of pattern, not in front of them as the headline. Build a running quote bank from your customer calls so the beams exist before you need to hold up a memo with them.
The 4-week practice plan
Week 1: rewrite an old memo answer-first. Pick a memo you wrote that landed flat. Move the recommendation to sentence four. Group the support into three claims. Compare versions. This rewires the instinct faster than any reading.
Week 2: SCQA your next status update. The lowest-stakes recurring artifact you own. Situation, complication, question, answer, every week from now on. The exec update template gives you the container.
Week 3: write a PR/FAQ for a real bet. Something actually on your roadmap, not a toy. Spend half a day. If the press release will not come together, that is information about the bet, not the format.
Week 4: run a premortem and write its narrative. Fifteen minutes with your team, everyone writes the failure story silently, then you synthesize one half-page narrative and read it at the next planning session. Log what it changed in your decision log; the premortem doubles as a judgment drill, which I cover in judgment reps(coming Jul 13).
The resource review, opinionated
Barbara Minto, The Pyramid Principle. Read part one carefully, skim the rest. Part one is the answer-first structure and grouping logic, which is the whole payload. The later parts are about problem analysis and are dated.
Wes Kao's Executive Communication course on Maven and her appearance on Lenny's podcast.** The podcast episode is the best free hour on this topic; her "signposting" and "managing up" frameworks are immediately usable. The course is worth it if your company pays.
Reforge's Storytelling for PMs. Good if you want the cohort structure and PM-specific cases. Skip if you have already done the four-week plan above; the overlap is real.
Nancy Duarte. The reference for deck-heavy orgs. If your decisions happen in slides rather than memos, her structure work transfers. If your org is memo-driven, Minto covers you.
What to skip: generic TED-style storytelling advice and hero's journey templates applied to B2B memos. Your VP does not need a call to adventure, they need the answer in sentence four. The hero's journey is for two-hour movies; you have ninety seconds of attention.
Pick one thing this week
Run the retelling test on the last memo you sent. Hand it to someone outside your team, wait an hour, ask for the argument back. Whatever fails to come back, that is your week-one rewrite. Start there.
Sources: Barbara Minto, Wes Kao on Maven, Wes Kao on Lenny's podcast, Bryar & Carr, Working Backwards, Gary Klein on premortems, HBR, Reforge, Nancy Duarte.
Further reading
- The Skill Stack: What PMs and CPOs Must Learn Now, the hub chapter this post deep-dives
- Show, Don't Tell, the prototype as the story you can touch
- The Investor and Board Narrative, storytelling at board altitude
- Wes Kao on Lenny's podcast, the best free hour on executive communication
Frequently asked
Why is storytelling a core PM skill and not just presentation polish?+
Because decisions in any org bigger than ten people get made when you are not in the room. Your argument travels through retellings: your VP repeats it to the CEO, an engineer repeats it to their team. Storytelling is the compression that makes the argument survive those retellings intact. Analysis that cannot be retold has no organizational force.
What is the retelling test for PM communication?+
Hand your memo or readout to someone outside your team. An hour later, ask them to repeat the argument back. If they can repeat the topic but not the argument (the claim, the reason, the ask), you wrote a report, not a story. The retelling test is the only eval of PM communication that matters, because retelling is how decisions actually propagate.
What are the three storytelling frameworks every PM needs?+
SCQA (Situation, Complication, Question, Answer) from Barbara Minto, for memos and readouts: state the answer first, then group the supporting arguments. The PR/FAQ from Amazon's working backwards process, for proposing new bets: write the press release for the finished thing and answer the hard questions before building. The premortem narrative from Gary Klein, for risk conversations: assume the project failed and write the story of why.
How is SCQA different from just writing a summary?+
A summary compresses what you did. SCQA compresses what you want decided. Situation establishes shared ground, Complication names what changed, Question frames the decision, Answer states your recommendation up front. Everything after the answer exists to support it in grouped, ordered arguments. Most PM memos bury the answer on page three. SCQA puts it in sentence four.
Should PMs use customer quotes or data in decision memos?+
Both, but understand that quotes are data wearing narrative. A verbatim customer quote carries the evidence and the story in one unit, which is why it survives retelling better than a chart. Use two or three load-bearing verbatim quotes per memo, with attribution context, and let the aggregate data sit behind them as the proof of pattern.
How long does it take to get good at PM storytelling?+
One framework per week for four weeks gets you from unstructured to dangerous. Week one, rewrite an old memo answer-first. Week two, SCQA your next status update. Week three, write a PR/FAQ for a real bet. Week four, run a premortem and write its narrative. Fluency takes longer, but the four-week loop builds the reflex that matters: structure before prose.
Comments (0)
Sign in with LinkedIn to leave a comment.
Sign in with LinkedIn