Why change programmes fail when they skip the research
Organisations make expensive structural and workforce decisions without properly researching the people affected. It happens constantly, across every sector, and the pattern is remarkably consistent.
A leadership team decides on a transformation – a restructure, a technology deployment, an operating model shift, an AI rollout. The direction is sound. The business case is solid. The programme plan is detailed, well-resourced and approved. Then it lands on the organisation and meets reality.
Adoption is slower than projected. Resistance appears in unexpected places. Teams that were supposed to embrace the change quietly work around it. Six months in, the programme is technically complete but the organisation hasn't actually changed. The investment is made but the return isn't materialising.
The usual suspects get blamed: poor communication, lack of leadership sponsorship, middle management inertia, cultural resistance. These factors are real. But they're symptoms, not causes. The cause, almost every time, is that the programme was designed without researching the people it was designed for.
This is such a common failure mode that it's worth spelling out what "skipping the research" actually looks like in practice.
It looks like designing a restructure based on spans of control and reporting lines without understanding how teams actually collaborate across the current structure. It looks like deploying a new technology platform based on process maps that don't reflect how people actually work – including the workarounds, informal practices and institutional knowledge that keep things running. It looks like setting adoption targets without mapping the real impact on daily work for the people expected to adopt.
It looks like treating resistance as a communications problem when it's actually an information problem. People resist change they don't understand, change they weren't consulted on, and change that makes their working lives harder without apparent reason. That's not stubbornness – it's rationality. If nobody asked them what their work actually involves, why would they trust that the new way of working accounts for it?
And it looks like underestimating change fatigue. Most large organisations are running multiple transformation programmes simultaneously. Each one lands on teams who are already carrying the cognitive and emotional weight of the last one. Without researching what people are already dealing with, you can't design a programme that accounts for it – and you end up stacking change on top of change until the organisation's capacity to absorb any of it collapses.
The alternative is straightforward, though it requires discipline and a willingness to hear things that complicate the plan.
You start with research. You interview the people whose work is about to change – not just their managers, not just the project sponsors, but the people doing the work. You map their current experience: what they actually do, how they do it, where the friction is, what they've already adapted to, and what capacity they have for more change. You identify the groups who will be most affected, the risks that are most likely to stall the programme, and the practical barriers to adoption that no amount of communication will overcome.
This research doesn't slow the programme down. It prevents the programme from slowing itself down later. A change readiness diagnostic – interviews, surveys, a scored assessment of where the organisation stands – can be done in four weeks. A change impact assessment – mapping what's changing, for whom, at what pace – takes four to six weeks. Both produce actionable output: a risk register, a set of prioritised recommendations, a clear picture of where attention and resource need to go.
The insight these exercises produce is often uncomfortable. They surface misalignment in the leadership team that was papered over in the business case. They reveal that the teams most affected by the change are also the teams with the least capacity to absorb it. They show that the process being replaced includes workarounds that solve real problems – problems that the new process doesn't account for.
But that discomfort is the point. It's far cheaper to discover these things in a four-week diagnostic than in a twelve-month programme that has to be restructured halfway through because the assumptions it was built on didn't hold.
Organisations that build research into the front of their change programmes consistently see better adoption, lower resistance, and faster time to value. Not because research is magic, but because it replaces assumptions with evidence. When you know how people actually work, you can design change that works with them. When you don't, you're guessing – and guessing at scale is expensive.
The question for any organisation about to commit to a transformation programme is simple: do you know how this change will actually land on the people it affects? If the answer is no, or "we think so", that's the gap where programmes fail. Fill it with research, and you give the programme a foundation it can actually stand on.