The Missing Middle of Change: Why Teams Matter More Than We Admit

Most change initiatives start with good intentions.  A new AI tool to boost productivity. A new sales reporting system to improve visibility. A new product launch designed to unlock growth. Leaders invest time in strategy, process design, training plans, and executive alignment. There is often a strong focus on the individual. What skills do people need? How do we reduce personal resistance? How do we incentivise adoption?
And yet, despite all this effort, change still fails more often than it succeeds.

One reason is surprisingly simple. We forget the team. Classic change management frameworks focus on four levels: the process, the individual, the region or function, and the organisation as a whole. Somewhere along the way, the team, the unit where people actually do their work day to day, gets lost. That omission matters more than most leaders realise.

Teams are where change actually shows up.
People do not experience change as abstract strategy. They experience it in weekly meetings, shared targets, handovers with other teams, and informal norms about what “good” looks like. The team is where new tools are either embraced or quietly worked around. It is where new KPIs are interpreted, compared, and sometimes resisted. It is where people decide whether this change helps them succeed or makes their lives harder.

Research consistently shows that teams are the strongest predictor of how individuals feel at work. Google’s Project Aristotle found that team dynamics, not individual talent, were the biggest driver of performance. Gallup data shows that engagement is far more correlated with immediate team experience than with organisational vision statements. Yet when change is rolled out, teams are rarely treated as a first-class stakeholder.

The issue is rarely a lack of intelligence or effort. It is a lack of alignment at the level where work actually happens.

The overlooked questions teams are asking
When a new system or way of working is introduced, teams quickly start asking questions. These questions are rarely voiced explicitly, but they shape behaviour:

• What does success look like for us now?
• Do our KPIs still make sense, or are we being measured on outdated assumptions?
• Does this change strengthen our position in the organisation or weaken it?
• How does this affect our dependency on other teams, and theirs on us?
• Are we expected to take on more risk, more visibility, or more accountability?

If these questions are not addressed, teams fill in the gaps themselves. Often that means protecting existing ways of working, minimising exposure, or quietly deprioritising the change in favour of what they know will be rewarded.

Why focusing only on individuals is not enough
Many change programmes assume that if you win over individuals, the change will follow. In practice, individuals take their cues from the team. If the team is sceptical, overloaded, or unclear about how the change benefits them collectively, even enthusiastic individuals will hesitate.

There is a well-established concept in behavioural science that norms drive behaviour more powerfully than instructions. Teams create norms. They decide what gets attention, what gets escalated, and what gets ignored. When change clashes with team norms, the norms usually win.

This is one reason why McKinsey has repeatedly found that around 70 percent of transformation efforts fail to deliver their intended outcomes. The issue is rarely a lack of intelligence or effort. It is a lack of alignment at the level where work actually happens.

What it means to engage the team, not just the individual
Engaging teams does not require complex frameworks or heavy process. It requires asking different questions and designing change with the team in mind.

First, teams need a shared narrative about why the change matters to them, not just to the organisation. How does this make the team more effective, more valued, or more resilient?
Second, teams need clarity on how success is defined. If KPIs, incentives, or performance reviews lag behind the change, teams will optimise for the old system. Updating metrics is not administrative hygiene. It is a signal of seriousness.

Third, teams need space to shape how the change shows up in their context. A sales team, a product team, and an operations team will experience the same change very differently. Allowing teams to adapt the “how” without undermining the “what” increases ownership and reduces resistance.

Finally, teams need recognition. When teams feel that change is something done to them, it breeds compliance at best. When they feel it is something they helped build, it becomes part of their identity.

Win the team, and the change sticks

Win the team, and the change sticks
There is a simple but often ignored truth. Win over the team, and you usually win over the individuals within it. When a team believes a change improves their collective success, resistance drops, adoption accelerates, and the change becomes harder to reverse.
Change that engages teams does something powerful. It shifts ownership. The new tool, system, or product is no longer “theirs”. It becomes “ours”.

In a world of constant transformation, that sense of ownership may be the most valuable outcome of all.