Join our Skool CommunityOn 9 June 2004, at 6:02 p.m., Jeff Bezos sent a two-sentence email to Amazon’s senior leadership team. The subject line read: “No powerpoint presentations from now on at steam.”
That email changed how one of the world’s most valuable companies operates. Years later, Bezos would call it “probably the smartest thing we ever did.”
What makes this remarkable is not the decision itself. Plenty of executives have quirky meeting rules. What makes it remarkable is what replaced PowerPoint — and why. Bezos didn’t just change the format of Amazon’s meetings. He changed how the company thinks.
The PowerPoint Problem
Bezos’s objection to PowerPoint was not aesthetic. It was intellectual. He believed that slide-based presentations fundamentally degrade the quality of thinking in an organisation.
“Powerpoint-style presentations somehow give permission to gloss over ideas, flatten out any sense of relative importance, and ignore the interconnectedness of ideas.”
The problem, as Bezos saw it, is structural. Bullet points let you list things without explaining how they relate to each other. A slide deck can look polished and professional while containing almost no real analysis. The presenter’s charisma and the designer’s skill can carry ideas that, if written out in full sentences, would fall apart under scrutiny.
This was not just Bezos’s intuition. Yale professor Edward Tufte published The Cognitive Style of PowerPoint in 2003, a year before Bezos sent his email. Tufte’s research demonstrated that slide presentations reduce complex subjects to oversimplified fragments, stripping away the context and nuance that decision-makers need. Bezos’s policy aligned almost exactly with Tufte’s findings.
The deeper issue is what Bezos described as “permission to gloss.” When you put six bullet points on a slide, no one asks whether those six things are actually the right six things, whether they are in the right order, or whether the relationships between them are accurately represented. The format does not demand rigour. And without a format that demands rigour, you get fuzzy thinking dressed up in professional graphics.
The Six-Page Memo
PowerPoint was replaced with something far more demanding: a “narratively structured six-page memo.” Not slides. Not bullet points. Full prose with verbs, complete sentences, topic sentences, and paragraphs that flow logically from one to the next.
“The reason writing a good 4 page memo is harder than ‘writing’ a 20 page powerpoint is because the narrative structure of a good memo forces better thought and better understanding of what’s more important than what, and how things are related.”
The key word is “forces.” Writing in full prose is not just a different format — it is a different cognitive process. When you write a sentence, you have to decide what the subject is, what the verb is, and what the object is. When you write a paragraph, you have to decide what the main point is and how the supporting points relate to it. When you write six pages of connected prose, you have to build an argument that holds together from beginning to end.
This is hard. Bezos knows it is hard. He has said that “the great memos are written and rewritten, shared with colleagues who are asked to improve the work, set aside for a couple of days, and then edited again with a fresh mind.” A great memo takes a week or more to produce.
That investment of time is not wasted. It is front-loaded thinking. The memo does the analytical work before the meeting begins, so the meeting itself can focus on what matters: discussion, debate, and decision-making.
The Study Hall
Here is the part that surprises most people. The first 30 minutes of every Amazon meeting are spent in complete silence.
When attendees arrive, copies of the six-page memo are distributed. Everyone sits together and reads the entire document from start to finish, taking notes in the margins. Bezos calls this the “study hall.” Only after every person has finished reading does the conversation begin.
“We do a study hall for 30 minutes, sitting silently together in the meeting to read... We take notes in the margins, and then we discuss.”
Why read together? The practical reason is honesty. Bezos explained that “people often don’t have time to read the memos in advance. They come to the meeting having only skimmed the memo or not read it at all.” By reading together, everyone starts from the same baseline. No one is bluffing. No one is nodding along without understanding. Every person in the room has genuinely engaged with the material before offering an opinion.
The result is a dramatically different quality of conversation. Instead of a presenter talking at a room, you have a room full of people who have all absorbed the same information and are ready to challenge, refine, or build on it. The memo creates shared context. The study hall ensures that context is real.
The Two-Pizza Rule
Bezos famously mandated that no meeting — and no team — should be so large that two pizzas cannot feed the entire group. In practice, this means five to eight people, maximum.
The two-pizza rule is not about pizza. It is about the mathematics of communication. In a group of five, there are ten possible one-to-one communication channels. In a group of ten, there are forty-five. In a group of twenty, there are one hundred and ninety. As group size increases, coordination overhead rises exponentially while individual contribution drops.
Small teams have advantages that large teams cannot replicate:
- Ownership: In a small team, every person’s contribution is visible. There is nowhere to hide, and no one wants to. People take ownership because they can see the direct impact of their work.
- Speed: Fewer people means fewer approval layers, fewer status meetings, and fewer email threads. Decisions happen faster because there are fewer people who need to agree.
- Accountability: When something goes wrong in a five-person team, it is clear who was responsible. When something goes wrong in a twenty-person team, responsibility diffuses until no one is accountable.
Amazon’s most important innovations came from two-pizza teams. Amazon Marketplace, early ecommerce refinements, and Amazon Web Services all started as small, autonomous teams given ownership over a specific problem. AWS, now a business generating over $80 billion in annual revenue, began as a small team working on internal infrastructure that later became a product.
Disagree and Commit
Great meetings produce decisions. But decisions in groups are hard because people disagree. Most organisations handle this badly: either they seek consensus (which takes forever and produces bland compromise) or they let the loudest voice win (which demoralises everyone else).
Bezos formalized a different approach, which became one of Amazon’s 16 Leadership Principles: “Have Backbone; Disagree and Commit.”
“If you have conviction on a particular direction even though there’s no consensus, it’s helpful to say, ‘Look, I know we disagree on this but will you gamble with me on it? Disagree and commit?’”
The principle works in two directions. First, it gives people permission to voice genuine disagreement. Bezos wants vigorous debate. He wants people to push back, challenge assumptions, and argue for their position. Silence in a meeting is not agreement — it is a failure of courage.
Second, once a decision is made, everyone commits fully. You don’t undermine the decision in hallway conversations. You don’t drag your feet during execution. You gave your input, the decision went a different way, and now you execute as if it were your own idea.
This eliminates two common problems: groupthink (where people stay quiet to avoid conflict) and analysis paralysis (where disagreement prevents any decision from being made). The result is faster, better decisions executed with full organisational commitment.
Type 1 vs. Type 2 Decisions
Bezos adds an important nuance: not all decisions deserve the same process. He distinguishes between “Type 1” decisions (irreversible, high-stakes — take your time, gather data, debate thoroughly) and “Type 2” decisions (reversible, lower-stakes — make a call and move).
Most decisions are Type 2. And most organisations treat them like Type 1, burying reversible choices under layers of review, approval, and committee deliberation. This is how large companies become slow. Not because the decisions are hard, but because they over-process easy ones.
What Entrepreneurs Can Learn
You do not need Amazon’s scale to benefit from these practices. In fact, they may be even more valuable for smaller teams, where every meeting matters more and wasted time costs proportionally more.
- Replace slides with writing. Before your next strategy discussion, write a one-page document instead of building a deck. Force yourself to explain your thinking in complete sentences. You will discover gaps in your logic that bullet points would have hidden.
- Read together before you discuss. Even if the document is just one page, take five minutes to read it silently at the start of the meeting. You will be surprised how much better the conversation is when everyone has genuinely engaged with the material.
- Keep meetings small. If you cannot feed the group with two pizzas, the meeting is too big. Identify who actually needs to be in the room to make the decision and excuse everyone else. They will thank you.
- Encourage dissent, then commit. Create a culture where people are expected to voice disagreement. But once the decision is made, move forward together. The worst outcome is a decision that nobody disagrees with because nobody cared enough to argue.
- Sort your decisions. Ask yourself: is this reversible? If yes, make the call quickly. Save your deliberation for the decisions that truly cannot be undone.
Most founders run meetings the way they have seen meetings run: someone presents slides, people half-listen, discussion meanders, nothing gets decided. Bezos redesigned meetings from first principles. He asked what a meeting is actually for — making good decisions with shared context — and built a system to produce that outcome.
Start with one change. Write a memo instead of building a deck. Read it together. Then discuss. You will be surprised how much better the conversation gets.
