Most business transformations fail in a very specific way: they treat people as a constraint to manage, not the mechanism that makes transformation real.
People-led transformation is a change model in which behavioural and identity shifts, not system implementations or process redesigns are treated as the primary delivery mechanism from the outset.
That sounds obvious, but it plays out subtly. Leaders talk about “bringing people along,” “managing change,” or “driving adoption,” as if the transformation exists independently of the people doing the work. As if strategy, technology, and operating models are the real transformation, and people just need to catch up.
In practice, the opposite is true. The transformation is the people.
I’ve seen organisations hit their stated transformation milestones, systems implemented, processes redesigned, costs reduced, and still feel fundamentally unchanged. The organisation chart looks different. The tools are new. The language has shifted. But decision-making, ownership, risk appetite, and collaboration all snap back to old patterns within months. Nothing really transformed. The uncomfortable truth here is that you can deliver outputs without changing how people think
In a previous programme I worked on, a company spent three years rolling out new technology alongside a new operating model. New processes were embedded, new teams were established, and a new commerce platform went live. On paper, the transformation was a success. The next step was to build on that momentum and scale the model globally.
But inside the teams, something was off.
Whilst the new system was live, the leadership team had not been adaptive to change. As a result I saw legacy patterns and behaviours starting to reappear, resulting in the old (but I guess technically new) inefficiencies. The structure had changed. The behaviour hadn’t.
Within six months, delivery slowed which meant no new markets went live. Frustration grew, and leadership started questioning what went wrong.
It wasn’t a process problem. It was a people problem, specifically, a belief problem. Leadership had not been given the space, safety, or clarity to actually operate differently. They had been asked to perform under a new system while thinking in the old one.
Transformation, in that sense, had been treated like an installation, not a transition.
Transformation as Installation vs. Transformation as Transition
Dimension | Installation Model | Transition Model |
|---|---|---|
Primary measure | Milestones delivered | Behaviours shifted |
How people are positioned | Recipients of change | Authors of change |
Definition of done | Programme close | New baseline established |
Risk model | Manage resistance | Expect and protect the dip |
Leadership role | Design the future state | Create conditions to move toward it |
Why Transformation Milestones Don't Change Behaviour
Most transformation plans assume that once you define the future state clearly enough, people will move toward it. They won’t.
Not because they’re resistant or incapable, but because transformation asks something deeper than new skills or processes. It asks people to let go of what has made them successful so far, and to operate in ways that feel slower, riskier, or less certain at first. That’s not a training gap. That’s an identity shift.
For example:
- A senior merchandiser who built their career on instinct is now being asked to trust data models.
- A store leader who was rewarded for control is now expected to empower frontline teams.
- A project manager who succeeded through detailed planning is now told to embrace ambiguity and iteration.
You can’t solve that with a workshop.
What I’ve seen repeatedly is this: transformation efforts invest heavily in defining the future, but far less in helping people navigate the loss of the past. And that loss is real - status, certainty, expertise, control.
Until that’s acknowledged, people will comply on the surface and resist underneath.
Transformation is built by today’s people, but it’s not really for them
Here’s the tension that rarely gets said out loud: most transformations are building a business that future hires will find natural, but current employees will find uncomfortable. You’re asking people to construct an environment they themselves may never fully benefit from. That changes how you need to lead.
The Transformation Authorship Model
Sustained transformation requires three structural conditions, not one. Together they form what I call the Transformation Authorship Model:
- Involve: Co-design the future with the people building it, not just for them.
- Illuminate: Make behaviour visible alongside deliverables, so the invisible work of transformation becomes measurable.
- Insulate: Protect teams through the performance dip that new ways of working always produce.
Most transformation programmes address one of these. The ones that hold address all three.
Three Structural Shifts That Sustain Transformation
The transformations that hold are the ones where people are not “impacted by change,” but actively shaping it. That sounds idealistic, but in practice it comes down to a few very specific shifts.
Involve
First, involve people in defining how the future works, not just what it is. I’ve seen teams go from passive resistance to active ownership when they’re asked questions like:
- “What would stop this working in reality?”
- “Where would this break under pressure?”
- “What trade-offs are we ignoring?”
Those conversations surface constraints early, but more importantly, they create a sense that the transformation is something people are building, not something being done to them.
Illuminate
Second, make behaviour visible, not just deliverables.
One company I worked with started tracking not just what teams delivered, but how they made decisions:
- How often did teams act without escalation?
- How frequently did they test and learn versus plan and delay?
- Where were decisions being blocked?
This wasn’t about policing. It was about making the invisible part of transformation, behaviour, explicit and discussable.
Because you can hit every milestone and still fail if behaviour doesn’t shift.
Insulate
Third, create safety to get worse before getting better. This is one of the most misunderstood parts of transformation. When people adopt new ways of working, performance often dips. Decision-making slows. Mistakes increase. Confidence drops. Many organisations interpret this as failure and revert to old ways. The better ones expect it. They plan for it, communicate it, and protect teams through it. They treat that dip not as a problem to fix, but as a necessary phase of learning.
Without that protection, people will always fall back to what feels efficient, even if it’s outdated.
Why People-Led Transformation Moves Faster, Not Slower
There’s a false trade-off that shows up in transformation conversations: that being “people-focused” means going slower, being softer, or compromising on outcomes.
In my experience, the opposite is true. The fastest transformations I’ve seen were deeply people-focused, but not in a vague or sentimental way. They were clear about expectations. They made tough calls. They moved quickly.
In one of my previous projects, I worked on a Global SAP transformation, moving SAP ECC to S/4 HANA. Now anyone who has used SAP ERP knows this is no quick and easy feat. However, this project was one of the highlights of my career to date. The people culture to support this project was exceptional - people were free to be open, challenge the status quo. We celebrated each others wins, and rallied around in times of hardship. We all locked in on what this project was trying to do, and the benefits it would bring to the business and it’s users. Was it uncomfortable at times? Yes, absolutely. It was hard work and long hours, but everyone was in it together working towards a common goal. The project went live as a big bang globally on time, and under budget (which is exceptionally rare in these times).
What made this work was not goodwill or culture as an abstract value. The programme embedded three specific conditions: psychological safety to challenge decisions without consequence, a shared success metric that made individual wins meaningless unless the programme succeeded, and leadership that modelled the behaviour it asked of others visibly, consistently, under pressure. Those three conditions are reproducible and are not personality-dependent.
Why Transformation Doesn't End When the Programme Does
Another pattern I’ve seen: organisations treat transformation like a project with a defined end.
There’s a roadmap, a timeline, a set of deliverables, and an implicit belief that once these are done, the business will “be transformed.”
But if transformation is fundamentally about how people think and behave, it doesn’t end when the programme does. It becomes the new baseline.
The companies that sustain transformation are the ones that:
- Embed new behaviours into performance management
- Hire and promote based on future-state capabilities
- Continuously revisit and refine ways of working
- Treat “how we operate” as a living system, not a fixed design
In other words, they don’t just build the future business. They keep building it.
What Leadership Looks Like in a People-Led Transformation
If transformation is about people, then the role of leadership shifts.
It’s less about designing the perfect future state and more about creating the conditions where people can move toward it.
That includes:
- Being consistent, even when it’s inconvenient
- Reinforcing new behaviours, not just new structures
- Making trade-offs explicit, rather than hidden
- Holding the tension between current performance and future capability
And perhaps most importantly, it means recognising that people are not just the recipients of transformation, they are the authors of it.
Key Takeaways: A Practical Framework for Transformation Leaders
The Transformation Authorship Model reframes the job of every transformation leader. Your primary deliverable is not the future state design. It is the conditions under which today's people can build it.
That means Involving them in shaping how the future actually works, Illuminating behaviour alongside output, and Insulating them through the discomfort of becoming something new. Every action item below maps to one of those three conditions.
What to Do
- Involve people early in shaping how the future will actually work, not just presenting it
- Measure behavioural change alongside delivery metrics
- Create explicit space for learning, mistakes, and temporary performance dips
- Invest in capability building that goes beyond tools and processes
What to Stop Doing
- Stop treating resistance as a problem to eliminate, rather than a signal to understand
- Stop assuming that clarity of strategy automatically leads to behavioural change
- Stop over-optimising for short-term efficiency at the expense of long-term capability
- Stop framing transformation as something that just happens to people
What to Rethink
- Rethink the idea that transformation has a clear “end”
- Rethink what it means to “care about people” in a high-change environment
- Rethink whether your current ways of working truly reflect the future you’re trying to build
- Rethink whether you’re designing for the people you have, or the people you’ll need
In Summary
- Business transformation fails when people are treated as recipients of change rather than its authors.
- Delivering programme milestones without shifting behaviour produces infrastructure without culture.
- The Transformation Authorship Model requires three conditions: Involve, Illuminate, and Insulate.
- The performance dip during adoption is not failure. It is a necessary phase that must be planned for and protected.
- Transformation does not end at programme close; it becomes the new operating baseline.
At its core, transformation is an act of building a future organisation using the people of today. If you treat those people as an obstacle, you might deliver the programme, but you won’t change the business. If you treat them as the builders, you have a chance to do both.
