By Kasper-Tanakrit Sermsuksan · Global Venture I: Playbook · Block G
You are here: G-04 · Block G · Telling Your Story · article 4 of 4 · Form G · Next: H-01 What Changed
In short: The six-page memo is a narrative document, with full sentences and no slides or bullets, that Amazon reads in silence at the start of a meeting and then discusses. It works because you cannot write six clear pages about something you do not understand. For a venture, it is the written report that explains your pitch deck.
"No PowerPoint. Here, we use six pages — narrative, not slides. Start drafting now, and keep refining."
That was the one instruction my boss gave me on my first day as a finance intern at Amazon's headquarters in Seattle. My job was to analyze Amazon's financial operations programs and find where the company could reduce costs.
I smiled and nodded, the way you do when you don't want to admit you have no idea what you've just agreed to.
I thought six pages would be plenty. I was wrong within the first hour.
I asked my boss for advice. She didn't soften it: "Trust me, six pages will feel too short. The first time I had to do it, I nearly cried."
She was right. I rewrote that memo more times than I can count. By the end, I knew that analysis better than anything I had written in three years of university. Not because the memo was long. Because it couldn't afford to be.
Then came the meeting. I handed a printed copy to everyone in the room — my boss, her boss, my teammates, HR — and waited.
For the first ten minutes, nobody spoke. Everyone read.
Ten minutes of silence is a long time when the document in their hands is yours. Every page-turn felt like a verdict. Then the questions came, fast and specific, the kind you only get from a room that has actually read what you wrote.
The project passed. My recommendations were adopted.1
That is why I ask every team I teach to write one.
What is the Amazon six-page memo?
The Amazon six-page memo, often called the Amazon 6-pager, is a narrative document of up to six pages, written in full sentences, that a meeting reads in silence before anyone discusses it.
On 9 June 2004, Jeff Bezos sent an email to Amazon's senior leadership team, the "S-team," that effectively banned PowerPoint from their meetings. The subject line: "No powerpoint presentations from now on at steam"2. Not recommended. Banned.
In its place: a written narrative. The 2004 email actually talked about a four-page memo2. Over time the standard became what Bezos later described as "narratively structured six-page memos," read in silence at the start of each meeting in "a kind of 'study hall'"3. No slides. No bullets. No presenter standing at the front of the room doing the thinking on behalf of the audience.
The reasoning was simple, and I think it still holds: bullet points hide thinking. A well-constructed sentence cannot. A memo forces you to construct complete arguments, acknowledge complexity, and write in a way that another intelligent person can evaluate critically.
Bullets let you hint at an idea. A sentence forces you to actually have one. I learned that in Seattle, one rewrite at a time.
For a venture-stage team, the memo does something even more important. It forces you to understand your own venture.
What does an Amazon six-pager look like?
Plain, on purpose. That surprises people the first time.
- Up to six pages of full paragraphs. That is why people call it a narrative memo. A few headings to guide the reader, and nothing that looks like a slide.
- Numbers only where they carry the argument. A small table or chart is fine. The reasoning around it stays in sentences.
- Printed and read first. In my meeting, everyone got a paper copy and read in silence before anyone spoke.
- Discussed second. The questions start only when everyone has finished reading.
I recommend the same for a venture memo: prose, up to six pages, following the six-part page plan below, with supporting material (your interview list, your numbers) in an appendix at the back.
How does Amazon actually run a memo meeting?
The meeting starts with reading, not talking.
In my meeting, the silent read lasted about ten minutes. Bezos has said the room reads in silence for about thirty minutes4. Either way, everyone arrives at the substantive discussion with the same depth of understanding. There is no warm-up, no context-setting, no one playing catch-up while the presenter builds the case.
The conversation that follows is about the substance. It is about what the memo argues, where the logic holds, where the evidence is thin, what is missing. The discussion is better because the document did the work it was supposed to do.
This is not a meeting efficiency hack. It is an intellectual standard.
Writing a memo at this level forces the author to close every loop they had left open in their own thinking. A document that was not ready to be read becomes obvious within minutes. A document that was solid becomes the foundation of a genuinely useful discussion.
My Amazon memo had to answer five questions: What is the customer problem? What is the proposed solution? What is the business impact? What are the risks? What is your recommendation? In my experience, Amazon did not prescribe what goes on each page. The structure below is our adaptation at SEA Bridge for an early-stage venture — the same five questions, plus the evidence and the team.
What should each of the six pages cover? (SEA Bridge's venture adaptation)
Page 1 — The problem and why it matters
State the problem clearly and make the reader feel its significance. Who has this problem? How widespread is it? What does it cost them — in time, money, frustration or missed opportunity? What does the status quo look like for someone living with this problem?
I want this page to end with the reader thinking: this is a real problem worth solving. Not "interesting." Not "plausible." Worth solving.
The specificity of the problem description is what earns that response. Vague problems sound like background noise. Specific ones land.
Page 2 — The customers and the evidence
Who specifically has this problem, and how do you know? This is where your field research lives — your 12 interviews and your interview report. Not "we surveyed the market" — who did you actually talk to, what did they tell you, and what pattern emerged across those conversations?
Many of my students learn this one the hard way. One wrote in a final reflection that the lesson that changed how they think about understanding a market was exactly this: you cannot just do research and assume your idea will work; you have to talk to people and hear their real problems. Page 2 is where that lesson either shows or does not.
I want real people (anonymized if needed), real quotes, real evidence of people experiencing the problem you described on Page 1. A strong Page 2 makes Page 1 undeniable. A weak Page 2 — one built on hypotheses about behavior rather than observed behavior — makes everything that follows feel shaky.
If your interviews revealed something you did not expect — a version of the problem you had not considered, a segment you had overlooked, a friction you had underweighted — Page 2 is where that appears. Evidence that surprised you is the most convincing kind.
Page 3 — The solution
What are you building, and why is it a better answer to the problem than what currently exists? Be specific. Be humble. Describe what it does, what it does not do, and why the gap between the status quo and your solution is meaningful. Include what your MVP test showed.
The most common mistake I see on this page: describing the product rather than the solution. A product is a thing. A solution is what that thing does for a specific person in a specific situation. "A mobile app with AI-powered recommendations" is a product. "A way for first-generation students to navigate scholarship applications without needing to know someone who went to university before them" is a solution.
Page 4 — The business model
How do you make money, from whom, at what price, through what channel? This page is the prose version of your Business Model Canvas. Include your best current understanding of unit economics — what it costs to acquire a customer and what that customer is worth over their lifetime (see Startup Metrics).
Be honest about what you know and what you are still testing.
I would much rather read "We believe our customer acquisition cost is approximately X, based on early experiments, and we will confirm this by running Y over the next ninety days" than a confident-sounding number that has no basis in reality. The first is a stronger statement.
One question I want answered here: who pays, and who uses? In many ventures these are not the same person. A school pays for a platform that students use. A hospital pays for software that doctors use. Understanding who controls the purchasing decision versus who experiences the product is fundamental to the model (see Who Are Your Customers?).
Page 5 — The plan and the risks
What are you doing in the next ninety days, and what would success look like? This is not a five-year roadmap. It is a clear, specific, credible account of your next move and how you will know if it is working. Name the biggest risks — the ones your FISHE Capital™ × CSTO™ map shows as threats or gaps — and how the plan tests them.
My test for a good plan: if someone else read Page 5, could they execute it? If the answer is no — if the plan is too vague, too aspirational, or too dependent on things you do not yet control — rewrite it until it is specific enough to be actionable by someone other than you.
Page 6 — The team and the ask
Who is building this, and why are you the right people? Relevant experience, complementary skills, honest acknowledgment of gaps. If there is a critical function you do not yet have covered, name it — and name your plan to address it.
Then, the ask. My advice is the same as in a pitch: be specific. If you are seeking funding, state the amount and what it will be used for — not in general terms, but in specific allocations tied to specific milestones. If you are seeking a partnership, state exactly what you need and what you are offering. If you are seeking an advisor, say what kind of expertise you are looking for and what the engagement would look like.
The ask that cannot be acted on is a missed opportunity. The more specific it is, the more useful the response can be.
Try it in 10 minutes
- Write Page 1 as a single paragraph: who has the problem, what it costs them, and what they do about it today. Full sentences. No bullets.
- Underline every sentence you could not back with an interview or a number.
- The underlined sentences are your to-do list for Page 2.
How do you know if your memo works? Read it cold
My standard: could a reasonably smart person who knew nothing about the subject read it and understand the argument? Not understand what the author meant — understand what the author actually wrote.
- Give your memo to someone who has never heard your pitch before — not a teammate, not a friend who has been following your journey. Someone genuinely cold.
- Ask them to read it without you explaining anything.
- Ask them to tell you back what they understood.
- The gap between what you intended and what they understood is your next edit.
- I recommend doing this three times before you send it.
The document you have after three cold reads is materially different from the one you had before.
Why do memos fail?
Two patterns show up again and again in the memos I read that do not work.
The first: writing it as a presentation script. Paragraphs that read as slide narration. Sentences that only make sense if you already know the context. Headers that do the work that arguments should be doing. A memo is a standalone document. It should be able to be read, understood and evaluated by someone who was not in the room when you built it.
The second: writing for an audience that already knows the venture rather than someone who does not. Every sentence should be testable against the question: would a smart, skeptical outsider understand and believe this? If not, rewrite it until they would.
A memo that is hard to write is a venture that is hard to understand.
Both problems have the same solution.
Reality check
This is the deliverable most teams leave too late, and the one that shows it most. Bullets creep back in. Page 2 turns out to be half a page because the interviews were thin. Page 4 has a confident number with nothing behind it. My own boss at Amazon nearly cried the first time she wrote one. You may feel the same.
If you are struggling at this stage, you are like most people. It means you are doing the real work.
Frequently asked questions
What is an Amazon 6-page memo?
A narrative document of up to six pages, written in full sentences, that Amazon uses instead of slide presentations. The room reads it in silence at the start of the meeting, then discusses it.
What is the Amazon memo format?
Prose paragraphs, a few headings, small tables or charts only where numbers need them, and supporting material at the back. No bullets carrying the argument: the reasoning stays in sentences. In my experience, Amazon set no fixed page topics; the six-part layout in this article is our adaptation at SEA Bridge for early-stage ventures.
What is a narrative memo?
A document that makes its case in connected paragraphs instead of slides or bullet points, so the reader can follow, and test, the reasoning. Amazon's six-pager is the best-known example.
Does the memo have to be exactly six pages?
Six pages is a ceiling, not a target. Shorter and clear beats six pages of padding. Appendices (interview list, numbers) do not count toward the six.
How is the memo different from the pitch deck?
The deck supports a spoken story and needs you in the room. The memo must stand alone. For a venture, the memo is the written report that explains the deck.
✦ A Note for Global Venture I Students · Block G: Telling Your Story · Form G
Your 6-page memo is one of the five final deliverables: the pitch deck (with your MVP), the Business Model Canvas, the FISHE Capital™ × CSTO™ map, the 6-page memo and the interview report. Your memo draft goes in Form G, one week before the final presentation, together with the final BMC, FISHE × CSTO map and interview report. All five are due at the final presentation. The memo is also — honestly — the most revealing one.
The pitch deck can be polished. The BMC can be filled in. The FISHE × CSTO map can be formatted. But the memo cannot be faked. Either you understand your venture well enough to construct a complete written argument about it, or you do not. It shows.
Start with Page 2. Write down exactly who you talked to and what they told you. If that page is thin, go back and do more interviews before you try to fill in the rest. Everything in a strong memo flows from real evidence about real people. The Amazon standard is not unachievable — but it does require that you have done the actual work first.
Do this before class:
- Draft Page 2 first, from your interview report and Venture Log.
- Get one cold read and write down the gap between what you meant and what they understood.
- Check your sent folder against your 12 interviews and any guest speakers. Each one should have a thank-you email, sent within 24 hours with kasper@seabridge.space in CC (not BCC) — one from each group member who took part. Log them in Form G. (How to write them: Thank-You Letters, in Block A.)
- In your Venture Log, note one claim you removed from the memo because you could not back it with evidence, and give your final readiness self-score (KTH IRL) with the evidence link (fill in the form's "AI used for:" field too). In your Book Log, reread your Chapter 19 entry.
Pre-class check (in Form G):
- Why does a narrative memo expose weak thinking faster than slides?
- Which page of your memo is weakest right now, and what evidence would fix it?
- What did your cold reader misunderstand?
Your progress: Business model readiness to level 3 and Funding readiness: confirm 2–3 with evidence — a written case someone can evaluate without you in the room. A tested funding pitch counts later (funding readiness 5 on KTH's summary sheet: "first pitch for funding tested on relevant audience"). Form G also records your final self-score on all areas. How we measure progress
Skills you practice: Analytical thinking · leadership and social influence · mobilizing others.
Keep reading
- The Pitch — Format, Structure, and the Art of Earning the Next Conversation — the spoken version of your memo
- Why We Ask You to Do 12 Interviews — and Why Only Five Are Customers — where Page 2 comes from
- FISHE Capital™ × CSTO™ (Company Edition) — the map behind Pages 5 and 6
- What Changed — And Why You Should Care That It Did — Block H starts here
All articles in Block G · Telling Your Story
- G-01 Is This a Business?
- G-02 The Pitch
- G-03 The Art of Pitching Less
- G-04 The Amazon 6-Page Memo (you are here)
References
- Sermsuksan, K.-T. (2023). The Startup Mindset [in Thai], Chapter 19. Wish Publishing (สำนักพิมพ์วิช). English: the author's own translation, not yet published.
- Stone, M. (2015, July 28). A 2004 email from Jeff Bezos explains why PowerPoint presentations aren't allowed at Amazon. Business Insider. Syndicated copy: https://ca.finance.yahoo.com/news/2004-email-jeff-bezos-explains-182123490.html — accessed Nov 2026.
- Bezos, J. (2018, April 18). 2017 letter to shareholders. Amazon.com, Inc. https://www.aboutamazon.com/news/company-news/2017-letter-to-shareholders — accessed Nov 2026.
- Bariso, J. (2023, December 20). Jeff Bezos says this is why he banned PowerPoint at Amazon. It's a lesson in how to think. Inc. https://www.inc.com/justin-bariso/amazon-jeff-bezos-powerpoint-meetings-how-to-think.html — accessed Nov 2026.
Further reading
- Bryar, C., & Carr, B. (2021). Working backwards: Insights, stories, and secrets from inside Amazon. St. Martin's Press.
About the author: Kasper-Tanakrit Sermsuksan is the Founder of SEA Bridge and a Visiting Lecturer in Computer Engineering and Digital Technology at Chulalongkorn University's Faculty of Engineering. Learn more →
