Change Management Office (CMO) vs Project Management Office (PMO): Understanding the difference
- Lena Ross
- 2 hours ago
- 4 min read

In organisations, two functions exist to navigate increasingly complex change: the Project Management Office (PMO) and the Change Management Office (CMO).
At first glance, they may appear similar because they both:
- provide governance
- support initiatives
- seek to improve outcomes
- work with leaders, sponsors and delivery teams.
And both are often asked the same question:
"What exactly do you do?"
Because of these similarities, PMOs and CMOs are frequently confused with one another. In some organisations they compete for influence, while in others they operate in silos. Yet the reality is that these functions are not competitors. They are complementary capabilities that, when working together, significantly improve the likelihood of successful organisational change.
Why the confusion exists
Traditionally, organisations have invested heavily in project management capability. PMOs have become an established part of the corporate landscape, providing governance, standards, reporting and oversight for projects and programs.
When a Change Management Office is proposed, a common reaction is:
"Don't we already have a PMO?"
It's a fair question.
The PMO provides structure for delivering initiatives. This is about delivery and implementation. The CMO provides structure for helping people adopt and sustain those initiatives. This is about the human factors, behaviours and mindset to build long-term change capability.
Both are concerned with introducing something new, but they focus on different dimensions of it.
This table provides a quick summary of the differences:
Project Management Office | Change Management Office |
Focus on project delivery | Focus on change adoption |
Project governance | Change governance |
Schedules, budgets, risks | Readiness, adoption, resilience |
Builds delivery capability | Builds change capability |
Measures project success | Measures change success |
What a PMO does
A Project Management Office exists to improve the consistency, governance and success of projects and programs.
Typical PMO responsibilities include:
Project governance and assurance
Delivery frameworks and methodologies
Resource planning
Portfolio reporting
Risk and issue management
Schedule and budget oversight
Benefits tracking
The PMO asks questions such as:
Are we delivering on time?
Are we within budget?
Are risks being managed?
Are dependencies understood?
Is the project meeting its objectives?
Without strong project management discipline, even the best ideas can fail before they are implemented.
What a CMO does
A Change Management Office takes a different perspective.
Rather than focusing solely on individual projects, the CMO focuses on building enterprise change capability, maturity and resilience across the organisation.
According to my research and experience working with organisations establishing CMOs, common functions include:
Enterprise change methodology and tools
Change capability development
Advisory services for leaders and practitioners
Governance and reporting
An enterprise view of change
Building strong alignment with the PMO
The CMO asks different questions:
Do our leaders know how to lead change?
How much change is the organisation absorbing right now?
Are we building change resilience?
Are employees adopting and sustaining new ways of working?
How mature is our change capability?
What can we learn from previous change initiatives?
Where the PMO focuses on project success, the CMO focuses on people success and organisational readiness.
Delivery Capability vs Change Capability Simply put, a simple way to understand the distinction is this:
The PMO builds delivery capability.
The CMO builds change capability.
A PMO helps organisations deliver projects more effectively.
A CMO helps organisations become better at navigating change itself.
This distinction becomes increasingly important in environments where change is continuous rather than occasional.
When organisations face digital transformation, regulatory shifts, restructures, new technologies and evolving customer expectations simultaneously, they need more than project delivery excellence. They need the ability to adapt repeatedly and sustainably.
This is where the CMO creates value.
Where the two functions meet
The most successful organisations recognise that PMOs and CMOs are stronger when working together.
In fact, one of the key functions of the CMO is building a close working relationship with the PMO so that project and change approaches are integrated.
Think of it this way:
A project can be delivered perfectly from a technical perspective and still fail if people do not adopt the change.
Likewise, a strong change approach cannot compensate for poor project governance, unclear scope or ineffective delivery.
Successful transformation requires both.
The PMO brings delivery discipline.
The CMO brings people-centred adoption and organisational capability.
Together, they provide a more complete picture of what success looks like.
The evolution of organisational capability
Interestingly, many organisations establish a PMO years before they consider creating a CMO.
This reflects the evolution of organisational change maturity.
Historically, success was measured by project outputs. Today, organisations are increasingly recognising that outputs alone do not create value.
Value is only realised when people embrace and sustain the intended change.
This growing awareness has led many organisations to establish or revive a Change Management Office as a strategic capability-building function.
The conversation shifts from:
"Did we deliver the project?"
to
"Did the change stick?"
and eventually to
"How do we become better at change as an organisation?"
It's not PMO or CMO. It's PMO and CMO.
The debate should not be about which function is more important.
Both play a critical role.
The PMO helps ensure projects are delivered effectively.
The CMO helps ensure organisations and people are ready, willing and able to adopt the outcomes.
As change is now relentless and continuous, organisations need both delivery excellence and change excellence.
The PMO provides the framework for execution.
The CMO builds the capability, resilience and maturity needed to thrive in an environment of ongoing change.
The organisations that recognise this distinction, and intentionally connect the two functions, are able to realise greater value from their investments in change.




























Comments