Choosing What Goes On Your Roadmap
Every roadmap has more good ideas competing for space than time to build them. This lesson covers a simple way to decide what actually makes the cut.
You Will Always Have More Ideas Than Time
No matter how small your team is, you will always have more good ideas than you have time to build. That's not a sign of poor planning — it's normal. The real skill is having a simple, repeatable way to decide what deserves a spot on the roadmap right now.
Impact vs. Effort: A Simple Starting Filter
You don't need a complex scoring model to start prioritizing well. Plotting ideas on a simple impact-versus-effort grid is often enough:
- High impact, low effort — do these first
- High impact, high effort — plan these deliberately
- Low impact, low effort — fit these in opportunistically
- Low impact, high effort — avoid, or deprioritize clearly
This isn't perfectly scientific, but it forces a useful conversation about trade-offs.
Weighing Ideas Against Your Strategy, Not Just Popularity
The loudest request in the room isn't always the most important one. Before adding something to the roadmap, ask whether it clearly supports your strategy — the customer you're serving and the problem you're solving — rather than just who asked for it most recently or most loudly.
Learning to Say No Without Burning Bridges
Saying no is easier when you can explain the reasoning. Instead of "we're not doing that," try "that doesn't fit what we're focused on solving right now, but here's what we are prioritizing and why." This keeps the relationship intact even when the answer is disappointing.
Leaving Room for the Unexpected
Don't fill 100% of your roadmap capacity with planned work. Leaving some room for urgent fixes, unexpected opportunities, or new learning keeps your roadmap realistic instead of constantly broken by the first surprise that comes along.
Practical Review Checklist
Before moving on, confirm that you can:
- Explain the difference between high-impact and low-impact work in your own words
- Describe how you'd weigh a stakeholder request against your strategy
- Give an example of how you'd say no to a request respectfully
- Identify why leaving some roadmap capacity unplanned is useful
- Name one idea you're deliberately not prioritizing right now, and why
Conclusion
Choosing what goes on your roadmap is really about choosing what you're willing to say no to. A clear filter makes that decision faster, fairer, and easier to explain to others.