Rolling Roadmap with Precision Tiers
A six-month roadmap refreshed quarterly, with 80% commitment in months 1-3 and 50% in months 4-6.
- Difficulty
- Moderate
- Time to result
- ~months to results
- Steps
- 4
- Confidence
- 90%
To satisfy enterprise customers who demand roadmap reviews while preserving the agility a PLG company needs, Miro runs a rolling six-month roadmap updated every three months, with explicit precision tiers: the first three months are committed at an 80% confidence level (80% of listed items will ship), and the next three months at 50%. The lower-resolution back half gives teams license to pivot toward new customer asks, competitive moves, or tech breakthroughs (like LLMs) without being penalized by customers or internally.
Origin
Designed at Miro under Varun Parmar to reconcile enterprise roadmap-review demands with PLG agility. Built on the backdrop of an annually published product strategy white paper.
Core principles
- 01Enterprises want roadmap commitments; PLG needs agility — precision tiers reconcile the two.
- 02Explicitly labeling confidence (80% vs 50%) sets honest expectations instead of over-promising.
- 03Lower-resolution far-out planning is a feature: it legitimizes pivots without penalty.
- 04Roadmaps ladder up from a published annual strategy, not ad hoc.
How to run it
- 1
Publish an annual strategy white paper
Each year, publish internally to every employee a strategy artifact stating the key bets, why you're making them, expected outcomes, and how they ladder up to OKRs and business strategy.
- 2
Build a rolling six-month roadmap against it
Have teams build roadmaps from the strategy white paper, spanning six months forward.
- 3
Assign precision tiers
Commit the first three months at an 80% precision level (80% of listed items will get done) and the next three months at 50% — a deliberately lower resolution.
Pro tip State the confidence number to the customer so a missed far-out item isn't a broken promise.
- 4
Refresh every three months and let teams pivot
Update the roadmap quarterly, using the lower-confidence back half as room to pivot toward customer asks, competitive moves, or technology breakthroughs without penalty.
Pro tip Use the roadmap review as your best enterprise-relationship meeting, not a defensive one.
Watch out Don't treat the 50% tier as a firm commitment — its purpose is to preserve agility.
In the wild
Parmar says large enterprises love asking for a roadmap review, and sitting down to walk enterprise leaders through the six-month plan is his favorite meeting — architected so customers get what they want without removing the agility to deliver value faster.
→ Enterprises get roadmap visibility while product teams retain freedom to pivot on new customer, competitive, or technology signals like large language models.
Common mistakes
Committing the whole horizon at one confidence level
Promising all six months as firm commitments either over-constrains the team or breaks trust when far-out items slip. Splitting into 80%/50% tiers sets honest expectations and legalizes pivots.
Building roadmaps without a published strategy anchor
Roadmaps built without laddering up to an annual strategy white paper and OKRs drift; the strategy artifact is what makes the bets and their business rationale legible across functions.
Is it for you?
Best for
PLG or product-led companies moving upmarket that must give enterprise buyers roadmap commitments while staying agile.
Not ideal for
Early-stage products with no enterprise customers demanding roadmap reviews, where formal precision tiers add unnecessary process.
From the transcript
“we have a rolling six month roadmap that gets updated every three months and the first three months of that that roadmap we have a…”
“for the for the next three months because it's six months so the first three months is eighty percent the next three months is 50”
“every year uh you know we uh publish a strategy white paper that it gets published internally available to every single millionaire”
From the episode
An inside look at how Miro builds product: Lessons on outmaneuvering competitors, team structure, product quality, and moving fast
Varun Parmar (CPO of Miro)