How to run a leadership team as a team, not a group of directors

The common problem

Most leadership teams are not really teams. They are a group of senior people who each run a part of the organisation.

That sounds similar, but it is not.

A group of directors meets to update each other. A leadership team meets to make the whole organisation work better. The difference shows up in the agenda, the behaviour, and the decisions that get made.

In a group of directors, people tend to:

• Represent their own function first
• Bring updates rather than dilemmas
• Negotiate for budget, people, and attention
• Avoid conflict to preserve working relationships
• Leave the room and continue solving things locally

This can feel efficient, but it creates a slow organisation. Cross-functional issues drag on. Priorities compete. Teams receive mixed signals. Strategy becomes a set of departmental plans stitched together after the fact.

What a real leadership team is for

A leadership team should not be a status meeting for senior people. It should be the place where the most important shared work happens.

That usually means:

• Setting and protecting a small number of organisation-wide priorities
• Making trade-offs across functions
• Removing systemic blockers that teams cannot solve alone
• Looking ahead at risks and opportunities
• Building the conditions for people to do good work
• Holding each other to account for the whole, not just the parts

This requires a mindset shift. Each leader still has a functional role, but in the leadership team they have a second role: steward of the wider organisation.

If that second role is weak, the team will default to local optimisation. Sales will push for speed. Operations will push for stability. Finance will push for control. Product will push for focus. All of these views matter, but none should win by default.

The leadership team exists to integrate these tensions, not pass them down the organisation.

Change the agenda

If you want different behaviour, start with the meeting design.

Many leadership agendas are built around functional updates. This reinforces the idea that each director owns a slot, gives a report, and receives questions.

A stronger agenda is built around shared outcomes and decisions.

For example:

• What are the top three organisation-wide priorities this quarter?
• Where are we creating conflicting demands for teams?
• Which decisions are stuck because they cut across functions?
• What risks are we not discussing openly enough?
• What do we need to stop, pause, or simplify?

Updates can still exist, but they should be short and mostly shared in advance. Meeting time should be used for judgement, challenge, and commitment.

A useful rule is simple: if one director can solve it alone, it probably does not need leadership team time.

Make conflict productive

A leadership team that avoids conflict will push conflict into the organisation. Teams then have to interpret unclear priorities, manage competing requests, and absorb the cost of senior disagreement.

Productive conflict is not about being aggressive. It is about putting real tensions on the table early enough to do something useful with them.

Leaders should be able to say:

• “These two priorities are competing for the same people.”
• “We are saying this matters, but our investment says otherwise.”
• “My function benefits from this, but I think it hurts the whole.”
• “We have not made a decision. We have only delayed the argument.”

This kind of honesty needs trust, but it also builds trust. People trust leadership teams that deal with reality.

Create shared accountability

The biggest test is what happens after the meeting.

In a group of directors, people leave with different interpretations. They brief their teams through a functional lens. The organisation hears several versions of the same decision.

In a real leadership team, leaders leave with a shared line. They may have disagreed in the room, but once a decision is made, they explain it consistently and own the trade-offs together.

Shared accountability can be strengthened by agreeing:

• The few outcomes the leadership team owns together
• The decisions that require collective commitment
• The behaviours expected inside and outside the room
• How the team will review whether decisions are working
• What happens when leaders undermine agreed priorities

This is not about forced harmony. It is about clarity.

Start with one practical reset

You do not need a major transformation to begin. Try this in the next leadership meeting:

• Remove half the updates
• Ask each leader to name one cross-functional tension that needs attention
• Pick the one that matters most
• Work it through to a clear decision or next step
• Agree the message everyone will take back to their teams

Then repeat.

Leadership teams become teams through practice. Not through titles, away days, or new reporting packs. The work is to keep choosing the whole organisation over the comfort of separate domains.