How Do I Make My Leadership Team More Accountable to Each Other?

Start by making commitments visible

Peer accountability is almost impossible when commitments live in memory. Someone says:

“I’ll sort that out.”

Another person says:

“Leave that with me.”

Everyone nods. Meeting ends. A week later:

“Where did we get to with that?”

Nobody is entirely sure what was actually agreed. That is not accountability. That is a conversation and a hope. If a commitment matters, capture: What will be done? Who owns it? By when? What does completed mean? Now everybody is looking at the same promise. That changes the quality of the follow-up.

One owner

Leadership teams often weaken accountability by spreading ownership too widely.

“We all need to work on that.”

Perhaps. But who is making sure it happens? If everyone owns it, there is a reasonable chance nobody does. A leadership action should usually have one named owner. Others can help. Others can contribute. But one person knows: This is mine. That makes peer accountability possible.

Come back to what was agreed

This is where the weekly meeting matters. The next meeting should not begin as though the previous meeting never happened. Come back to commitments. Completed? Good. Not completed? What happened? Still relevant? Needs renegotiating? Blocked? No longer required? Close it consciously.

Do not allow actions to roll forward indefinitely until everyone stops seeing them. Stale actions become wallpaper. And once the team learns that nothing really happens when commitments are missed, the register may still exist but accountability does not.

Accountability is not the CEO interrogating everyone

A weekly leadership meeting should not feel like the head teacher checking homework. That creates dependence too. Instead, the team should be able to see the same information. The scoreboard. The commitments. The misses. The patterns. Then accountability becomes part of the team's normal operating rhythm. Someone can say:

“We agreed that would be done by Friday. What happened?”

without it automatically being treated as a personal attack. That is maturity.

Make the standard impersonal

Peer accountability becomes much easier when the standard was agreed beforehand. Not:

“Christine thinks you should have done this.”

But:

“We agreed this.”

Not:

“I don't think your result is good enough.”

But:

“This is the target we agreed.”

Not:

“You seem behind.”

But:

“This was due Tuesday and it is still open.”

That distinction matters. The conversation is no longer about one leader's mood. It is about a visible commitment.

Evidence reduces politics

Leadership teams can become political very quickly if accountability depends on opinion.

“I think Operations isn't pulling its weight.”

“Sales never gives us enough notice.”

“Finance always slows things down.”

Perhaps. But what does the evidence say? What was agreed? What happened? When? How often? What was the effect? Evidence moves the conversation away from departmental folklore and towards something the team can examine together. That does not make every conversation comfortable. It does make it more useful.

Make it safe to say something is off track

This matters. If every red number or missed commitment produces humiliation, people will not become more accountable. They will become more defensive. They will hide. Explain. Reframe. Manipulate. Delay admitting there is a problem. You want leaders able to say:

“This is off track.”

Early. Without feeling that admission itself is failure. The useful questions are: What happened? What are you learning? What needs to change? What support do you need? What are you recommending? What is the new commitment? That is accountability without theatre.

But don't make accountability toothless The opposite problem is just as damaging. Everyone is endlessly understanding. A commitment is missed.

“No worries.”

Missed again.

“These things happen.”

Again.

“Let's roll it forward.”

At some point the team has to ask: Why does this keep happening? Does the person have the capability? Was the commitment realistic? Do they have authority? Are priorities conflicting? Or are we simply tolerating behaviour we say matters? Accountability without consequence eventually becomes meaningless.

Encourage challenge across functions

A real leadership team is not five functional leaders sitting beside each other protecting their own patch. They have a collective responsibility for the business. That means the Sales leader can appropriately ask Operations a question. Operations can challenge Finance.

Finance can challenge the CEO. Not because everybody is interfering in everybody else's job. Because leadership-team membership creates an obligation to care about the whole business. This is where peer accountability starts becoming powerful.

Business first

One of the hardest shifts for leadership teams is moving from:

“I represent my department.”

towards:

“I am part of the leadership of the whole business.”

Of course you still lead your function. But around the leadership table, the question becomes: What is best for the business? That may occasionally mean supporting a decision that makes your own area less comfortable. That is leadership-team accountability too.

If every leader simply advocates for their own territory, you have a committee of functional representatives. Not necessarily a leadership team.

Agree the behaviour expected around the table

Teams often define financial targets but never define leadership behaviour. What does good leadership-team membership look like? Perhaps:

prepare before meetings; raise issues directly; challenge ideas, not people; support decisions once made; do what you said you would do; speak business-first rather than function-first; bring thinking, not just problems; avoid side conversations and political manoeuvring; address concerns in the room rather than afterwards; tell the truth early when something is off track.

If those behaviours matter, make them visible. Then the team can hold itself to them.

Challenge in the room

One of the weakest leadership-team behaviours is false agreement. Everyone nods. Meeting ends. Then in the corridor:

“I knew that would never work.”

Or:

“I didn't agree with that.”

That is not useful. If you disagree, bring the disagreement into the conversation while the decision can still be improved. Healthy teams debate. They challenge. They ask difficult questions. Then they decide. Peer accountability includes being willing to say:

“I don't agree yet, and here is why.”

That is much better than passive compliance followed by quiet resistance.

Once the decision is made, act like a team

Debate before the decision. Afterwards, leadership needs alignment. That does not require pretending everybody privately loves the outcome. It means not undermining it afterwards. If the team decides something and one leader leaves the room telling their department:

“I didn't agree with this, but apparently we have to do it.”

what happened? The decision has already been weakened. Leadership-team accountability includes responsibility for how collective decisions are carried into the organisation.

Don't let the CEO rescue the team from accountability

This is another version of catching the problem ball. Two leaders have an issue. They both go to the CEO. CEO decides. Problem solved. Except neither leader learned how to resolve the issue together. Next time, back to the CEO. If the matter can reasonably be resolved between them, ask:

“What have you two discussed?”

“Where exactly do you disagree?”

“What do each of you recommend?”

“What does the business need?”

Keep the thinking with the leaders where possible. Otherwise the CEO becomes the permanent referee of the leadership team.

The CEO must be accountable too

Nothing destroys an accountability culture faster than a leader who exempts themselves. If the CEO says commitments matter but repeatedly misses their own commitments, everyone notices. If everybody else has to prepare for meetings but the CEO does not, everyone notices.

If leaders are expected to take challenge but the CEO reacts badly when challenged, everyone notices. The standard has to apply upwards too. A strong leadership team should be able to ask the CEO:

“You committed to that last week. Where is it up to?”

That is not disrespect. That is a functioning accountability system.

Recognise reliable follow-through

Accountability should not only appear when somebody misses. Notice the leaders who repeatedly deliver. The person who raises a risk early. The leader who comes prepared. The person who says:

“I said Friday. It was done Friday.”

Those behaviours make the whole team easier to work in. Reliability reduces chasing. Reduces uncertainty. Reduces workarounds. It builds trust. Say so.

Make preparation part of accountability

A leadership meeting is not the place to discover for the first time what has happened in each function. Ask leaders to prepare beforehand. What happened against commitments? What is on track? What is off track? What patterns are emerging? Where is a decision needed? What do they recommend?

Now meeting time can be used for thinking and deciding. If preparation is repeatedly optional, meetings become long reporting sessions. And the CEO becomes the person dragging information out of everyone. Again.

Use the scoreboard as shared evidence

Peer accountability improves when everybody can see the score. Not hundreds of measures. A useful handful. Where are we winning? Where are we not? What changed? What requires attention? Then the leadership team asks together: What does this mean? What are we going to do? Who owns it? This moves accountability away from:

“The CEO isn't happy.”

towards:

“The evidence says we have a gap.”

Much healthier.

Peer accountability requires trust

People will not challenge each other well if every challenge becomes personal. Trust is not everybody being nice. It is confidence that: we can tell the truth; we can disagree; we can admit a miss; we can challenge something; and the relationship will survive. Without that, accountability becomes either aggression or avoidance. Neither is particularly useful.

Learn to distinguish challenge from attack

A useful accountability question might be:

“You committed to Wednesday. What happened?”

An attack sounds more like:

“You never deliver anything on time.”

One is about the commitment. The other is a judgement about the person. Keep the conversation around facts, standards, actions and patterns. If there is a repeated pattern, name it. But build the case with evidence.

Don't tolerate the untouchable leader

Sometimes one leadership-team member is commercially strong or long-serving and everybody knows normal rules do not quite apply. They interrupt. Do not prepare. Ignore actions. Undermine decisions. Perhaps they hit their numbers, so nobody says much. That damages peer accountability enormously.

Because why should anybody hold the line if the team visibly has two sets of standards? Consistency matters at the leadership table first.

Ask whether the team is willing to protect its own standard

This is a useful test. If someone repeatedly behaves below the team's agreed standard, who addresses it? Only the CEO? Or will another leader respectfully say:

“That's not what we agreed.”

That is where a leadership team starts behaving like a team rather than a collection of individuals who happen to attend the same meeting.

A practical peer-accountability rhythm

A simple structure helps.

Before the meeting

Each leader reports briefly:

• progress against commitments;
• key numbers;
• what is off track;
• emerging issues;
• decisions required;
• recommendations.

At the meeting

Review:

• the score;
• wins;
• misses;
• recurring patterns;
• choke points;
• decisions.

For every action

Agree: What? Who? By when? What does done mean?