The first five principles make meetings worth having. This one asks whether the most common meeting needs to exist at all.
The first five principles make your meetings worth having. This one asks whether the most common meeting you hold needs to exist at all.
Think about the last time your team spent thirty minutes on a read-out. Someone shared their screen. A deck appeared. Numbers were announced. People nodded. The presenter felt heard. And everyone in that room — including the presenter — could have absorbed the same information in four minutes, alone, reading at their own pace.
The read-out is the most expensive form of information delivery ever invented. It forces every person in the room to receive the same update at exactly the same speed — the presenter's speed — regardless of how much of it they already know, how fast they can process, or whether any of it is relevant to them at all. It consumes focused, collective time to transmit what is fundamentally a one-directional signal.
Status updates are not decisions. They do not require a room. They require a document, sent in advance, read at individual pace, with questions submitted in writing. The meeting — if it happens at all — handles only the questions, not the content.
"Every read-out meeting assumes people can't read. Write the update. Send the document. Use the room for the one thing writing can't do: decide."
What a read-out actually costs
The hidden cost is not the meeting time. It is the attention it replaces. When eight people spend forty minutes in a status read-out, that is not one hour lost — it is five-and-a-half hours of focused work evaporated across the team. Multiplied across weekly standups, quarterly business reviews, and project check-ins, a status-update culture can easily consume a third of an organization's most expensive resource: the deep, undivided concentration of capable people.
The document eliminates this tax. It lets each person read at their own pace, skip what they already know, and spend their focused attention only on the gaps that matter to them. The writer spends more time crafting — and that is a feature, not a bug. A person who must write their update clearly will discover, while writing it, exactly what is and is not important. The discipline of writing is the discipline of thinking.
In practice — the shift from meeting to document
Each team member shares what they worked on, what's blocked, and what's next
A shared living document — each person posts their three-line update before 9am Monday. Anyone can read, comment, or flag blockers in writing. No meeting required.
Leadership presents quarterly results to the senior team via a 40-slide deck read aloud
A two-page written summary distributed 48 hours in advance. The thirty-minute meeting exists only to address questions submitted in writing beforehand — not to present information everyone can read.
Team leads share progress against milestones in a recurring sixty-minute meeting
A live project doc shows current status against milestones. A meeting is called only when a milestone is at risk and a decision is required — not to report that things are on track.
Leadership reads company metrics, announcements, and team highlights to the full organization
A monthly company memo covers all updates in writing. An optional, recorded AMA session lets people ask questions — but attending is a choice, not an obligation.
The four components of a proper status document
The shift from read-out to document only works if the document is actually useful. Bullet lists dumped into Slack are not documents — they are read-outs in text form. A proper status document has structure, brevity, and a clear ask.
The TL;DR
Three sentences maximum. What is the overall state? What changed since last time? What does the reader need to know right now? If this is all they read, they should be informed.
Key Updates
Five bullets or fewer. Progress, blockers, and surprises only — not a comprehensive account of everything that happened. If it didn't change anything, it doesn't belong here.
Decisions Needed
An explicit list of any decisions required from the reader — with a named owner, the options under consideration, and the consequence of not deciding. This is the only part that might generate a meeting.
Response Deadline
A clear date by which any input or questions should be submitted. Silence past this deadline means no objection. Without a deadline, async documents generate the same drag as meetings without end times.
When a status meeting is actually justified
There are narrow circumstances where a live status conversation earns its time. They are rarer than most organizations assume — but they exist.
A status discussion belongs in a room only when:
Notice what is not on this list: "people prefer hearing it in person," "it's easier to ask questions live," "we've always done a check-in on Fridays." Comfort and habit are not justifications. They are the reason Chaos persists.
"The test is not whether a meeting is convenient. It is whether the outcome requires presence that writing cannot provide."
Framework tool
The Read-Out Rewriter
Describe the update you were going to present in a meeting. The tool converts it into a written brief — ready to send instead of calling a room.