As the name suggests, roadmaps should have the properties of a map (What are the properties of maps?) Maps are multi-scale, Maps help you understand the state of something, Maps help you figure out possibilities and explicitly point out those possibilities and associated tradeoffs.
Most roadmaps do a poor job on many of these points. Instead, they feel like a mush of keywords and key phrases that someone evaluating a grant could check against and say “aha! This grant is legitimate because they’re trying to do this this thing that’s mentioned in the roadmap.”
Of course, it’s possible that creating a good roadmap is an impossible task. It may be impossible to create a roadmap that actually enables coordination and progress that would not happen otherwise. However, the assertion that most roadmaps suck is based on a list of points that are very possible to fix.
THIS IS NOT A ROADMAP
The Rejuvenation Roadmap | Lifespan.io - reasonable
This can’t help you make any decision https://nowandnext.com/PDF/Mega%20Trends%20and%20Technologies%202017-2050%20(Web).png
The International Roadmap for Devices and Systems is actually useful for guiding the semiconductor industry. I suspect this is because there are well-defined interfaces, most progress will be incremental, entities are fairly fungible, and there’s strong incentive for new entities to take on different pieces of the roadmap (like in the semiconductor industry .