The cost of a meeting, in engineering terms

The standard argument against meetings is arithmetic: eight people, thirty minutes, four person-hours, multiply by salary.

That understates it by a large factor, and the reason is the same reason context switching is expensive for a CPU.

the fragmentation cost#

Deep engineering work requires holding a system in your head: the call graph, the invariants, the specific thing you were about to check, the four hypotheses you had narrowed to two.

Building that state takes time — call it twenty to forty minutes for nontrivial work. Losing it takes one interruption.

So a meeting at 2 p.m. does not cost thirty minutes. It costs:

• The twenty minutes before it, where you cannot start anything substantial because you will be interrupted.
• The thirty minutes of the meeting.
• The twenty to forty minutes after it, rebuilding the state you lost.

That is roughly ninety minutes for a thirty-minute meeting, per person, and it is the optimistic case.

Worse: a meeting placed in the middle of a morning does not remove ninety minutes from a four-hour block. It removes the block. Two ninety-minute fragments are not equivalent to one three-hour stretch, because the hardest work requires depth that ninety minutes cannot reach.

the schedule shapes that work#

Meeting-free days. Two full days a week with no recurring meetings. Not "try to keep them clear" — a calendar policy. This is the single highest-impact scheduling change available and it is nearly free.

Meetings at the edges. Cluster them at the start or end of the day. A day with three meetings from 9 to 11 and nothing after is dramatically more productive than one with three meetings at 10, 1, and 3.

Default to 25 and 50 minutes. Not 30 and 60. The buffer prevents the cascade where every meeting starts late and the person coming from the previous one misses the first five minutes.

Async by default for status. Standup is a meeting to exchange information that could be a written update. The argument for synchronous standup is that it surfaces blockers, which it does, and a written update with a "blocked on" field surfaces them too, in a searchable form, without costing everyone their morning.

when meetings are actually right#

They are, frequently, and the anti-meeting position overcorrects.

High-bandwidth disagreement. Two people who disagree about a design will resolve it in twenty minutes of conversation and in nine days of comment threads. Real-time is enormously better for anything with back-and-forth.

Ambiguity resolution. When nobody is sure what the problem even is, a conversation converges much faster than writing, because you can ask the clarifying question immediately.

Anything with emotional content. Feedback, conflict, bad news. Writing is the wrong medium and using it is usually avoidance.

Building relationships. Real, unmeasurable, and the reason fully-async organizations struggle in ways they cannot diagnose.

The rule: meet for things that require interaction. Write for things that require information.

the tests#

Before scheduling, three questions:

What decision will be made? If none, this is a status update. Write it.

Who must be there for that decision? The answer is usually two to four people. Everyone else can read the outcome.

What would happen if we did not have it? If the answer is "nothing," you have found a recurring meeting that outlived its purpose. Every organization has several.

the audit worth doing#

Take a recurring meeting and cancel it for a month. Not "make it optional" — cancel it.

If someone notices and asks for it back, with a reason, reinstate it. Most of the time nobody notices, which tells you what you needed to know.

This works because recurring meetings are created for a reason that expires and never re-evaluated, and the social cost of proposing cancellation is high enough that nobody does it. A trial cancellation removes the social cost.

the part managers should hear#

Your calendar is not your team's calendar. A manager's day is legitimately made of meetings — that is the job, and thirty-minute chunks are the natural unit.

An engineer's day is not, and scheduling as if it were is the single most common way well-meaning managers destroy their team's output while looking at metrics that do not show it.

Protect the blocks. It is most of what schedule-level management can do.