Reference proof 01 · Practice productShipped
Turn a discovery lesson into a runnable field kit
Should Product Discovery remain an explanatory lesson or become a workflow a builder can run end to end?
- Original Bet
- A staged five-day workbench will be more useful than another page of methods, questions, and rubric copy.
- Threshold
- One saved flow must frame the decision, recruit, capture interviews, synthesize evidence, force a call, and export the memo.
- Current result
- The static lesson was replaced by a 15-action workbench with evidence gates, local persistence, memo export, and a reusable agent skill.
- Next move
- Measure sprint starts, completed evidence records, exported memos, and return-to-finish behaviour before claiming learning impact.
Product DiscoveryUser ResearchWorkflow Design
Evidence ledger
Observation → consequence
- Problem
The page described discovery but gave the builder nowhere to conduct it.
Replace passive instruction with a staged working surface.
- Revision
A method, question list, exercise, and rubric still left the hard operational steps implicit.
Add recruiting, structured evidence, decision gates, and required artifacts.
- Current evidence
The complete workflow is usable and testable; real completion and outcome data is not yet available.
Keep the claim at “runnable,” instrument use, and do not call the skill mastered from checkboxes.