Product Discovery interactive guide
The assignment
Build an interactive guide that teaches YOU Product Discovery.
✳What Baskar shipped
Proof (Preparation OS) is a deployed PM-readiness simulator with Console, Studio, and Artifacts sections, designed around describing a real upcoming situation to receive a tailored preparation brief. It covers general PM readiness topics including interviewing, stakeholder management, and executive presence.
✳Our read on this build
Baskar shipped a deployed web app you can open. This read comes from the artifact and Baskar's own account of it — no scores, just what the build does and does not show.
What it demonstrates
- There is something here to do rather than read: a simulator put the learner in the driver's seat.
- The curriculum names real discovery craft — user interviews — which is the difference between teaching discovery and describing it.
- It also tries to be about you rather than about the subject: tailored output.
Take this awayCopy the shape, not the syllabus. The decision-forcing moment is what makes discovery stick — the content is the easy half.
✳Why this quest matters
Discovery isn't a chapter you read — it's a muscle. The strongest builds here force a decision out of the learner, because the fastest way to internalise discovery vs. delivery is to practise the judgment call, not memorise the definition.
✳What separated the strongest builds
The learner has to make a call
The builds that landed put a decision in front of you — a scenario, a branching choice, feedback on your answer. The ones that didn't were articles with a nav bar.
Discovery vocabulary that holds up
Mom Test interviews, opportunity trees, riskiest-assumption tests, small prototypes shown to real users — the framing that separates discovery from delivery.
It teaches you, specifically
Your product as the worked example, your notes kept, your progress tracked. The brief said teaches YOU — and the generic explainers all read interchangeably.
No numeric scores are published here. These pages are written reads of what each builder shipped — the build is the point, not a mark out of a hundred.