Discovery
Understanding customer problems and validating what’s worth building before you commit
About this domain
Discovery is the work of reducing uncertainty before a team commits. It spans talking to users, researching the market and the alternatives customers could choose, mapping and assessing opportunities, testing the riskiest assumptions, and prototyping just enough to learn — all aimed at separating problems that are real from problems that merely sound plausible.
Its purpose is to make commitment cheap to get right and expensive mistakes rare. Discovery produces the evidence that roadmapping, specification, and delivery decisions later rest on, and it is as successful when it kills an idea as when it validates one. It is distinct from delivery, which builds what discovery has judged worth building.
Trigger, mindset & exit
An opportunity, problem, or idea that is not yet understood or validated well enough to build against.
Curious and skeptical — assuming you are wrong until evidence says otherwise, chasing the real problem rather than a favorite solution.
The problem is understood and the opportunity is validated (or killed) — there is enough evidence to decide whether it is worth building.
How the workflows connect
Open one to see its agents.