A change initiative often fails in the gap between “approved” and “adopted.” Appointing a project manager to manage the project lifecycle closes part of that gap by creating a visible owner for planning, coordination, risks, dependencies, escalation, and follow-through. This is a change-management intervention in governance, planning, and operating model design because it clarifies how decisions will be made, how work will be sequenced, and how impacted groups will receive practical support.

APM defines governance as the authority and accountability framework that controls project outputs, outcomes, and benefits [APM Governance]. (apm.org.uk) Prosci similarly emphasizes that project management and change management should work together so technical delivery and human adoption are both managed across the lifecycle [Prosci, 2025]. (prosci.com)

This action establishes that a named project manager is formally appointed, documented, and empowered to manage the lifecycle of the project during a change. APM describes a project life cycle as distinct high-level stages that turn an idea into reality in an orderly way [APM Life Cycle]. (apm.org.uk) The project manager’s role is to coordinate that journey, not merely maintain a task list.

Use this action when a change has cross-functional impacts, unclear ownership, multiple workstreams, adoption risks, competing manager priorities, or repeated delays in decisions. It is especially useful before solution design, before launch, after a troubled pilot, or when frontline managers are asking, “Who is actually running this?”

Before facilitating the appointment, gather the project brief, business case, impact assessment, known milestones, risk log, stakeholder map, current governance structure, and any existing change plan. APM describes the project manager as responsible for day-to-day management across scope, schedule, finance, risk, quality, and resources [APM Project Manager]. (apm.org.uk)

The key stakeholders are the sponsor or SRO, project manager candidate, change lead, PMO, business owner, people managers from impacted areas, product or process owner, HR/L&D where relevant, and representatives from operations. The sponsor or governance body should decide appointment authority, decision rights, budget access, reporting cadence, escalation route, and whether the project manager owns all workstreams or coordinates several leads. PMI’s governance research notes that steering groups often appoint the project manager, set constraints, define goals, provide resources, and advise the project manager [PMI, 2016]. (pmi.org)

A company is replacing its manual field-service scheduling process with a new mobile workflow. Supervisors are worried about technician resistance and customer delays. The sponsor appoints a project manager before pilot planning. The role charter gives the project manager authority to coordinate process design, pilot readiness, training dependencies, risk reviews, and go-live decisions. The change lead owns stakeholder engagement, training approach, and adoption measurement. Supervisors own local coaching and resistance feedback.

During the pilot, technicians report that job notes are hard to enter in the app. Because the project manager has an agreed escalation path, the issue is logged, prioritized, and resolved before full deployment. Adoption improves because the lifecycle is actively managed rather than pushed through a date-driven launch.

A common mistake is appointing someone in name only while decisions still bypass them. Another is assuming a strong project manager can compensate for an absent sponsor. PMI’s governance research distinguishes governance support, resources, and steering decisions from day-to-day management [PMI, 2016]. (pmi.org)

Also avoid appointing the project manager too late, after design choices and launch dates are fixed. That turns the role into issue administration rather than lifecycle management. Finally, do not let role clarity become rigid bureaucracy. The goal is enough structure to accelerate decisions and adoption, not a governance layer that slows learning.

The action is working when stakeholders can name the project manager, decisions move through the agreed route, risks are visible before they become crises, managers know where to escalate adoption barriers, and phase-gate decisions include readiness evidence. Prosci recommends looking beyond traditional delivery measures to adoption-related indicators such as utilization, proficiency, stakeholder engagement, and sustainment [Prosci, 2025]. (prosci.com)

Useful indicators include fewer unresolved decisions, fewer duplicate workstream meetings, on-time completion of readiness activities, manager confidence scores, training completion and proficiency, usage data after go-live, resistance themes resolved, and benefits measures reviewed after stabilization.

Project manager appointed:
​Sponsor/SRO:
​Change initiative:
​Lifecycle phases in scope:
​Primary outcomes and adoption goals:
​Project manager decision rights:
​Decisions requiring sponsor approval:
​Key partners: Change lead, PMO, business owner, people managers, product/process owner
​Cadence: Weekly delivery review; fortnightly adoption review; monthly sponsor decision forum
​Escalation path:
​Success indicators: Delivery milestones, readiness, adoption, proficiency, benefits, unresolved risks
​Date effective:
​Review date: