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
Test an onboarding change before you ship it to everyone
Find out whether a shorter onboarding flow gets more people through, measured against success criteria set before the first user sees it.
The situation
New users drop off at step 4 of onboarding, and the team wants to cut the flow to three steps. Redesigns are easy to ship and hard to judge afterward, because other things change at the same time. Without criteria set first, almost any number can be read as a win.
What you find out
- Whether the change moved the number you cared about, against what you said in advance.
- What to test next, because the next idea starts from this record.
- Who decided to ship it and why, when someone asks in six months.
Decision Recordworked example
- assumption
People drop off at step 4 because the flow is too long.
- experiment
Show a 3-step flow to half of new sign-ups for two weeks. The other half keeps the current flow.
- success criteria · locked
At least 15% more people finish onboarding in the 3-step flow. Locked before the first sign-up sees it.
- evidence
18% more finished.met
decision
Move forward
Ship the 3-step flow to everyone, and test whether two steps does better.
Product manager decides; design builds the new flow; agent drafts the experiment.