Cut Calendar Debt: Make Empty the Default, Keep One Bottleneck

Your calendar is full of recurring invites and ad-hoc pings. Calendar debt is the interest you pay on every invite you accepted before thinking. Atlassian's 2024 survey showed that nearly three out of four meetings do not spread information effectively, and 77% of respondents said meetings lead to more meetings. For a manager, the hard part is the social cost of saying no without sounding difficult. The fix is two moves: publish a default no on new invites, and hold one recurring bottleneck huddle where the team brings its single biggest blocker.

Make empty the default

Ali Ghodsi, CEO of Databricks, treats an empty calendar as the starting point, allowing it to fill only partially so free blocks remain for his main work. That is the move managers need. You do not start by asking what you can remove. You start by assuming nothing belongs there until it earns a place. An empty calendar is a rule that protects the hours where the actual work happens.

Give interruptions one recurring slot

Ghodsi holds 8 a.m. meetings with his team on Mondays, Wednesdays, and Fridays to identify the company's biggest bottleneck. He focuses on the issue he believes could deliver a 10x outcome for Databricks. His management approach is to find the single biggest bottleneck in Databricks and give it disproportionate attention for two or three years. The days are not the important part. A recurring slot gives scattered asks a fixed place, so a manager can say no to the ping and yes to the blocker.

The two moves are default no and one bottleneck huddle

• Publish a default no on new invites. Your calendar should not be a default yes. When a new recurring invite arrives, the answer is no unless it has a named owner, a clear output, and a reason it cannot be handled in writing. Reply that you can’t take it on now, ask for the decision you need, and offer the bottleneck huddle if it must be live.
• Protect the empty blocks. The mistake is making empty the default and then filling it with ad-hoc meetings that never get reviewed. That moves the debt from recurring invites to ad-hoc pings. The result is unbroken focus blocks that no one can book. A meeting that must happen fits inside the bottleneck slot or becomes an ad-hoc meeting with a clear output.
• Hold a recurring bottleneck huddle. The team brings its single biggest blocker. No status updates, no project-by-project tour, no open brainstorm. The agenda is short: a blocker, an owner, a decision or next step. Keep the huddle short enough that the team can bring one blocker without preparing a status report. Small blockers get a written answer. Large blockers get the manager’s attention and a clear next move.
• Cancel old meetings with a replacement, not an apology. Say you are cutting recurring meetings to make room for the work that needs them. A meeting that needs a live conversation goes to the bottleneck huddle or asks for the decision you need. Put the replacement in the calendar, not just in the message. The calendar should show fewer recurring blocks and a short list of meetings that actually earn their time.

For recurring invites nobody reviews, ask each organizer to confirm the meeting still has an owner, an output, and a reason to be live. If they cannot answer, cancel it and offer the bottleneck huddle or a written brief. Then keep the focus blocks empty: a quick chat becomes a written brief or a blocker in the huddle, and only real blockers get a decision.