The Leadership Team Has No Cadence to Borrow From

A sales team's weekly meeting takes its shape from the leadership team's monthly review, which takes its shape from the board's quarterly cycle. Each layer down the org chart can point upward and say, correctly, that its rhythm was set by what the layer above needs from it. The leadership team has no such layer to point to. Its own rhythm — what it reviews weekly, what it defers to a monthly session, what only comes up once a quarter — is not handed down. It is the first rhythm in the company, and someone at that table has to have actually designed it rather than inherited it from a template used at a previous job. That absence is easy to overlook precisely because everything else in the company has the opposite experience: a rhythm someone else already justified, that only needs to be adopted rather than argued for from first principles.

Most leadership teams never make that design decision explicitly. They arrive at a weekly cadence because weekly is the default interval for an executive calendar, fill the hour with whatever is urgent that week, and call the result an operating rhythm because it recurs. Recurrence is not the same thing as design, and the gap between the two is where a leadership team's own rhythm quietly stops doing the job the rest of the company's cadence depends on it doing.

What the room is actually for

A functional head brings a decision to the leadership team for one of two reasons: either it requires trading off against another function's priorities, or it requires authority the function head does not have alone. Both reasons describe the same underlying job — the leadership team exists to make the calls that cannot be made correctly from inside a single function, because a single function cannot see the whole trade it is proposing. If the room spends its time on updates instead, those calls do not disappear. They get made anyway, later, by whoever is under the most pressure to decide something, usually without the cross-functional view the leadership team exists to supply.

This is the layer beneath what a weekly, monthly, and quarterly review are each built to catch: the tiering only works if the weekly session is actually resolving weekly-grade decisions rather than reporting on decisions that were already made elsewhere, informally, because the room that should have made them was busy with status.

The two purposes compete for the same attention, and status wins by default because it is easier: a function head can walk through what shipped last week without asking anyone in the room to take a position, while a genuine trade-off requires someone to argue against another function's proposal in front of that function's leader. Given the choice between an hour that stays comfortable and an hour that produces friction, most rooms drift toward comfortable, and the drift compounds — a room that has not exercised real disagreement in several sessions finds it progressively harder to introduce, because doing so now reads as a departure from how the meeting normally runs. The asymmetry is not a flaw in any individual's judgment. It is a structural feature of what a status update costs to deliver versus what a genuine disagreement costs to raise in front of a peer whose plan it contradicts.

A short account of what separates the two kinds of session makes the difference concrete:

• A status item is information one function already has and is relaying to the room, with no decision attached to it
• A decision item is a trade-off that at least two functions see differently, and the room exists specifically to resolve it
• Most leadership agendas do not label which is which, so both get the same amount of discussion time regardless of which one actually needed the room

The instinct when a leadership meeting feels unproductive is usually to extend it, or to add a second weekly session to cover what the first one is not getting to. Both responses treat the problem as a capacity shortage. It is more often a design problem: the meeting is trying to do reporting and adjudication in the same slot, and adding time lets both continue, badly, rather than forcing the separation that would fix either one. A leadership team that moves reporting to an asynchronous written update, and reserves its actual room time for the decisions only that room can make, usually needs less time together, not more.

The written update does the job a status segment was doing less efficiently anyway — every function head reads it before the room convenes, which means the room opens already informed, and the first question anyone asks is about a trade-off rather than a summary. What is left for the live session is the part that genuinely requires people in the same room: the argument, not the recap.

A leadership team rarely notices its own rhythm is broken from the inside, for the same reason a person struggles to hear their own accent — the meeting has always run this way, so it does not register as a design choice that could have gone differently. It registers, instead, as simply what a leadership meeting is. Naming the gap between a room that reports and a room that decides, and rebuilding the agenda around the second, is the specific kind of work our engagements are built to do — not because the leadership team lacks the judgment to separate the two, but because a room cannot audit its own habitual shape from inside the habit. That is closer to an outside function than an executive one, which is why it rarely gets done without someone whose job is exactly that walking in and asking what the hour was actually for. The habit is invisible to the people inside it in a way it is rarely invisible to someone sitting in the room for the first time, which is most of what an outside review of a leadership cadence is actually doing in its first few sessions.