Skip to Content

What is the difference between a Change Manager and a Project Manager?

The Role of a Change Manager and How It Differs from a Project Manager.

Change Managers and Project Managers are both critical to the success of initiatives, but their roles focus on different aspects of delivery. While the Project Manager (PM) ensures that a project is delivered on time, within budget, and meets its objectives, the Change Manager (CM) ensures that the people impacted by the project adopt the changes effectively to achieve the desired business outcomes.

What Does a Change Manager Do?

The Change Manager focuses on the people side of change, ensuring a smooth transition from the current state to the desired future state.

Key Responsibilities

  1. Change Strategy and Planning:
    • Develop a change management strategy based on the project scope and the organization's culture.
    • Identify and assess the impact of changes on stakeholders.
  2. Stakeholder Engagement and Communication:
    • Build awareness and buy-in among stakeholders.
    • Design and execute communication plans to keep stakeholders informed and engaged.
  3. Training and Support:
    • Develop and implement training programs to upskill users on new tools, processes, or systems.
    • Provide post-implementation support to address adoption challenges.
  4. Measuring Success:
    • Define metrics for adoption and usage (e.g., employee satisfaction, productivity).
    • Monitor and report on adoption progress, making adjustments as necessary.

Example

In an ERP system implementation:

  • The Change Manager works to ensure employees across departments adopt the new system by addressing resistance, providing training, and communicating the benefits.

What Does a Project Manager Do?

The Project Manager focuses on the technical and logistical aspects of project delivery.

Key Responsibilities

  1. Project Planning and Execution:
    • Develop and manage the project plan, including timelines, milestones, resources, and budgets.
    • Ensure deliverables meet the agreed scope and quality standards.
  2. Risk and Issue Management:
    • Identify and mitigate risks that could derail the project.
    • Resolve issues that arise during execution.
  3. Team Coordination:
    • Lead cross-functional teams to ensure tasks are completed on time.
    • Facilitate collaboration among stakeholders.
  4. Governance and Reporting:
    • Regularly update stakeholders on project progress.
    • Ensure adherence to organizational governance standards.

Example

In the same ERP system implementation:

  • The Project Manager ensures the system is configured, tested, and deployed according to the project plan.

Key Differences Between Change Manager and Project Manager

AspectChange ManagerProject Manager
FocusPeople and behavioral adoptionDeliverables and technical implementation
Success MetricsEmployee adoption, resistance reductionOn-time, on-budget delivery
ScopeCultural and organizational change impactsTechnical and process-related tasks
Stakeholder InteractionPrimarily user-focusedBroadly across technical and business teams
Training and CommunicationCore responsibilityMinimal involvement, relies on CM

How They Work Together

The Change Manager and Project Manager collaborate closely to ensure both technical delivery and people adoption succeed.

Example Collaboration

In a digital workplace transformation:

  1. Project Manager ensures the tools (e.g., Microsoft Teams) are deployed.
  2. Change Manager ensures employees understand and adopt the tools, creating usage guides, conducting workshops, and addressing resistance.

Potential Gaps Without Collaboration

  • Without a Change Manager:
    • The project is delivered technically but adoption fails (e.g., employees refuse to use a new CRM system).
  • Without a Project Manager:
    • The project lacks clear timelines and structure, leading to missed deadlines or budget overruns.

References and Citations

  1. Prosci. (n.d.). What is Change Management? Retrieved from https://www.prosci.com.
  2. PMI. (2021). The Standard for Project Management. Retrieved from https://www.pmi.org.
  3. Kotter, J. P. (1996). Leading Change. Harvard Business Review Press.
  4. Atlassian. (n.d.). Change Management vs. Project Management. Retrieved from https://www.atlassian.com.
  5. Harvard Business Review. (2018). Why Organizations Don’t Learn. Retrieved from https://hbr.org.

By combining technical execution and behavioral adoption, both roles ensure that projects not only deliver their intended outcomes but also achieve long-term success.

Share this post
Our blogs
Archive
Double Diamond in Product and Project Lifecycle Management