How do you balance the level of complexity / granularity of a roadmap? What is just enough fix and flex?
7 Answers
BILL Director, Product Management (Data, AI, DevEx, Identity) | Formerly Twitter/X • 1y
Your roadmap should have just enough details on the top level that will explain the below three things:WHAT?Summary of the problem, high level potential solution and the ...
3475 Views
AlphaSense SVP, Product and Design • 1y
It's Product's job to identify and articulate: where you're going, where you are today, and what you do next. Product vision answers the first, and roadmaps answer the se...
2747 Views
Confluent Senior Director of Product, AI Products and Strategy • Apr 1
With how fast things are moving, especially with AI, the idea of a detailed 18–24 month roadmap is starting to die. You just can’t predict that far out with real confiden...
352 Views
JetBrains Head of Product | Formerly GitLab, Jit.io, Cellebrite, Anima • 1y
A roadmap should provide structure without rigidity—a foundation for change rather than a fixed plan. The tech world is dynamic, and no 12-month roadmap will remain untou...
1070 Views
Chainguard Senior Director of Product Management • 1y
My preference is to focus a roadmap on "big digs" or themes of investment. Customers (and your sales team) generally want to see a roadmap not because they care about eac...
942 Views
Barracuda Networks Sr. Director, Product Management • 1y
Roadmaps are as much about communication as they are about planning—so the right level of detail depends on who it’s for and how far ahead you're looking.I usually approa...
1058 Views
ATG Group Product Manager | Formerly Doppler, GitLab, Twilio/SendGrid • 1y
What is shared on the roadmap is all about who the audience is you are talking or preparing it for review and what incentives they have. Some things I have found success ...
928 Views
Related Questions
How do you determine how much of your roadmap should be focused on existing customers vs prospects?What are some of the lenses your look through or principles you apply when prioritizing a roadmap? How are they weighted relative to each other? What is your end to end process for prioritizing features on your roadmap?How do you balance long-term vision with the fast-moving, often unpredictable nature of health tech? What does your planning horizon actually look like?
Where do ideas for new features come from? How do you decide which ones to build?How do you manage a roadmap when company leadership cannot or will not provide guidance? (e.g. the C-team is all newly hired and don't know enough about the product or customers)