How often do you update your roadmap?

  • 22 October 2021
  • 5 replies

Userlevel 2
Badge +1

I’m always interested to know how often teams update their roadmaps, and how they communicate this to their wider teams! Keen to hear how you do this, and maybe if you would do it differently if it was completely up to you? (assuming isn’t not always the case)

5 replies

Userlevel 2

Hi @ashivory, in our company we do update them on quarterly basis. We ditched scrum sprints and now have two-month development cycles (focused only on building new functionality) with up to one month for refinement (technical debt, maintenance, ux improvements), so our development really follows quarterly pace.

We do have monthly check with development stakeholders (PM team, VP Engineering, VP UX, CTO) where we discuss how we’re progressing and whether there are any major changes/risks.

Userlevel 2
Badge +2

Here, our PM team update the “main roadmap”  every month and we have a separate GtM roadmap which is updated on quarterly bases. 


Like what Martin mentioned, we have a similar approach which is a monthly check PM<>GtM to keep both sides updated also we have Voice of the Customer call within the GtM to see what themes are important to focus on the next quarter


Hasso. I’m wondering at what fidelity is your roadmap if your updating it once per month? The overhead of that seems a bit excessive, so my guess is our roadmaps are a bit different in their fidelity. 

Userlevel 2
Badge +1

I like the idea of a voice of customer call! That sounds seriously effective if you are extracting themes and not just verbatim feedback.

Userlevel 5
Badge +8

We end up updating the short-term roadmap with everything from bug fixes/tech debt to stories/epics for features/enhancements. Long-term and/or “Visionary” roadmap gets reviewed once a quarter, to make sure we’re headed in that direction (any dependencies that are being worked on are on time or headed in a way that will give us the foundation/scaffolding for the “future” feature). 

Smaller companies tend to have less “fidelity” in their roadmaps due to the pivots from customer-specific focus and identifying higher priority needs in the product from the market. It’s not always a great way to outline roadmaps, as they’re less stable in the short-term, but it does give the range of communication to the needed departments as to deliverables and when to expect them in the product.