Leadership Team Effectiveness: When Senior Leaders Don't Lead as a Team (And How to Fix It)
- 23 minutes ago
- 9 min read
What Good Looks Like: Signs of Strong Leadership Team Effectiveness
When senior leaders reach the upper echelons of an organisation, technical competence is rarely the issue. The real question is the one that keeps CEOs awake is how to transform a collection of accomplished individuals into a single, coherent force.
The usual pattern is familiar. Finance knows finance. Operations knows operations. Risk knows risk. Each leader is credible, busy and accountable for a particular stretch of ground. Their meetings are often polite, informed and productive enough to pass as alignment. Yet when a difficult decision crosses boundaries, the conversation becomes careful. People protect their territory. They wait for complete certainty. The most senior person in the room ends up joining the dots.
That is not a failure of character. It is the natural outcome of how most senior teams are assembled. Organisations promote depth of expertise, then assume shared purpose will do the rest. It will not. A leadership team has to be built with as much intention as any other operating system.
The question is not whether your leaders are strong. The question is whether they lead together when the work becomes ambiguous, political or inconvenient.
What We Have Learned
I have spent more than two decades in rooms with senior leaders across Asia Pacific. Boardrooms, offsite venues, hotels with bad coffee and excellent views. Across all of it, one thing has remained consistent.
The higher you go, the lonelier leadership gets — and the harder it becomes to find people who will tell you something true. Senior leaders are rarely short of competence. What they are often short of is honest company. People who will sit in the same discomfort, name the same tensions, and commit to something together rather than simply nodding in the direction of alignment and returning to their separate lanes.
This happens when organisations build teams of exceptional individuals and assume that proximity will eventually produce cohesion. It rarely does. Not without design.
Here is what we have learned about building the real thing.
1. Begin with the Work Beneath the Work
The first task is not to gather people in a hotel meeting room and hand them a framework. It is to understand what is already happening between them.
When we were invited to work with a senior leadership team at a large multinational — twelve leaders with formidable experience operating across a demanding environment — we did not begin with an agenda. We began with listening.
In the weeks before the workshop, we conducted a pre-programme diagnostic: individual conversations, a carefully constructed survey, and a quiet read of the organisational context. By the time the team arrived, we already understood what each person was carrying. The pressures particular to their role. The dynamics that shaped how they showed up. The questions they had not yet had space to ask aloud.
A senior leader should not have to spend the first hour explaining who they are and what their world looks like. That is an extraordinary waste of their time — and ours. When the groundwork is done properly, the first conversation in the room can begin somewhere genuine. The trust that usually takes days to build can begin to form within hours.
2. Make Psychological Safety Useful
Psychological safety is often treated as a soft subject. It is not. In a senior team, it is the practical condition that allows people to say: "I do not agree", "I do not understand", "This will not work", or "We have missed something."
The test is not whether the room feels warm. The test is whether people can make a difficult contribution without needing to first calculate the political cost.
In one recent engagement, the team we worked with consisted of deep specialists who had been operating in adjacent lanes for some time without ever quite merging. Each person was exceptionally capable within their own territory. Each person, perhaps instinctively, reluctant to wander into someone else's.
There was something else present too. A quality of weariness that had nothing to do with the individuals themselves and everything to do with the operating environment. These were people navigating genuine complexity — priorities shifting before previous ones had closed, new demands arriving before old commitments had resolved. Not resistance to change. Something more honest than that. An anticipatory tiredness.
We spent the first part of the morning on something that sounds deceptively simple. We asked people to share something true. Not a professional biography. Not a strengths inventory. Something closer to the story beneath the story — the values, the formative moments, the reasons that brought each person into the work they do. The kind of conversation that does not usually happen in a leadership team because there is always something more urgent on the agenda.
It did not take long before the room shifted. Leaders who had sat in meetings together for months began to hear each other in a different register. The professional composure softened, not into vulnerability for its own sake, but into something more useful: genuine recognition. People began to see not just what their colleagues did, but something of who they were.
In strong teams, leaders learn what sits behind one another's professional styles. The quiet person may be exercising rigour, not disengagement. The direct person may be carrying the consequences of a risk nobody else has seen. The leader who appears to challenge everything may be trying to protect a standard that matters.
When people understand the intention behind a colleague's behaviour, they stop inventing the worst explanation. That alone can change the quality of a team's conversations.
3. Replace Consensus with Clear Decision Practice
Many senior teams have no shortage of discussion. What they lack is a shared discipline for deciding.
Consensus has its place. It is not, however, a substitute for a decision. When every voice must be fully persuaded before a team moves, urgent work drifts and accountability becomes hazy. People leave the room believing something has been agreed, only to discover that nobody has the authority, the deadline or the courage to act.
When the team we worked with began grappling with how they make decisions together — the tendency to circle rather than commit, the consensus-seeking that can masquerade as rigour — the conversation that followed was not theoretical. It was grounded in the shared recognition of people who had navigated the same terrain.
A useful decision practice answers four questions:
What decision is needed?
Who owns it?
What information is sufficient?
By when will we move?
The best teams are not reckless. They use the best available information, make the call, and adjust when new evidence appears. Mature leadership includes the ability to course-correct without treating every change of mind as a loss of face.
4. Protect Momentum by Closing What You Start
In high-change organisations, fatigue rarely comes from hard work alone. It comes from unfinished work.
A new priority arrives before the previous one has been settled. A decision is made but not translated into action. A piece of improvement work is announced, then swallowed by the next urgent matter. Over time, the team becomes understandably cautious. Not because it resists change, but because it has learned that not every commitment survives the calendar.
Leaders need a visible habit of close-out. What did we commit to? What has moved?
What is blocked? What now needs to be deliberately stopped, rather than quietly abandoned?
Momentum is not speed for its own sake. It is the confidence that work will be carried through.
5. Create Accountability That Runs Across the Table
The moment after a leadership session is usually where good intentions go to die. People return to full inboxes, familiar pressures and the normal hierarchy of urgent things. The team may feel closer, but closeness is not the same as changed behaviour.
This is why follow-through must be designed at the start, not added as a hopeful afterthought. The team needs a small number of observable commitments, an agreed rhythm for checking progress, and evidence of what has changed in practice.
We did not present the team with a framework and ask them to adopt it. We helped them build their own. Over the course of the workshop, they identified the specific commitments they needed to make — not as individuals, but as a collective leadership voice. How they would move decisions forward. How they would maintain momentum when complexity pushed back. How they would adapt their ways of working without losing the clarity they had begun to build together.
Each commitment was authored by the team. Each was anchored to a concrete, measurable action. Each was signed by every member of the Leadership Team.
Then came the part that separates a development engagement from a development event. A forty-five day accountability window. Specific evidence to bring to the follow-through session. Not a general reflection. Evidence. What was done, what was learned, and what the team intends to do differently.
The follow-through session — a full day, held in a different city — is not a debrief. It is a reckoning. The team speaks first. The leader responds last. This is deliberate. The accountability runs horizontally through the team, not only upward to the sponsor.
This is what a ninety-day arc of development looks like when it is designed properly. Not a workshop followed by good intentions. A journey with checkpoints, evidence, and consequences.
What Genuine Progress Looks Like
When the work is done properly, something shifts that is difficult to manufacture.
One of the most senior people in the room — someone who had walked in carrying the particular stillness of a leader who has seen a great deal — said something quietly at the end of our programme that has stayed with me:
"I am taken aback by how aligned we actually are — and how we can play on each other's strengths."
That is the moment we are always working toward. Not the framework on the slide. The realisation in the room.
The participant feedback, collected independently and aggregated anonymously, returned an overall score of 4.58 out of 5.00 across twelve participants and ten assessment criteria. Ninety-eight percent of all ratings fell at Agree or Strongly Agree. Not one negative rating was recorded across any criterion or any participant.
What struck me most in the open-ended responses was not the praise, warm as it was. It was the nature of the suggestions. The team wanted more time. More depth. More of the team-based work. They were not asking for something different. They were asking for more of what they had begun.
Three quarters of participants indicated openness to continued individual coaching as part of their leadership development. That quality of readiness is not something a programme can manufacture. It is what genuine psychological safety — built carefully, over time — makes possible.
How to Know If This Describes Your Team
Consider whether any of these sound familiar:
Your team meetings are polite, but difficult topics are raised in corridors afterwards
Decisions take longer than they should because people wait for complete certainty
Leaders protect their own functions rather than advocating for the collective good
The most senior person in the room ends up making most of the decisions
Strategic priorities are announced but never quite closed out
New initiatives arrive before previous ones have been completed
People are exhausted, but it feels like it is from unfinished work, not hard work
If more than two or three of these resonate, your team is functioning as a collection of talented individuals rather than a true leadership team.
What Good Looks Like
A healthy senior leadership team does not avoid tension. It knows how to use it — with candour, trust and a shared responsibility for what happens next.
In strong teams:
People say what they think because they trust the intention behind the conversation
Decisions are made with the best available information and adjusted when new evidence appears
Accountability runs across the table, not just upward to the leader
Work gets closed out — commitments survive the calendar
Difficult conversations happen in the room, not in corridors afterwards
The Difference in a Nutshell
Senior leadership team work is not complicated to describe. It is extraordinarily difficult to do well.
The difference, in our experience, lies in three things:
The depth of preparation before the room — so that what happens inside it is not a cold start, but a continuation of something already begun.
The quality of facilitation in the room — not the kind that manages a process, but the kind that holds a space in which something true can be said.
The rigour of accountability after the room — because without it, the best facilitated day in the world produces nothing more durable than a warm memory and a set of good intentions.
A Question for Your Leadership Team
When a cross-functional decision lands on the table, does your team become more useful together — or does everyone retreat to their own patch of expertise?
That answer will tell you more about team effectiveness than any annual survey.
Is Your Leadership Team Ready for What's Next?
The Performance Edge Programme is a leadership team effectiveness programme built for senior teams navigating exactly this. Diagnostic-led. Grounded in how real leadership teams actually function.
If this piece resonated, it's worth a conversation. petadiri.com — or reach out directly to explore what this could look like for your team.
Trusted by organisations across Malaysia and Singapore:
