the meeting that should have been a message

the thirty minute meeting that could have been a two line message costs more than thirty minutes, it costs the momentum of everyone who had to context switch to attend it.

calendars fill up with meetings because scheduling one feels productive and low risk in the moment, and because declining a meeting request feels socially awkward in a way that accepting one doesn't. but every meeting has a hidden cost beyond its own duration: the mental transition into and out of it, the fragmentation it creates in what would otherwise be a longer, deeper block of focused work. a day with six thirty minute meetings scattered through it produces far less real output than a day with two hours of meetings clustered together and the rest left open.

the discipline worth building here is a simple filter before scheduling anything: does this require real time, synchronous back and forth, or could it be resolved with a clear, well written message that gives the other person everything they need to respond asynchronously. most status updates, most simple approvals, most single question exchanges pass that test easily. what genuinely needs a meeting is anything with real ambiguity, real negotiation, or a relationship dimension that benefits from tone and presence that text can't carry.

the harder version of this discipline is applying it to meetings you're invited to, not just ones you're scheduling. declining or proposing an async alternative feels risky reputationally, like you might come across as unavailable or dismissive. but the people who do this well tend to frame it clearly, “happy to jump on a call if useful, but here’s my quick take in the meantime,” which usually resolves the matter without anyone needing to actually block calendar time.

the compounding effect over a year of protecting focus this aggressively is enormous, even though any single declined meeting feels small in isolation.

how many meetings on your calendar this week could have been a clear, well written message instead?