Lean Product Discovery: How to Build What Customers Actually Want

Introduction

Building great products is hard. Research shows that most new products fail. For every hit like Apple, Google, or Facebook, countless failed products have pushed companies out of business.

If you have ever built a product that customers truly love, you know how powerful that success can be. When users are genuinely excited, business metrics grow fast. Yet only a small share of products ever reach that level.

Guessing what customers want leads either to lucky wins or to costly failures. So what makes it so hard to build products people love, and why do so many products fail?

The Necessity of Discovery

Successful products do not come from guesswork. They come from a deliberate, systematic discovery process. Before a product can succeed in the market, it must go through this phase.

Product discovery is an iterative, adaptable process. It focuses on understanding customer needs and market dynamics, then uses that knowledge to guide product development.

For founders and product managers, mastering this process is essential as a product moves from concept to launch.

At its core, product discovery is the process of deciding what to build. It makes sure every item in the product backlog is validated before development. It also makes that validation part of your daily routine.

Product discovery is not a one-time event. It is a continuous process that strong product teams build into their everyday work. Its purpose is to steadily reduce uncertainty around a product idea.

That is why companies should move away from one-off, large-scale design efforts. Instead, they should empower product teams to improve the product continuously, in line with business goals.

Origins and Foundations

The term “Product Discovery” comes from two serial entrepreneurs, Steve Blank and Eric Ries. Both are known for their work on the Lean Startup methodology. Eric Ries wrote The Lean Startup (2010).

Steve Blank wrote “Why the Lean Startup Changes Everything” for the Harvard Business Review in 2013. The Lean Startup approach is built on engaging customers early in the business development process. That early engagement is exactly what Product Discovery is based on.

Brant Cooper, author of The Lean Entrepreneur, puts it simply: Customer Discovery is about questioning your core business assumptions. Done well, it is a customer-focused, scientific process. It replaces an assumed product-market fit with real evidence.

Need expert help launching your product? LA NPDT can support you with strategy, planning, and execution. Visit LA NPDT to see how we can help you refine your product launch checklist and reach your business goals.

Begin with the end in mind

Every product development process starts with a clear goal or challenge. It ends with a decision to build a product or feature. Between those two points sits a dual-loop process of Exploration and Validation. Within this loop, several key decision points come up:

This structured approach keeps each stage of product development deliberate and evidence-based. It reduces uncertainty and improves your chances of reaching strong product-market fit.

The Lean Product Process, shown in the figure below, is a step-by-step framework. It guides you through the layers of the product development pyramid, from the foundation upward.

This process has six steps:

Keep in mind that not all six steps are needed for every product or feature. Some steps only apply when you are building a completely new product. For example, defining target customers, finding underserved needs, and setting the value proposition are foundational.

You usually complete them once, when launching a new product. After version one is live, you improve the product by cycling through the last three steps: choosing features, building them, and testing them with customers.

Product Discovery versus Product Delivery

Building successful products comes down to two core activities: deciding what to build, and building it. Product Discovery is the systematic process of figuring out what to build. It reduces uncertainty around a business idea step by step and ends with validated backlog items. Product Delivery is the process of actually building the product.

Traditionally, companies have focused most of their effort on the build phase and neglected discovery. The right balance depends on the product life cycle stage. Starting a brand-new business idea is very different from targeting a new customer segment or running a recurring campaign, such as a Black Friday promotion.

At its core, Product Discovery is an evidence-based process. It reduces uncertainty in two ways: by finding problems worth solving, and by validating that a proposed solution can work. It usually unfolds as a series of nonlinear activities carried out by cross-functional teams. In short, Product Discovery is a flexible period focused on choosing the right thing to build. Product Delivery, by contrast, focuses on building it well.

The structure of Product Discovery can vary, and we will cover that in the sections below. Product teams usually focus on one of two areas. The first is the problem space: checking whether users, customers, or stakeholders truly have a problem.

The second is the solution space: designing and testing a matching solution. You need both to serve users well and meet business goals. But teams often spend their time on the wrong one. Ideally, Product Discovery should focus mainly on the problem space.

Product Discovery is a critical pillar of successful product development. But it works best when paired with an outcome-oriented approach to Product Strategy, Product Goals, and Product Roadmaps. Start by understanding your strategic context. The goal is not an elaborate, McKinsey-level company strategy. It is a practical framework that guides trade-off decisions as you explore the problem space during Discovery.

Ready to launch your product like a pro? Contact us today to learn how LA NPDT can help you navigate the path to a successful product introduction.

A few of the companies that have adopted the Lean Approach:

A general definition of Lean Principles applicable to any Lean Enterprise includes ten guiding principles grouped into four dimensions.

Ten Best Practices for Creating Successful Products

In Summary

Although the selection and quality of Product Discovery activities are critical, the overall volume of activities is not the primary concern. The main objective is to gather robust evidence that supports evidence-based decisions regarding whether a problem is worth solving and whether a solution is worth pursuing.

Product discovery techniques differ mainly in how much money they cost and how much they lie to you. Stated preference is cheap and unreliable; revealed preference is expensive and honest. A good discovery plan spends the first dollars on the cheap methods and reserves the expensive ones for the assumptions that would kill the business if wrong.

The discipline that separates useful discovery from theater is the stop condition. If the team cannot state in advance what result would make them abandon the concept, the study is a budget for reassurance rather than a decision tool, and the money is better spent on the first prototype.

Lean Product Discovery is a systematic process. It aims to understand customer needs and market dynamics. This knowledge then guides product development. It is an iterative and adaptable process. The goal is to reduce uncertainty around a product idea. This approach helps determine what to build.

Product discovery is essential because many new products fail. Relying on guesswork can lead to failure. It helps ensure product success. This process validates product ideas in advance. It reduces uncertainty and enhances the likelihood of product-market fit. This leads to products customers truly love.

The term "Product Discovery" originated from the work of Steve Blank and Eric Ries. They are known for their contributions to the Lean Startup methodology. Eric Ries authored "The Lean Startup" and Steve Blank wrote for Harvard Business Review. Their work emphasizes early customer engagement.

The Lean Product Process has six steps. These include determining target customers and identifying their underserved needs. Next, define your value proposition. Then, specify your Minimum Viable Product (MVP) feature set. After that, create your MVP prototype. Finally, test your MVP with customers.

Not all six steps are always necessary. They are primarily for developing a completely new product. For example, determining target customers and defining the value proposition are foundational. Once a version one product launches, continuous improvement can focus on the latter three steps. These steps involve specifying, creating, and testing new features.

Most discovery work goes wrong because teams pick a familiar method rather than the method that addresses their biggest unknown. Every product carries four risks — value, usability, feasibility and viability — and each product discovery technique is good at retiring one or two of them and useless against the rest.

Caption: evidence quality rises with the amount the customer must actually commit — money and time beat opinion.

A discovery activity without a pre-agreed threshold produces a debate, not a decision. Write the number down before you collect data, and specify what you will do in each outcome.

Discovery is the front end of our process, not a separate service. Findings flow straight into product discovery deliverables and then into product development consulting where the validated concept is scoped, costed and engineered.