Skip to content
BENIBIX Learn

Product Discovery

Business📦 Product ManagementProduct Discovery

Also known as Discovery, Continuous Discovery, Discovery Phase, Product Discovery Process

Find out what to build, and test ideas, before you build them.

Think of it like

Before you cook for a friend, you ask what they like. Then you make a small taste first.

Example

Lucy's team thinks users want a budget planner. Five calls and a clickable mockup show they just want spending alerts. So they build alerts.

Why it matters

Many new features are used far less than the team hoped. Discovery throws out weak ideas while they are still cheap to drop.

Definition

Product discovery is the work of finding out what to build before building it. The team talks to users to learn their problems. It then tests ideas cheaply, with sketches, mockups or fake buttons. It checks four risks: will people want it, can they use it, can we build it, and does it pay. Ideas that fail are dropped before they cost much. Building the chosen idea for real is called delivery.
Discovery decides what is worth building. Delivery builds it. Both loops run at the same time.

Common mistake

Treating it as a phase done once at the start. Good teams keep doing discovery every week, next to delivery.

Key takeaways

  1. 1
    Learn before building. Talk to users first.
  2. 2
    Test cheaply. A sketch costs less than code.
  3. 3
    Never really done. It runs beside delivery every week.

Compare

Learn it properly