Article
Share this article
Follow us on Linkedin
One of the most common mistakes we see in transformation programs is the assumption that Organizational Change Management can be folded into the project team, or carried by the Project Manager on top of everything else. Project management and OCM have to work closely together, but they are not the same discipline. They pursue different objectives, rely on different skills, are judged by different measures of success, and need their own leadership.
The Central Point
A project can be delivered on time and within budget, yet still fail to create value if people do not adopt the new way of working.
The misconception: “The Project Manager can handle change”.
At first, handing OCM to the Project Manager sounds practical. The PM already coordinates stakeholders, tracks activities, manages deadlines, reports risks, and drives the implementation, so communication, training, and engagement can look like more of the same. But change asks for a different lens. A Project Manager is accountable for delivering the solution. A Change Manager is accountable for preparing the organization to use it.
Project management and OCM solve different problems.
Project management asks whether the solution is delivered. OCM asks whether the organization is ready, willing, and able to adopt it. The contrast is easiest to see side by side:
Project Management
Delivers scope, schedule, budget, and quality
Coordinates implementation activities
Manages project risks and dependencies
Measures delivery progress
Asks: “Did we deploy it?”
Organizational Change Management
Builds understanding, readiness & commitment
Engages leaders, managers, and impacted groups
Identifies resistance and adoption risks
Measures readiness, adoption, and reinforcement
Asks: “Are people using it effectively?”
Simple Distinction
Project management helps the organization reach go-live. OCM helps the organization move beyond go-live into sustained adoption.
Why the roles can conflict.
In our experience the two roles can also pull against each other, and it helps to be honest about that. When timelines tighten, a Project Manager has to protect delivery, which in practice often means compressing workshops, shortening training, scaling back engagement, or pushing adoption work to after go-live. That is not bad project management. It reflects the PM’s core accountability for schedule, scope, and cost. The problem is that the activities first on the chopping block are usually the very ones that prepare people for the change. A separate OCM lead gives us an independent voice in that moment, someone who can spell out the adoption cost of a delivery decision and make people-related risks visible before they turn into operational problems.
OCM is a specialism, not a side task.
OCM is a specialism in its own right. A capable Project Manager can book a training session. An experienced OCM practitioner works out who actually needs training, what has changed in each role, which barriers will get in the way, how managers should reinforce the learning, and how capability will hold up after go-live. Strong OCM leadership brings real depth across stakeholder analysis and engagement, change impact and readiness assessment, leadership alignment and sponsorship, communication strategy and message design, resistance management and feedback loops, training strategy and role-based capability building, and adoption measurement and reinforcement.
It is also more than communication and training. When OCM is treated as a side task, it usually shrinks to newsletters, slide decks, and a training calendar. Those things matter, but they are only a fraction of the work. Real OCM connects leadership, stakeholder engagement, change impacts, readiness, communication, learning, adoption, and reinforcement, so that people understand what is changing, why it matters, what they need to do differently, and how they will be supported.
Why OCM needs its own team and manager.
So why does OCM need its own team and its own manager? Six reasons stand out:
1
Clear accountability
Someone has to be directly accountable for adoption, not just for completing change-related tasks.
2
Protected capacity
The work needs sustained attention, and a dedicated team keeps critical people activities from slipping behind technical delivery.
3
Independent reporting
Leaders need a clear read on readiness, resistance, stakeholder sentiment, and adoption risk alongside the usual project dashboard.
4
Consistent methodology
A specialist OCM manager makes sure that stakeholder, impact, communication, training, and adoption activities work as one integrated approach.
5
Stronger business connection
OCM works across both the project and the business, helping leaders and line managers translate the transformation into practical changes for their teams.
6
Better long-term outcomes
A dedicated function stays focused on behavior, capability, reinforcement, and benefit realization well beyond the deployment milestone.
The right operating model: partnership, not duplication.
None of this means separating OCM from the program. The right model is partnership, not duplication: give OCM clear ownership and integrate it tightly with delivery. The Project Manager owns delivery governance, scope, schedule, budget, dependencies, and implementation coordination. The OCM Manager owns the change strategy, stakeholder readiness, engagement, learning, adoption, and reinforcement. The two share risks, align their plans, coordinate milestones, and advise the sponsor from their own perspectives.
What Good Looks Like
Two connected workstreams, each with clear accountability, working toward one transformation outcome.
A practical test for leaders.
If a program still expects one person to carry both, we would ask a few plain questions. Who has final accountability for adoption? Who can challenge a timeline decision that creates readiness risk? Who is measuring whether new behaviors are actually taking hold? Who is coaching sponsors and people managers? And who stays focused on adoption when delivery pressure climbs? If the answer to all of them is “the Project Manager,” the program has handed out OCM activities, but it has not put OCM leadership in place.
Conclusion.
In our experience, Project Managers make excellent partners to OCM. They support engagement, protect dependencies, align schedules, and clear delivery barriers. But asking them to lead OCM as a bolt-on responsibility builds in an avoidable conflict between delivery pressure and adoption needs. OCM earns its own team, capacity, methodology, and leadership because it answers a different question: not simply how to implement a change, but how to get an organization to embrace it and keep it.
Final Thought
Technology creates the possibility of value. Project management delivers the solution. OCM helps people turn that solution into results.
