Many products fail for a simple reason: nobody needed them. A team spends months building an app, launches it, and finds that people carry on doing things the old way. Discovery is the work you do before building to avoid that waste. Employers value it because it saves money, and product and analyst roles often ask for user research and market research skills.
What discovery means
Discovery is learning, as cheaply as possible, three things:
- Is the problem real? Do people actually struggle with this, and how often?
- Is it worth solving? Is it painful enough that people would change their habits or pay?
- Will our idea help? Does a rough version of the solution get used?
You answer these with conversations, observation, simple data and small tests, not with software.
The mindset
Good discovery starts from humility. Your first idea is a guess. Your job is to find out where the guess is wrong while being wrong is still cheap. That means listening more than pitching, and being glad when evidence surprises you.
It also means separating the problem from the solution. "Farmers need an app" is a solution. "Farmers sell tomatoes at a loss because they cannot reach buyers before the produce spoils" is a problem. Many solutions could fix that problem, and an app may not be the best one.