I’m working one for the evolution of our intranet/digital workplace. I need to think about all the activities people do online, all the tools that fulfil those needs and what development is being thought of for the tools. For added fun, quite a lot of these tools aren’t strictly speaking my responsibility.
Roadmap sounds a bit buzzword-y, but a roadmap is just a high-level plan that sets out the major steps on the way to a strategic goal. It might cover more than one project and indicate dependencies, it should show phases and expected release dates. A technology roadmap will lean towards process steps, and it can be used to communicate across project teams for all steps in the all projects.
My need is a little different, I want to communicate with a wider audience, for stakeholders and end users who are outside the project teams. I’m trying to bring clarity to a diverse group who haven’t got time to read a lot of detail, but need something more specific than a beautiful vision. It should convey what they can expect to see and when – and give some idea of where they can give input. A roadmap has the right level of detail, and if I can make it visually appealing people will understand what to expect almost at a glance. For a project like putting a new publication environment in place for digital channels it will look something like this.
I used to joke about how my answer to any work question could be given with boxes and arrows. It’s time to bring out those boxes and arrows in a big way.
Image via pixabay