Introduction: why this action matters for adoption

Establishing project scope during a change is more than defining deliverables. For adoption, scope clarifies who is affected, what will change in day-to-day work, what support will be provided, who can make decisions, and how success will be judged. PMI defines project scope as the work performed to deliver a result with specified features and functions, while a scope statement describes major deliverables, assumptions, and constraints [PMI, 2026]. In change work, that definition needs to extend to impacted groups, behavior changes, readiness, sponsorship, learning, and sustainability [ACMP, 2025]. (pmi.org)

When scope is vague, managers give inconsistent answers, sponsors approve work without resourcing adoption, and employees experience “moving targets.” Empirical research on construction projects found that scope creep factors were negatively associated with project success, with complexity worsening the relationship [Ahmed & Jawad, 2022]. The setting is specific, but the practical lesson is highly relevant: unclear boundaries create adoption risk as well as delivery risk. (sciencedirect.com)

What this action is and when to use it

This action is a facilitated scope agreement for the people side and operating model side of a change. It creates a documented, actively used agreement about the change boundaries, impacted populations, adoption support, responsibilities, governance cadence, decision rights, and success measures.

Use it when a project charter exists but the adoption implications are unclear; when multiple teams, functions, regions, or vendors are involved; when leaders disagree about what is “in scope”; when managers are being asked to support a change without clear time or resources; before pilots, launches, phase gates, or major design decisions; and whenever resistance is being amplified by uncertainty. Government Project Delivery guidance states that organizational change should be addressed and planned into solution design and delivery from the start, and that readiness and progress toward the future state should be assessed throughout the life cycle [Government Project Delivery, 2025]. (projectdelivery.gov.uk)

Preparation: inputs, stakeholders, materials, timing, and decisions needed

Bring the project charter or business case, current and future process views, known requirements, stakeholder and impact assessments, readiness data, risk and issue logs, resource assumptions, manager feedback, and draft benefits or adoption measures. Invite the sponsor, project manager or product owner, change manager, process owner, HR/L&D or communications partners, representative people managers, impacted employee representatives or SMEs, and any function that owns policy, data, controls, or operations.

Use a simple scope canvas, an in-scope/out-of-scope log, a decision-rights table, a RACI, and a parking lot for unresolved assumptions. PMI defines a RACI matrix as a responsibility assignment matrix using responsible, accountable, consulted, and informed categories [PMI, 2026]. Run the session early enough to influence solution design, then revisit it at design approval, pilot exit, launch readiness, and transition to business-as-usual. (pmi.org)

Step-by-step facilitation guide

Start with the adoption outcome. Ask: “What must people do differently, consistently, for this change to deliver value?” This keeps the conversation from becoming only a deliverables review. Prosci describes project management as the technical side and change management as the people side; both need a shared definition of success [Prosci, 2025]. (prosci.com)
Map the affected work. Confirm which processes, roles, teams, systems, policies, locations, customer moments, reports, controls, and handoffs will change. For executives, frame this as value and risk. For managers, translate it into workload, coaching, scheduling, and performance expectations. For employees, focus on “what changes for me.”
Draw the boundaries. Define what is in scope, out of scope, and undecided. Include adoption support, not only technical outputs: training, manager toolkits, reinforcement, help channels, floor support, job aids, data migration support, process coaching, and transition rules.
Surface assumptions and constraints. Ask what must be true for adoption to work: time for training, manager capacity, policy approval, union or works council consultation, data quality, operational backfill, or system access. Government Project Delivery guidance says plans should include assumptions, constraints, dependencies, schedule, cost, resources, assurance, and decision activities [Government Project Delivery, 2025]. (projectdelivery.gov.uk)
Agree decisions and roles. Identify who approves scope, who owns adoption readiness, who resolves cross-functional conflicts, and who can accept trade-offs between time, cost, quality, risk, and adoption. Prosci emphasizes distinct roles for sponsors, people managers, project managers, change practitioners, and impacted employees [Prosci, 2026]. (prosci.com)
Test the scope against resistance. If resistance is low, validate quickly with representative managers. If resistance is moderate, add listening sessions and a stronger feedback loop. If resistance is high, slow down the decision, name the concerns, and separate negotiable scope from non-negotiable business constraints. Gallup advises involving the right people based on the type of change and influence dynamics, and giving managers ownership of interpersonal aspects of change [Gallup, 2020]. (gallup.com)
Set change-control rules. Decide how new requests will be logged, impact-assessed, approved, deferred, or rejected. Changes to a baseline should be controlled, impact-assessed, communicated, and incorporated into updated records [Government Project Delivery, 2025].
Document and activate. Publish a one-page scope agreement, use it in sponsor updates and manager briefings, and review it in every readiness meeting. A scope document that is approved but not used is not governance; it is archive material.

Example: how this could be applied in a real change initiative

A company is implementing a new CRM and sales operating rhythm. The project team initially defines scope as “launch CRM to the enterprise sales team.” The change manager facilitates a scope session and reveals that adoption also requires new pipeline stages, manager inspection routines, revised sales meeting agendas, mobile access, data hygiene rules, and coaching for regional managers.

The final scope agreement includes two pilot regions, 300 sales users, manager coaching sessions, revised reporting definitions, and hypercare for four weeks after go-live. Compensation redesign, marketing automation, and advanced AI forecasting are explicitly out of scope for phase one. When a senior leader later requests a new dashboard before launch, the team uses the change-control rule to assess impact and defers it to phase two rather than quietly overloading the pilot.

Roles and responsibilities

Role	Responsibility
Sponsor	Owns business outcomes, approves scope trade-offs, removes barriers, and reinforces priorities.
Change manager	Facilitates scope alignment, translates impacts into adoption support, maintains the scope agreement, and monitors readiness.
Project manager/product owner	Owns technical delivery scope, dependencies, schedule, risks, and integration with change activities.
People managers	Validate team impacts, coach employees, raise local risks, and reinforce new behaviors.
Adoption leads/champions	Test practicality, collect feedback, support peer adoption, and identify confusion early.
Impacted employees	Provide input on work realities and adopt the agreed new processes, tools, or behaviors.

People managers are especially important because they connect strategy to day-to-day work and influence change interventions and new practices [CIPD, 2023]. (cipd.org)

Common mistakes to avoid

The first mistake is confusing technical scope with adoption scope. A system can be delivered while the operating model remains unclear. The second is leaving managers out until launch; this creates avoidable resistance because managers cannot answer practical employee questions. The third is treating “out of scope” as negative. In reality, clear exclusions protect focus and help sponsors make transparent trade-offs. The fourth is accepting new work without adjusting time, cost, resources, or adoption support, which PMI defines as scope creep when expansion is uncontrolled [PMI, 2026]. (pmi.org)

Measures of success or adoption indicators

A clear scope intervention is working when stakeholders can explain what is changing and what is not; managers can describe their role; unresolved assumptions are shrinking; scope changes are being logged and impact-assessed; and readiness discussions focus on decisions rather than confusion. Adoption indicators should include usage of the new process or tool, proficiency, manager coaching completion, employee sentiment, help requests, process compliance, operational performance, and benefit realization. ACMP includes change performance measurement, monitoring progress, and sustaining the change as part of change management practice [ACMP, 2025]. (acmpmexico.org)

Checklist for the change manager

Scope includes impacted groups, behaviors, support, roles, decisions, resources, and success measures.
In-scope, out-of-scope, and undecided items are documented.
Sponsor, project lead, process owner, and manager representatives have reviewed and agreed.
Adoption risks and assumptions have owners.
Scope-change rules are clear and actively used.
Managers have a practical version they can explain to teams.
The scope agreement is revisited at each phase gate, pilot review, and launch readiness check.

Optional reusable worksheet: change scope canvas

Question	Working answer
What business outcome is this change meant to enable?
Which employee groups, roles, locations, or customers are impacted?
What must people do differently after the change?
What adoption support is in scope?
What is explicitly out of scope for this phase?
What assumptions or constraints could affect adoption?
Who approves scope changes?
What measures will show adoption is occurring?
When will scope be reviewed next?

References

PMI Lexicon of Project Management Terms, Version 5.0. Project Management Institute. 2026.
https://www.pmi.org/-/media/pmi/documents/registered/pdf/pmbok-standards/pmi-lexicon-pm-terms.pdf

Government Functional Standard GovS 002: Project Delivery. Government Project Delivery Function. Published 1 September 2025; last modified 29 March 2026.
https://projectdelivery.gov.uk/library-products/government-functional-standard-govs-002-project-delivery/

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

Core Roles in Change Management. Prosci. Published 20 May 2020; updated 1 May 2026.
https://www.prosci.com/blog/core-roles-in-change-management

Effective People Managers: An Evidence Review. CIPD. 2023.
https://www.cipd.org/globalassets/media/knowledge/knowledge-hub/evidence-reviews/2023-pdfs/8424-effective-people-managers-practice-summary.pdf

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

Ahmed, R., and Jawad, M. “Avoiding or Disregarding: Exploring the Relationship Between Scope Creep, Project Complexity, and the Success of Construction Projects.” Project Leadership and Society, Volume 3, December 2022.
https://www.sciencedirect.com/science/article/pii/S2666721522000242

How to Define Change Scope Clearly and Set Teams Up for Adoption