Product Discovery interactive guide
The assignment
Build an interactive guide that teaches YOU Product Discovery.
✳What Juhi shipped
A tightly-scoped, no-signup coaching app structured around a Learn, Simulate, and Recall loop for each discovery stage. Each stage opens with a conversational walkthrough, moves into a pre-scripted scenario where the learner makes real calls, and closes with a written recall exercise compared against a model answer, aimed at internalizing discovery behavior rather than just reading about it.
✳Our read on this build
Juhi shipped a deployed web app you can open. This read comes from the artifact and Juhi'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, scenarios and exercises put the learner in the driver's seat.
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.
- It is built as a general course rather than around your product — the part of 'teaches YOU' most entries left on the table.
Take this awayWorth opening if you are designing learning UX, then asking the question this build raises: what would make the learner commit to an answer before the app supplies one?
✳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.