By Paul Clavering · May 2026
Paul Clavering · Founder, theChangeTracker & Just Enough Change Ltd
If you have ever had to explain that you do not manage change requests, you will know the feeling. ITIL change management is everywhere in IT. Change Advisory Boards, RFC forms, approval workflows, change tickets. OCM (Organisational Change Management) is something different entirely. And the fact that both use the word change causes more confusion than it probably should.
The difference in one sentence
ITIL change management manages changes to IT systems and infrastructure. OCM manages the impact of change on people. One is about controlling what gets deployed to your environment. The other is about making sure your people can actually work in the new environment once it arrives. Both matter. Neither replaces the other. But they are solving completely different problems.
What ITIL change management actually does
ITIL change management is a process framework designed to minimise risk when changes are made to IT systems. Its primary concerns are:
- Logging and categorising change requests
- Assessing technical risk and impact
- Getting the right approvals before changes go live
- Maintaining an audit trail of what changed, when, and why
The people it is designed for are IT teams, service managers, and CAB members. The question it answers is: did this change to our system go through the right process? Tools like ServiceNow and TOPDesk do this well. They are built for it.
What OCM software actually does
OCM software is built for a completely different question: are the people affected by this change ready, willing, and able to work in the new way? When an organisation rolls out a new ERP system, moves to a new operating model, or restructures a team, there are technical workstreams and there are human workstreams. OCM software supports the human side:
- Who is affected by this change, and how significantly?
- Which stakeholders need to be engaged, and at what level?
- What benefits is the organisation trying to achieve, and is it on track?
- Are people overloaded with too many concurrent changes?
- What does the training and engagement plan look like, and is it working?
The people it is designed for are change managers, project managers with change responsibility, and transformation leads. The question it answers is: are our people ready for this change, and do we have evidence to prove it?
Why the confusion exists
The overlap in language is real and it causes genuine problems. Both disciplines use words like impact assessment, risk, stakeholder, and approval. Both sit within large transformation programmes. In many organisations, the IT team and the change team are working on the same programme from completely different angles. The ITIL world also has a long head start. ServiceNow has been in the enterprise market for twenty years. OCM as a recognised software category is much newer. Most change managers are still working in spreadsheets because the tooling has not caught up with the discipline. That is starting to change.
What good OCM software looks like
A proper OCM platform should give a change manager visibility across the three things every programme needs to track:
- WHY: the benefits the organisation is trying to achieve, with owners, KPIs, and progress tracking
- WHO: the stakeholders affected, their level of impact, their engagement status, and who is responsible for managing each relationship
- WHAT: the specific changes landing on specific groups of people, mapped against roles and functions, with a clear view of where change load is building
Beyond those three, the best OCM tools also surface saturation, the point at which people are being asked to absorb more change than is realistic, and give change managers a way to track frontline sentiment without waiting for a formal survey cycle. None of that requires a Change Advisory Board. None of it involves a change ticket. It is an entirely different discipline, served by entirely different tooling.
The practical question
If you are evaluating tooling for your change programme and you have been looking at ITSM platforms, it is worth stepping back and asking what problem you are actually trying to solve.
If
I need to control and audit changes to our IT systems
Then
ITIL tooling is what you need. ServiceNow and TOPDesk are built for this.
If
I need to manage the impact of change on our people, track stakeholder engagement, measure benefits, and show leadership that our change programme is working
Then
That is OCM. And it needs a different kind of tool.
A note on methodology
OCM software should be methodology-agnostic. Whether you use ADKAR, Kotter, or your own approach, the platform should flex around how you work, not force you into a prescribed framework. Be wary of tools that are built around a single methodology. They work well for organisations that have bought into that approach and less well for everyone else.
theChangeTracker approach
THECHANGETRACKER APPROACH
theChangeTracker is an OCM platform built for change managers and project managers in mid-market organisations. It is not an ITIL tool, a project management tool, or a digital adoption platform. It works alongside any methodology, or none.
Managing the human side of change?
theChangeTracker gives you one place to track benefits, stakeholders, impacts, and readiness, without the enterprise price tag.
Sources
- Prosci. "What is Change Management?" prosci.com
- AXELOS. "ITIL 4 Foundation." axelos.com
- ServiceNow. "IT Change Management." servicenow.com