Strategy
Discovery
Plain English
Figuring out what to glossaryBuildA build is the process of compiling and packaging code into a runnable application.Open glossary term and why.
Definition
Discovery is the phase of understanding problems, users, and opportunities before building solutions.
In practice
Includes serviceUser ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service, ideation, and validation activities.
In context
The most useful outcome is often a decision not to glossaryBuildA build is the process of compiling and packaging code into a runnable application.Open glossary term. That is also the hardest one to report as progress, which is why discovery gets quietly reduced to serviceUser ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service theatre.
The reality
Often rushed or skipped, leading to solving the wrong problem.
Compared with
Discovery vs Delivery
Discovery reduces uncertainty about what is worth building. glossaryDeliveryDelivery is the process of building, testing, and releasing a product or feature.Open glossary term reduces uncertainty about whether it can be built well. Different questions, different methods, and the same team can run both if the outputs are judged differently.
FAQ
Common questions
A few practical answers to the questions that usually come up around this term.
What is discovery?
Understanding problems before building solutions.
What happens in discovery?
serviceUser ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service, ideation, and validation.
Why is it important?
It reduces the risk of building the wrong thing.
When should you do it?
Before committing to glossaryDeliveryDelivery is the process of building, testing, and releasing a product or feature.Open glossary term.
Related Services
Related Guides
Related Terms
