Vision maps vs roadmaps
Most stuck roadmaps I see have one thing in common: they stopped changing. Someone drew a timeline, filled it with features and dates, showed it to the board, and everyone felt good for about two weeks. Then reality hit. Priorities shifted, customers surprised you, half the plan became irrelevant. The roadmap didn't.
If your roadmap doesn't change every few iterations, you're not being agile. You're following a plan and calling it agile. And the items nobody believes in anymore just sit there, open for months, blocking the ones that matter.
Keep the roadmap, but steer by a vision map. A vision map shows where you believe your product or business should be in the future, without pretending to know exactly how you'll get there. The roadmap becomes the next few steps toward it, rewritten as you learn from customers and the market. It's the difference between navigating and following a script.
Roadmaps pretend to know the future. Vision maps admit you don't, and that's a much better starting point.
Roadmap already stuck? The roadmap and delivery review finds where, and what to do first.
More writing, or see how it plays out in previous work.