Meeting cadence optimisation

Meeting cadence optimisation is the practice of measuring and adjusting how often recurring meetings happen so that each one earns the time it costs. A weekly meeting that could be fortnightly, or a thirty-person standup that only needs five, is a cadence problem. The metric scores how much of your recurring meeting time produces decisions or actions against how much is pure repetition.

The simplest way to read it is as a ratio. If a team spends 40 hours a month in recurring meetings and only 24 of those hours produce a decision, an owned action, or a genuine unblock, the cadence optimisation score is 60 percent. The remaining 16 hours are status updates that could have been a written note. Tracking this over time tells you whether your meeting rhythm is tightening or sprawling.

Cadence optimisation matters because recurring meetings are the most expensive habit a company never reviews. They are scheduled once and inherited forever. Nobody owns the question of whether the weekly sync still needs to be weekly. Measuring cadence turns that silent cost into a number you can act on, the same way you would track cycle time or any other operational signal.

There is no single universal formula, because cadence optimisation is a composite of frequency, duration, attendance, and output. The most practical approach is to score the share of recurring meeting time that produces a decision or an owned action, then layer in the supporting inputs below to explain the score.

1. 1

   Total recurring meeting hours

   Sum every recurring meeting on the calendar over the period, multiplied by attendee count, to get person-hours. A weekly one-hour meeting with eight people is 32 person-hours a month, not four. Counting heads is what turns cadence into a real cost.

2. 2

   Productive meeting hours

   The share of that time that produced a documented decision, an assigned action, or a genuine unblock. A meeting that ended with a clear owner and next step counts. A meeting that only relayed information that could have been written down does not.

3. 3

   Decision yield per meeting

   Decisions or actions divided by meetings held. A recurring meeting that consistently yields zero decisions is a candidate to make less frequent, shorter, or asynchronous.

4. 4

   Right-sized attendance

   The proportion of attendees who spoke, owned an action, or were named in the notes. If most attendees are silent and unactioned, the invite list is too wide and the cadence cost is inflated.

Putting these together, the headline cadence optimisation score is productive meeting hours divided by total recurring meeting hours, expressed as a percentage. A score climbing toward 80 percent or more means most of your recurring time earns its place. A score below 50 percent means at least half of your recurring meetings are running on inertia. The supporting inputs tell you whether the fix is frequency, duration, or the invite list.

A metric tree decomposes the cadence optimisation score into the levers that actually move it, so you can see why your meeting time is or is not earning its cost. This is the gap between a dashboard that shows a low score and a decision about which meeting to change.

The first level splits the score into the drivers that determine whether recurring time is productive: how often meetings happen, how long they run, who attends, and what each one produces. Each driver then decomposes into the operational choices a team can actually adjust. Frequency breaks down into the recurrence interval and whether that interval matches the pace of new information. Attendance breaks down into invite-list size and the share of attendees who are active rather than passive.

The tree turns a vague feeling that there are too many meetings into a precise diagnosis. If the score is falling, the tree tells you whether the cause is meetings that recur too often, run too long, pull in too many passive attendees, or produce too few decisions. Each of those leads to a different fix owned by a different person.

Benchmarks for cadence optimisation depend on team type and stage. Engineering and operations teams running tight delivery cycles tolerate a different rhythm than a leadership team coordinating across functions. The useful comparison is not the absolute number of meetings but the share of recurring meeting time that produces decisions and how much of the working week meetings consume.

As a rough rule, individual contributors lose ground when recurring meetings exceed 15 to 20 percent of the working week, because the remaining time fragments into blocks too short for deep work. Managers and coordinators sit higher, often 30 to 40 percent, because coordination is part of the role. The point of benchmarking is not to hit a target number of meetings but to keep the productive share high as headcount and complexity grow.

Improving cadence optimisation means raising the share of recurring meeting time that produces decisions, usually by cutting frequency, tightening invite lists, and moving status to writing. The most common mistake is adding new meetings to fix problems caused by old ones.

The metric tree approach to improving cadence starts by finding the driver with the largest gap between current and ideal. If output per meeting is low, the fix is agenda and attendance, not frequency. If frequency fit is poor, re-timing recovers the most hours fastest.

KPI Tree lets you connect each cadence driver to the person accountable for it. A recurring meeting has an owner, and that owner sits on the relevant branch of the tree with clear RACI: responsible for the agenda, accountable for whether the cadence still earns its place. When the productive share of a team meeting load drops, the change is pushed to the owner who can act on it rather than buried in a quarterly review. This is the difference between a calendar that sprawls quietly and one where every recurring slot has someone answerable for it.

1. 1

   Counting meetings instead of person-hours

   A single recurring meeting can cost dozens of person-hours once you multiply by attendees. Measuring the number of meetings alone hides the real cost. Always weight by how many people are in the room.

2. 2

   Treating all meetings as equally optimisable

   A one-to-one or a genuine decision forum is not the same as a recurring all-hands status readout. Optimise the meetings that recur on inertia, and leave the high-trust, high-decision meetings alone.

3. 3

   Optimising duration before frequency

   Trimming minutes off a meeting that should not recur weekly at all is the small lever. Fix the interval first. Re-timing a low-yield meeting recovers far more hours than shaving the agenda.

4. 4

   Adding a meeting to solve a meeting problem

   When a sync feels chaotic, the instinct is to add a pre-meeting or a follow-up. This compounds the cadence cost. The fix is usually fewer, better-prepared sessions, not more of them.

5. 5

   Reviewing cadence once and never again

   Meeting load creeps back the moment attention moves elsewhere. Without a standing review and a clear owner, an optimised calendar drifts back to bloated within a quarter.