The Meeting That Should Have Been a Document
Any meeting whose purpose is to update, inform, or share status should be a document. Keep the room for judgment and live debate; move everything else to the page. With Claude drafting that page from your bullets or a voice memo in a few minutes, the "writing it up is too much work" excuse is gone. So is your reason for holding the meeting.
There's almost certainly more than one meeting on your calendar right now that fits. The weekly status call where everyone reads off what could have been a dashboard. The "discussion" that's one person broadcasting while eight people half-listen. The decision meeting where the call actually got made three days earlier on a side thread, and this is the ceremony.
Senior people lose a lot of the week to this. Common estimates put executives north of 20 hours a week in meetings, and most will quietly admit a big chunk is unnecessary. Call it 7 or 8 hours, almost a full workday, spent in a room for information you could have read standing up.
If you're 45 to 62, this hurts more than it did at 30. Your limiting factor isn't ambition or even capital. It's uninterrupted time where your experience actually changes the outcome. Every recurring status session you sit through is an hour you didn't spend on the two or three decisions only you're qualified to make. The meeting tax is regressive: it hits your most experienced people hardest.
When does a meeting actually earn its hour?
A meeting earns its slot when it needs the room, when what you say next depends on how someone just reacted. Three situations clear that bar. Working through real conflict, where tone and the live read matter. Making a decision where the arguing in the room is what produces the alignment. Doing creative or strategic work that builds on what someone said ten seconds ago.
That's most of the honest list. Nearly everything else is a candidate for a document. Status update? Document. Information-sharing where you can already guess 90% of the questions? Document plus an async Q&A window. Announcing a decision that's already made? Document with a short clarification window. The Tuesday check-in that survives purely because it has always been there? Probably a document. Possibly nothing at all.
One test runs in a single breath. I call it the One-Sentence-Purpose test: say the meeting's purpose out loud in one sentence. If that sentence has to contain "update," "inform," "share," or "align on," it's a document by default. A COO at a mid-size professional services firm ran that rule for a quarter and cleared about six hours a week off her calendar. Not through a clever framework. By applying the test with no exceptions.
Why do we keep scheduling meetings we don't need?
Most experienced people already know half their meetings are dead weight, yet the invites keep going out. Part of it is practical, part of it is perception. Writing a clean document feels slower than calling a meeting. A meeting lets you think out loud and offload the synthesis onto the room; a document makes you finish the thought before anyone sees it.
And then there's the part nobody says at the offsite: a packed calendar looks like proof you matter. Being in meetings signals importance. Writing a document is solitary and quiet, even when it saves ten people an hour each.
Claude flattens the practical barriers. A briefing that would take a senior leader 90 minutes to write well can be drafted in minutes from a handful of bullets or a voice memo. The time math that used to favor the easy meeting now tilts toward the page. The social-signaling reason is real, and I'd warn you against pretending it isn't. The fix isn't to cling to hollow meetings. It's to spend that social budget on the sessions that are genuinely human and stop dressing one-way broadcasts up as "collaboration."
The workflow: turning a meeting into a document with Claude
The mechanics are dull, which is the point. Before you book anything, write down, in bullets, what you'd cover. Not what you'd "discuss." What you want people to know or decide. Those bullets are your prompt.
Hand them to Claude with something like: "Turn these bullets into a structured briefing I can send instead of holding a meeting. Include a one-paragraph situation summary, the key facts, exactly what I need from each person, and a response deadline. Keep it under one page." What comes back is a first draft, not a final one. You spend five to ten minutes fixing facts and putting it in your voice, Claude doesn't know which number is sensitive or which name to soften. Then you send it and wait for replies.
Here's a pattern I've watched play out across a few operations leaders (a composite, to keep them anonymous). A VP of operations replaced her 75-minute Monday production review with a two-page brief sent Sunday evening. The team reads it before the week starts. Questions land by 10am Monday. She holds a 15-minute call only for what's still open. Net: roughly an hour a week back, for her and for every person who used to sit in that room. Multiply by a team of ten and you're recovering close to a workday a week across the group.
Three document formats, and when to reach for each
Not every document does the same job. Build three templates once and you'll stop reinventing the format every time you're in a hurry.
| Format | Use it when | Must contain |
|---|---|---|
| Briefing | You need people informed, not deciding | What's happening, why it matters, what (if anything) you need, from whom, by when |
| Decision memo | You need a sign-off or a choice | The decision requested, options weighed, your recommendation and reasoning, the ask: approve / reject / one clarifying question |
| Pre-read | A meeting genuinely has to happen, but could run 20 minutes instead of 60 | Context, agenda, the prep each person owes, and the single decision on the table |
Save each as a Claude Project or a saved prompt with the structure baked in. After that, producing one is a 10-minute job, not a 90-minute one, and the format stops drifting every time someone's slammed.
What happens to the meetings that survive
Clear the dead meetings and the ones left over change character. The people in the room actually need to be there. The agenda reflects something that genuinely requires a live exchange. The meetings run shorter, because the information dump already happened on paper.
A general counsel who rebuilt her cadence this way said it was the first time in years she enjoyed walking into a meeting. That's not sentiment; it's what's left when you reserve the room for what rooms are good at. She added a sharper point: her team writes better now. When you have to turn your thinking into something a person will actually read, you can't hide behind a vague "let's discuss." Documents force precision. Meetings forgive its absence. The discipline leaks into the team's thinking, not just its calendar.
How do I roll this out without people feeling shut out?
Some people read a document where a meeting used to be as cold. "Why didn't they just call me?" Frame it honestly: you're not replacing the relationship, you're replacing a format. You're still reachable for a real conversation when one's warranted. You're just not assembling twelve people to say something they could read in four minutes.
Start with your own meetings. Don't issue a memo banning meetings; that's its own kind of theater. Change the ones you control, let people feel the relief of a clean brief, and let demand pull the practice across the team. I changed my mind on this, for what it's worth. I used to push the policy top-down and it bred resentment every time. Modeling it quietly works; mandating it doesn't.
Frequently asked questions
What about people who genuinely prefer meetings?
Acknowledge it and don't over-argue. Send a brief that's complete and clear, and the meeting usually becomes optional. Most people, given the choice, won't schedule it.
Doesn't this kill the relationship-building meetings?
No, keep those. This is about information-transfer and status, not the lunch or the check-in that exists to keep a relationship warm. Protect those by clearing the junk around them.
How long should a replacement brief be?
One to two pages. Complete enough to stand alone, short enough that a busy person finishes it. The brevity is doing real work; it's a feature, not a constraint.
Can Claude help with the replies, not just the brief?
Yes. When a briefing comes back with a dozen threaded responses, paste them into Claude and ask it to surface the open decisions and draft your replies. That's where the loop actually closes.
Pick one recurring meeting this week, the one you'd skip if you could. Before the next instance, write the bullets, run them through Claude, and send the brief instead. Watch what comes back. If the meeting turns out to have been load-bearing, you'll know within a week and you can put it back. My bet is you won't.