The Change Management Deliverables That Earn Their Keep

Version française : Les livrables de gestion du changement qui servent vraiment

By Marc-André Rochefort, Eng., MBA, CCMP®, MCMP™, Prosci® certified, founder of Leanova Academy, an ACMP® Qualified Education Provider™.
Last reviewed: October 2026

Disclosure: Leanova Academy sells change management training, including the courses mentioned below. The views on how deliverables are used come from our own practice.

Key takeaways

• Six deliverables cover most of the weekly work on an active project. They are the readiness assessment, stakeholder map, sponsor roadmap, communication plan, training strategy and adoption measurement plan.
• The sponsor roadmap and the communication plan are the two deliverables used every week during an active rollout.
• A stakeholder map is only useful if it gets updated. One built at kickoff and never revisited ends up misleading the project team.
• The readiness assessment and the adoption plan matter mostly at the start and end of a project. Draft the adoption plan alongside the project charter, with a baseline captured before the change starts.
• A training strategy should be judged on capability checked after training, not on completion rates.
• For a CCMP® application, these deliverables supply the raw material for answers mapped to the ACMP® Standard's process groups. Leanova Academy covers them in its 21-hour self-paced CCMP® exam prep course.

A change practitioner writes two kinds of documents. A few get read and updated all the time, while the rest get written once and archived. Six deliverables cover most of what crosses your desk week to week on an active project. They are the readiness assessment, stakeholder map, sponsor roadmap, communication plan, training strategy and adoption measurement plan. Knowing which ones stay alive tells you how much of your time goes to paperwork rather than to the work it's meant to support.

What does a readiness assessment do?

A readiness assessment gauges how ready an organization is to absorb change before a specific initiative launches. It looks at past change history, how leaders behave and the culture. It also asks how much room teams really have for something new, given everything already competing for their attention.

Sponsors and steering committees read it, usually once, at the start of an engagement. It shapes how much the project invests in change management and how aggressive the timeline can be.

The classic mistake is treating the assessment as a box to tick on the methodology checklist, when it should change the plan. Say it finds low change capacity and the project goes ahead exactly as it would have anyway. Then it hasn't done its job, because a finding that doesn't move a decision was only decoration.

Why does a stakeholder map go stale?

A stakeholder map shows who the change affects, how much influence they have, and where they stand right now. Each person or group is marked as supportive, neutral or resistant. The good maps go past name and role and record what each party stands to gain or lose, and what would shift their position.

Project leads and sponsors read it often, so it has to be kept current rather than written once and filed. Positions shift as a project moves from announcement to implementation. A month-one map still used to describe month six is actively misleading.

The classic mistake is building the map at kickoff and never touching it again. Someone neutral at launch may since have turned into a vocal blocker, and that won't show on a map nobody opens. You then find out about the resistance in a meeting, not from your own documentation.

What goes into a sponsor roadmap?

A sponsor roadmap sets out what the senior sponsor needs to say and do at each stage of the change, and when. It usually covers the main messages and visible actions, such as town halls or one-on-ones with resistant managers. It also sets the order of sponsor activity relative to project milestones.

The sponsor is the primary reader, along with the practitioner coaching them. It's one of the deliverables used weekly during an active rollout, because sponsors need reminding of what's coming and why each stage matters.

The classic mistake is writing a roadmap for a highly engaged sponsor with unlimited time. It then falls apart when the real sponsor has three other priorities. A roadmap that ignores the sponsor's actual availability and appetite for being visible gets dropped within a month. The practitioner ends up handling sponsor-level communication personally, which defeats the purpose of having a sponsor at all.

How should a communication plan be built?

A communication plan matches messages to audiences, channels, timing and the person who delivers them. It should separate one-way information sharing from real two-way engagement, where feedback changes what happens next.

Project teams read it, and often the sponsor does too. It gets pulled up constantly during the active phases of a change, especially around go-live and whenever resistance is expected to spike.

The classic mistake is planning for volume instead of audience. Send the same message through five channels to everyone, and you generate noise that teaches people to stop reading. That happens when nobody asks what each group needs to know or what worries it. A plan built around each audience's needs, sent through the channel it actually uses, gets more done with fewer messages.

What should a training strategy measure?

A training strategy defines what people need to be able to do differently after the change, not only which system or process they must learn. It maps roles to specific capability gaps. It then picks a format, whether instructor-led, self-paced, job aids or a mix, based on how much each role changes and how many people need training.

L&D teams and project leads read it at the planning stage. They come back to it once training starts and the gaps in the original plan show up. If you work in L&D or HR and want that skill to stay in-house, we've written a guide on how to build internal change capability.

The classic mistake is confusing training delivered with capability built. A completion rate is simply the share of people who sat through a session. It says nothing about whether they can actually run the new process. So the strategy needs a way to check capability after training, not just attendance during it. Otherwise the organization finds the gap at go-live instead of before.

When should the adoption measurement plan be written?

An adoption measurement plan spells out what "successful adoption" looks like in specific, observable terms, and how you'll track it. Project completion metrics like go-live date or budget are a different thing. They tell you whether the project happened, not whether people changed how they work.

Sponsors and project leadership read it at the end of a project, and sometimes months later when someone asks whether the change stuck. It's also the deliverable most often skipped or written too late to help. The reason is simple: it forces you to define success criteria before the change happens.

The classic mistake is writing it after go-live, once someone finally asks how adoption will be measured. By then there's no baseline to compare against. The metrics get built around whatever data happens to be lying around, rather than what would show the change worked. Draft the plan at the same time as the project charter and capture a baseline before the change starts. That version answers the question the plan exists to answer.

Where does each deliverable sit in the ACMP® Standard?

The ACMP® Standard organizes change work into five process groups and treats them as iterative, so it doesn't assign a deliverable to a single group. The table below is our practical reading of where each one does most of its work.

Which deliverables actually get used?

On most active projects, the sponsor roadmap and communication plan get used weekly. Sponsorship and communication run continuously through a change effort, so that makes sense. The stakeholder map gets regular use if it's kept current and turns into dead weight quickly if it isn't. The readiness assessment and adoption plan do their heavy lifting at two points, the start and the end. In between they add little, unless someone makes a point of going back to them. The training strategy sits somewhere in the middle: heavily used while training is delivered, then mostly archived once it's done.

That pattern tells you where to put your effort. In our view, a stakeholder map updated every week beats a beautifully designed one built once. Likewise, a rough adoption plan drafted early beats a polished one written after the fact with no baseline.

If you're preparing a CCMP® application, these deliverables are also the raw material for answers mapped to the Standard's process groups. Before you start writing, check the CCMP® certification requirements and which projects qualify for your application. How to Write a CCMP® Application That Gets Approved covers how to describe this kind of work in application language.

Leanova's 21-hour self-paced CCMP® course (US$595, ACMP® course code Q000607) walks through each process group and its deliverables in more detail than one article can. To build them as an applied skill, LCeX-Specialist™ (US$295) moves into practical work. And if you'd like a practitioner to review your own deliverables, on-demand coaching is built for that.

This article is also available in French: Les livrables de gestion du changement qui servent vraiment.

Sources, checked October 2026: ACMP® Standard, 2nd edition: process group study aid. Leanova prices are current list prices and may change. ACMP®, CCMP®, MCMP™ and QEP™ are trademarks of the Association of Change Management Professionals.