Product discovery playbooks
Turn uncertain opportunities into focused research questions and useful experiments. Choose a scenario, then the decision you need to make.
Discovery Assumption Testing
A team has beliefs about users, value, or feasibility and needs small, observable tests before committing to a solution.
Opportunity Comparison
Several opportunity statements compete for attention, and the team needs a defensible comparison rooted in user evidence.
Interview Bias
Interview wording and facilitator behavior may steer participants, weakening the evidence used to frame a product decision.
Product Experiments
A bounded product experiment needs a clear hypothesis, comparison, guardrail, and stopping rule before results can guide investment.
Problem Framing
A requested feature may hide a different user problem, so discovery must define the outcome and constraints before solution work begins.
User Needs Evidence
User needs are often written in internal language; this workflow ties each need to observed behavior, context, and a desired outcome.
Research Question Prioritization
A discovery backlog contains more questions than the next research round can answer, so the team needs an explicit selection rule.
Participant Recruitment Fit
Recruitment should match the decision under study, including relevant contexts and access needs rather than only convenient availability.
Contextual Observation
Observed work reveals interruptions, tools, and workarounds that interviews or idealized process descriptions can miss.
Journey Map Validation
A journey map becomes useful when its stages, waits, and handoffs are checked against real evidence rather than inferred from team consensus.
Usability Session Analysis
Session analysis turns observed behavior into findings with evidence, confidence, affected tasks, and a concrete product decision.
Research Synthesis Themes
Synthesis should reveal useful patterns while preserving participant differences, counterexamples, and the limits of the source material.
Baseline Problem Cost
A baseline makes improvement testable by describing current effort, delay, rework, or support burden before a solution is selected.
Prototype Task Design
Prototype tests need neutral, realistic tasks that let participants reveal their own strategy instead of following the designer instruction.
Concept Comprehension
Early concept checks test whether people understand the promised job and language before visual polish creates false confidence.
Solution Alternative Comparison
An opportunity may be addressed by a product change, process change, reuse, or a deliberate decision to defer.
Survey Question Quality
A survey can produce precise-looking numbers while asking ambiguous, leading, or double-barreled questions that respondents interpret differently.
Accessibility Discovery
Discovery evidence is incomplete when disabled people, assistive technology, or low digital skill contexts are absent from the research plan.
Naming and Language Test
Terminology should be tested in context so labels reflect words users recognize and support correct decisions without coaching.
Discovery Decision Readiness
A discovery decision should reflect answered questions, known constraints, and critical unknowns rather than schedule pressure or team enthusiasm.