How Do I Know Whether My Leadership Team Is Actually Working as a Team?

The first test: business first

Do people come into the room primarily representing their department? Or do they come in thinking about the whole business? Sales. Operations. Finance. People. Each function matters. But around the leadership table, the standard needs to be broader:

“What is best for the business?”

If everyone only advocates for their own patch, the CEO remains the only person joining the pieces together. That is not much of a leadership team. The second test: can they challenge each other? A healthy team can disagree. Directly. Professionally. In the room. They can say:

“I don't think that will work.”

“I think we're missing something.”

“The evidence doesn't support that.”

“I disagree with the recommendation.”

That is useful. The problem is not disagreement. The problem is when disagreement goes underground.

False harmony is not teamwork

Some leadership teams look calm. Everyone is polite. Nobody challenges. Meeting ends. Then the real conversation begins in the corridor. Or on Teams. Or in private calls.

“I knew that would never work.”

“I didn't agree with any of that.”

“Operations always does this.”

That is not harmony. It is avoidance. If the issue belongs in the room, bring it into the room.

Challenge ideas, not people

Direct debate does not mean aggression. There is a difference between:

“I don't think the proposal deals with the risk.”

and:

“You never think these things through.”

One challenges the idea. The other attacks the person. A strong leadership team can be robust without becoming personal. The third test: can they make a decision? Some teams are excellent at discussion. Less good at deciding. They analyse. Explore. Debate. Add context. Then the meeting drifts on. A functioning leadership team needs to be able to say:

“This is the decision.”

Then move into execution. The fourth test: what happens after the decision? This may tell you more than the meeting itself. The team debates. A decision is made. Then one manager goes back to their department and says:

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

What happened? The collective decision has already been weakened. You do not have to pretend you personally preferred the outcome. But once the leadership team has made a legitimate decision, leadership requires professional support afterwards. Debate before. Alignment after. That is the discipline.

Before the decision: challenge; question; bring evidence; argue the case. After the decision: lead it. If circumstances change, bring the issue back. Do not quietly undermine the agreement. The fifth test: can they hold each other accountable? Does accountability always travel through the CEO?

Or can one senior leader say to another:

“You committed to that by Friday. What happened?”

without everybody becoming uncomfortable? A real team gradually develops peer accountability. The promise was made to the team. The team can come back to it.

If only the CEO can challenge a miss, accountability is still vertical

That means everyone reports upward. The next stage is horizontal accountability. People feel answerable to each other because their work is interdependent. That is much stronger. The sixth test: do they solve problems with each other? Two leaders disagree. What happens? Do they talk?

Or do both go separately to the CEO? If the CEO is permanently mediating between senior managers, the team may not be functioning independently enough. Ask:

“What have you two discussed?”

“Where exactly do you disagree?”

“What does the business need?”

Senior leaders should increasingly resolve ordinary tension directly.

The CEO should not be the permanent referee

If every cross-functional issue comes upward, the CEO becomes: arbitrator; translator; decision-maker; relationship counsellor; court of appeal. That creates dependence. A strong leadership team reduces, rather than increases, that burden.

The seventh test: do they trust each other enough to tell the truth? Trust is not everybody liking each other. It is confidence that people can: raise a concern; admit a miss; challenge a proposal; say they do not understand; change their mind; and the relationship survives.

Without that, teams become political. People protect themselves. Information gets edited. Problems arrive late. That weakens everything.

Trust and accountability belong together

Too much challenge without trust becomes aggression. Too much trust without challenge becomes comfortable underperformance. Strong teams need both. We can tell each other the truth. And we can rely on each other afterwards. The eighth test: do they prepare?

A leadership team is not working particularly well if every meeting begins with people discovering what is happening for the first time. Senior leaders should come prepared. What happened? What does the evidence say? What is off track? What decision is needed? What do they recommend?

Preparation respects everybody else's time. The ninth test: do they bring thinking? Not:

“We've got a problem.”

But:

“Here's the issue, here's the evidence, here are the options, and this is what I recommend.”

That is leadership-team contribution. People should not merely transport operational problems into the room and wait for somebody else to solve them. The tenth test: do they know the score? Does the leadership team have a shared view of how the business is performing?

Or does each function bring its own version? A useful scoreboard gives the team common evidence. Where are we winning? Where are we off track? What changed? Where does the team need to think? Shared evidence improves shared leadership. The eleventh test: do they understand each other's dependencies?

Does Sales understand what Operations needs? Does Operations understand customer consequences? Does Finance understand what its decisions do downstream? Does each leader know what another function depends upon them for?

A team cannot work well if each person understands only their own box on the organisational chart. The twelfth test: are commitments visible? Meeting ends. Can everyone answer: What was decided? Who owns what? By when? What does done mean?

If not, the team may have had an excellent conversation but a weak execution system. The thirteenth test: do they come back to those commitments? The next meeting should connect with the previous one. What happened? What was completed? What slipped? What changed? What did we learn?

If the team continually starts fresh, commitments lose meaning. The fourteenth test: can people say “I got that wrong”? This is a strong sign of maturity. Can a leader say:

“I made the wrong call.”

Or:

“That evidence changes my view.”

Or:

“I should have raised that earlier.”

Without needing a ten-minute defence? Teams become much stronger when people can own mistakes without feeling that every admission reduces their status. The fifteenth test: does the same standard apply to everyone? Including the CEO. Does everybody prepare? Everybody keep commitments?

Everybody accept challenge? Everybody follow agreed processes? If one powerful person is exempt, the team learns that standards are conditional. That damages trust quickly. The sixteenth test: do they protect the team outside the room? Senior leaders can damage each other very easily.

A manager leaves the leadership meeting and criticises another leader to their own team. Now the organisation learns that the leadership group is fragmented. Disagreement belongs where it can be resolved. Not as departmental entertainment afterwards.

Do not demand artificial loyalty

Protecting the team does not mean hiding serious misconduct or pretending poor decisions are good. It means dealing with concerns in the right place. Directly. Professionally. With the people who can do something about them. The seventeenth test: can they put ego aside?

Leadership-team decisions sometimes mean: your idea does not win; your department does not get the resource; someone else has the better proposal; you need to change your view. Can leaders handle that? If every disagreement becomes a status contest, teamwork becomes exhausting.

The eighteenth test: do they care when another function fails? A weak team thinks:

“Not my department.”

A stronger team thinks:

“How does this affect the business, and is there something useful I can do?”

Not interference. Shared responsibility. The nineteenth test: do they avoid collective ownership without named owners? A team can collectively care about an outcome. But actions still need one owner. “We all own this” can become:

“Nobody owns the next step.”

A functioning team knows the difference. The twentieth test: do they solve recurring friction? If Sales and Operations have the same argument every month, a good leadership team eventually asks:

“What system needs changing?”

Do not turn recurring dysfunction into a standing agenda item. Fix the cause.

Use conflict as data

Repeated conflict may tell you: responsibility is unclear; incentives conflict; information is missing; decision rights overlap; standards differ; or trust is poor. Do not only manage the argument. Understand the system underneath it.

A leadership team should make the business calmer

This is an interesting test. As the leadership team matures, does the business beneath it become clearer? Decisions faster? Responsibilities clearer? Problems addressed earlier? Less politicking? Fewer issues requiring the CEO? If not, what exactly is the leadership team producing?

Meetings are not evidence of teamwork

Meeting regularly is useful. But meeting attendance is not the outcome. The question is: What becomes better because this group works together? Strategy? Execution? Decision quality? Cross-functional coordination? Leadership capability? That is what matters.

You should hear the word “we” more often

Not in a cheesy way. In the thinking.

“We agreed.”

“We missed this.”

“We need to fix the handover.”

“We haven't made the standard clear enough.”

That is different from:

“They need to sort themselves out.”

Watch for factions

Leadership teams can develop alliances. Sales and Marketing against Operations. Owner and Finance against everybody else. Long-serving managers against newer leaders. That is dangerous. Debate should follow issues. Not permanent camps.

Do not use consensus as the definition of teamwork

Strong teams will not agree on everything. Nor should they. The objective is not unanimous enthusiasm. It is enough constructive debate to improve the decision, followed by clarity about what happens next.

Sometimes the leader has to decide

Not every issue needs consensus. The CEO may ultimately own the decision. Fine. But good leadership teams still improve the quality of that decision by bringing evidence and challenge. Then everyone understands how the decision was reached.

Make behavioural expectations explicit

A leadership team benefits from agreed standards such as: Business first. Prepare. Challenge directly. Bring evidence. Bring recommendations. Do what you said you would do. Support decisions once made. Address concerns in the room. Own your contribution. Protect the leadership team's credibility outside the room. Now teamwork has behavioural meaning.

Review the team against its own standard

Occasionally ask: How are we actually going? Not financially. As a leadership team. Where are we strong? Where do we still avoid? Who dominates? Where is trust weak? Which commitment keeps being broken? Which behaviour have we agreed matters but continue tolerating? That conversation itself can be valuable.

Ask team members to score themselves

Self-assessment can reveal interesting gaps. Business-first thinking. Trust. Direct debate. Ownership. One-team behaviour. Proactive problem-solving. Follow-through. Then discuss the evidence behind the score. Not:

“I think we're green.”

Why? What behaviour supports that?

Evidence matters here too

Do not assess the team from mood. Look at what actually happens. How many commitments are completed? How often are actions rolled? Are issues raised in the room? Are cross-functional problems resolved? Does the CEO still mediate constantly? Are decisions supported afterwards? That tells you much more.

The leadership team should develop each other

This is an advanced sign. Feedback and challenge do not flow only from the CEO. Peers help peers think. Someone asks a better question. Challenges an assumption. Shares useful experience. Recognises strong leadership behaviour. Now the group itself becomes developmental.

The team should be able to function when the CEO is absent

Another useful test. If the CEO misses one meeting, does the whole system collapse? Does nobody know what to do? Or can the leadership team still: review the score; make appropriate decisions; agree actions; and follow through? If it cannot, too much capability may still sit at the top.

A practical leadership-team test

Ask these questions:

Business first

Do we make decisions for the whole business?

Direct debate

Can we disagree in the room? Trust Can we tell each other uncomfortable truths? Evidence Do we discuss facts rather than departmental folklore? Decisions Do conversations reach clear conclusions? Alignment Do we support decisions afterwards? Ownership Does every action have one owner? Follow-through Do commitments mean something?

Peer accountability

Can we challenge each other without waiting for the CEO?

Cross-functional leadership

Do we understand and manage dependencies? Learning Do we improve systems when problems recur?

CEO dependence

Are fewer ordinary leadership issues requiring the CEO? If those things are strengthening, you are probably building a genuine leadership team.