GuideBeginner
Product Discovery And Prototyping
Teaches how to validate a bet with real users before building it. Building is the most expensive way to learn; this guide buys cheap evidence about risky assumptions before spending weeks of engineering time. It covers continuous discovery as a habit, not a one-time phase; interviews that don't lie — asking about past behavior, not future intentions, following the Mom Test approach; the opportunity solution tree for mapping the problem before jumping to a solution; turning an assumption into a falsifiable hypothesis and designing the cheapest test that can refute it (the riskiest assumption test); prototyping at the right fidelity level — paper, clickable, wizard-of-oz, fake door; avoiding confirmation bias and the say-do gap; and synthesizing findings to decide whether to continue, pivot, or kill the bet. It picks up exactly where the Product Thinking guide left off: Mercado's `recommendations` bet, with its riskiest assumption already identified but untested. All the decision logic — which test to pick, how to weigh evidence, how to update confidence — runs as executed Node.js code. It closes with a capstone project that validates that bet end to end.
- 64
- lessons
- 8
- modules
- English · Spanish
- available in
- Yes
- certificate
- Free
- access
Outcomes
What you'll be able to do
- Understand why building is the most expensive way to learn, and adopt discovery as a continuous habit, not a one-time phase
- Interview without getting lied to: ask about past behavior, not future intentions (the *Mom Test*)
- Map the problem space with the opportunity solution tree (outcome → opportunities → solutions → experiments) before jumping to a solution
- Turn an assumption into a falsifiable hypothesis and design the riskiest assumption test: the cheapest one that can actually refute it, run with `pickTest`
- Prototype at the right fidelity level: paper, clickable, wizard-of-oz, fake door — matched to cost and what it can test
- Avoid the biases that ruin discovery: confirmation bias, leading questions, the *say-do gap*; weigh evidence by strength (observed behavior beats stated opinion)
- Synthesize interview findings by counting signals, not noise, and update a bet's confidence with `updateConfidence`, connecting back to RICE's `confidence` input
- Decide to continue, pivot, or kill a bet with evidence, applied end to end to Mercado's recommendations bet in the capstone project
Before you start
What you need to bring
It's for you if...
- Engineers who already identified a bet's riskiest assumption in the Product Thinking guide and now need to validate it with real users
- Devs who want to run cheap, fast validation before writing weeks of production code
- Anyone who's watched a team ship a "validated" feature that was only ever validated by asking people what they'd like
- Engineers who want a structured alternative to guessing, or to waiting for a PM or researcher to hand them the decision already made
Requirements and materials
- Product Thinking for Engineers Guide completed (or equivalent: outcomes vs. outputs, RICE, finding a bet's riskiest assumption)
- Comfort running simple Node.js scripts (no dependencies)
- No prior user research or interviewing experience required — the guide teaches it from scratch
Content
The syllabus, module by module
Open any of them to see its lessons.
- Guide overview: validate the bet before you build it
- Building is the most expensive way to learn
- Continuous discovery vs. big-bang research
- The cost of building the wrong thing
- What discovery buys: cheap evidence
- Discovery and delivery, together
- What discovery is NOT
- Mini-project: decide what to discover this week about `recommendations`
- Module overview: how to talk to users without contaminating the answer
- Past behavior, not future intentions
- The Mom Test
- Open questions, not leading ones
- Listen to the problem, don't sell the solution
- The say-do gap
- Running a good interview, start to finish
- Mini-project: the interview script to validate `recommendations`
- Module overview: from loose interview notes to the problem tree
- The tree's four levels
- The outcome, at the top of the tree
- Opportunities are problems, not solutions
- From opportunity to solutions
- From solution to experiment
- Branching and pruning the tree
- Mini-project: Mercado's recommendations opportunity solution tree
- Module overview: design the experiment that can sink your bet
- From assumption to falsifiable hypothesis
- Making it truly falsifiable
- The riskiest assumption test
- Design to falsify, not to confirm
- What a good test looks like
- Cheap vs. strong: evidence isn't binary
- Mini-project: the riskiest assumption test for `recommendations`
- Module overview: from the chosen test to the right fidelity
- What a prototype is for (and what it isn't)
- Paper and clickable: the first two levels
- Wizard-of-oz: when there's a human behind the curtain
- The fake door: it measures interest, not satisfaction
- Fidelity vs. cost: why more expensive isn't always better
- Choosing the right fidelity: `pickFidelity`
- Mini-project: choose and run the lowest-fidelity prototype for `recommendations`
- Module overview: from "we ran the test well" to "what do we decide"
- Clustering findings by problem: `clusterByProblem`
- Counting signals: `countUnpromptedUsers`
- Signal vs. noise: complete `synthesize`
- How much is enough to decide?: saturation
- Persevere, pivot, or kill: `decide`
- Updating confidence: `updateConfidence`
- Mini-project: synthesize `recommendations`'s discovery and decide
- Module overview: validate `recommendations`, end to end
- Step 1: turn the assumption into a falsifiable hypothesis
- Step 2: choose the cheapest test that can truly refute it
- Step 3: prepare the interview script, without selling the solution
- Step 4: run the main test and read the signal, without dressing it up
- Step 5: audit the sample and weigh the evidence without bias
- Step 6: synthesize the signals, update confidence, decide
- Final project: validate `recommendations`, end to end
Common questions
What people usually ask
No limit. It's a free guide: come in whenever you like, as often as you like.
No. Modules run from easier to harder, but you can jump to the one you need. Progress is saved per lesson.
Whatever is needed is listed under “What you need to bring”, above. If nothing is listed there, you can start from zero.
In the Club's WhatsApp group, and every two weeks there's a live with an instructor where questions get worked through.
Yes. It's issued automatically once you finish every lesson, with a verifiable code you can share on LinkedIn.
Start whenever you like
What students say
These reviews are from enrolled students who completed at least 50% of the course. We moderate reviews only on content grounds (spam, offensive language, personal data), never for being critical or negative.
No approved reviews yet.
Be the first to share your experience!