Meetings that earn their cost

Problem. Meetings pile up. The calendar fills with them, productivity drops, and a growing share of the team's time goes into keeping each other aligned instead of building. At some point the team notices that less is shipping, and starts debating which meetings to cut. The debate is one-sided. The cost of a meeting is concrete: minutes per attendee, dollars per hour. Every productivity newsletter has a worksheet for the math, but the case for keeping the meeting has none. People say a meeting is good for alignment, or for the team, with no number behind those words. That is why most meeting audits I have watched fade inside two quarters. The same recurring blocks come back, the same people sit in them, and nobody remembers what was supposed to change.

An audit that holds is one that measures value as carefully as cost, runs on a schedule, and defends the meetings it keeps on the half nobody is counting.

The test. A meeting earns its place when the value it delivers is greater than the cost it imposes. Both numbers can be moved.

Cost is the half that gets a formula. The published meeting-cost calculators all break it into the same three pieces:

Cost ≈ attendees × hourly rate × (direct time + prep + 23 min recovery)

The first piece is direct time on the calendar. The second is the prep work going into the meeting. The third is the least visible: a meeting in the middle of an engineer's morning breaks their focus, and it takes about twenty-three minutes on average to get back into a hard problem. A thirty-minute meeting is not a thirty-minute cost. Even a quick call is rarely cheap by the time you finish paying for it. Most writing about meeting cost gets this half right, especially the broken-focus piece.

Value is the harder half, and the one that disappears from every calculator. There is no clean formula. The two components I have learned to defend explicitly are alignment and culture. Alignment is the work of pulling everyone back to the same plan, which is what a regular meeting does as a checkpoint. The longer the project runs, the more easily a team drifts without one. Culture is the work of being in the same room together. On a remote team, that is where leadership actually shows up. Other components show up in particular meetings, like trust between teammates or mentoring when the room mixes seniority.

Run the audit on a schedule

Most of the meeting cuts I have made came from a recurring audit that fires on its own schedule, even when nothing is going wrong. Run the audit every three to six months, whichever rhythm you can actually hold.

Waiting for something to go wrong produces the wrong cuts. An incident reveals the meeting somebody complained about, but never the meeting that has quietly stopped earning its cost. A one-shot calendar purge (the kind Shopify made a headline of) gets the easy cuts once and then loses momentum, because the meetings with political defenders come back and the second purge inside the same company is always weaker than the first. A recurring audit avoids both traps because the audit fires on its own; nobody has to be angry enough to call for one.

One example. An engineering and QA team had a weekly meeting to talk through new production bugs. It came up in an audit and failed the test, because the work could be moved into a ticket flow. We killed the meeting and ran the same conversation through tickets and short written updates. The rate at which production bugs got fixed did not change. We did not need anyone to argue against the meeting. The audit was enough.

Rework before killing

Two halves of the same move. First, see whether the meeting passes the test after some rework:

• Shorten it. Sixty minutes down to thirty, thirty down to fifteen.
• Drop attendees who do not need to be there.
• Sharpen the agenda.

Fifteen-minute slots are underused. A short slot forces you to cut everything that does not matter; a sixty-minute slot lets you keep all of it. Most of the meetings I have tried to shrink, I should have tried to shrink earlier.

If rework cannot get the value above the cost, ask the next question: can the work this meeting is doing live in an artifact instead? A ticket flow. A written update circulated async. A status doc. If the answer is yes, kill the meeting and stand the artifact up in the same week so nothing rots in the gap. If the answer is no, the meeting is doing something a process cannot, and that is the value you defend.

Defend the value, fix the spectators

When someone pushes to make a kept meeting shorter or cheaper, the easy answer is to give in. Trim the duration. Drop a few people. Cut the prep. The right answer is to show the value analysis. If the slack in the meeting is what makes it work, refuse the trim.

The example I keep coming back to is a product-engineering team standup. It runs twice a week, forty-five minutes, and has run that way since covid. We have questioned the length of it ourselves, more than once, because forty-five minutes across that many people is a real cost. The answer has always been the same: the fifteen minutes beyond the textbook thirty are buying connection on a remote team, which is the whole reason the meeting exists. Trimming it would hurt the value side directly, and the cost argument alone does not earn the trim. When someone asks why we keep it that long, I show them the analysis. The defense is the math, with the value half filled in.

Inside any meeting of that size, there is a spectator problem. A junior engineer who treats the meeting as something to watch is a real cost the calculator misses, and one you can fix. Three causes worth separating:

1. They do not feel like a participant, because nobody has invited them to be one. Ask them direct questions and leave a slot in the agenda for their input.
2. They are shy because the room is large. Offer encouragement, often in private first.
3. The spectator habit is bad meeting hygiene. Give direct feedback.

The structural lever that makes any of this last is to write participation into the engineering ladder. On our SDE2 rubric, the collaboration line explicitly rates active participation in team and cross-team discussions. Once it is a measured skill, the room behaves differently, and the leader does not have to relitigate it every quarter.

Defend the focus block

Push all meetings into one window of the day, so the rest of the day belongs to the engineers writing code, who need unbroken hours to do hard work. On my team that window is three to six in the afternoon. Engineers get three to four hours of focus on either side of it, depending on whether they work better in the morning or the evening.

The block is under constant pressure:

• New joiners do not know it exists.
• The broader org does not share it.
• Urgent startup work shows up at unpredictable times and wants the next open slot.

Without a deliberate defense, the block falls apart inside a quarter.

The defense is a rule of thumb. If you treat it as untouchable, the team starts ignoring it. Every meeting has to go on the calendar, including the quick calls, because you cannot defend a block you cannot see. Every month or so, export the team's meetings and look at them. If a handful have landed outside the focus window, fine. If the drift is adding up, say so to the team. Keeping the rule visible and adjusting it on a rhythm is what keeps it alive.

Tradeoffs

Running the team mostly over written, asynchronous channels is the right default, and what we do most of the time. It also breaks down on long projects. I once tried to run a year-long initiative without any recurring meeting at all, on the theory that a senior team would coordinate itself even while everyone was juggling other priorities. The team lost the thread. People could not remember what we had done since the last quiet stretch or what was supposed to come next. We added a meeting back in as a regular checkpoint: what got done since last time, what is planned until next time, with written updates in between unless something needed a real conversation. The longer the horizon of a piece of work, the more a regular meeting earns its place.

The second tradeoff is duration. Some meetings should be longer than the shortest possible version, because the meeting's job is connection or context-setting, and the looseness in the room is what does the work.

Not every meeting can be replaced by an artifact. Some meetings clear their cost even when they are deliberately loose. The deeper failure mode in this whole discipline is letting the cost calculator do the leader's thinking for them. The audit tests the meeting; sometimes the meeting passes.