The starting position is unusually blunt: "Meetings are a necessary evil. But only a tiny part of meetings are essential — the rest actually is evil." The test for essential is whether it must happen synchronously, and the answer for most meeting content is no. ### **What I'm thinking about** 1. **Only three things genuinely need a room** – **Personal connection**, five minutes, thirty seconds per person. **Issues**, because hearing someone describe the problem out loud reveals which emotion they are in, and that changes how much weight their proposed solution deserves. **Critical feedback**, so that if it lands badly you can see it happen and respond immediately. 2. **Everything else reads faster than it listens** – Updates, status, metrics, action review. Reading is roughly five times faster at transferring facts and lets each person absorb at their own speed. 3. **Written prep gives quiet people a voice** – The under-appreciated benefit. Verbal-only meetings systematically over-weight whoever is most comfortable interrupting, which correlates with confidence rather than correctness. 4. **The hierarchy is both, not either** – "Writing is a faster download of fact-based information. But to understand the nuance — context, emotion — I need to hear it spoken. The ultimate communication is both written and verbal." Write to clarify thinking, then present briefly to convey nuance. 5. **There are three levels and you climb them** – **Level 1**: write for fifteen minutes in the meeting, read for fifteen, then discuss. **Level 2**: write beforehand, read and comment in the first fifteen minutes. **Level 3**: write 24 hours ahead, everyone pre-reads and pre-comments, meeting starts at the discussion. Most teams settle at Level 2 — including Amazon — and that is explicitly fine. ### **So what?** The standard objection is that preparation is expensive. The answer given is that participants' ability to absorb the material rises about fivefold, making the synchronous portion shorter and better. A team meeting that takes three hours verbally can take thirty minutes and produce better decisions. For distributed teams there's a further extension: pair each written issue with a sub-two-minute video of the author describing it. Content and nuance both travel asynchronously, and many decisions can then be made without meeting at all. Related: [[Issue, Proposed Solution]] [[The Loudest Voice in the Room]] [[Meetings]] [[Bias to Action Is a Two-Minute Rule]] [[Executive Operating System MOC]]