Discovery
Product Discovery: From Problem to Solution
Product Discovery Review: Finding Problems, Researching Users, Testing Assumptions, and Choosing Solutions Before Large-scale Development.
Discovery reduces uncertainty before expensive solutions, but does not have to end with absolute certainty. The team consistently tests four risks — value, convenience, feasibility and viability — and selects the next test for the cost of the error.
**Discovery: Why and how to conduct research in the product cycle
Discovery (discovery, product research) is a key part of the development of any IT product. Here you find out what is worth building, for whom it is valuable and why. Mindlessly cloning trending features or running features without understanding the task quickly turns the product into an expensive museum of unnecessary options.
In the Discovery phase, you minimize risks: you spend less resources on useless developments, adjust goals and solutions to maturity, and get real data to prioritize. Product companies use Discovery at the start of a new product, when displaying features or for a regular update of hypotheses.
Main stages of Discovery
Framing problems and hypotheses
It is always worth starting with a clear formulation of the problem: which user and what is faced with, why it is important for the business and what data confirm it. Assumptions are your assumptions about what is stopping the user or where there is an opportunity to grow.
Problem framing and assumptions
Opportunity Solution Tree
In order not to dig into one idea and see all the options, use the Opportunity Solution Tree map. This approach gives you a transparent tree: these are the problems we see, here are the solutions, here’s how you can test hypotheses.
User interviews
Research rarely works without personal interviews. Preparation of the script, recruiting the right respondents, clear conduct – all this allows you to hear genuine problems of the target audience, and not think them up for her.
Read more: Interview: Preparation and Conduct
** Usability tests and quick checks* *
To understand how users really behave, usability tests allow. You show the prototype to people alive, you look behind your hands, and you capture where it’s slowing down, confusing, or irritating.
Research methods: what to choose and when
Not all hypotheses are tested the same way. There are quantitative and qualitative methods, field and laboratory tests, research of competitors and own users. Choosing a proper approach is a separate art.
Research: Methods and When to Choose
** Market analysis and insights* *
Competitive analysis
Always look at who has already closed this problem in the market, what they win and where their weaknesses are. Competitive analysis is not for urgent copying, but to search for growth zones and underrated pain.
Read more: Competitive analysis (product)
Synthesis of insights and decision-making
The studies provide a lot of disparate data. The main skill is to synthesize conclusions, isolate insights, understand where and how to dig deeper, and where there is enough information to start developing an MVP or the next test.
Insight Synthesis and Solutions
Discovery Documentation and Artifacts
**Product brief, PRD-lite and other fast specifications **
Any research work loses value if it is not designed in visual and short documents. Product brief, PRD-lite – simple templates where you fix the problem, key metrics, audience, insights and recommended solution. This document is the anchor for all development and communication within the team.
Artifacts: problem brief / PRD-lite
Useful references on the topic
FAQ
**1. Why waste time on Discovery when the idea seems obvious? ** Because evidence is subjective. Without Discovery, the team loses the chance to test their assumptions on real users.
2. Which Discovery Methods are Best for Starting a New Product? Most often, problem framing, competitive analysis, and interviews with potential target audiences work.
3. When is it time to complete the Discovery phase? When there are clearly articulated insights, validated problems, formed a set of proven hypotheses and can justify the focus for MVP.
4. Discovery Artifacts – Should You Always Do It? It is recommended to capture key results so that the team and stakeholders are on the same wavelength. Even a short one-pager is more useful than verbal agreements.
5. How to convince the team of the importance of Discovery? Show the cases of failures, when the teams built the solution not for real pain, and successful results after qualitative research.
6. What mistakes are most often made with Discovery? Jump to decisions, neglect independent analysis of competitors, adjust research results to their beliefs, work with the wrong audience.