Organisational Change Management and Projects: Building the Bridge

Organisational Change Management (OCM) is the structured approach to transitioning individuals, teams, and organisations from a current state to a desired future state. It is not a communications plan. It is not a training programme. It is a comprehensive discipline that addresses the human side of change — the psychology, the stakeholder dynamics, the cultural forces, and the behavioural patterns that determine whether a change actually sticks.

The statistics on transformation projects are sobering. Depending on the study you consult, somewhere between 50% and 70% of large-scale change initiatives fail to achieve their intended outcomes. Technology is rarely the culprit. The systems usually work. What fails is adoption — the degree to which the intended users actually change their behaviour to realise the benefits the project was designed to deliver.

The Most Common Failure Mode

Consider a mid-sized organisation implementing a new enterprise resource planning (ERP) system. The implementation team selects the software, configures it, tests it, and goes live on schedule and within budget. Six months later, the finance team is still running parallel spreadsheets. The procurement team is re-entering data from the new system into the old one because they trust the old one more. The reporting that was supposed to be automated is still being done manually. The project is a technical success and a business failure.

This is not an unusual story. It plays out in ERP implementations, process redesigns, organisational restructurings, and digital transformations alike. The pattern is consistent: the technical delivery was managed rigorously; the human transition was not. Change management was treated as a communications afterthought rather than a parallel workstream.

Integrating OCM into the Project Life Cycle

Effective OCM begins before the project does. The moment a change initiative is conceived, the question should be asked: who is affected, and how? The answer shapes the change strategy.

1. Stakeholder impact assessment: Identify every group that will be affected by the change, and characterise the nature and magnitude of that impact. Which stakeholders will experience the greatest disruption? Which have the most influence over adoption? This assessment drives the entire OCM plan.

2. Change readiness assessment: Before the change is deployed, assess the organisation's readiness to receive it. Is there organisational fatigue from recent changes? Is there trust in leadership? Is there alignment on the case for change? Readiness gaps must be addressed before go-live, not after.

3. Communication planning: Develop a communication plan that is targeted, sequenced, and two-way. Different stakeholder groups need different messages at different times. Senior leaders need the strategic case; front-line staff need the practical impact on their day-to-day work. Critically, communication must include mechanisms for feedback — so the organisation can hear what is and is not landing.

4. Training and enablement: Training should be role-specific, just-in-time, and reinforced through practice. Generic training delivered weeks before go-live is largely forgotten by the time it is needed. The most effective enablement programmes layer initial training with on-the-job support, coaching, and accessible reference materials.

5. Resistance management: Resistance to change is not pathological — it is rational. People resist because they have legitimate concerns: about job security, about added complexity, about whether the change actually solves the problems they experience. Effective resistance management starts by listening, not by dismissing. When resistance is acknowledged and addressed substantively, it frequently converts to advocacy.

6. Sustainability planning: The riskiest period for any change is the six months after go-live. This is when the project team disbands, the urgency recedes, and old habits reassert themselves. Sustainability planning defines how the new state will be reinforced through performance management, process audits, recognition programmes, and leadership behaviours.

Roles and Responsibilities

The question of who is responsible for OCM is frequently contested and frequently unanswered. The project manager focuses on scope, schedule, and budget. The change manager focuses on adoption and stakeholder experience. The sponsor provides visible, active commitment to the change — not just approval at the start, but sustained advocacy throughout.

In organisations that do not have a dedicated change management function, the project manager often absorbs the OCM workload. This is manageable for smaller changes but creates capacity and expertise gaps on larger transformations. The risk is that OCM activities are deprioritised whenever the technical delivery encounters pressure — which is exactly when the human dimension most needs attention.

The most successful transformation programmes treat OCM as a parallel workstream with its own plan, its own milestones, its own budget, and its own accountabilities — not as a subset of the communications plan or a line item in the training budget. When OCM is structurally embedded in the project from the outset, adoption rates improve, benefit realisation accelerates, and the risk of the organisation reverting to old habits is materially reduced.

XNM Consulting integrates change management expertise into every project engagement. Learn more about our Program and Project Delivery services.