The Meeting That Shouldn't Have Been an Email (or a Meeting)

At some point in the last five years, someone decided that the ideal working day involves attending eight video calls, sending forty-three Slack messages, and at some point, somewhere in the middle of it, doing some actual work. Nobody voted for this. It just sort of happened.
Nobody voted for eight video calls a day. It just sort of happened.

The companies that have figured this out tend to share a few habits. They have clear policies about what warrants a meeting and what doesn't. They write things down more than they talk about them — asynchronous communication gets a genuine investment, not just a passing mention in a company values document. And they protect blocks of uninterrupted time with an almost religious fervour, because they've noticed that the deep work, the
None of this is revolutionary. Researchers who study productivity have been saying versions of it for years. The hard part isn't knowing it. It's doing it when every piece of collaboration software in existence is optimised to make booking another call feel like the natural next step.
A useful test, borrowed from teams who've got this right: before scheduling anything, ask whether the outcome could be achieved with a well-written message instead. Not a wall of text — a clear, specific message with context and a question. More often than not, the answer comes back faster than the meeting would have started. Worth a try, next time you reach for the calendar.
Features















