26 Jul 2026•3 min read
Meeting load is an organisational design decision that gets made by accident. Treating calendar time as a fixed budget with an owner changes what gets scheduled.
31 July 2026•3 min read
There is a specific number in every organisation that nobody owns: the total hours per week the company spends in meetings. It is the largest recurring expense that never appears in a budget review, it grows monotonically, and any individual meeting is easy to justify against a total nobody is tracking.
Three mechanisms, all rational at the individual level. Adding a recurring meeting solves an immediate coordination problem, and the cost is distributed across other people's weeks. Cancelling a meeting requires someone to assert it is not needed, which is socially expensive and offers no personal reward. And headcount growth multiplies attendees on existing meetings without anyone deciding to.
The intervention that works is embarrassingly simple: decide what share of a working week should be available for uninterrupted work, and treat the remainder as the meeting budget. Anything new must fit inside it, which means adding a meeting requires removing one. This forces the comparison that never otherwise happens.
The single largest category of recoverable time is status reporting. A written update read asynchronously conveys more information than a verbal round-robin, is searchable later, and does not require eight people to be free simultaneously. The objection is that people will not read it, which is usually true when the update is long and unstructured, and false when it is five lines with a clear headline.
A meeting is the most expensive way to distribute information and the cheapest way to make a decision. Schedule accordingly.
Deep work does not fit into thirty-minute gaps, and a calendar that is technically only half booked can still be entirely useless if the free time is fragmented. Consolidation matters more than total hours: four hours in one block is worth more than six hours in twenty-minute pieces. When defending calendar time, argue for contiguity first.
@umarrafique923
Author and writer at CandyWrite. Sharing knowledge, tutorials, and reflections on technology, design, and ideas.
Join 12,000+ readers getting our Saturday morning editorial dispatch with our top essays and reading recommendations.
26 Jul 2026•3 min read
27 Jul 2026•2 min read
29 Jul 2026•3 min read
30 Jul 2026•2 min read
Discussion (0)
Join the conversation. Sign in to leave a response or reply to comments.