The thing that never gets assessed
When a deal closes, the real work begins.
Legal completion. Integration admin. Banking covenants. Getting properly into the numbers. Clarifying the Value Creation Plan. The first weeks post-deal are full of motion.
What almost never gets the same quality of attention is the executive team itself.
Not the individuals. Those assessments usually happened during diligence.
The thing they will form together.
That omission matters. A group of capable executives is not the same thing as a leadership team. Yet many PE-backed businesses behave as if it is. Put a credible CEO, a strong CFO, a hungry CRO and a capable COO in the same room and surely alignment will emerge.
It often does not.
As Richard Hackman, whose research on team effectiveness remains the most rigorous in the field, once put it:
“I have no question that a team can generate magic. But don’t count on it.”
What the exec team is actually for
The executive team has a specific job that no function can do alone.
Its purpose is not simply to maximise profit. That is an outcome. The executive team exists to make the cross-functional decisions and trade-offs that require the whole business to align. To allocate resources across competing priorities. To resolve tensions between growth, margin, capacity, risk and timing. To build the conditions in which the Value Creation Plan can actually be executed.
As AI accelerates the pace and complexity of those decisions - where to invest, what to automate, which capabilities to build before the window closes - the cost of a poorly functioning exec team is rising.
That is a harder job than most teams realise.
And it requires more design than most firms give it.
Where the leverage actually sits
Richard Hackman, Ruth Wageman and, more recently, Colin Fisher point to a finding that should make any investor or chair stop and think.
60% of team effectiveness is determined by structural choices made before the team ever meets.
30% is determined by how the team is launched.
10% comes from coaching and intervention once the team is already underway.
Most firms spend most of their energy on the 10%.
That is the mistake.
When the executive team starts to wobble, the instinct is to intervene in motion. Coach the CEO. Challenge the CFO. Run the offsite. Facilitate the difficult conversation. Sometimes those things help. But they are often attempts to repair halfway through the journey, a team that was never properly designed at the start.
What gets set early
Fisher makes the structural issue concrete. Four things matter disproportionately.
Composition: the most neglected pillar
Most executive teams are assembled, not designed. A firm backs a CEO it trusts. It brings in a CFO from a previous deal. It hires a commercial leader from outside. The operations lead was already there. Functional boxes get filled through familiarity, availability and urgency.
Almost nobody works backwards from the Value Creation Plan to ask what kind of executive team it will actually require.
PE is good at selecting for track record, credibility and pace. It is far less good at designing for collective intelligence. The result is often a room full of impressive individuals and a mediocre team.
Most firms think about composition as functional coverage. The better ones also think carefully about diversity: gender, background, nationality. That matters and should not be an afterthought. But Fisher is clear that for collective performance, diversity of representation needs to be accompanied by diversity of thought - differences in what people know, how they think, and what they are willing to say. A leadership team where everyone has come up through similar organisations and reached similar conclusions is a team with a dangerous blind spot - not because of who they are, but because of what they share.
Fisher’s research also points to something most PE hiring processes rarely assess: social sensitivity - the capacity to read others, notice who hasn’t spoken, and pick up on what isn’t being said. It is one of the strongest predictors of how well a group thinks together. A team of brilliant individuals with low social sensitivity will consistently miss what is in the room.
Without that range, dysfunction gets misread as personality. The problem is not always that the CFO is difficult or the CRO political. Sometimes the team was simply built for individual credibility rather than collective performance.
Goals: the alignment that isn’t
Purpose is why the team exists as a collective. Goals are the outcomes that it must deliver together. Fisher is right that goals need to be clear, challenging and - critically - important. That final word is where the two connect. Without a shared sense of what matters and why, goals become functional targets rather than collective commitments.
Most exec teams would say they are aligned. Ask them separately - without the others in the room - what the team’s single most important collective priority is right now, and the answers will rarely match. Not because anyone is wrong. Because each person is answering a slightly different question shaped by the pressures they feel most directly.
The CEO is thinking about the exit story and whether the business is growing fast enough to hold the multiple. The CFO is thinking about covenant headroom and what happens if growth slips. The CRO is thinking about pipeline quality and whether the numbers are real. The COO is thinking about whether the operation can hold if the CRO delivers what they are promising.
All legitimate. All pointing in slightly different directions. All shaped by the pressures of the function rather than the needs of the team.
The CRO pushes volume. The CFO protects cash. The COO protects delivery. The CEO assumes the tension will somehow resolve itself in the weekly meeting.
It usually does not.
That drift often stays hidden for a while. Then it shows up all at once as a missed quarter, an overstretched operation, or a strategy that looked coherent on paper but incoherent in practice.
Tasks: the work no single function can do
A senior team whose collective task is reduced to reviewing functional updates has a badly designed task. It does not force interdependence. It does not require the team to think as a team. Fisher is clear that real team tasks need to be whole, visible and meaningful - people should see the work from beginning to end and understand its impact. Most exec team meetings are not designed that way.
Real executive team work looks different. Consider a decision most PE-backed businesses face: the growth engine is working but the business is starting to strain. Do you invest ahead of the curve - in product, headcount and operational infrastructure - or do you protect margin and let the model prove itself first?
No single function can answer that. The CFO can model the trade-offs but cannot assess what the market will bear. The CRO knows what customers want but cannot judge what the operation can absorb. The COO can see where the business will break but cannot determine whether the competitive window will still be open if they wait. None of them can make that call alone - and the CEO cannot make it well without all three thinking together openly, with their real concerns on the table rather than the version that protects their function.
There is a point here that most team development misses. The conventional assumption is that you build trust first - the offsite, the exercises - and then work effectively together. Fisher challenges that directly. Social cohesion is as much a result of effective cooperation as a cause of it. You build trust by doing real work together, not by simulating it. The first real cross-functional decision builds more psychological safety than any offsite.
Norms: the invisible rules running the room
Norms are the invisible rules of the room. Who speaks first? Who defers. What challenge sounds like here? What happens when someone raises an uncomfortable truth? Nobody declares these rules. They emerge early and harden quickly.
The team does not experience them as rules. It experiences them as normal.
The leader’s job is to make the invisible visible. To say out loud what the room is doing without realising it.
“I notice we never really challenge the revenue forecast in this meeting. What is that about?“
That question does more structural work than a values workshop. Once a norm is named, it can be examined. Until then, it keeps running the room.
Why launch matters so much
The first meetings of an executive team do more than cover agenda items. They teach the group how this team works.
If awkward truths are softened early, they will keep being softened. If the challenge gets closed down too quickly, apparent harmony starts to matter more than real clarity. If the revenue forecast is never really tested, silence around it becomes normal.
By the time the executive team feels political, performative or strangely careful, those patterns have usually been rehearsed for months. You cannot coach your way out of a norm that the group keeps recreating every week.
The missing document in many PE-backed businesses is not another performance plan for an individual.
It is a team development plan for the executive team itself.
Why replacing people often fails
Executive teams are not machines. They are complex systems. Change one part and the rest of the system responds.
Replace the CFO, and you do not just improve finance. You change the chemistry of the room. The CEO may tighten control. Another executive may withdraw. A political balance shifts. Sometimes the change helps. Sometimes it simply produces a new version of the old pattern.
The problem was never just the person. It was the conditions inside where the person was operating. Change the person without changing the conditions, and the conditions tend to win.
The implication is not that people changes are wrong. It is that the highest-leverage work that starts earlier.
Before the first difficult quarter. Before the first silent meeting. Before the first awkward truth gets edited.
The question beneath the plan
The norms nobody named. The purpose assumed rather than built. The composition choices made through urgency rather than design. The goals set without the conversation about why they matter.
These things travel. What the executive team teaches itself about what truth costs here - who speaks, who edits, whether challenge is welcomed or managed - those lessons move through the organisation without anyone deciding to pass them on.
Nobody chose the pattern. By the time anyone names it, everyone is already living inside it.
A group of executives is not a leadership team.
And if you want one, you have to design it.