PRODUCT DISCOVERY
Product Discovery.Build evidence before you build product.
Discovery is the work that reduces uncertainty before delivery becomes expensive. We research the customer problem, make the assumptions visible, prototype possible answers and use the evidence to decide what deserves to move forward.
WHAT IS DISCOVERY?
What Product Discovery Is
Product discovery is the evidence-gathering and decision work that happens before or alongside delivery. Its purpose is to understand the customer problem, test important assumptions and reduce the risk of committing significant effort to the wrong solution.
Good discovery ends in a decision, not an ever-growing research repository.
THE PROCESS
The CommView Product Discovery Process
Research is useful when it changes what the team decides to do.
Frame
Define the customer, problem and decision the discovery needs to inform.
Research
Use interviews, product data, frontline evidence and market context appropriate to the question.
Synthesis
Turn observations into patterns, assumptions and competing explanations.
Prototype
Make possible solutions concrete enough for users and stakeholders to react to.
Test
Collect evidence against the important assumptions rather than seeking general approval.
Decide
Move forward, change direction, gather more evidence or stop.
CONTINUOUS OR PROJECT
Continuous Product Discovery vs a Focused Discovery Project
Both can be useful. The right model depends on the product, team and decision cadence.
Continuous discovery
- Useful when a product team is making regular product decisions
- Keeps customer contact and evidence inside the operating rhythm
- Works best when the team has the capacity and ownership to sustain it
Focused discovery
- Useful when a specific strategic decision needs concentrated evidence
- Can reset a product that has drifted or de-risk a significant new bet
- Creates a defined decision point before larger investment
FAQ
Product Discovery FAQ
What does a product discovery service include?
A product discovery service can include problem framing, customer research, analysis of product and commercial evidence, synthesis, assumption mapping, prototyping, user testing and a recommendation on what should happen next. The exact mix should follow the decision being made rather than a fixed workshop checklist. CommView can continue into specification and delivery.
How long does product discovery take?
Product discovery has no universal duration. A narrow decision with accessible users and existing evidence can move quickly, while a new market or complex workflow may need deeper research and several test cycles. We scope discovery around the uncertainty that must be reduced and aim to reach a useful decision without extending research unnecessarily.
Do we need discovery if we already know what customers want?
Existing customer knowledge is valuable evidence, but it does not automatically tell you which problem matters most or which solution will work. Discovery can be lighter when the evidence is already strong. The key is to identify what remains uncertain before committing delivery effort, rather than repeating research simply because a process says you should.
PRODUCT
Discovery should end with a better decision, not just more notes.
Bring the customer problem, evidence and product decision into the same piece of work.
Problem before roadmap.
Evidence before opinion.
Delivery stays connected.