The calendar is the enemy. Meetings fill the day, yet decisions do not get made in them. The same topics recur week after week because nothing was resolved last time.
People sit in meetings they have no reason to attend, half-present, doing other work. Status gets recited instead of read. And the cruelest part: the people who most need uninterrupted time to produce are the ones most fragmented by a meeting load nobody designed on purpose. It simply accreted, one standing invite at a time, until coordination became the thing that prevents work rather than enables it. This guide treats your meetings as what they are, the organization's coordination and information-flow infrastructure, and rebuilds them as a system: it audits the true load, cuts what should not exist, redesigns what remains so it produces decisions, and installs a deliberate rhythm where the right information reaches the right people through the right channel.
Plan two to three hours for the audit and redesign, then short recurring reviews. You need the authority to actually cancel, consolidate, and reshape meetings, and access to the real calendar. The true load is almost always larger than anyone's estimate.
If meetings fail specifically because leadership cannot decide or is misaligned, the meeting is exposing a leadership problem, that is leadership development. If meetings are fine but the work discussed in them stalls afterward, that is a completion problem, go to Execution Cadence and Initiative Completion. If meetings are full because priorities are unsettled and everything needs re-litigating, fix that first in Priority Clarity and Alignment.
See the true cost of your meetings before changing any of them. Inventory every recurring meeting across the team. For each, capture its purpose, frequency, duration, who attends, and, critically, its real cost: duration multiplied by the number of attendees, which converts a "quick weekly sync" into the actual person-hours it consumes. Then judge each honestly against one question: does this meeting reliably produce a decision, an alignment, or an output that could not be achieved more cheaply another way? The totaled load, and the count of meetings that fail the question, is the evidence base for everything that follows.
Open the Meeting Audit →Reclaim time by acting on the audit. This is the highest-leverage move, and the one most often skipped, because canceling a standing meeting feels socially risky. Sort every meeting into one decision: eliminate the ones that do not earn their cost and cancel them outright; consolidate meetings covering overlapping ground or people; right-size the ones worth keeping but bloated, by trimming attendees, cutting duration, or reducing frequency; and keep as is the meetings that already produce real value. Be aggressive on elimination. The reclaimed hours flow directly back into capacity and protected focus time.
Record the decisions in the Meeting Audit →A meeting that meets is not the goal; a meeting that decides, aligns, or unblocks is. Give each kept meeting an explicit design with five elements: a clear purpose stated in outcome terms, the right attendees and only them, a structured agenda with time allocations, a decision-and-action discipline where every item resolves to a decision or a named next step with an owner, and a brief written record of decisions and owners that flows to anyone affected who was not present. The governing rule is that no recurring meeting runs without a purpose and an agenda; if a given week has no agenda, the meeting is canceled for that week. That single rule ends the standing meeting that meets only because it is on the calendar.
Open the Meeting Design Template →Coordination is not a pile of meetings; it is a designed rhythm in which the right information reaches the right people at the right interval, through the right channel. First, lay out the surviving meetings as a single operating rhythm: which conversations happen daily, weekly, monthly, and quarterly, who is in each, and what each is for, so the cadence covers what you need to coordinate without overlap or gaps. Second, draw the line between synchronous and asynchronous: define what genuinely requires a live meeting versus what should move to a written channel, and set channel norms so status stops consuming live meeting time.
Open the Meeting Operating Rhythm Map → Open the Sync and Async Channel Protocol →Meetings accrete by default, a new standing invite here, an expanded attendee list there, until the load creeps back to where it started. Set a recurring review, commonly quarterly, to re-run the audit on a lighter scale: total the current load, check whether new meetings have crept in without earning their place, confirm that kept meetings still produce decisions and still run with agendas, and verify the sync-versus-async lines are holding. Watch the warning signs, meetings without agendas creeping back, attendee lists quietly expanding, status creeping back into live time, and "let's just add a quick weekly" becoming the default answer to any coordination gap. Re-cut as needed.
Re-run the load assessment in the Meeting Audit →The total meeting load is lower and the reclaimed hours are visible and going to real work. Every recurring meeting has a purpose and an agenda and runs only when it has one, meetings end with decisions and owned next steps, status has moved to written channels off live time, and people can describe the operating rhythm (Communication: Level 2 toward Level 3 and 4).
With coordination working, the next question is whether the work the meetings coordinate actually reaches done. Move to Execution Cadence and Initiative Completion, or protect the reclaimed time as individual focus. Execution Cadence and Initiative Completion →