Why Organisational Change Fails (And Why Training Is Usually The Reason)

Here’s a quick summary

• 60–70% of organisational change initiatives fail, and the rate hasn’t improved in 20+ years.
• The cause isn’t strategy or communication — it’s that training is treated as an afterthought.
• Most training builds knowledge (“what’s changing”) but not capability to perform under real conditions.
• Employees forget 70% of new information within 24 hours, and only 10% say compliance training has changed their work.
• Safe Work Australia classifies insufficient training during change as a psychosocial hazard.
• Australian mental health claims have risen over 160% in the past decade, making change management a safety issue.
• Effective change requires training designed before launch, measured by behaviour, and built with psychological safety.

On paper, the change initiative was a success. It launched on time, came in on budget, and leadership ticked every box on the project plan. The new system was live, the comms had gone out, teams had completed their training, and the CEO sent a congratulatory email to the whole organisation.

Six months later, half the workforce was still using workarounds. Managers were interpreting the new process differently across every team. Data quality had dropped, not improved. The change had technically happened, but the behaviour hadn’t followed. For the L&D team who built the training programme, it was a familiar kind of defeat: everything went to plan, and nothing actually worked.

This pattern plays out across Australian organisations every day. And it points to something nobody seems to be questioning.

Roughly two-thirds of change initiatives fail. That figure has held steady for more than two decades, despite organisations pouring billions into change management methodologies, communication strategies, leadership development, and transformation programmes.

And yet the failure rate hasn’t moved. This is the paradox at the heart of why organisational change fails: organisations are spending more on training than ever, and change is failing at the same rate it always has.

Most post-mortems point to the usual suspects: poor leadership, lack of vision, inadequate communication, and employee resistance. These are real factors, but they’re surface-level explanations for a deeper, structural problem.

The consistent reason why organisational change fails is that the one thing responsible for turning strategy into actual behaviour (training) is almost always treated as an afterthought. Not because organisations don’t value it, but because they fundamentally misunderstand what it needs to do.

Where change actually breaks down

Change rarely fails because the strategy was wrong. It fails at the point where someone has to do their job differently and doesn’t know how.

The gap between ‘we’ve communicated the change’ and ‘people are executing it correctly and consistently’ is where most initiatives quietly unravel. This is the execution layer, and it depends almost entirely on how well people have been prepared to perform.

On the ground, this shows up as inconsistency in how work gets done across teams and locations. People who understand what changed but can’t do it reliably under real conditions. Workarounds that emerge within weeks of a rollout, and the slow erosion of a change that ‘launched successfully’ but never stuck.

So the question worth asking is: when adoption stalls, is the problem resistance or a lack of capability?

‘Resistance’ tends to be the default diagnosis. But what gets labelled as resistance is often something quieter: people feeling unprepared, overwhelmed, or unsupported. Research by Mosadeghrad and Ansarian (2014), reviewing literature spanning three decades, identified ‘insufficient education and training’ as the first-listed cause of change programme failure.

This distinction matters because the interventions look completely different. If it’s resistance, you double down on communication and leadership. If it’s a capability gap, you redesign the training. Most organisations default to the first and never seriously consider the second.

The role training actually plays in change

Training is often treated as the process of telling people what’s changing. A briefing. A slide deck. An eLearning module that covers the ‘what.’

But knowing what to do is not the same as being able to do it correctly, consistently, and under real conditions.

Training is capability building, not knowledge transfer

People forget approximately 70% of new information within 24 hours when it’s not reinforced. This is grounded in Ebbinghaus’s foundational psychology research and has been validated repeatedly in corporate settings. Industry data suggests just 10% of employees believe compliance training has meaningfully impacted the way they work.

Consider a CRM rollout. Training covers features, navigation, and where to click. Employees leave the session understanding the system. But in practice, data gets entered inconsistently, steps are skipped, and reporting becomes unreliable. The gap isn’t knowledge — training simply didn’t prepare people to use the system correctly in real workflows, under real time pressure, with real competing priorities.

Training is what translates strategy into behaviour

An organisation can have a clear strategy and communicate it well, but neither of those things determines whether people can actually execute the change in their day-to-day work. Training is the layer that does that. Without it, strategy stays aspirational.

Take a compliance process change designed to reduce risk. The strategy is sound, the communication covers it: emails, briefings, documentation. But teams interpret steps differently, shortcuts emerge, and compliance remains inconsistent. Organisational training should translate ‘we need to be compliant’ into ‘this is exactly how you complete this task, every time.’

Under the Managing Psychosocial Hazards at Work Code of Practice 2024, ‘insufficient support, information or training during change’ is formally listed as an indicator of poor organisational change management. Safe Work Australia classifies this as a psychosocial hazard. When compliance training doesn’t change behaviour, it’s not just an inefficiency. It’s a genuine risk exposure.

Training drives consistency, clarity, and confidence

At scale, organisations don’t fail because people don’t try. They fail because everyone does things slightly differently, and the inconsistency compounds over time. Confidence plays a bigger role here than most leaders realise. When someone doesn’t feel confident in a new process, they’ll default to what they know, not because they’re resisting, but because it feels safer than getting it wrong in front of their team.

Consider a company rolling out a new onboarding process across multiple locations. Without strong training, each manager adapts it slightly, steps are skipped or reordered, and new hires have wildly different experiences. With effective training, onboarding is delivered consistently, expectations are clear, and managers feel confident executing it.

What happens when training is treated as an afterthought

When training is bolted on at the end of a change initiative rather than built into its architecture, the consequences compound. Workarounds multiply as people fill gaps with whatever works, creating new risks the change was supposed to reduce. Help desks and managers end up troubleshooting what training should have prevented. Timelines slip, confidence drops, and the change loses momentum. With each poorly landed initiative, people become less willing to engage with the next one.

The human cost is real. Gartner’s research on change fatigue found that 73% of HR leaders report their employees are fatigued from change. Not a temporary discomfort, but a lasting reduction in how people approach the next initiative. Change-fatigued employees disengage, underperform, and look for the door.

The Australian legal dimension

There’s also a compliance angle here that elevates this beyond a performance conversation.

Mental health conditions now account for approximately 12% of all serious workers’ compensation claims nationally, up nearly 15% in a single year. Claim rates have increased more than 160% over the past decade.

Safe Work Australia’s WHS Strategy 2023–2033 explicitly flags psychosocial hazards, including poorly managed organisational change, as creating risks of both physical and psychological harm. The Commonwealth Code of Practice lists insufficient training during change as a specific hazard indicator.

Inadequate organisational training during change is no longer just a performance issue. It’s a workplace safety issue with regulatory implications, and understanding why organisational change fails at this level matters for any leader managing a transformation in Australia.

Why this keeps happening

If the pattern is this well-documented, why does it repeat? Understanding why organisational change fails means looking beyond the obvious explanations. Five structural problems keep showing up.

Training is designed too late in the project lifecycle

Most change initiatives design training after the strategy is set, the systems are built, and the launch date is locked in. By the time L&D gets the brief, the window to properly design for behaviour change has already closed. McKinsey’s 2025 research on successful transformations found that leaders should invest in skills and change capacity first, before implementation. The organisations that sequenced learning before launch consistently outperformed those that bolted it on after.

The complexity of behaviour change is underestimated

Organisations routinely underestimate what it takes for someone to do their job differently. Changing a process on paper takes a week. Changing how 500 people perform that process under pressure takes months. The Dynamic Transfer Model (Blume, Ford, Surface, & Olenick, 2019) found that if employees don’t apply a new skill within the first few weeks post-training, they’re unlikely to apply it at all. The window is narrow, and most organisations miss it entirely.

Communication is mistaken for capability

Telling people what’s changing is not the same as equipping them to execute it. But many organisations treat the communication plan as the training plan (emails, town halls, FAQs, intranet updates) and assume awareness creates ability.

Prosci’s ADKAR model makes this distinction explicit: most training addresses only Knowledge (understanding what’s changing). It rarely builds Ability (performing under real conditions) or Reinforcement (sustaining the new behaviour over time).

Managers are expected to carry the change, but aren’t equipped

Gartner found that 74% of HR leaders agree managers are not equipped to lead change. Critically, the research also found that giving managers more training doesn’t solve this. Making the manager role more manageable is far more effective than building more skills.

Most managers are already stretched thin. They’re carrying their own workload, managing team performance, fielding HR issues, and now they’re expected to champion a change they had limited input on. When they can’t confidently guide their teams through a transition, the change fragments and every team ends up with a slightly different version of reality. There’s a telling perception gap here, too: McKinsey found that 86% of leaders say they role-model the desired change behaviours. Only 53% of their direct reports agree.

Success is measured by completion, not behaviour change

If your evaluation stops at ‘87% completed the course,’ you’re not measuring what matters. Completion tells you people showed up. It tells you nothing about whether risk has reduced, errors have dropped, or people feel more confident and capable in their roles.

This creates a false signal of success. The training ‘worked’ on paper, but the change still fails in practice. Organisations need to stop asking ‘did people complete the training?’ and start asking ‘what behaviour changed as a result?’

How organisations should actually approach change

If training is the execution layer of change, it needs to be treated like one. That means designing it with the same rigour, resourcing it with the same commitment, and measuring it with the same accountability as any other critical workstream.

Start with the work, not the training

Before designing any training, understand what actually needs to change in how people perform their work. What decisions are different? Where will the pressure points be? This is the diagnostic step most organisations skip, jumping straight to building content without properly analysing the work.

Diagnose where change will break down

Every change has predictable failure points: the moments where people are most likely to revert, improvise, or disengage. Effective training is designed around those moments, not around a generic overview of ‘what’s new.’

A common practical challenge is that the details are often still shifting when training needs to start being built. The answer isn’t to wait until everything is locked in. It’s to design around the decisions and behaviours that won’t change, even if the system details do. The workflow logic, the judgement calls, the escalation points. Those are stable enough to build on early, with the tactical detail layered in closer to launch.

Align change, communication, and training as one workstream

McKinsey explicitly warned against separating performance from the people side of change. When they run as parallel workstreams that don’t talk to each other, the change invariably fails. Communication tells people why the change matters; training builds their ability to execute it. These need to be designed together, not handed off to different teams.

If you’re an L&D leader reading this and thinking ‘we always get the brief after everything else is decided,’ you’re not alone. But here’s the reframe worth taking to your project sponsors: if training is designed after everything else is locked in, it’s being designed with the least amount of time, the least amount of influence, and the highest stakes. That’s not a training risk. It’s a project risk.

Design for real-world performance

Training should be built around how people actually perform tasks, not around how the system works in a demo environment. That means realistic scenarios, practice under conditions that mirror the actual work, and time to build confidence before performance pressure kicks in. Spaced repetition can improve retention by 80% after 60 days compared to one-off sessions, and focusing on two or three key behaviours rather than overwhelming participants with everything at once consistently produces better outcomes.

Build for consistency at scale

There’s a meaningful difference between having content available and having learning designed for a specific change. A library of modules is useful, but training built for a particular change initiative, targeting the specific workflows, failure points, and behavioural shifts required, is a different thing entirely. This is where instructional design earns its place: clear standards, structured learning pathways, and repeatable delivery that works across teams and locations.

Psychological safety matters here, too. Gartner found that when managers create psychologically safe environments during change, change fatigue drops by up to 46%. People need to feel safe to practise, make mistakes, and ask questions, not just be told what to do.

And if the last three change projects were exhausting and adoption was patchy, the question isn’t about fatigue management. It’s about whether there’s a way to rebuild trust after a string of poorly landed changes. The answer is that the next initiative needs to be visibly different in how it treats people, and training is the most tangible way to demonstrate that.

The real question isn’t whether your strategy is right

Change doesn’t fail at the strategy level. It fails at execution, in the gap between what the organisation decided and what people actually do. Training isn’t a support function bolted on at the end. It’s the core mechanism for making change work — and the most commonly overlooked reason why organisational change fails. Organisations that treat training as an afterthought will keep seeing the same pattern: well-planned changes that don’t land, and a workforce that grows more fatigued with every initiative.

If you’ve ever felt like you did everything right and it still didn’t work (the comms plan ran, the training was built, leadership was on board, completion targets were hit) and adoption still fell apart within three months, the answer is usually this: training was designed for knowledge, not capability. The environment people returned to was unchanged. Success was measured by completion, not behaviour. That’s not a failure of effort. It’s a failure of design — and it’s fixable.

Before your next change initiative, ask three questions:

These aren’t trick questions. They’re the ones that tend to surface what actually went wrong.

1. When in the project timeline is training being designed: at the start, or after everything else is locked in?
2. What are you measuring: completion rates, or actual behaviour change?
3. Are the people expected to execute this change being given time and psychological safety to practise before performance pressure kicks in?

If the answer to any of those doesn’t feel right, the issue probably isn’t your strategy. It’s how that strategy is being translated into what people actually do every day. That’s why organisational change fails. Not because the plan was wrong, but because the plan was never properly built into how people work.

If you’re planning a change initiative and want to think through how training fits into the architecture, not just the rollout, that’s a conversation worth having early.

Frequently asked questions

Why do most organisational change initiatives fail? 

Around two-thirds of change initiatives fail, and the failure rate hasn’t improved in over two decades. While communication, leadership, and resistance are commonly blamed, the underlying issue is usually that training is treated as an afterthought rather than as the mechanism that turns strategy into actual behaviour.

What’s the difference between knowledge transfer and capability building? 

Knowledge transfer is telling people what’s changing. Capability building equips them to perform differently under real conditions, including time pressure, competing priorities, and the moments where they’d otherwise revert to old behaviour. Most organisational training stops at knowledge.

Why doesn’t completing a training course mean the change has worked? 

Completion measures attendance, not behaviour. An 87% completion rate tells you people showed up. It tells you nothing about whether errors have dropped, risk has reduced, or people feel confident performing the new way of working. Behaviour change is the metric that matters.

When should training be designed in a change project? 

Before implementation, not after. Organisations that sequence skills and capability work before launch consistently outperform those that design training after the strategy and systems are locked in.