What Makes a Roadmap Actually Useful
Most roadmaps are read once, at the meeting where they're presented, and never again. Here's the format we switched to that engineers and clients both actually keep open.
We used to ship quarterly roadmaps as a slide deck with dated milestones: "Q3 — Launch v2." Every single one was wrong by week three, and once it was wrong, nobody trusted the rest of it either. The problem wasn't our estimation. It was the format demanding a precision we never actually had.
Dates create false confidence, on both sides
A date on a roadmap slide reads as a commitment even when it's explicitly labeled as an estimate. Clients plan around it. Engineers feel obligated to hit it even after new information makes it clearly wrong. The date becomes a target that gets defended long after it's stopped being useful, instead of an estimate that should update as reality does.
The problem isn't that estimates are wrong — all estimates are wrong to some degree. The problem is a format that hides how wrong, and doesn't make it easy to update.
What replaced it: now / next / later
We switched every client roadmap to three horizons instead of dated quarters:
- Now — actively being built, updated weekly, specific enough to include acceptance criteria.
- Next — scoped and prioritized, no committed date, sequence can still shift based on what we learn from "Now."
- Later — directionally agreed, deliberately vague, revisited every planning cycle rather than promised.
## Now
- [ ] Multi-tenant billing migration (in progress, targeting internal QA this week)
## Next
- Usage-based pricing tiers
- Self-serve team invites
## Later
- SSO for enterprise accounts
- Public API
Why this format survives contact with reality
A now/next/later roadmap doesn't need to be "corrected" when priorities shift — shifting priorities is exactly what moving something from Next to Now, or Later to Next, already represents. There's no broken promise to explain, because nothing in Next or Later was ever presented as a promise in the first place.
"A roadmap's job isn't to predict the future accurately. It's to tell the truth about how confident you actually are, at every point on it."
Now, Next, Later roadmap board with items moving between columns
What changed for clients
Clients stopped asking "why did the date move" and started asking "what moved into Now this week" — a much healthier question, and one the format itself invites. Trust in the roadmap went up, not because we got better at estimating, but because we stopped pretending precision we never had.
One email, every other Friday
Engineering notes, new articles, and things we learned the hard way — no marketing, ever.
Read by 2,400+ engineers. Unsubscribe anytime.
Let's talk
Let's build what's next.
If any of this sounds like the kind of work you want done on your systems, our engineers are the ones who'll actually do it.