A work breakdown structure, or WBS, is not just a project planning artifact. Used well, it helps the change manager see what the project will actually deliver, when impacted groups will feel the change, and where adoption work must be built into the delivery plan. PMI defines a WBS as the hierarchical decomposition of the total scope of work needed to accomplish project objectives and create required deliverables [PMI Lexicon, 2026]. For change managers, that matters because adoption depends on connecting the technical work to the people work: stakeholder engagement, manager readiness, training, behavior change, and reinforcement. (pmi.org)

Requesting the WBS is a stakeholder engagement and commitment intervention. It secures a concrete deliverable from the project manager and creates a shared planning basis for impacted groups. This is especially important because WBS information supports schedule, cost, resource, risk, quality, change management, and status reporting decisions [PMI/Lukas, 2014]. (pmi.org)

This action is a specific, time-bound request to the project manager for the current WBS, relevant WBS dictionary details, and any assumptions or unresolved scope items that affect adoption planning. The change manager is not asking to take over project planning. The purpose is to translate delivery scope into adoption implications.

Use this action when the project is moving from discovery into planning, when a scope change is being considered, before training and communications are finalized, or when impacted managers are asking practical questions such as “What is changing for my team?” and “When will we need to be ready?” It is also useful when adoption activities are missing from the project plan, because a work package is the WBS level where cost, effort, duration, and resources can be estimated and managed [PMI Lexicon, 2026]. (pmi.org)

Before making the request, review the business case, scope statement, known impacted groups, change impact assessment, project schedule, risk log, and any adoption deliverables already promised. Clarify whether you need the full WBS or only the portions that affect people, process, systems, data, policy, learning, communications, or readiness.

Stakeholders typically include the project manager, change manager, sponsor, business owner, PMO, workstream leads, HR or learning leads, communications, and representatives of impacted managers. If terminology is causing confusion, distinguish the WBS from a product breakdown structure or a task list. APM notes that product and work breakdown structures have different purposes and can lose effectiveness when language is used loosely [APM]. (apm.org.uk)

The best timing is after major deliverables are known but before the schedule and budget are treated as final. If the baseline is already approved, ask how updates will be handled through governance, because PMI defines a change request as a formal proposal to modify a document, deliverable, or baseline [PMI Lexicon, 2026]. (pmi.org)

In an ERP rollout, the project schedule may show “training complete” four weeks before go-live. The WBS may reveal several underlying deliverables: role mapping, data migration, workflow design, access provisioning, testing, training materials, and cutover support. During the review, the change manager discovers that frontline supervisors need new approval routines but no manager coaching work package exists. Because line managers help make transformation tangible for frontline employees, this gap is material to adoption [McKinsey, 2021]. (mckinsey.com)

The change manager asks the project manager to add or link adoption work packages for supervisor briefings, scenario-based practice, hypercare scripts, and readiness checkpoints. The sponsor agrees that these items will be tracked in the steering committee dashboard. The request turns a vague adoption concern into visible project work with owners and deadlines.

Do not ask for “the plan” when you need the WBS. A schedule shows timing; a WBS clarifies deliverables and work scope. Do not accept a high-level slide if adoption planning requires work-package detail. Avoid positioning the request as an audit of the project manager’s competence. The tone should be collaborative: “I need this to help impacted groups adopt what the project is delivering.”

Another mistake is keeping adoption work outside the project structure. When people-side work requires effort, resources, or sequencing, it should be visible in governance. Finally, do not wait until go-live. Peer-reviewed engagement research emphasizes early two-way interaction and active participation, not late-stage information sharing [Norris et al., 2017]. (implementationscience.biomedcentral.com)

Useful indicators include whether the WBS is received by the agreed date, whether adoption deliverables are traceable to project deliverables, whether impacted groups have been mapped to work packages, whether missing readiness work is logged with owners, and whether managers can explain what is changing for their teams. Stronger indicators include reduced late-stage scope surprises, fewer unresolved adoption risks, readiness scores by impacted group, training completion tied to role-specific work packages, and adoption barriers being raised through governance rather than informal escalation.

Subject: Request for project WBS to support adoption planning

Hi [Project Manager],

To complete the change impact and adoption plan for [initiative], could you please share the current work breakdown structure by [date]? I am especially looking for deliverables and work packages that affect impacted users, people managers, process changes, training, communications, testing, cutover, and hypercare.

If available, please include work package owners, key dependencies, assumptions, and any WBS dictionary details. I would also like to schedule 45 minutes to review the WBS together so we can identify adoption risks, missing change deliverables, and any items that need to be raised through project governance.

The purpose is to make sure the people-side work is aligned with the delivery scope and that impacted groups receive the right support at the right time.

Thanks,
[Name]