E01 · Choose the value unit
Synthetic practice, not company performance.
One decision
Should the North Star count accounts, people, minutes or exports?
Run the exact query
WITH b AS (SELECT * FROM v_task WHERE ('all'='all' OR persona='all') AND ('all'='all' OR workflow='all') AND ('all'='all' OR substr(signup_at,1,7)='all') AND date(confirmed_use_at)>='2026-05-01' AND date(confirmed_use_at)<'2026-10-01') SELECT date(confirmed_use_at,'weekday 0','-6 days') week_start,COUNT(DISTINCT account_id) value_accounts,COUNT(*) confirmed_tasks FROM b WHERE confirmed_quality_use=1 AND date(confirmed_use_at,'weekday 0')<date((SELECT value FROM manifest WHERE key='cutoff_utc')) AND date(confirmed_use_at,'weekday 0','-6 days')>='2026-05-01' AND date(confirmed_use_at,'weekday 0')<'2026-10-01' GROUP BY 1 ORDER BY 1;
Download SQL · Result CSV · Metabase saved question
Chart and reading
Compare DB01 account reach with task volume and confirmation coverage.
Challenge your recommendation
Would one large account or repeated locale versions distort the story?
Guardrails: Filters use date, unlike task cards. Only whole UTC weeks fully inside the selected date range and ended before cutoff are included. Missing confirmations limit interpretation.
Next evidence: Confirm account identity, repeated job frequency and use-confirmation method.
PRD sections: 2, 14. Open proposed PRD
Your spoken decision
State one takeaway, one caveat and one action in 30 seconds. Then stop.
Connect this finding
What this chart helps decide · Follow the connected decision · Canonical metric definitions
Optional model answer — try your own first
E01 · Choose the value unit
Decision: Should the North Star count accounts, people, minutes or exports?
Readout: Compare DB01 account reach with task volume and confirmation coverage.
Actual query output (synthetic), first rows:
| week_start | value_accounts | confirmed_tasks |
|---|---|---|
| 2026-05-11 | 1 | 1 |
| 2026-05-18 | 3 | 3 |
| 2026-05-25 | 3 | 3 |
Model spoken answer: I would track accounts receiving confirmed quality value, with coverage and cost beside the count.
Caveat/counterargument: Would one large account or repeated locale versions distort the story? Filters use date, unlike task cards. Only whole UTC weeks fully inside the selected date range and ended before cutoff are included. Missing confirmations limit interpretation.
Next evidence: Confirm account identity, repeated job frequency and use-confirmation method.
Deliberately left out: Minute totals, because they measure production load rather than which accounts received value.