Let us call a change management plan the schedule of the mobilisation, communication and training actions that a project plans for each of the populations whose work it changes, each action with its owner and the milestone to which it is tied. This definition is ours; each organisation adjusts it to its own vocabulary. It bears the same name as one of the typical pieces of work on our change management page.
We suggest building it in an order: the scope and the populations affected, the impact analysis by business function, the change champions, communication, skills development, start-up support, the measurement of adoption. The order has a reason. You do not choose change champions without knowing the teams affected, nor the content of a training course without knowing what changes in each business function. Each step delivers a written document, and the plan is these documents brought together on a single schedule.
Defining the scope and naming the populations affected
The scope of the change is distinct from that of the project. The project is described by what it delivers. The change is described by what will be done differently, by whom and from when. The first step therefore writes three lists, which form the first page of the plan: what the project changes in the work (tools, sequence of tasks, roles), what it leaves as it is, and the populations concerned.
We call a population a group that performs the same job and will experience the same change on the same date. Two sites served by two deployment waves form two lines. For each, the list shows the headcount, the sites, the direct management and the wave. It includes people who will not use the result of the project but will feel its effects: support desk, operations, departments that receive the data produced.
The human resources department and the lawyers should be consulted from this step: it is for them to say whether the project calls for informing or consulting employee representatives, and on what date. Their answer, which we do not settle here, may shift the plan’s schedule.
An impact analysis carried out with each business function
The analysis is conducted with people who do the work. We suggest one workshop per business function, which follows a real case from end to end, first as it is handled today, then as the solution provides. Each gap is noted: a task that disappears, a new task, a task that changes form. Our service page classifies these gaps into four kinds (tool, process, role, profession), which do not call for the same response; we do not return to them here.
The analysis has two recipients. The plan finds in it, for each population, the scale of the effort required and the actions that respond to it. The project team finds in it objections to investigate, some of which may lead to reviewing the solution or spreading the deployment. That is why we start the analysis at the framing stage, on assumptions, and complete it once the design has been finalised.
The impact matrix comes out of it. In an IT project, its absence leaves traces at every step, as noted in our article on change management in an IT project.
Change champions named before the first message
A change champion is a person from the business function who explains to colleagues what is coming and reports back to the project team on what is getting stuck. Our service page makes the credibility they enjoy with their colleagues the criterion for choosing them. The plan, as we propose it, adds what makes the role sustainable: one change champion per team or per site on the list of populations, time freed up with the written agreement of their manager, and a short description of what is asked of them before, during and after go-live.
Front-line managers have a separate place, because they carry the requirement to their team. The plan provides for them to be informed before the team and to have the answers to foreseeable questions.
Then comes communication. Its messages follow from the impact matrix, and its dates from the project’s milestones. How to build it is the subject of a separate article, devoted to the project communication plan, one of the documents of the change management plan.
Skills development aligned with go-live
The impact matrix says what each role will need to be able to do on the first day. Skills development follows from it: one path per role, built on the work situations identified in the workshops, and a schedule of sessions placed as close as possible to go-live. When the role or profession changes, beyond the tool alone, training on the tool is no longer enough: the plan also records what falls to management and, depending on the case, to human resources.
The choices specific to this workstream (audiences, timing, format, delivery, checking the effect) are covered in our guide on user training. To identify what a population lacks before training it, the grid of the ADKAR model can serve as a checklist.
Supported start-up, then adoption measured
The first days of real use have their own arrangements, written before go-live: change champions present in the teams, reinforced support, separate routes for tool defects and for usage questions, a daily check-in between the project and management. The plan also sets their end, by a date or by an observable condition, together with the date on which the old tool ceases to be available.
The measurement of adoption is also prepared before go-live. We suggest three readings per population: observed use of the functions the project was meant to get adopted, support requests, in volume and in kind, and feedback from the change champions. When it is measurable, the baseline value is recorded before the first day. We do not propose any threshold: the target for each reading is set with the business departments, which present the results to the steering committee.
The last two documents are the description of the start-up arrangements and the adoption dashboard, with its first values.
A change management plan aligned with the project’s milestones
The documents are only worth anything once dated. Each is tied to a project milestone, at which the steering committee can ask for it before deciding. The table below is a proposal, to be adjusted to each project’s cycle.
| Project milestone | Plan documents expected at this milestone |
|---|---|
| End of framing | Scope of the change, list of populations, first impact assumptions |
| Design finalised | Completed impact matrix, change champions named |
| Start of acceptance testing | Communication plan, paths by role, change champions involved in acceptance testing |
| Go-live decision | Sessions held, start-up arrangements ready, baseline values recorded |
| End of the start-up period | Adoption readings, corrective actions, retirement of the old tool |
We suggest that a named person maintain the plan: the change management lead when the project has one, otherwise the project manager. Each business department approves the lines that concern its teams. On a programme, each project’s plan fits into the overall plan, which programme management follows alongside the programme’s other milestones.
The plan is reread at each milestone. A line whose date has passed without the document existing is presented to the steering committee as a project delay, together with what it shifts.