Cut planning meetings, keep 1:1s: trim your calendar

Your calendar is full, but the recurring planning sync is the one to trim first. In a field study of software practitioners, ad-hoc meetings were rated most useful with a mean of 4.11, planning meetings most disruptive with a mean of 3.38, and one-on-ones least disruptive with a mean of 1.86. The invite that should stay is the one-on-one that keeps the team aligned. The fix is a triage pass: count the hours, label the debt, and protect the conversation that actually carries the work.

A mixed-methods study of software practitioners gives the map. Its first phase collected survey data from 55 software practitioners. Its second phase was a two-week field study that produced 135 post-meeting ratings and 40 end-of-day reports. In the baseline survey, 61.8% of respondents reported at least moderate disruption to flow. In the same survey, 76.4% of respondents reported lower productivity on days with many meetings.

Use that ranking to compress the planning invite that taxes focus, defend the one-on-one that sustains the team, and give ad-hoc asks a place that does not eat the whole day.

Compress the planning invite that taxes focus

Start with the recurring planning meeting. A status-only meeting can be canceled and replaced with a written update. A decision meeting stays, but the decision must be forced into the agenda. Done means a short invite with a decision, an owner, a clear date, and a hard stop. The agenda names the choice, the deadline, and the information needed before the call. When the team cannot state the decision, the meeting does not happen.

Shorten standing planning syncs by moving background to a shared doc. Keep only the questions that need a live answer. The meeting becomes a decision checkpoint, not a status loop. Review the invite regularly. A changed decision owner signals drift. A short agenda is easier to defend than a long default.

Protect the one-on-one that sustains the team

Do not cut the one-on-one to save time. It is the cheapest recurring conversation you have. It carries the issues that never reach a planning meeting because they are too small to raise and too large to ignore. Keep the cadence. Ask the direct report to set the agenda. When they cannot, use the time to ask what is slowing them down. A protected one-on-one has a clear purpose, a private channel for notes, and no default slot that drifts into a project review. A quiet direct report gets one question: what would make the next one useful.

The easy mistake is to protect the one-on-one as a favor and let it become another planning meeting. A status list at the start is a stop signal. Ask for a decision or blocker that needs your help.

Give ad-hoc asks a named slot

Ad-hoc asks are useful when they are small and time-boxed. Do not accept every interruption; stop treating quick asks as open-ended requests. Create a named slot, such as a short block called “quick asks.” Put it on your calendar and tell the team that small questions, approvals, and small decisions go there. A working slot has a simple rule: small asks go there, and decisions get a planning invite. The slot is for small asks, not new projects, and it should be visible, not hidden behind a busy calendar.

Cancel the rest gracefully. Say the meeting no longer produces a decision, name the replacement, and give the owner a path. I’m canceling the recurring planning sync. We’ll post decisions in the shared doc, and I’ll take quick asks in the named slot. Larger asks need a written summary and a decision owner before anything gets scheduled. That keeps the slot from becoming a standing meeting.