What is Product Discovery?

TL;DR

• Product discovery helps teams learn before making expensive commitments.
• It starts with problems and evidence, not polished solutions.
• User interviews, analytics, prototypes, and usability tests can all contribute.
• Discovery can continue while delivery is happening.
• An MVP or prototype can be used to test an important assumption.

What happens during product discovery?

Suppose users say: “I want more control over AI-generated playlists.”

That is useful evidence, but it leaves major questions unanswered. What kind of control? Before generation or afterward? Do users dislike individual tracks, the order, the mood, or the entire result? How frequently does this problem happen?

Discovery narrows those unknowns until the team has enough evidence to choose a direction.

Figr’s Spotify AI playlist steering project shows this kind of narrowing. A broad idea becomes a more specific product direction around post-generation steering, including locking songs, swapping suggestions, and undoing changes.

What methods are used in product discovery?

Discovery can combine several forms of evidence:

• User interviews to understand motivations, goals, and problems.
• Product analytics to understand what users actually do.
• Support and sales feedback to identify recurring problems.
• Competitive research to understand alternatives and expectations.
• User flows to expose interaction complexity.
• Wireframes and prototypes to make ideas testable.
• Usability testing to observe where an experience fails.
• Experiments to test assumptions with real behavior.

No single method provides the whole answer. Strong discovery combines evidence rather than treating one interview or one dashboard as truth.

Product discovery vs. product delivery

Discovery asks: Should we build this, and what might work?

Delivery asks: How do we build and ship it reliably?

Modern teams often do both at the same time. Discovery can stay one step ahead of delivery, reducing uncertainty before the team commits heavily to upcoming work.

Figr’s deeper guide on discovery vs. delivery product management explores how the two rhythms work together.

How do you run product discovery?

1. Start with the problem, not the requested feature.
2. Write down the assumptions that would make the idea succeed or fail.
3. Rank the assumptions by risk and uncertainty.
4. Choose the cheapest useful way to test the riskiest assumption.
5. Collect evidence from users, behavior, prototypes, or experiments.
6. Update the problem framing and solution direction based on what you learn.
7. Decide whether to proceed, change direction, narrow scope, or stop.

Product discovery and MVPs

An MVP can be part of discovery when the team needs real usage to test an assumption.

The goal is not simply to ship a smaller product. The MVP should answer a question the team cannot answer reliably through cheaper methods.

Common product discovery mistakes

Asking users to design the solution

Users are excellent sources of problems and context. Their requested feature is not automatically the correct solution.

Validating only the idea you already prefer

Discovery should be capable of changing the team’s mind.

Only talking to users

What people say and what they actually do can differ. Pair qualitative evidence with product behavior where possible.

Creating polished prototypes too early

High visual polish can make weak ideas feel more resolved than they are.

Treating discovery as a workshop

A two-day exercise is not continuous learning.

Frequently asked questions

Who should participate in product discovery?

Usually product, design, and engineering, with research, data, customer-facing teams, and stakeholders involved when useful.

Does discovery always require user interviews?

No. Existing analytics, support tickets, research, session recordings, and product behavior may already provide useful evidence.

When does product discovery end?

Often it does not have a clean endpoint. Teams can continue learning throughout design, development, launch, and iteration.

The bottom line

Product discovery reduces the distance between “we think this is a good idea” and “we have enough evidence to justify the next investment.”

Its job is not to eliminate uncertainty. It is to make the remaining uncertainty visible.

Related terms

Product management · Product strategy · MVP · User story · PRD

Relevant Figr resource

Read Discovery vs Delivery Product Management for a deeper operating model.