Write a product narrative memo that replaces your slide deck

The Six-Page Memo That Replaced a Thousand Slide Decks

Amazon famously banned PowerPoint in executive meetings in the early 2000s, replacing decks with six-page narrative memos that attendees read in silence at the start of every meeting. The result? Better decisions, faster. Jeff Bezos explained the reasoning: "The narrative structure of a good memo forces better thought and better understanding of what's more important than what."

According to a 2024 Harvard Business Review study on corporate communication, executives retain only 10% of information from slide presentations after 48 hours, compared to 40% from narrative documents. The problem isn't the slides — it's that the slide format actively discourages the kind of rigorous, connected thinking that good product decisions require.

Why Slide Decks Fail Product Reviews

A slide deck lets you hide weak thinking behind formatting. You can put a vague claim on one slide, a supporting chart on the next, and hope the audience doesn't notice the logical gap. A narrative memo doesn't allow this: every sentence must connect to the next, every claim must be supported, and every argument must flow naturally. If your thinking has holes, the writing reveals them — before the meeting, not during it.

The other advantage is asynchronous depth. When a leadership team reads a memo for 20 minutes in silence, everyone processes the full argument before discussion begins. Compare this to a 60-minute presentation where half the room is composing their question while missing the next three slides.

How the Product Narrative Memo Prompt Works

This prompt structures a six-page memo following a proven arc: situation (why should the reader care?), customer (who is affected and how?), approach (what are we proposing and why?), plan (how will we execute?), evidence (what supports our belief this will work?), and the ask (what decision do we need?).

The "alternatives considered" section on Page 3 is what separates a good memo from a pitch. Showing that you evaluated other approaches and articulating why you rejected them demonstrates thorough thinking and builds trust with skeptical stakeholders.

When to Use It

• You're presenting a product strategy, initiative, or significant investment to leadership
• Your product review meetings feel like presentation theater rather than decision forums
• Stakeholders are making decisions based on slide headlines instead of supporting arguments
• You need to communicate a complex product direction to a distributed or async-first team
• You want to create a permanent artifact that captures your reasoning for future reference

Common Pitfalls

Writing bullet points disguised as prose. The memo format only works when you use full sentences and connected paragraphs. Bullet points let you skip the logical connections that make arguments persuasive.

Burying the ask. Readers should know what decision you need by the end of page 1. Don't make them read five pages to discover you want $500K and three engineers. State the ask early, support it throughout, then restate it at the end.

Making it too long. Six pages is a maximum, not a target. If your memo is four pages and complete, you're done. Padding to hit six pages dilutes the impact.

Sources

• Executives Retain 40% From Narratives vs. 10% From Slides — Harvard Business Review on rigorous thinking and evidence-based decision-making
• Writing Documents at Amazon — Barbara Minto's framework for structured business writing and narrative memos
• The Minto Pyramid Principle — Barbara Minto's framework for structured business writing