How to build accountability across leadership teams

Accountability in a leadership team means that every important outcome has one named owner, everyone knows what was committed and by when, progress is visible without anyone having to ask, and the team reviews it on a fixed rhythm with predictable consequences. It is not about blame. It is about making ownership explicit enough that nobody has to guess who will move something, and nobody is surprised when it is raised.

Most leadership teams believe they already have it. The test is simple: pick the three outcomes that matter most this quarter and ask each member of the team, separately, who owns each one. If the answers differ, or if the answer is "we all do", accountability is weaker than it looks.

What accountability is, and what it is not

The word has picked up a punitive edge. In many companies, "holding someone accountable" has come to mean finding who to blame after something goes wrong. That version makes people defensive, encourages cautious targets and pushes bad news underground, which is the opposite of what a leadership team needs.

• It is ownership of an outcome, not just a list of tasks.
• It is a commitment made in advance, with a clear standard of what done looks like.
• It is visible: the team can see progress without waiting for a status update.
• It is not blame after the fact.
• It is not the same as doing the work. An owner can rely on others to deliver, but cannot hand the outcome back.
• It is not shared. Several people can contribute; only one person owns.

Why accountability breaks in growing companies

In a company of fifteen people, accountability tends to work without design. Everyone sees everything, the founder is in every conversation, and gaps are spotted quickly. Somewhere between thirty and a few hundred people that stops being true, and three problems tend to appear together.

Shared ownership

Cross-functional outcomes, such as a new product line, a pricing change or a customer experience target, get assigned to "sales and operations" or to a committee. Each function delivers its part, and nobody owns the whole. When the outcome slips, every function can show that its own piece was done.

Unclear decision rights

Leaders are told they own an outcome but cannot make the decisions it requires without approval from the founder or a peer. Ownership without the right to decide is not ownership; it is exposure. This is often the same pattern described in our article on reducing founder dependency.

No consequences loop

Commitments are made in a planning meeting and then never formally revisited. Nothing happens when they are met, and nothing happens when they are missed. The team learns, quickly and rationally, that commitments are aspirations.

The accountability framework

The framework we use with leadership teams has five elements. None of them is new. What matters is that all five are present at the same time, because each one fails without the others.

1. A single owner per outcome. Every priority, KPI and major initiative has one named person. Not a team, not a pair. If two people are proposed, the outcome is usually too broad and should be split.
2. Explicit expectations. The owner and the team agree, in writing, what success looks like, by when, and what resources and decision rights come with it.
3. Visible metrics. Progress is tracked in a shared place, such as the executive KPI dashboard, so nobody needs to chase an update.
4. Regular review. Outcomes are reviewed on a fixed rhythm: weekly for priorities, monthly for KPIs, quarterly for objectives.
5. Consequences. Meeting or missing a commitment leads to something predictable: recognition, a change of plan, extra support, or a change of owner.

Consequences are the element most teams skip, and the word is often misread. It does not mean sanctions. It means that what happens after a commitment is met or missed is known in advance and applied consistently. Most of the time, the consequence of a miss is a better plan.

The regular review usually lives in the weekly leadership meeting, where each owner reports by exception, and in the wider operating cadence of monthly and quarterly reviews.

RACI vs an ownership matrix

The RACI matrix is the best-known tool for this. It assigns four roles for each task or decision: Responsible (does the work), Accountable (answers for the result), Consulted (gives input before) and Informed (is told after). It is useful, and it has variants such as DACI and RAPID that focus more tightly on decisions.

RACI works well for processes and projects with many contributors. It is less useful at leadership level, where the question is not who does which task, but who owns which result. For that, a simpler ownership matrix tends to work better.

In practice, most companies need both: an ownership matrix for the leadership team and a RACI for the handful of processes where handovers break. The accountability and ownership matrix and the RACI matrix template are built to be used together.

Leadership behaviours that make it stick

Tools set up accountability. Behaviour keeps it alive. The patterns that matter most are visible in the leadership team itself, because the rest of the company watches how leaders treat each other's commitments.

• The CEO goes first. If the CEO's own commitments are vague or never reviewed, nobody else's will be either.
• Bad news travels early. Leaders raise a likely miss as soon as they see it, and are thanked for it rather than questioned on why it was not avoided.
• Peers hold peers. Accountability is not only vertical. Leaders challenge each other in the room, respectfully and specifically.
• No silent rescues. When someone steps in to fix another leader's outcome without saying so, ownership erodes for both of them.
• Commitments are small enough to keep. A team that commits to everything learns to deliver nothing in full.

Running the conversation when a commitment slips

Slips will happen. The way the first few are handled decides whether people keep making honest commitments. A short, predictable structure helps, both in the leadership meeting and in a one-to-one:

1. State the facts. What was committed, by when, and where it stands now. No adjectives.
2. Ask for the owner's view first. What happened, and what did they learn that the team did not know at the start?
3. Separate the cause. Was it the target, the plan, the resources, a dependency, or execution? Each points to a different fix.
4. Agree the new commitment. A revised date or scope, with what will be different this time.
5. Decide what the team needs to change. Sometimes the fix belongs to the system, not to the person.
6. Record it and review it. The new commitment goes back into the same tracking and the same rhythm.

The goal of the conversation is not to establish fault. It is to leave with a commitment that is more likely to be kept than the last one.

Where the same person misses repeatedly, the conversation changes. The question becomes whether the role, the scope or the person is the right fit, and that is a separate, private discussion, not something for the leadership meeting.

That individual follow-up needs its own performance management system, as People by Design explains, separate from the team’s review of commitments.

Example: Ferraria Norte

Ferraria Norte is a fictional company used for illustration: an engineering services business with around ninety people and a leadership team of five. Its priorities for the year included reducing late project deliveries. The priority had been assigned to "operations and engineering", and both directors attended every review.

Each quarter, both functions reported progress on their own actions, and deliveries stayed late. When the team built an ownership matrix, the gap became obvious. Nobody owned the measure itself, and the decisions that would move it, such as when to refuse a client's change request, sat with the CEO.

The team made three changes. The operations director became the single owner of on-time delivery, with a weekly measure on the dashboard. She received the right to decide on scope changes below an agreed threshold. And the engineering director became Responsible for estimates in a RACI covering the handover from sales to delivery. In the next quarterly review, the conversation was no longer about whose actions were done, but about whether the measure had moved and why.

Where to start

Accountability is built over a few quarters, but the first steps fit in a month:

• List the company's priorities, KPIs and major initiatives on one page.
• Name one owner for each, and split anything that has two.
• For each owner, write down the decisions they can make without approval.
• Put every measure in one shared place and review it in the weekly meeting.
• Agree, as a team, how slips will be handled before the first one happens.

This is the core of our leadership operating system work, where we implement ownership, decision rights and review rhythms with the leadership team rather than describe them.

If your leadership team commits to more than it delivers, or nobody is quite sure who owns what, the Operating Assessment is a good place to start. It maps where ownership is unclear and what to fix first.