How Many Priorities a Leadership Team Can Run

The question tends to arrive in almost the same words every time: how many priorities is too many for a leadership team. It is rarely asked early. It is asked once a team of eight is carrying eleven named initiatives into a quarter, each with a sponsor, each with a slide, and someone has started to suspect that the list is the reason execution feels heavier than the work itself should be. What that person usually wants is a number — small, defensible, quotable back to whoever proposed the eleventh item.

The number is worth having. But it is not selected, and treating it as a matter of preference is what makes the conversation unwinnable, because every proposed ceiling can be argued down by one more good idea. A leadership team is already running a priority count, and that count can be measured rather than debated. It is not written in the strategy deck. It is written in the minutes of the last two quarters of review meetings, and it is almost always smaller than the deck claims.

Two counts, only one of which governs

The declared count is the one on the plan: eleven initiatives, eleven owners, eleven lines in the quarterly pack. The working count is the number of those eleven that the senior team actually made a decision about in the period — not received an update on, not nodded at, but resolved something for. These two numbers are almost never the same, and the second one is the one that determines what moved.

The exercise is mechanical enough to run in an afternoon, and it is the one we reach for before anyone argues about a ceiling. Take the last two quarters of leadership review minutes. For each named initiative, ask a single question: did the senior team make a decision about it — a trade-off resolved, a resource moved, a date changed, a scope cut — or did it only appear as a status line? Sort the list into three piles.

• Items that received a real decision, where something was chosen and something else was consequently not done.
• Items that received a status update and nothing else, cycle after cycle, usually reported green.
• Items nobody raised at all, which remain on the deck because removing them requires a conversation with their sponsor.

The first pile is the team's actual priority count, and the other two piles are the gap between what the organisation was told and what the organisation was given. In our experience the first pile lands between three and five on a deck of ten to twelve, and the team's reaction to seeing it is rarely surprise at the number. It is recognition — those are the items they would have named if asked which ones were genuinely being run.

What the middle pile is actually telling you

An initiative reported green for six straight cycles without ever generating a decision is not necessarily healthy. Often it is unattended: nothing has gone wrong that was visible enough to reach the room, and nothing has been decided that would change its course. The green status is a report on the absence of attention, not on progress. This is the same mechanism that makes a list where everything is nominally a priority behave as though nothing is — the items do not stop existing, they stop being decided about.

Once the working count is visible, the ceiling stops being a philosophical question and becomes an arithmetic one, because a leadership priority spends two resources that exist in fixed quantities.

• A named owner with genuine slack — not a function head who already carries two other initiatives alongside their operating responsibility.
• A recurring slot in the senior team's cadence where that initiative's trade-offs get resolved, which is a share of a finite agenda rather than an unlimited good.

The second constraint is the one teams consistently underestimate. A leadership team meeting weekly for ninety minutes, with the standing operating business taking half of that, has perhaps forty-five minutes of real decision capacity per week. An initiative that needs the senior team's judgment needs a meaningful share of that, not a mention. Divide the available decision time by what one initiative actually requires and the ceiling calculates itself, which is why the answer keeps landing near the same range regardless of how ambitious the company is.

This is also why the fix belongs to the cadence rather than the plan. A ceiling defended in a planning offsite and never reflected in what the weekly, monthly and quarterly reviews are each responsible for deciding survives about one quarter.

The green status is a report on the absence of attention, not on progress.

The range is worth stating plainly because teams ask for it, but it is worth stating with its reasoning attached, because a number without its derivation is just someone else's opinion and will lose to the next persuasive proposal. Three to five is what falls out of a senior team's decision capacity divided by what one contested initiative consumes. A team with an unusually disciplined cadence, or unusually few contested trade-offs, can run more. A team in the middle of a transition can run fewer.

The items that do not count against the ceiling

The count under discussion is specifically the count of initiatives requiring the senior team's judgment. Work that has been genuinely delegated — an owner with authority, a decision rule agreed in advance, its own review rhythm one level down — is no longer a leadership priority. It is a functional one, and it does not consume the scarce resource. This distinction is what allows a company to run more than five things at once without the leadership list growing, and getting it wrong in either direction is costly: counting delegated work against the ceiling makes the company look busier than it is, while counting undelegated work as delegated is how the middle pile fills up.

The ceiling is therefore not a limit on ambition but a statement about which decisions have to happen in one room. Set against that, the reason the list grows is easier to see than it is to stop — adding an item costs the person adding it nothing today, and a count derived from the minutes is one of the few things that puts a real price on the eleventh proposal.

A leadership team can run the three-pile exercise without help, and some do. What is harder from inside the reporting line is the part immediately after: telling the sponsor of a six-quarter green initiative that it was never actually being run, and then deciding whether to resource it properly or to stop it. Both answers are defensible. Leaving it on the deck, reported green, is the one that is not, and it is also the one that requires nobody to have an uncomfortable conversation.

This sits inside the wider discipline the pillar is about — that growth quietly consumes capacity nobody declared it could have, and that the consumption shows up in attention long before it shows up in a number anyone reports. The count read off the minutes is the earliest honest signal available.

It is close to how we open consulting engagements with growth-stage leadership teams: before anything is proposed, the last two quarters of review minutes get sorted into the three piles, because the resulting number is not contestable in the way a recommended ceiling is. It is simply what the team has been doing. Whether it stays that number is then a choice the team makes deliberately, once, rather than eleven times in eleven separate meetings.