Step 1 / 5 · 10 min
Prevent a dashboard from becoming the deliverable.Name the decision
- Write the choice and decision date.
- Name who has authority to act.
Learn · Core skill lab
Decision-Grade Measurement Plan
Instrument the behaviour that proves value and pre-commit to what the numbers will make you do.
- Decision
- What user behaviour would make us continue, change, or stop this product move?
- Timebox
- 60–90 minutes
- Output
- Measurement decision plan
Bring to the bench
- One live feature or workflow
- A named product decision
- Access to someone who can verify event feasibility
Your work saves in this browser.
Field tools
Use the instrument, not a blank page.
Copy these into your interview, agent, review, or working document. They are specific to this repetition.
template
Event contract
Give each event one behavioural meaning.
EVENT: [actor]_[past-tense action]_[object] FIRES WHEN: exact observable condition REQUIRED PROPERTIES: identity, object, source, timestamp MUST NOT FIRE WHEN: test/retry/preview conditions QUALITY CHECK: raw records or session replay used to verify it DECISION SUPPORTED: continue / change / stop
script
Metric review agenda
Run this ritual before proposing features.
1. Is the data trustworthy enough to decide? 2. Which segment moved, and what mechanism could explain it? 3. Where did users fail or need rescue? 4. What do five raw examples show? 5. Which pre-committed rule applies? 6. What will we change, by whom, by when?
Calibrate judgment
Compare the evidence, not the polish.
Metric with a consequence
A team is testing guided setup for collaborative workspaces.
Continue only if 35% of new workspace owners invite a teammate and both complete one shared task within 24 hours, while fewer than 10% need support rescue. Review by team vs solo intent and replay five failures before changing UI.
Why it works: The event proves collaborative value, includes a quality guardrail, and dictates the next decision.
Dashboard theatre
Track signups, DAU, button clicks, time on page, and NPS. Review monthly and improve onboarding if engagement is low.
Why it fails: The metrics do not define value, cannot diagnose failure, and have no pre-committed action.
Review → revise → repeat
The artifact is the beginning of the rep.
Check only standards your current artifact actually meets. Then record one consequential revision before exporting it.