Insights

Leadership meetings are broken. Here's a cadence that actually works

Published 22 October 2026

TemplatesGovernance
Leadership meetings are broken. Here's a cadence that actually works

Ask a delivery leader how many meetings they sit in each week and the answer is usually a groan. Most of them are some form of status call. Someone reads out where their project is, everyone nods, nobody decides anything, and the group meets again next week to hear roughly the same update.

The fix isn't fewer meetings for the sake of it. It's a small set of recurring meetings where each one has a single job, a standing agenda, and a clear thing that has to come out of it. This post sets out a cadence that works for a midsize agency, and the template that goes with it.

Why leadership meetings drift into status calls

Nobody sets out to build a bad meeting. Most leadership meetings start with a real need, such as keeping an eye on live projects or spotting overbooked people. Then each new problem gets its own new call, and the old calls never get removed.

Over time the same people sit in several overlapping meetings that cover the same ground from slightly different angles. Because nobody wrote down what each one is for, they default to the easiest thing to do in a room, which is to go round the table and give updates.

Four meetings, one job each

WEEKLYDeliveryReviewRed and amberprojects onlyWEEKLYCapacityCheckOverbooking in thenext 4 weeksMONTHLYRiskReviewRisks and stuckescalationsQUARTERLYOperatingReviewKeep, changeor dropEach meeting has one job

A workable leadership cadence is four meetings, not a calendar full of status calls.

MeetingIts one jobRhythmWho is in the room
Weekly Delivery ReviewDecide what needs leadership attention on live projects this weekWeekly, 45 minutesDelivery leads and PMs with red or amber projects
Capacity CheckSpot overbooking and gaps over the next 4 weeksWeekly, 20 minutesResource lead and delivery leads
Monthly Risk and Escalation ReviewLook at risks above the line and escalations that have not movedMonthly, 45 minutesDelivery leadership and account leads
Quarterly Operating ReviewStep back and decide what to keep, change or dropQuarterly, 90 minutesThe full leadership group

The timings are starting points. Adjust them to the size of your team.

If you can't say what a meeting's one job is in a single sentence, that is the meeting to cut or merge. And if two meetings share a job, one of them has to go.

What a standing agenda looks like

A fixed agenda is what stops the meeting drifting. Here is the weekly delivery review as an example, in 45 minutes:

1. Decisions needed (5 minutes)

Anything that needs a call from this group goes first, while people are fresh. Each decision is made in the room or given a named owner and a date.

2. Red and amber projects only (20 minutes)

Green projects are skipped. The time goes on the projects that need help, and each one leaves with a clear next step.

3. New work coming in (10 minutes)

What is landing, what it needs, and whether the answer is go, hold or push back. This is where the capacity conversation meets the sales pipeline.

4. Actions read back (10 minutes)

Every action is read out with an owner and a date. An action without both isn't an action.

The ground rules that keep it working

Read before you attend. One page of notes goes out 24 hours before. Nobody reads their project out loud in the room.

Decisions, not updates. If an item needs no decision and no help, it goes in the notes, not on the agenda.

Send the right person. A delegate who can't make the decision just carries the question back out of the room. If the decider can't attend, the item moves.

Finish when the agenda is done. A meeting that ends early isn't a failure. It's the point.

Where leaders get it wrong

Adding without removing. Every new problem gets a new meeting. If you add one, drop or merge another.

Treating the cadence as fixed. A model that is never reviewed drifts back into status calls. Score each meeting every quarter on three questions: did it produce decisions, did the right people attend, did it run to time.

No record of what was decided. Without a shared decision and action log, the same issue comes back the following week, because nobody can point at what was agreed.

No named owner. Someone has to own the cadence itself, keeping the agendas, sending the notes and calling time on a meeting that has stopped earning its place.

A workable way to start

List every recurring meeting your delivery leadership group attends today and write the one job of each next to it. Cut or merge anything that shares a job. Then set a standing agenda for what's left, agree the ground rules with the group, and book every date for the next quarter in one go. Put a review in the diary for the end of the quarter, so the cadence gets checked before it drifts.

A good leadership meeting isn't a status update with more senior people in the room. It's a short, regular slot where decisions get made and written down.

From the vaultLeadership Meeting Model

The four meeting cadence from this post as a ready to use document: meeting set, standing agendas, ground rules, a quarterly health check and a decision log. Founding members get it free.

9 templates live · lifetime access · 14 day refund

← More Insights