By the time this 40-person B2B SaaS team asked for help, their public roadmap had slipped twice in one quarter. Sales had already promised one of the dates to a customer. Trust in the roadmap — both from leadership and from the sales team — had quietly collapsed.
Where the dates came from
The roadmap had been built backward from a launch event six months out: someone picked a date, then features got slotted in to fill the time until it. None of the dates were tied to how long the actual work would take, just to how much calendar was left.
What changed first
The team replaced every dated roadmap item with an outcome statement and a RICE score. "Ship referral program by March 15" became "Increase referral-driven signups from 4% to 8% of new accounts" — with no date attached, and a published score showing how it was prioritized against everything else on the list.
The uncomfortable part
Sales leadership pushed back hard in the first roadmap review. Removing dates felt, to them, like removing accountability. The compromise was a quarterly confidence rating (high / medium / low) attached to each outcome instead of a date — an honest signal without a false promise.
The result
Two quarters later, the referral outcome shipped at 7.6% — close enough to count as a win, reached a few weeks later than the team's own internal estimate, but with no external date ever broken. The sales team's complaints about the roadmap dropped to zero in the next internal survey, not because delivery got faster, but because nothing promised in public was missed again.
The takeaway
- A missed date breaks trust even when the work itself goes well; an honest confidence rating rarely does.
- Outcome statements force a conversation about what "done" means that date-only roadmaps skip entirely.
- The hardest part of this change wasn't writing outcomes — it was the first review meeting after removing the dates.