product-discovery

name	product-discovery
description	Turn a product opportunity or feature idea into an evidence-backed decision using problem framing, hypotheses, user research, opportunity sizing, prioritization, and a testable product brief. Use when deciding what or whether to build; do not use for implementing an already-approved feature.

Product discovery

Reduce uncertainty before committing implementation effort.

Workflow

1. Define the user, situation, unmet need, desired outcome, and current alternatives.
2. Separate observed evidence from assumptions.
3. Write a falsifiable hypothesis and the riskiest assumption behind it.
4. Choose the smallest validation method that can change the decision: interviews, prototype test, concierge test, data analysis, demand test, or technical spike.
5. Size impact and effort using one consistent framework such as RICE or ICE; do not mix scoring systems without explanation.
6. Decide: advance, revise, defer, or reject.
7. For approved work, produce a concise brief with scope, non-goals, user stories, acceptance criteria, success measures, dependencies, and open questions.

Do not manufacture user evidence or treat stakeholder enthusiasm as validation. State confidence and what evidence would reverse the decision.

Read detailed-guide.md for interview prompts, scoring models, roadmap patterns, JTBD, and full product-requirement templates.