Product Discovery interactive guide
The assignment
Build an interactive guide that teaches YOU Product Discovery.
✳What Shaswat shipped
Product Discovery School is a live, no-login web app built as an eight-module curriculum with clear discovery-vs-delivery framing. It was built using a multi-tool pipeline — an initial version drafted in Google AI Studio, refined in Cursor, with authentication and a database added via Supabase, and deployed through GitHub and Vercel — and includes an interactive workspace for learners to apply concepts.
✳Our read on this build
Shaswat shipped a deployed web app you can open. Parts of it sit behind a sign-in, so this read leans on what is public plus Shaswat's own description.
What it demonstrates
- There is something here to do rather than read: interactive modules put the learner in the driver's seat.
- It also tries to be about you rather than about the subject: a saved account and a personal workspace.
What is not shown
- It stays at the level of 'discovery' as a topic without naming the craft — interviews, assumptions, prototypes — so the depth is hard to judge from outside.
Take this awayThe reason this shape works is friction in the right place. A build that makes you choose before it explains is teaching judgment — the part of discovery that never transfers from reading.
✳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.