Every year, organisations across Australia, New Zealand, Singapore, and the Philippines invest significant capital in new systems, restructures, process overhauls, and strategic pivots, and a substantial proportion of those investments fail to deliver what was expected of them. McKinsey's research on large-scale transformation, which has been consistent for decades, places the failure rate at roughly 70 percent - a figure that has not moved materially in thirty years despite advances in strategy, technology, and organisational design.
The common theme within this failure rate is that organisations concentrate their investment of time, money and energy on building the solution and preparing for go-live, then hand the team a standard operating procedure (SOP), provide a brief walkthrough and consider the change managed.
Change management is not a supplementary workstream or a communication exercise bolted onto an implementation - it is the discipline that determines whether the investment translates into lasting adoption or becomes another initiative the business will need move on from or remediate later.
Strip away the corporate language and change management is the discipline of moving an organisation from one way of operating to another, while keeping the business functioning throughout the transition. That is it. No more, no less.
It is not a communications plan. It is not a training schedule. It is not a series of workshops where people talk about how they feel about a new ERP system. Those activities might form part of a change program, but mistaking them for the full picture is precisely where most businesses go wrong.
A genuine change management process addresses five interconnected domains: leadership alignment, stakeholder readiness, process and system integration, communication architecture, and sustainability of the new state. Remove any one of those domains and you have a gap. Gaps become resistance. Resistance becomes delay. Delay becomes cost.
Organisational change management, at its core, is an operational discipline. It belongs in the same category as project delivery and quality control. It requires method, sequencing, clear accountability and someone who understands what failure looks like before it becomes visible in the numbers.
Change management is not a soft capability bolted onto a hard project. It is the mechanism by which the hard project actually lands.
The failure is almost never about people being resistant to change. That framing lets organisations off the hook too easily. People resist poorly explained, poorly timed, poorly sequenced change. They do not resist change that is logical, visible and supported. The structural causes of failure run deeper than culture or attitude.
.png)
The most common pattern in mid-market businesses is a compressed timeline with a hard go-live date. Everything is pointed at that date. The assumption is that once the new system is live, or the new structure is announced, or the new process is published, the change is complete. It is not. The go-live date is the beginning of the hardest part, not the end of it. Without a structured post-implementation change management process, adoption stalls, workarounds proliferate, and the organisation quietly reverts to its previous behaviour while the official line remains that the project succeeded.
Most change programs have a sponsor on paper. A general manager or a CEO whose name appears at the top of the project charter. That is not sponsorship. Active sponsorship means the senior leader is visibly and consistently engaged with the change management process over its full duration. It means they are removing blockers, reinforcing the rationale, and signaling through their own behaviour that the new way of operating is the expected standard. Harvard Business Review research on change leadership is unambiguous on this point: sponsorship quality is the single strongest predictor of change success. When leadership treats a project as something the project team owns, the organisation reads that signal accurately.
The Change Is Sequenced Around the Technology, Not the People
System implementations, in particular, fall into this trap. The vendor sets the timeline. The integration workstream drives the plan. Change readiness activities are scheduled around system milestones rather than around the pace at which the organisation can genuinely absorb and adopt new ways of working. The result is a workforce that is technically trained but operationally unprepared. Training is not the same as readiness. Awareness is not the same as adoption.
Organisations frequently begin change programs without a clear diagnosis of current-state operations. They know something needs to change but they have not mapped precisely what is broken, why it is broken, or what the flow-on effects of changing it will be. The absence of a current-state baseline makes it impossible to design a coherent change management process, because you cannot sequence what you have not understood. You end up addressing symptoms rather than causes, which means the change does not hold.
Change Management Is Underfunded and Underresourced
In most project budgets, change management is either absent as a line item or allocated a fraction of what the technical workstream receives. Prosci's research on change management effectiveness consistently shows that projects with dedicated change management resources are significantly more likely to meet their objectives and stay on timeline. Yet the default instinct in mid-market businesses is to assign change management responsibilities to whoever has the most available capacity, rather than whoever has the right capability. The outcome is predictable.
The costs are specific and observable, even when they are not formally measured.
Productivity drops in the months following a poorly managed transition. This is expected and normal in any change program. What is not normal is when that productivity drop extends for six, twelve or eighteen months because the new state was never properly embedded. The organisation carries the cost of transition without ever arriving at the destination.
Voluntary attrition increases during poorly managed change. Experienced people, the ones who understand how the organisation actually works, are the first to disengage. They do not announce their frustration loudly. They simply stop investing discretionary effort, and eventually they leave. That institutional knowledge leaves with them.
Workarounds become permanent. When a new process or system is poorly embedded, people find ways around it that fit their existing habits. Those workarounds are invisible in the official process documentation but entirely visible in the actual operational data. Over time, they become the de facto standard, and the organisation ends up maintaining two parallel ways of working: the official one and the real one.
The original investment fails to generate the projected return. A system that is only partially adopted delivers partial benefit. A restructure that is not fully implemented delivers partial efficiency. The return on investment calculations that justified the change program are rendered meaningless by poor organisational change management execution.
Good change management is not visible in isolation. It is embedded in the project itself. When it is working, the organisation moves through the transition without the dramatic resistance spikes and performance valleys that characterise poorly managed change. That invisibility is often mistaken for the change being easy. It is not. It is evidence that the work was done properly, upstream.
It begins with diagnosis. Before a change program is designed, the current state needs to be mapped with precision. Not at a surface level, but at the level of actual process behaviour: how work moves through the organisation, where decisions are made, where accountability is unclear, where the unofficial ways of working diverge from the official ones. That diagnosis shapes everything that follows.
It requires genuine leadership engagement from the outset. Not endorsement. Engagement. Leaders who understand what the change requires of them personally, not just what it requires of their teams.
It treats communication as a sequenced discipline, not a broadcast activity. The right message, to the right audience, at the right point in the change curve. Not a single launch email and a series of updates.
It stays through delivery. The change management process does not end at go-live. It extends through the embedding phase, monitoring adoption, addressing resistance in real time, and adjusting the approach based on what is actually happening in the organisation rather than what the project plan assumed would happen.
The Australian Institute of Management has long recognised change capability as a core leadership competency. Organisations that build that capability internally, rather than treating every change as a one-off event, develop a genuine structural advantage over time.
The change management process does not conclude when the new system is live or the announcement is made. It concludes when the new way of working is the default, not the exception.
At Winston Gray, the change management process is not a separate workstream that runs alongside delivery. It is built into the methodology from the first conversation.
The work begins with The Audit - a structured diagnostic of current-state operations. The Audit identifies not just what is not working, but why it is not working and what the organisation's actual readiness for change looks like. That distinction matters. The design of any change program should be calibrated to the organisation's genuine capacity for change, not its theoretical capacity. Without that baseline, change programs are designed for an idealised version of the organisation rather than the real one.
From that foundation, The Project delivers structured implementation with organisational change management embedded throughout. The Project is built on the Winston Gray DDD Framework: Diagnose, Design, Deliver. Grounded in Lean Six Sigma, DMAIC and Agile principles, the framework ensures that change is sequenced logically, that adoption is tracked with rigor, and that the new state is embedded before the engagement closes.
The distinction that matters most: Winston Gray does not diagnose and disappear. The team stays through delivery. That continuity of presence is what generates the 92 percent adoption rates and the 40 percent improvement in delivery timelines that Winston Gray clients consistently see. It is also what prevents the slow reversion to previous behaviour that undermines so many change programs in the months after a vendor or consultant has left. For an overview of the full methodology, Our Approach sets out how Diagnose, Design, Deliver operates across different types of engagements.
Having worked inside complex change programs across financial services, professional services, logistics and distribution, healthcare operations and technology-led transformation, the pattern is consistent. The organisations that manage change well do not have better people. They have better processes for managing the human and operational dimensions of change alongside the technical ones. They treat the change management process as a first-class discipline, not an afterthought.
The organisations that struggle do not lack intelligence or ambition. They lack the structural discipline to sequence change in a way that the organisation can genuinely absorb. They invest in the system and underinvest in the transition. They announce the change and assume that understanding will follow. It rarely does.
Organisational change management is not complicated in concept. It is demanding in execution. It requires staying in the problem longer than is comfortable, adjusting to what the organisation is actually experiencing rather than what the plan assumed, and maintaining a long enough view to know that embedding a new way of working takes considerably more time than implementing it.
The 70 percent failure rate is not a mystery. It is the predictable output of treating change as an event. The path to a different outcome is not a better framework on a whiteboard. It is disciplined, embedded, sequenced delivery with someone who remains accountable for the result all the way through.
Winston Gray works with founders and leadership teams across Australia, New Zealand, the Philippines and Singapore who are preparing for or currently navigating significant operational change. The work begins with a clear-eyed diagnosis of where the organisation actually is, and it stays through delivery until the new way of working is embedded and performing.
Our latest news and trending topics
.png)