Decide whether to commit a quarter to a roadmap item
Before two engineers spend a quarter on it, find out whether the roadmap item would fix the problem it was proposed for.
See the record →Use cases · Product teams
Decide whether to reopen an idea you already dropped
See what was tested last time and who decided, then find out whether anything has changed enough to change the answer.
The situation
A new VP wants custom dashboards back on the roadmap. The record shows the team dropped them last year, when 4% of accounts used the beta, and who made that decision. Since then the customer mix has changed, so the question is whether that changes the answer.
What you find out
- What was already tested and decided, before anyone spends a sprint on it again.
- Whether something real has changed, tested against new criteria instead of argued.
- A shorter debate next time, because the record answers the first questions.
Decision Recordworked example
- assumption
Enterprise admins, now 40% of revenue, will use custom dashboards every week.
- experiment
Give the old beta to 25 enterprise accounts for four weeks.
- success criteria · locked
At least 40% of those accounts build a dashboard and open it in 3 of the 4 weeks. Locked before the beta goes out.
- evidence
22% did.not met
decision
Drop it
Two experiments a year apart now point the same way, and both are on the record.
Head of product decides; agent pulls up last year’s record and drafts the new experiment.