Six signs your roadmap is giving priority to the wrong things
A nagging feeling about your plan is worth testing. Six signals to check against your current roadmap, and what to do about each.
How to use this
Open your current roadmap next to this page. For each signal, mark it as clear, unsure or present. Two or more “present” marks is worth a proper look.
1. The top items came from the loudest customer
One big prospect or investor asked for it, and it jumped the queue. Check how many customers would actually use it, and whether it serves the customers you want more of.
2. Nobody can say what success looks like
If an item doesn’t have a measure attached, such as activation, retention or time saved, you won’t know if it worked. Ask for one sentence per item: “this works if…”.
3. Usage data and the plan disagree
Your most-used features get little attention while rarely used ones get extensions. Compare the roadmap against what customers actually do in the product, not what they say in calls.
4. Big bets with no small test first
Several months of engineering is committed to an idea nobody has tried in a cheaper form. A prototype, a manual version or a landing page could tell you most of what you need in days.
5. The plan only ever grows
Items get added each quarter but nothing is dropped. A healthy roadmap loses items as you learn. If yours hasn’t, some of what’s on it is there out of habit.
6. Engineering and sales tell different stories
Ask both teams what the next three priorities are and why. If the answers differ, the roadmap isn’t doing its job of keeping everyone pointed the same way.
What to do next
- Mark each item: keep, move, drop or test first.
- For anything marked “test first”, write the one question a prototype or experiment would answer.
- Share the marked-up version with your team and ask what you’ve missed.