OCM vs Change Management
Organisational change management, OCM, is the discipline of helping people adopt new processes, tools, or structures, through communication, training, sponsorship, and reinforcement. IT change management, or change enablement, controls modifications to IT systems so they are assessed, approved, and implemented safely. OCM manages human adoption; IT change management manages technical risk. Large projects usually need both.
What OCM covers
Organisational change management helps employees understand why a change is happening, build willingness to adopt it, learn new skills, and sustain new behaviours. It involves stakeholder analysis, sponsorship from leaders, communication plans, training, resistance management, and reinforcement. Success means people actually work the new way.
What IT change management covers
IT change management controls technical changes to services and infrastructure: deployments, configuration changes, upgrades, and decommissioning. It assesses risk, schedules changes, ensures testing and rollback plans exist, and records what changed. Success means changes land without unacceptable incidents.
Different models
OCM practitioners use models such as Prosci's ADKAR, which tracks awareness, desire, knowledge, ability, and reinforcement, and Kotter's eight-step process for leading change. IT change management uses frameworks such as ITIL change enablement and continuous delivery practices with automated controls.
Where they meet
Introducing a new incident management tool is both: IT change management governs migration, configuration, and cutover, while OCM ensures responders, support agents, and managers know why the tool is changing, how to use it, and stop using the old one. Skipping OCM leaves a technically successful migration that nobody uses properly.
Different owners
OCM is often led by HR, transformation offices, or project teams with dedicated change managers. IT change management is owned by IT operations, platform teams, or service management functions. Coordination between them is frequently missing.
Measuring success
OCM measures adoption: usage rates, proficiency, satisfaction, and sustained behaviour change. IT change management measures change success rate, lead time, and incidents caused by changes. Both sets of metrics matter for major initiatives.
Common failure modes
Without OCM, new tools and processes go unused or are worked around. Without IT change management, technical changes cause outages. Confusing the two leads to IT teams writing communication plans for system cutovers, or transformation teams trying to approve production changes.
Practical advice
For any significant tool or process change, pair a technical change plan with an adoption plan. Identify who is affected, what they need to know and do differently, how they will be trained, and how adoption will be measured.
An example rollout
Moving a service desk to a new incident tool involves IT change work, such as data migration, integrations, and cutover scheduling with rollback, and OCM work, such as explaining why, training agents and responders, running a pilot, collecting feedback, and retiring the old tool. Plan both on one timeline with clear owners.
Resistance and how to handle it
Resistance to new tools or processes usually has reasons: extra work, unclear benefit, or fear of being measured. OCM addresses these through involvement, clear explanation, and removing friction. Technical controls cannot fix resistance; listening and adjusting the change often can.
OCM vs Change Management in brief
Plan technical change and human adoption together on one timeline, with a named owner for each.
| Aspect | OCM | IT change management |
|---|---|---|
| Focus | People adopting new ways of working | Safe modification of IT systems |
| Typical models | ADKAR, Kotter | ITIL change enablement, continuous delivery |
| Activities | Communication, training, sponsorship | Risk assessment, approval, rollback |
| Success measure | Adoption and sustained behaviour | Change success rate, low incident impact |
| Typical owner | Transformation or HR teams | IT operations or platform teams |
Frequently asked questions
- What does OCM stand for?
- OCM stands for organisational change management. It covers the people side of change: helping employees understand, accept, learn, and sustain new processes, tools, or structures, through communication, training, leadership sponsorship, and reinforcement after the change goes live. It complements technical change control.
- Is ITIL change management the same as OCM?
- No. ITIL change enablement controls technical changes to IT services by assessing and authorising them based on risk. OCM manages how people adopt organisational changes. They often apply to the same project, but they address different risks and use different methods.
- Do IT teams need organisational change management?
- Yes, for significant changes to tools or processes. A technically perfect rollout can still fail if people do not understand or adopt the change. Even small adoption plans, covering who is affected, training, and feedback, improve outcomes considerably. Measure adoption after launch.