Why every function has a partial claim

The reason so many functions feel entitled to claim change management expertise is that they are all, in a genuine sense, partially right. Change management as a discipline draws on theories and practices that have been developed across psychology, organisational behaviour, communications, project management, and HR. Each of these fields has made real contributions to our understanding of how individuals and organisations adapt. The problem arises when a partial contribution is mistaken for the whole discipline.

HR’s claim is grounded in the fact that people are at the centre of every change. Resistance, capability development, role redesign, and cultural alignment are all genuinely HR concerns, and the best HR practitioners bring sophisticated people skills to change work. What HR frameworks often underweight is the structural and portfolio-level complexity of managing multiple concurrent changes — the governance, sequencing, and organisational capacity questions that are distinct from any individual people initiative.

Project management’s claim is grounded in the reality that most organisational change is delivered through projects. Disciplined planning, risk management, milestone tracking, and resource allocation are essential to any successful transformation. But project management frameworks are designed to deliver defined outputs within a scope boundary. Change management is concerned with what happens to the organisation after the outputs are delivered — whether behaviours actually shift, whether capabilities are actually built, whether the change is actually absorbed into how work gets done.

Communications’ claim is well-founded because uncertainty is the primary psychological driver of change-related stress, and communication is the primary tool for replacing uncertainty with clarity. But communication without genuine understanding of the change’s impact on specific roles and workflows becomes messaging without meaning — polished announcements that tell employees what is changing without helping them understand what it means for how they do their job on Monday morning.

IT’s claim stems from the fact that many of the most significant organisational changes in recent decades have been system implementations — ERP rollouts, CRM migrations, digital transformation programmes — where adoption of a new technology platform is the primary measure of success. Technology change is real change management work, but it is a subset. Organisations that define change management as system adoption have implicitly limited their change capability to one category of change, leaving them less equipped for structural reorganisations, process redesigns, or strategic pivots that do not have a technology component.

The consequences of fragmented ownership

When change management ownership is fragmented across functions, several predictable problems emerge. The first is methodology inconsistency. Employees who have been through five transformations in three years may have experienced five different approaches to stakeholder engagement, five different formats for impact assessment, five different ideas about what “being consulted” means. This inconsistency erodes trust. When people cannot predict how change will be handled, they become cynical about the process before it has even begun.

The second problem is invisible cumulative load. No single function has a view across the entire change portfolio. HR sees the people initiatives. The PMO sees the project list. Communications sees the announcement schedule. But no one is looking at what all of these add up to for a specific team or role group at a specific point in time. The result is change saturation — teams absorbing more concurrent change than their adaptive capacity can handle — that is entirely visible in retrospect but was invisible to every function at the time.

The third problem is accountability diffusion. When everyone owns change management, no one is truly accountable for whether a change lands well. The PMO can point to on-time delivery. HR can point to the training programme that was run. Communications can point to the number of messages sent. But if adoption is low, productivity has not recovered, and employees are still doing things the old way six months after go-live, the responsibility can be passed indefinitely between functions. No one is accountable for the outcome, only for their slice of the input.

What genuine organisational change capability actually looks like

Genuine change management capability is not located in any single function, but it does require a recognised discipline with its own body of knowledge, its own accountability structures, and its own seat at the table when strategic decisions are made. The most capable organisations treat change management the way they treat other enterprise capabilities — as something that requires deliberate investment, clear ownership, and measurable standards.

The characteristics of organisations with mature change capability are well documented in the research literature. Prosci’s longitudinal research on change management best practices consistently finds that the highest-performing organisations share several features: dedicated change management practitioners who are not also wearing project management or HR hats; executive sponsorship that is active rather than nominal; structured methodology applied consistently across programmes; and formal mechanisms for capturing and applying lessons from past changes.

Critically, mature change capability is not about the size of the change team. Small change teams that have organisational authority, cross-portfolio visibility, and rigorous methodology consistently outperform larger teams that are embedded in individual functions without coordination. The key variable is not resource quantity but structural position.

The role of data in adjudicating functional claims

One of the reasons functional disputes about change management ownership persist is that they are typically conducted without data. Each function makes its claim on the basis of its professional identity and its past experience, not on the basis of evidence about what actually drives change outcomes in the specific organisation. This is a solvable problem.

Organisations that measure change outcomes — adoption rates, productivity recovery, attrition during transitions, error rates in new processes — quickly develop an evidence base for understanding which factors actually determine whether changes land well. In most organisations that collect this data systematically, the findings consistently point to the same variables: the quality of people leadership through the transition, the degree to which employees understood what the change meant for their specific role, the pace of change relative to the organisation’s absorption capacity, and the degree to which concerns raised during implementation were visibly acted upon.

Notably, these factors cut across all the functional claims. Quality people leadership is relevant to HR’s concerns. Understanding what change means for specific roles is a communications challenge. Absorption capacity is a portfolio management question. Acting on concerns is a governance issue. The data, in other words, vindicates the view that change management is genuinely cross-functional — while also making clear that it cannot be owned by any single function in isolation.

This is precisely the insight that drives the design of platforms like The Change Compass, which provides organisations with portfolio-level visibility into change load, impact, and capacity across the enterprise. Rather than giving any one function a proprietary view of the change landscape, this kind of platform creates a shared data layer that all functions can draw on — and that makes the aggregate picture visible to decision-makers who would otherwise be managing blind.

A framework for resolving functional tension

Rather than attempting to definitively answer which function should own change management — a question that will be answered differently in every organisation depending on history, structure, and culture — it is more useful to describe the conditions under which cross-functional change capability works well.

The first condition is a single point of accountability. Even when change management work is distributed across functions, there needs to be one person or team that is ultimately accountable for whether the organisation’s change portfolio is being managed well. This does not mean centralising all change activity — it means ensuring there is someone whose job it is to hold the cross-portfolio view and escalate when capacity constraints, methodology inconsistencies, or accountability gaps are creating risk.

The second condition is agreed methodology. Functions can and should contribute their specialist expertise to change work. But the overarching framework — how impact is assessed, how stakeholders are engaged, how readiness is measured, how adoption is tracked — needs to be consistent across programmes. Agreed methodology does not suppress functional contribution; it channels it.

The third condition is shared data. When all functions can see the same picture of the organisation’s change landscape — the same impact data, the same capacity measures, the same adoption indicators — functional disputes about ownership become less important, because the shared data makes the organisational need clear regardless of which team is doing the work. Harvard Business Review research on organisational judgment consistently finds that shared information reduces the inter-functional conflicts that arise from asymmetric awareness.

The fourth condition is executive sponsorship that cuts across functions. When the senior leader who sponsors the change management capability is positioned above the functional disputes — at the executive team level rather than embedded within any single function — it becomes possible to make governance decisions about methodology, accountability, and resource allocation that no individual function can make unilaterally.

Building maturity rather than winning territory

The framing of change management ownership as a territorial dispute — which function wins? — is ultimately counterproductive. The more useful question is: how does the organisation build mature change capability, and what role does each function play in that maturity journey?

Prosci’s change management maturity model describes five levels of organisational capability, from ad hoc and project-specific at the lower end to organisational competency and standardised methodology at the higher end. What distinguishes higher-maturity organisations is not that they have resolved the question of which function owns change management. It is that they have transcended the functional dispute entirely — change management has become an enterprise capability with its own governance, its own standards, and its own accountability, drawing on but not subordinated to any single function.

Reaching that level of maturity requires each function to make a genuine contribution: HR bringing its understanding of people and culture, the PMO bringing its project governance rigour, Communications bringing its ability to create meaning and clarity, IT bringing its implementation discipline. But it also requires each function to recognise the limits of its contribution — the things that its professional lens does not equip it to see.

The organisations that manage change most effectively are not those where one function has won the territorial dispute. They are those where the discipline has grown beyond the territory entirely.

Frequently asked questions

Why do so many functions claim change management expertise?

Change management draws on knowledge from HR, communications, project management, psychology, and organisational design. Each of these fields makes a genuine partial contribution to the discipline, which means that practitioners from each field can legitimately claim relevant expertise. The problem arises when a partial contribution is mistaken for the whole discipline, leading to fragmented ownership and inconsistent practice.

What are the consequences of fragmented change management ownership?

Fragmented ownership produces methodology inconsistency across programmes, invisible cumulative change load on employee groups, and diffused accountability for outcomes. When every function claims ownership and none is truly responsible for whether changes land well, the organisation loses the ability to learn systematically from change experience and to govern the change portfolio as a coherent whole.

Does change management belong in HR or the PMO?

Neither location is inherently correct. What matters more than location is structural position, accountability clarity, and methodology consistency. Change management capability that sits within HR tends to be strong on people and culture dimensions but may lack portfolio governance. Capability that sits within the PMO tends to be strong on project discipline but may underweight the sustained adoption and cultural dimensions of change. Many mature organisations establish change management as a distinct capability that draws on both functions without being subordinated to either.

What does genuine organisational change maturity look like?

Mature change capability is characterised by consistent methodology applied across programmes, cross-portfolio visibility into change load and capacity, clear accountability for change outcomes rather than just change activities, and systematic capture and application of lessons from past programmes. It is an enterprise capability with its own governance and standards, rather than an activity embedded within any single functional team.