Count the meetings on a leadership team's calendar for one week and then count how many decisions actually got made in them. At most companies we work with, the first number is somewhere around fifteen and the second number is close to zero.
Nobody scheduled these meetings to waste time. They accumulated the same way most organizational bloat accumulates: one reasonable addition at a time, never subtracted.
Every one of those meetings made sense the day it got added. A crisis needed a standing check in. A new initiative needed visibility. Two years later the crisis is over and the initiative shipped, and the meeting is still on the calendar because removing a recurring meeting requires someone to actively decide it is no longer needed, which almost never happens on its own.
Status updates matter, but they do not require a room full of decision makers reading numbers to each other that everyone could have read on their own beforehand. When a leadership meeting spends most of its time on updates, the actual decisions get pushed into hallway conversations, side threads, and one on one messages after the fact, which is a worse version of the meeting that just happened without being called one.
Watch what happens the next time your leadership team leaves a meeting. If three separate follow up conversations start within the hour, the meeting did not do its job.
We defined decision concentration as decisions queuing behind one person because they are the only one permitted to make them, not the only one capable. Meetings are where this becomes visible, because a meeting with no defined decision owner defaults to whoever has the most authority in the room, regardless of who actually has the best information.
A meeting cadence that actually works assigns an owner to every recurring decision before the meeting happens, not during it. The meeting becomes the forum where that owner presents a recommendation and takes input, not the place where the decision gets discovered in real time.
Weekly leadership meetings became a default the same way most business rituals become defaults: someone did it once, it seemed reasonable, and nobody revisited whether the cadence still matched the actual rhythm of decisions that needed making.
Some decisions genuinely need a weekly cadence, particularly anything tied to a fast moving pipeline or active operational issue. Many decisions on a typical leadership agenda are monthly or quarterly in nature and get forced into a weekly slot purely out of habit, which dilutes the meeting and trains the room to expect low stakes discussion as the norm.
A useful test for any recurring meeting: can every agenda item be rewritten as a question with a name attached, something like who decides X by when. If an item cannot be rewritten that way, it is either a status update that belongs in a written summary, or a discussion that has not yet been narrowed down to an actual decision.
This single rewrite eliminates most of the vague agenda items that make meetings feel long without feeling productive. Vague topics produce vague conversation. Specific decisions with named owners produce specific outcomes.
Try running this test against your own leadership agenda from last week. Most teams find that fewer than half the items survive the rewrite, and the ones that do not survive are usually the ones that ran longest.
Information lag is the elapsed time between something going wrong and leadership finding out. A meeting cadence built around status updates instead of decisions often makes this worse, because problems get mentioned in passing during an update slot and then quietly dropped when the agenda moves to the next topic, with nobody assigned to actually resolve them.
A well run cadence does the opposite. Problems raised in one meeting get an owner and a follow up date, which means they either get resolved by the next meeting or come back with a clear reason why not, rather than disappearing into the general noise of a long status update.
Large leadership meetings tend to produce cautious, diluted decisions, because nobody wants to commit to a clear position in front of eight peers if there is any chance of being wrong. Smaller meetings, with only the people who actually own the decision at hand, produce sharper outcomes because the social cost of a wrong call drops significantly.
This is why the most effective operating rhythms usually separate a small weekly decision meeting from a larger monthly or quarterly meeting focused on alignment and visibility. Different rooms serve different purposes, and collapsing them into one recurring meeting usually serves neither well.
Leadership teams sometimes respond to meeting fatigue by canceling meetings wholesale, which usually just moves the same undefined decisions into slower, less visible channels like email threads and hallway conversations. The problem was never the existence of the meeting. It was the absence of a decision inside it.
A shorter, sharper cadence built around named decisions and named owners produces more actual progress than a longer one built around updates, even though it looks, from the outside, like the company is meeting less.
We have watched leadership teams cut their combined meeting time nearly in half after redesigning the agenda around decisions instead of topics, and come out the other side making faster calls, not slower ones. The time did not disappear. It stopped being spent on conversations that were never going anywhere.
How many leadership meetings should we actually have per week?
Fewer than most companies run, and the number matters less than whether each one has a defined decision owner attached to every agenda item.
What should we do with pure status updates?
Move them to a written summary sent before the meeting, so the room's time gets spent on decisions and open questions rather than reading numbers aloud that everyone could have read on their own.
How do we know if our current cadence is actually working?
Track how many decisions each meeting produced versus how many topics it covered. A large gap between those two numbers is the clearest signal something needs to change.
Should every decision go through a leadership meeting?
No. Only decisions that genuinely require cross functional input belong there. Decisions with a clear individual owner should be made outside the meeting entirely, which is itself a sign of healthy decision rights.