Free Framework · 1 Page
Roadmap
With Receipts.
A pattern for structuring a roadmap so every priority cites its evidence.
Quarter: ______
PM: ______
PM: ______
The Pattern
Every roadmap item gets four labels. If you can’t fill any of these in, the item isn’t ready for the roadmap.
Roadmap item template
[FEATURE]Search redesign with semantic matching
[SIGNAL]47 customer signals · 5 channels · last 30 days
[OKR]Q2 activation: 25% → 35% (search-to-action drop is 60% of churn)
[SCORE]WSJF 8.4 · effort M · revenue impact ~$28k MRR
Example (Q2 Roadmap)
#1
Search redesign w/ semantic matching
Signal47 signals · 5 channels
OKRQ2 activation 25 → 35%
ScoreWSJF 8.4 · effort M
OKRQ2 activation 25 → 35%
ScoreWSJF 8.4 · effort M
#2
SSO for enterprise (SAML/OIDC)
Signal23 signals · enterprise plan
OKRQ2 enterprise expansion
ScoreWSJF 7.1 · effort L · ~$45k ARR unlock
OKRQ2 enterprise expansion
ScoreWSJF 7.1 · effort L · ~$45k ARR unlock
#3
Mobile push notifications fix
Signal34 signals · App Store + Slack · 18 high-urgency
OKRQ2 retention NPS > 40
ScoreWSJF 6.9 · effort S · churn-blocking
OKRQ2 retention NPS > 40
ScoreWSJF 6.9 · effort S · churn-blocking
Objection Handler — "Why is this #3?"
Default response (without receipts): "Because I think mobile is important." — loses the argument.
With receipts: "WSJF 6.9 vs. SSO at 7.1. Mobile has more signals (34 vs. 23) but lower revenue tie. Push fix is smaller effort, ships faster, blocks churn from a different segment than SSO. Both ship Q2 — SSO first because it unlocks $45k ARR." — argument over.
The rule
If a roadmap item can’t fill all four labels, it’s not on the roadmap. It’s on the discovery list. Discovery items belong in a separate doc until you can defend them.