Product Discovery
Product discovery is the skill of finding out what to build by talking to users and reading evidence, rather than by assuming. It is assessed on question quality and on whether someone changes their mind when the evidence says they should.
Also called: customer discovery, user research, problem discovery
What is product discovery?
Discovery covers identifying the real problem behind a request, designing research that could disprove your own hypothesis, running non-leading interviews, and turning raw signal into a decision.
Most wasted engineering time traces to building the wrong thing confidently. Discovery is also the skill people most often learn sideways — engineers, support leads, and founders acquire it without ever holding a PM title.
What do the levels of product discovery mean?
Four levels, each defined by observable behaviour rather than by years. This is the definition employers set their bar against, and the one every proof is scored to.
- L1Aware
Talks to users and gathers feedback, but mostly confirms what was already assumed.
Evidence: Interview notes with findings recorded.
- L2Working
Asks non-leading questions, separates what users said from what they did, and reports uncomfortable findings.
Evidence: Research notes showing a finding that contradicted the original plan.
- L3Independent
Designs research that could disprove the hypothesis, triangulates qualitative and quantitative evidence, and changes the plan when it should change.
Evidence: A discovery plan with a falsifiable hypothesis and a decision traced to evidence.
- L4Leading
Builds discovery practice across a team and shifts organisational decisions away from opinion toward evidence.
Evidence: A discovery process others run, with decisions attributable to it.
| Level | Label | People proven here |
|---|---|---|
| L1 | Aware | 0 |
| L2 | Working | 0 |
| L3 | Independent | 2 |
| L4 | Leading | 0 |
How is product discovery assessed?
Candidates get a stakeholder request plus contradictory data and must design the discovery that would resolve it. Scoring rewards non-leading questions, a stated hypothesis that could be falsified, and a decision that follows from the evidence rather than from the original request.
Which roles require product discovery?
| Role | Level required | Status |
|---|---|---|
| AI Builder | L2 Working | Nice to have |
| AI Product Manager | L3 Independent | Required |
| Product Manager | L3 Independent | Required |
| Founding Engineer | L2 Working | Required |
How do you prove product discovery?
You have capacity for two of five things. Decide, and tell the person who loses.
One vague request, one Slack thread of contradictions. Produce a spec a team can build without you.
Product Discovery: questions people ask
- I do this but I'm not a PM. Does it count?
- It counts. This is the single most common sideways-acquired skill we see — engineers who ran the customer calls, support leads who found the real problem. The proof records the skill, not the title you had while using it.
- What if my company never let me do formal research?
- Formal research is not required. The challenge measures how you would design discovery and how you reason from conflicting evidence, both of which you can demonstrate without ever having run a research programme.
- How is this scored fairly across industries?
- The rubric scores reasoning quality, not domain knowledge. The brief supplies the domain context you need, so candidates from other industries are not penalised.