Cut Recurring Meetings Without Becoming Difficult

Your calendar opens with a status sync, a planning check-in, a cross-team review, and a retro. Six recurring meetings a week is a full workday gone before the first deep task starts. A half-hour sync five days a week is two hours; eight such syncs make the calendar the product.

Your calendar is full of coordination roles

Most standing invites were created as coordination roles, and nobody has asked whether the role still earns its time. A recurring meeting is a small job description: it has a cadence, an audience, and an expected output. When the output is only to align people, the meeting is doing coordination work.

Uber announced a global restructuring that cut about 3,300 roles, or 10 percent of its worldwide staff. The same plan lowered the manager count by 20 percent, with some managers reassigned as individual contributors. It also trimmed the workforce at least seven levels below the CEO by 20 percent and cut micro-teams by almost half.

Uber CEO Dara Khosrowshahi cited excessive employee time spent on coordination work, rather than creating, launching, or supporting customers, as a reason. Uber expected the restructuring to improve accountability, speed decisions, and increase time spent creating products rather than coordinating. The invite must justify its hours.

The hardest invites are the ones that feel like leadership: a team sync, a direct check-in, and a planning review. The test still applies.

The coordination-role test is owner, output, and alignment

Run the coordination-role test on every standing invite that repeats weekly, biweekly, or monthly. Finish with a short list that shows title, owner, cadence, and expected output. Include the meetings you inherited, the ones you host, and the ones you merely attend.

• Name a single owner for each invite. You are done when a person can say what decision or artifact the meeting is supposed to produce. When the owner cannot name it, the invite is a coordination role waiting to be removed.
• Write the output in a single line. A clear output names a decision, a document, a shipped item, a risk cleared, or a customer problem solved. Flag the line when it says alignment, status, or check-in. Those words describe the process, not the product.
• Ask whether the only output is alignment. Mark each invite with a yes or no. A yes means cancel, merge, or async. A no means keep it only when the owner can defend the cadence and the output.

Cancel gracefully by restoring ownership

Choose the smallest replacement that carries the same decision: a shared document, a ticket, a thread, or a short sync reserved for exceptions. It must have a deadline and a place where the answer is visible.

Async works when the output is a decision, a status, or a question. It fails when the output is trust, conflict, or a decision that needs live debate.

Make it about the invite, not your preference. Do not say you are too busy. Say the invite has no owner or output, and you are moving it to a channel where the answer can be seen.

“This recurring invite has no clear output. Move it to an async document with a decision deadline. If a live sync is needed, a new invite will include an agenda and owner.”

Cancel, merge, or move the invite in the same message. Put overlapping invites under a single owner, and move status updates to a written channel.

Protect the hours you just bought back

Block the recovered time as protected work time. A real block has a title that says what you will produce, not what you will avoid. Decline any new invite that lands in that block with the same test: owner, output, and alignment.

Review the list monthly. Keep it short and focused on the invites that survived. Cancel any meeting that has run through a full cycle without a visible output. The next review should be shorter than the last.