The problem with a project roadmap

Many project teams sweat over the project roadmap, the “what’s going to happen and when” of the project. It’s important. It keeps focus and shares intentions and expectations.

And this is all good.

But there could be a problem ... a disconnect of sorts. It’s right there in the name of it, roadmap.

Too often roadmaps are presented as boxes, tables full of words, cells from spreadsheets or complicated-looking calendars.

Tables, cells and columns may be great for actually working on the project, but for many people who don’t work in this way, they’re not so great for engaging and updating on the project story.

When you're dealing with future states or concepts, you've got to go for something that's as realistic as possible. People are in pain from information overload, bandwidth and capacity they don’t have, plus the fear and uncertainty of the unknown stuff that's ahead.

They may not even understand your table.

While you may love your spreadsheet, it may be saying so little to so many.

Road. Map. Keep tables for the work to be done and get better at sensemaking via map making.