Should Change Management Be the PM's Job or Should They Get Support?

For internal and external projects, across varying levels of complexity and scale, the answer is: "it depends" — but we shouldn't normalize overload.

In small or low-impact projects, it’s often assumed the PM “owns” everything — scope, schedule, communication, and yes, change management.
While this may be manageable in the short term, it usually comes at the cost of depth, sustainability, and meaningful people engagement.

In large-scale or transformational initiatives, treating change management as a side task is a strategic risk.
Expecting the PM to lead technical delivery and support behavioral, cultural, or structural change — without dedicated support — is simply unrealistic.

The best outcomes I’ve seen stem from clear role separation: the PM leads execution, while a change leader supports the people transition — and they work in close partnership.

You're also right to point out that change management isn’t yet explicitly defined as a performance domain in the PMBOK® Guide — although the "Stakeholder" and "Team" domains do touch on aspects of it.
In more mature organizations, I’ve seen Change Management Offices embedded within the project structure, or at least specialized roles assigned to complex initiatives.

Ultimately, change is not just a deliverable — it’s a journey for people.
And supporting that journey often requires more than one backpack.

I’d love to hear how others have handled this in different organizational settings and maturity levels.

Your reflection is very accurate, and in fact opens the door to an important conversation about the limits of the project manager's role and how organizational change management issues are addressed.

It is true: change management (in the sense of changing behaviors, culture, or ways of working) is not a formal knowledge area in the PMBOK®, although it is mentioned as a critical complementary skill, especially in transformational environments. The guide recognizes that projects bring about change, but leaves it up to the organization to define how that impact is managed.

A transformation is a significant change that must be led by the business that wants to change. It should be run as a program, as it will be evaluated by the benefits it delivers to different stakeholder groups. Plus, it will include a portfolio of projects, some of which might be run by contractors who see their project as most important, like technology implementation or process improvement.

I have run several SAP roll-out projects for clients, and the client always retained responsibility for the business transformation intended by implementing SAP. Sometimes, parts of the change management scope, like training, stakeholder monitoring, or communication, were contracted too.

I think project managers have a large role to play in change management, certainly, since we handle so many of the specific pieces that bring process changes to life through projects we manage. However, PMs already handle so many domain and practice group areas that I think it's unfair to solely rely on a PM to conduct change management on a large scale. As others have said, depending on project scope the PM can manage an integrated change process within the project itself, but projects of increasing size/complexity that touch on other arms of the business will need assistance -- in my experience, usually from VP-level or above personnel. The organizations I've worked in are pretty flat and it's rare to have a dedicated business analyst role, so change comes with support from above.

Responsabilidade do Gerente de Projetos:

Planejamento e Avaliação de Impactos: O gerente de projetos deve avaliar as mudanças solicitadas ou necessárias e analisar seu impacto no cronograma, no orçamento e na qualidade do projeto. Ele deve planejar como implementar essas mudanças de maneira eficaz.

Comunicação: O gerente de projetos precisa manter as partes interessadas informadas sobre as mudanças e seus impactos. A comunicação clara é fundamental para garantir que todos os envolvidos compreendam os motivos e as consequências das mudanças.

Controle de Mudanças: É papel do gerente de projetos garantir que o processo de controle de mudanças seja seguido corretamente, registrando, analisando, aprovando ou rejeitando mudanças de maneira formal e documentada.

2. Suporte Necessário:

Partes Interessadas: O gerente de projetos não trabalha sozinho. A gestão de mudanças exige o envolvimento das partes interessadas para definir e avaliar o impacto das mudanças. Os líderes das áreas funcionais ou os patrocinadores do projeto podem fornecer o suporte necessário para decisões críticas sobre mudanças que afetem suas respectivas áreas.

Equipes Funcionais: Algumas mudanças podem exigir suporte específico de equipes técnicas ou operacionais. Por exemplo, mudanças no design do projeto podem exigir a colaboração de engenheiros ou arquitetos, e mudanças nos processos podem demandar a cooperação de departamentos de TI ou de recursos humanos.

Processos Organizacionais: Em algumas organizações, existem processos formais de gestão de mudanças, como a inclusão de uma comissão de controle de mudanças ou a implementação de softwares especializados que auxiliam o gerente de projetos no controle e rastreamento dessas alterações.

3. Gestão de Mudanças como Uma Competência:

A gestão de mudanças vai além de uma simples tarefa administrativa. Ela envolve a capacidade de lidar com resistências, alinhar expectativas e garantir que todos os envolvidos sigam as novas diretrizes de forma eficaz.

O gerente de projetos deve ser habilidoso não só em controlar as mudanças, mas também em gerenciar a aceitação delas por parte das equipes e das partes interessadas, garantindo que as alterações não impactem negativamente o andamento do projeto.

Good question, Francisco! In my experience, PMs often lead change efforts by default but effective change management needs dedicated focus. Ideally, a change lead or comms partner supports the PM. This ensures adoption, not just delivery, especially in people-heavy transformations.