Amazon / Bezos Narrative Memo Meeting Template

Overview

The narrative memo meeting, popularised by Amazon under Jeff Bezos's leadership, replaces slide presentations with structured written documents. Instead of watching a presenter talk through bullet points, attendees spend the first portion of the meeting reading a carefully crafted memo in silence. Only after everyone has read the full document does discussion begin.

The rationale is straightforward: slide decks reward presentation skill over analytical rigour. A charismatic presenter can gloss over weak logic, while a thorough but less polished speaker may struggle to convey a strong argument. Written prose forces the author to think through their reasoning completely, because narrative sentences expose gaps in logic that bullet points can hide.

At Amazon, these memos are typically four to six pages of dense prose, including supporting data, customer anecdotes, and financial projections. The format demands significant preparation from the author, but the payoff is a meeting where every attendee arrives at the discussion with a deep, shared understanding of the proposal. This leads to sharper questions, better debate, and faster decision-making. For decisions that do not require this level of depth, consider a lighter-weight decision review meeting instead.

When to Use This Framework

The narrative memo format is best suited for high-stakes decisions that benefit from deep analysis. Consider this approach when:

• A significant investment, strategic pivot, or new market entry requires executive approval, such as topics typically covered during an executive strategy offsite
• The decision involves complex trade-offs that cannot be adequately communicated in a few slides
• You want to ensure every attendee has the same depth of understanding before discussion begins
• Previous meetings on the topic have been unproductive because attendees were not sufficiently prepared
• The proposal requires input from leaders across multiple functions (finance, engineering, marketing, operations) who need full context. Coordinate scheduling with Meeting Planner to find a time that works across departments
• You want to create a durable written record of the reasoning behind a decision for future reference. Browse all available formats in our leadership templates collection

Who Should Attend

Sample Agenda

Example Use Case

A VP of International at a B2B software company is proposing expansion into the Japanese market. The opportunity is significant but complex, requiring localisation of the product, establishment of a local entity, and partnerships with regional distributors. The VP has prepared a six-page narrative memo covering market size and growth projections, competitive landscape, go-to-market strategy, required investment, expected timeline to profitability, and key risks.

At the meeting, eight senior leaders read the memo in silence for 20 minutes. During the discussion, the CFO challenges the revenue projections, noting that the memo assumes a sales cycle comparable to the UK market when Japanese enterprise sales typically take 40% longer. The VP acknowledges the gap and agrees to revise the financial model with a longer ramp period. The CTO raises concerns about the localisation timeline, noting that right-to-left text rendering in the product's charting library will require significant engineering effort not accounted for in the memo.

After 25 minutes of discussion, the CEO decides to approve the market research phase but holds the full investment decision pending revised financials and a detailed engineering assessment. The note-taker captures three action items: revised financial model (VP, two weeks), engineering effort estimate (CTO, one week), and legal entity formation timeline (General Counsel, one week). A follow-up memo meeting is scheduled for four weeks later. The entire process, from reading to decision, takes under 60 minutes.

Best Practices

• Write in complete sentences and paragraphs, never bullet points. The discipline of prose forces the author to articulate cause and effect, acknowledge trade-offs, and build a coherent argument. Bullet points allow hand-waving.
• Distribute the memo at the meeting, not before. Pre-distributing leads to uneven preparation. Some people read it thoroughly, others skim, and a few do not read it at all. In-meeting silent reading ensures everyone starts from the same baseline.
• Protect the silent reading time absolutely. No chatting, no checking phones, no "quick questions." The value of this format depends on every person reading the full memo before discussion begins.
• Include data and customer evidence. Assertions without evidence are opinions. Ground the memo in market data, customer quotes, financial analysis, and competitive benchmarks.
• Address counterarguments proactively. A strong memo anticipates objections and addresses them. This shows intellectual honesty and accelerates the discussion by pre-empting predictable challenges.
• Keep the memo to six pages or fewer. Brevity forces prioritisation. If the author cannot make their case in six pages, the thinking is not yet clear enough.
• Separate clarifying questions from debate. A quick round of factual clarifications before the main discussion prevents the conversation from getting derailed by misunderstandings.
• End with a clear decision. The meeting should conclude with an explicit outcome. "We need to think about it more" is not a decision. If the proposal needs revision, specify exactly what must change and schedule a follow-up.

Common Mistakes

• Writing a slide deck in paragraph form. A memo full of vague, high-level statements is not a narrative. The format demands analytical depth, specific data, and rigorous reasoning.
• Sending the memo in advance and skipping the silent reading. This defeats the purpose. People who "already read it" often skimmed it days ago and retain little. The shared reading ritual is what makes the discussion productive.
• Allowing discussion to start before everyone has finished reading. Fast readers who start talking while others are still reading create an uneven playing field. Wait until the last person looks up.
• Using the memo format for routine updates. Narrative memos are high-effort documents suited for significant decisions. Using them for weekly status updates burns out writers and trivialises the format. For regular updates, a weekly leadership sync or stakeholder update meeting is a better fit.
• Failing to include risks and trade-offs. A memo that only presents the upside is advocacy, not analysis. Decision makers will trust the author more when they see a balanced assessment.
• Not reaching a decision at the end. If the meeting ends without a clear yes, no, or conditional approval with specific revisions, the entire exercise was wasted. The facilitator must push for a definitive outcome.

Related Templates

Related Tools