A Leadership Agenda Holds What No One Below Can Settle

Most leadership team agendas are assembled the same way. A chief of staff or an executive assistant collects requests during the week, orders them by seniority or urgency, and the list that results is the agenda. Nobody decides what the meeting is for. The meeting is for whatever arrived.

Two reasons an item arrives

An item reaches the leadership table for one of two reasons. Either the person raising it lacks the authority to settle it, or they hold the authority and would prefer not to use it alone. The first is an escalation for authority. The second is an escalation for cover, and on the agenda the two look identical: a heading, a name, a request for twenty minutes.

Cover is not a character flaw. A sales director who approves an unusual discount for a large renewal carries the outcome personally if the account later sours. Bringing it to the leadership team spreads that outcome across eight people. An agenda that admits every request becomes the place where functional decisions go to be shared, and the cross-functional ones wait behind them.

The result is familiar from the note on a leadership team's own rhythm: a room meant to resolve what no single function can see spends its hour endorsing what a single function could have decided. The weekly review has its own repair, which is an agenda built from exceptions. The question here is narrower and comes first. Before an item is ordered, timed or prepared, something has to decide whether it belongs at this table at all.

The admission test

The test we use with leadership teams is short, and it is applied to every proposed item before it is scheduled. An item is admitted if at least one of three things is true of it:

• It is a trade-off between functions, where each side is right about its own area and the two cannot both be satisfied.
• It commits the whole company to something hard to reverse: capital, headcount beyond plan, a public commitment, a change in how much risk is accepted.
• It needs authority that no single member of the team holds, even though one of them owns the work.

An item that passes none of these is returned to the person who raised it, with the name of whoever holds the right to decide it. Often that is the same person. The return is not a refusal of help. A leader who wants advice can get it from two colleagues in a short conversation, which costs everyone less than a slot in front of all of them.

What the test leaves out

Applied honestly, the test removes more than teams expect. Functional plans presented for awareness move to the pre-read. Decisions a leader has already made and wants endorsed go back to that leader. Updates on projects running to plan go nowhere, because nothing about them needs a room. What remains is short, and it is the part of the company's work that only this group can do.

A checkout change shows where the boundary falls. A product lead who wants to remove a verification step from a payment flow owns the roadmap but not the bank's risk appetite. The change crosses functions and needs authority no single head holds, so it is admitted. The same lead asking the room to choose between two designs for the confirmation screen is not, and the agenda should not pretend otherwise.

An agenda built only from requests has a second blind spot. Some of the most consequential items for a leadership team are owned by no single member, so nobody brings them. A dependency between two programmes that belongs to both and to neither. A risk spread across three functions, each holding a small and tolerable share of it. The team's own commitments to the rest of the company, made at the start of the year and never reviewed since.

A standing slot for the unsponsored

These items need an owner on the agenda even when they have no owner in the organisation. In practice that is the chief executive or a chief of staff, who reserves one slot in each meeting for an item nobody requested and says why it is there. The leadership team is the one room in the company where an item can be raised without a sponsor, and an agenda that waits for sponsors gives that up.

The slot is small. One item, prepared like any other, with the trade-off stated and the cost of waiting attached, in the form set out in the note on meetings that end in decisions. Over a quarter it tends to carry the items that would otherwise have surfaced only as a crisis, when the choices left are fewer and dearer.

The admission test has a by-product worth more than the shorter meeting. Every returned item has a source and a reason, and logged over a quarter they form a pattern. The same kinds of item turn up again and again: pricing exceptions above some informal threshold, hiring requests just outside plan, scope changes on a platform two teams share.

A recurring escalation is a decision right that was never written down.

Each recurring type points to a right below the table that is missing, unclear or held by someone who does not trust it. Pricing exceptions arrive because nobody beneath the leadership team has a written limit. Scope changes arrive because two product owners share a platform and neither holds the final call. As the note on inherited decision rights describes, gaps like these were rarely designed. They accumulated.

Settling the right instead of hearing the item

The response is to settle the right once rather than the item every month: a written discount limit, a named owner for the shared platform, a hiring band that does not need a meeting. Each right settled below the table removes a whole category from the agenda for good, which is the only kind of agenda reduction that lasts. A leadership agenda that shrinks this way is evidence that the organisation beneath it is deciding more on its own.

The first step is an audit of the last two months of agendas. Each item is marked against the three admission tests, and each item that fails is traced to the decision right that would have kept it off the table. The audit usually shows two things at once: how much of the hour went to items that never needed the room, and which few rights, once written down below the table, would keep them away.

Our consulting work runs that audit with the leadership team and settles the rights it surfaces, inside the operating cadence pillar. Our training programmes cover the habit that is hardest to keep, which is returning an item to its owner without it reading as a refusal. A leadership agenda is working when what reaches it could not have been settled anywhere else.