Last December, I ran a poll to find out what people were most interested in learning about, and developing a change roadmap got 100% of the votes. So, I’m going to walk you through what a Change Roadmap is and how I go about creating one.
What exactly is a Change Roadmap?
It’s a strategic plan that lays out the different stages of change. The plan includes the key activities that need to happen at each stage, and the important milestones along the way. It’s usually designed as a one-page visual to give you a snapshot of the whole change process. The main goal is to create a clear, structured plan that helps everyone involved stay aligned and navigate the change successfully.
Here’s my approach
I start by working with key stakeholders to get a sense of a few things:
- What type of change is happening (Is it organisational change or more of a system change?)
- What’s the timeline for the project?
- Who are the stakeholders or teams involved in the change?
This gives me a high-level view to kick off the Change Roadmap. I always like to start with the timeline—even if it’s just an estimate at first. Having a timeline helps give us a sense of structure, and then we can plug the phases of change into it.
Next, I break down each phase with key activities and any deliverables or artifacts that need to be produced. Then I’ll add milestones, which are key progress points where decisions or signoffs may be needed.
Once the roadmap is put together, I’ll circulate it to stakeholders for their feedback. Based on their input, I’ll make any necessary adjustments and finalize it.
If I’m working with a project team, I’ll present the Change Roadmap to make sure that the change-related activities are incorporated into the overall project plan.
The result?
The roadmap becomes the go-to guide for the entire change process, helping everyone stay on track, monitor progress, and ensure that the change is rolled out smoothly.
