Meeting cap
A practice that sets in advance the maximum number / maximum hours of meetings allowed per day or per week to protect focus time.
A meeting cap is a practice of setting in advance the maximum number (or maximum hours) of meetings allowed per day or per week. It is a self-management technique for protecting individual focus time, and at the same time, introducing it at the organizational level can structurally correct a culture of meeting overload. A widely known example is Shopify, which in 2023 deleted recurring meetings across the company at once and introduced “no-meeting Wednesdays,” and was reported to have greatly reduced meeting time.
How to decide the cap
There is no industry standard for the right cap value; it is something decided by organization and role. There are two axes for deciding it. The first is role: individual contributors whose work is mainly building / producing should have a lower cap, because continuous focus time links directly to results, while managers / executives, whose work centers on coordination and decision-making, can set it higher. The second is measurement: first measure your current weekly meeting hours for 2 weeks, set an initial cap 20-30% below that, and adjust while running it. Aiming for the ideal value from the start tends to turn it into an empty formality because of the gap with reality.
Examples from companies that adopted it
Shopify’s “meeting cost calculator” (2023)
- Deleted more than 12,000 recurring meetings with 3 or more participants across the company at once
- Made Wednesday a day with no meetings and limited large meetings of more than 50 people to Thursdays only
- Automatically displays “Cost of this meeting: $X” when sending a meeting invitation
- The deleted meetings were reported to amount to a total of 322,000 hours (multiple reports in 2023)
Implementing it with tools
There are also scheduling support tools that automatically block open slots on days when the limit has been reached. Even with a calendar alone, you can set up a pseudo cap by blocking focus time first. More important than the mechanism is whether you can actually stick to the practice of “pushing requests beyond the limit to the next day or later,” and that is a matter not of tools but of agreement between the person and their team.