Change programs can be executed well and still fall short of lasting impact. When adoption is uneven after go-live, the cause is rarely a process failure. It comes down to how the change connects to people’s actual work, and whether the conditions around it have been shaped to support it.
Key Insights:
- Structured change programs generate activity and visibility, but neither guarantees that people will actually work differently once the project closes.
- People engage with change based on what they see around them, not what they are told through formal channels.
- Effective change management requires reading the environment accurately before applying a methodology to it.
Most organisations are capable of running structured change programs around their projects, typically made up of pro forma, template driven communications and training activities. The work might appear to be executed well, with a clear sequence of activity and consistent methodology. Activities signal progress.
From a delivery standpoint, it all appears controlled and disciplined. Yet in many cases, benefits realisation falls short of the mark – especially in the longer-term.
Programs that appear successful on paper do not always lead to meaningful changes in how people work. Even when the process is followed, the outcome may not take hold. This is where many change efforts struggle, and where expected benefits begin to fall away.
Where project benefits are won or lost
In practice, it’s rarely during project delivery that change initiatives start to fail. The issues tend to surface after go-live. A system goes live, but people use it unevenly. Some parts of a new process are picked up, others are ignored. Teams fall back on familiar ways of working where they can. Over time, alternative paths start to form around the intended one.
A program can reach handover with every requirement met and still fall short in practice. The change has been delivered, but it has not fully carried into day-to-day operations. That is where the pressure on benefits begins.
Change management is often treated as a secondary concern, yet it determines whether value is realised over time. Benefits are tied to how consistently people use what has been introduced, not to the moment it goes live.
When usage is uneven, outcomes follow the same pattern. Project activity may be tracked and reported, but that alone does not establish new ways of working or guarantee a change in behaviour. The result is a gap between the cost of change and the value returned.
The gap between behaviour and activity
Organisations that follow established change processes and still see uneven outcomes are not dealing with a process gap or methodology issue in the change practice. The limitation usually sits elsewhere.
Communications go out, training is completed and milestones are met. From a governance perspective, this creates visibility and a sense of control and progress.
Completing the cookie-cutter change activities doesn’t guarantee is a change in how people work. In many cases, people engage with the change to the extent required. They complete the tasks in front of them and operate within the parameters that have been set. This creates movement, but it doesn’t mean the change has been absorbed into day-to-day practice. That’s where outcomes begin to diverge.
Whether a change takes hold comes down to what it feels like in practice. People look at what’s happening around them and take cues from those they trust, before deciding how seriously to engage. If it doesn’t connect to the reality of their work, it tends to fall away.
That is where outcomes are determined, well beyond what process can control.
When change doesn’t fit the context
A trap for project and change teams is being too focused on being structured around program needs. It’s understandable, when most project leaders live and breathe milestones, activities and communications that are strictly aligned to key messages.
However, the reality is that people don’t experience change at that level. They experience it through their role, and assess it against their own priorities and pressures. If the change doesn’t translate into their context, or the connection is unclear, they will see no reason to adopt it and revert to familiar ways of working.
Context and environment also shape how change is received. Every initiative enters an environment influenced by previous programs, and past outcomes affect current perceptions. In some organisations, there’s change fatigue from repeated initiatives. In others, there might be limited trust in particular teams or functions.
What this points to is a simple constraint. A standardised approach to change rarely holds across different programs. What worked in one context won’t carry across to another.
Effective change depends on reading the environment accurately, understanding how the work is actually done and adjusting the approach to fit.
What influences behaviour in practice
Behaviour rarely changes just because something has been delivered. A system can go live and training can be completed, but if nothing else changes, people fall back on what they already know.
What happens around them tends to matter more. People watch their team, notice what others are doing and take cues from those they trust. Informal signals often carry more weight than anything coming through formal channels.
Adoption becomes easier when the change feels grounded in how work actually gets done and when it’s visible in the behaviour of others. People start to adjust once they can see it in practice. As trust builds, the change is more likely to take hold.
Why project handover isn’t the finish line
Project execution on its own isn’t a reliable indicator of success. What matters over time is whether people actually work differently once the change is in place.
Leaders often assume that following the process will lead to adoption. It’s rarely enough. What people experience day to day carries more weight than the plan itself. Leadership behaviour, local context and what is reinforced in practice all shape whether the change settles. Where these are inconsistent, adoption slows and benefits are only partially realised after delivery.
Successful change depends on how well these conditions are understood and addressed. It requires a clear view of how the change will be experienced, where resistance is likely to emerge and what needs to adjust for it to carry through into daily work.
Change can’t successfully be reduced to a process or a set of activities. It depends on how well the conditions around it are shaped, and how accurately the environment is understood. This has the greatest impact on how the change is read, applied and reinforced in practice.
Ultimately, outcomes aren’t determined by what gets delivered. They’re determined by what people actually do.
Whether you’re leading a project, PMO, or driving transformation, we invite you to stay informed and connected. Join the Quay Roundtable Network for access to expert insight, practical tools and real-world discussion that cuts through the noise
Quay Consulting is a professional services business specialising in the project landscape, transforming strategy into fit-for-purpose delivery. Meet our team or reach out to have a discussion today.