What product discovery is

Product development has two kinds of work. Delivery is building, testing and releasing software reliably. Discovery is deciding what is worth building in the first place. Most teams are much better at delivery than discovery, so they become very efficient at building things that do not help.

Discovery in one sentence

Product discovery is the continuous work of reducing uncertainty about what to build, by learning from customers and testing ideas quickly and cheaply before committing to full development.

Two words matter there. Continuous means discovery is not a phase at the start of a project; it happens every week. Cheaply means you use the smallest effort that can answer a question, such as a conversation, a sketch or a fake button, rather than a finished feature.

Why most ideas fail

Ideas often fail for predictable reasons:

• Customers do not have the problem, or not badly enough to change behaviour.
• The solution solves the problem, but people cannot figure out how to use it.
• It is far harder to build than expected.
• It works for customers but not for the business, for example it costs too much to support.

Discovery tries to expose these failures early, when changing direction costs a few days rather than a quarter.

Who does discovery

Discovery works best as a team activity. A product trio, typically a product manager, a designer and an engineer, shares the work. Each brings a different lens: the PM on value and viability, the designer on usability and the engineer on feasibility and on what new technology makes possible. Engineers often spot cheaper ways to test or build an idea that nobody else would see.

Our running example

We will work with a team building an expense management tool for small and medium companies. Leadership wants to launch company cards so employees can pay directly instead of submitting receipts later. It sounds promising, but it is a big investment involving partners, compliance and new user flows. The team's job is to find out, quickly, whether and how to do it.

What discovery is not

It is not asking customers what they want and building it. It is not running a big research project for months. And it is not a way to avoid decisions. Discovery leads to decisions, made with better evidence. By the end of this section you will have mapped the assumptions behind the company card idea and chosen what to test first.