A project can deliver a system, process, policy, or structure and still fail to deliver value if people continue working the old way. Integrating the change management plan with the project management plan closes that gap. It connects the technical delivery work—design, build, test, deploy—with the people-side work required for adoption, capability, reinforcement, and benefits realization [Prosci, 2025; ACMP, 2025]. (prosci.com)

This action sits in the adoption category of embedding change into day-to-day work. Its purpose is not to create a larger plan for the sake of governance. It is to make sure the new behavior appears in tasks, routines, tools, manager conversations, performance measures, standard operating procedures, and role expectations. McKinsey’s implementation guidance similarly emphasizes that sustainment depends on integrating new KPIs and routines into normal business operations, so the change becomes “the way of working,” not a side activity [McKinsey, 2018]. (mckinsey.com)

Integrating the plans means taking the change management activities—impact assessment, stakeholder engagement, manager coaching, training, readiness checks, resistance management, reinforcement, and adoption measurement—and placing them into the project’s delivery schedule, governance rhythm, risk log, decision points, and benefits plan. ACMP’s standard explicitly identifies “Integrate the Change Management and Project Management Plans” as part of developing the change management plan and emphasizes coordination with project leadership to avoid duplication and align milestones [ACMP, 2025]. (acmpmexico.org)

Use this action when the change requires people to do work differently: adopt a new system, follow a new process, use new decision rights, stop using an old workaround, serve customers differently, or take on new role expectations. It is most valuable at project initiation, before design decisions are locked, before pilot or user acceptance testing, before go-live, and during hypercare. If the project is already underway, use it as a recovery intervention when adoption risk, manager confusion, resistance, or old workarounds are visible.

Before facilitating integration, gather the current project plan or agile roadmap, change strategy, impact assessment, stakeholder map, training plan, communications plan, business process maps, role descriptions, risk log, benefits case, and any adoption or performance metrics. PMI’s practice guide positions organizational change as something that should be designed, implemented, and sustained through portfolio, program, and project approaches, so the change manager should work from project artifacts rather than in a parallel change silo [PMI, 2013]. (pmi.org)

The essential stakeholders are the project manager, change manager, sponsor, product or process owner, impacted people managers, HR or L&D partners, communications support, frontline representatives, and data owners. The key decisions are: what new behaviors must be visible by go-live; which old routines, templates, reports, or tools must be retired; who will reinforce the change after project closure; and what adoption evidence will be reviewed in normal business meetings.

1. Align on the adoption outcome. Begin with a short working session. Ask: “What must people do differently for this project to deliver value?” Translate the answer into observable behaviors. Prosci’s ADKAR model is useful here because it frames adoption as individual movement through Awareness, Desire, Knowledge, Ability, and Reinforcement [Prosci ADKAR]. (prosci.com)

2. Map people impacts to project milestones. For each project milestone, identify what impacted groups need before, during, and after it. For example, before testing, users may need process walk-throughs; before go-live, managers may need coaching guides; after go-live, teams may need floor support and performance feedback. Prosci recommends aligning change milestones with project milestones so people are ready and able at the right point in the lifecycle [Prosci, 2025]. (prosci.com)

3. Add change work into the project plan. Insert adoption tasks into the schedule or backlog with owners and due dates. Do not leave “training” or “communications” as broad placeholders. Add specific deliverables such as manager briefing, role-based practice session, SOP update, old-tool shutdown, performance dashboard update, help-channel staffing, and reinforcement huddle.

4. Integrate risks and decisions. Add adoption risks to the project risk log: manager capacity, low readiness, unclear process ownership, conflicting incentives, union or employee relations concerns, data quality issues, or continued use of legacy tools. Decide which risks require sponsor escalation.

5. Equip managers to reinforce the new way. Gallup emphasizes that managers play a central role in answering employee questions, handling emotional reactions, and escalating feedback during change [Gallup, 2020]. Give managers talking points, observation prompts, escalation routes, and permission to remove old workarounds. (gallup.com)

6. Build feedback and adaptation into governance. Add adoption metrics and employee feedback to project meetings, stand-ups, steering committees, and business reviews. CIPD’s guidance on employee voice emphasizes that managers and leaders should listen, act on feedback, and create safe channels for people to raise concerns [CIPD]. (cipd.org)

A sales organization is implementing a new CRM and account planning process. The project plan originally includes configuration, data migration, testing, training, and go-live. The change manager facilitates an integration workshop and adds adoption tasks: managers will review pipeline hygiene in weekly team meetings, old spreadsheets will be archived two weeks after go-live, account plan quality will be sampled, sales scripts will be updated, and top objections will be reviewed daily during hypercare.

The plan also adds a readiness checkpoint before go-live. If fewer than 80% of managers can demonstrate the new coaching routine, the sponsor agrees to delay decommissioning the old report by one week while manager support is intensified. This protects adoption without losing accountability.

Use a mix of leading, behavioral, and outcome indicators. Leading indicators include manager briefing completion, readiness scores, practice participation, open risks, and help-channel themes. Behavioral indicators include system usage, process compliance, quality of completed work, reduction in old workarounds, manager observation results, and employee-reported confidence. Outcome indicators include cycle time, error rate, customer experience, productivity, revenue, cost, safety, or compliance results tied to the business case. McKinsey’s sustainment guidance stresses that new KPIs should be integrated into day-to-day business operations, not reviewed separately as a temporary project dashboard [McKinsey, 2018]. (mckinsey.com)

Prosci. “Integrating Change Management and Project Management.” Published May 14, 2025; updated August 7, 2025.
​https://www.prosci.com/blog/integrating-change-management-and-project-management

Association of Change Management Professionals. “Standard for Change Management© 2.0.” 2025.
​https://acmpmexico.org/wp-content/uploads/2025/10/ACMP_Standard_2.0.pdf

Project Management Institute. “Managing Change in Organizations: A Practice Guide.” 2013.
​https://www.pmi.org/shop/p-/book/managing-change-in-organizations-a-practice-guide/00101469401

Prosci. “The Prosci ADKAR® Model.” No publication date shown.
​https://www.prosci.com/methodology/adkar

McKinsey & Company. “How to implement and sustain organizational change.” July 3, 2018.
​https://www.mckinsey.com/capabilities/implementation/our-insights/how-to-implement-and-sustain-organizational-change

Gallup. “Proven Change Management Principles: How to Effectively Initiate It.” July 15, 2020.
​https://www.gallup.com/workplace/315602/proven-change-management-principles-effectively-initiate.aspx

CIPD. “Employee Voice.” No publication date shown.
​https://www.cipd.org/en/knowledge/factsheets/voice-factsheet/