A new executive walks into a meeting at Amazon and waits for someone to start presenting. Nobody does. Everyone gets six pages of text instead, and for about half an hour the room is silent. People read. They write in the margins. Only then does anyone speak.
Jeff Bezos calls it study hall. New people, he has said, are “a little taken aback.”
Thirty minutes of silence is an odd use of a room full of senior people. If the point were only to share information, a deck would do it faster. The reason for the silence lies less with the readers than with whoever wrote those six pages, and the week or more that a good one takes, by Bezos’s estimate.
The rule began with an email. On June 9, 2004, replying in a thread titled “No powerpoint presentations from now on at steam,” Bezos laid out why. Bullet points typed into Word, he wrote, would be “just as bad as powerpoint.” And a good four-page memo is harder to write than a 20-page deck.
He meant that as a recommendation.
Four pages against twenty
Bezos’s email said what the difficulty buys. The structure of a narrative, he wrote, “forces better thought” and a better understanding of what matters more than what, and how things are related. Slides, by contrast, let people gloss over ideas and “flatten out any sense of relative importance.”
A slide deck is like a list of ingredients. Flour, eggs, butter, an oven at 200 degrees: every item can be correct, and you still don’t know whether the cake will rise. A memo has to be the recipe. The order and the amounts are written down, so anyone reading can see the step that doesn’t work.
Nearly twenty years later, Bezos put it more bluntly to Lex Fridman: “you can hide a lot of sloppy thinking behind bullet points.” PowerPoint, he said, is “easy for the author and hard for the audience,” and a memo is the opposite. In his 2017 letter to shareholders he wrote that a great six-pager probably takes a week or more, and that weak ones often come from authors who thought they could do it in a day or two.
Slides that hide things have their own entry in an accident report. While the shuttle Columbia was still in orbit in 2003, engineers briefed NASA managers on a foam strike to its wing in slides, one of which put its most worrying estimate at the bottom under a reassuring title, and the investigation board later called NASA’s “endemic use of PowerPoint briefing slides instead of technical papers” an illustration of its problems with technical communication.
The silent reading completes the bargain. Bezos would rather people read ahead, he said, but they don’t have time and end up bluffing. So the reading moved into the meeting.
Write the argument in full sentences. Let the room read it in silence before anyone talks.
One page for the partners
Say the office manager of a dental clinic wants to replace reminder phone calls with text messages, and the partners will decide at next month’s meeting. Her first draft is four slides: no-shows at 11%, six staff hours a week spent calling, texts at $40 a month, a chart from the software vendor.
Then she tries to write it as a page. Halfway down she reaches the sentence that has to join the slides together: texts will cut no-shows because… and stops. She doesn’t know how many of last month’s no-shows had been reached by phone and missed the appointment anyway. On the slides, the numbers could sit next to each other without anyone asking. In a paragraph, she has to write “because.”
She pulls the call log before the meeting instead of after it. The partners spend the first five minutes reading her page, and when the talking starts, nobody has to ask the question that stopped her.
Not every meeting needs this. Bezos told Fridman that Amazon’s regular business reviews, which go over the same metrics every time, can start and end on time. The memo is for the hard question, where the connections between the facts are the thing being decided.
A reader who can’t raise a hand
Anthropic’s guide to its coding agent, Claude Code, as of October 2026, suggests a version of the same trade. For larger features, it says, have Claude interview you and write a spec, then start a fresh session to build from it. The most useful specs, the guide says, are self-contained: they name the files involved, say what is out of scope, and end with a test that proves the feature works. It adds that time spent making the spec precise pays off more than time spent watching it being built. That is Bezos’s bargain again, hard for the author so it can be easy for the reader.
The match is not exact. Anthropic’s prompting guide recommends numbered lists or bullet points when the order or completeness of steps matters. Bezos objected to bullets for arguments, where the links between points are the content.
The same guide offers a test that fits both. Show your prompt to a colleague with minimal context on the task and ask them to follow it. Then watch where they stop and look up.
