The Lean Product Playbook: reaching product-market fit layer by layer

Who should use it, and when not to

Use it when a product has users but doesn't take off, before deciding an MVP's scope, or when a team debates features while nobody agrees who the customer is.

If you don't know yet whether the business idea works at all, start with the build-measure-learn loop. To decide which feature to build next in a mature product, a prioritization method is more direct.

The core ideas

The pyramid. Product-market fit is how well the decisions in the top three, product, layers match the bottom two, market, layers. Each layer is a hypothesis to test.

Problem space and solution space. Needs belong to the customer and exist whether or not you build anything. Features are your solution. Mixing the two, such as treating a feature request as a need, is a common error.

Importance and satisfaction. The best opportunities are needs that matter a lot to customers and are poorly met by today's options.

Value proposition. Decide which needs you will meet better than alternatives, which you'll match, and which you won't address.

MVP. The smallest feature set that tests the value proposition. Olsen shows that an MVP test can be a prototype or a landing page, not always working software.

A worked mini example

This is an illustration. A shared shopping-list app for families in Brazil got 3,000 sign-ups from an Instagram campaign; 9% still use it after a month. It has five features. The team says it's for "busy parents". Four of six interviewees said price comparison was the only reason they'd pay, and support tickets complain that prices are out of date.

Working up the pyramid, the lowest weak layer is the target customer: "busy parents" is broad, and nobody knows who the 9% are. The next test is to interview ten active users and check their usage by feature. A likely value proposition, accurate price comparison, would make the meal planner and barcode scanner cut candidates.

How to review your product

1. Write the target customer as one narrow description.
2. List underserved needs, rated for importance and current satisfaction.
3. Write the value proposition: better at, match on, won't address.
4. Map features to needs, and list cut candidates and gaps.
5. Check the UX of the features that carry the value proposition.
6. Grade each layer's evidence and find the lowest weak one.
7. Design the next test for that layer, with results that confirm or change it.

The product-market fit pyramid review skill runs these steps with your data and marks layers without evidence.

Common mistakes

• Starting at the top. UX polish can't fix the wrong customer.
• A customer like "everyone". Narrow it until needs are shared.
• Feature requests taken as needs. Ask what problem the request solves.
• An MVP with every feature. It tests nothing clearly.

Where it comes from

Dan Olsen is a product management consultant and trainer who has worked with companies from early-stage startups to large public firms. Wiley published The Lean Product Playbook in 2015. Olsen also presents the pyramid in talks, such as one written up by Mind the Product.

This page is an independent summary in our own words. It is not affiliated with or endorsed by Dan Olsen or Wiley. The book's title is used only to name it. More explainers are in the business books index.

Questions

What is the product-market fit pyramid?

Dan Olsen's model of product-market fit as five layers: target customer and underserved needs (the market), then value proposition, feature set and user experience (the product). Each layer rests on the one below.

What are the steps of the Lean Product Process?

Determine your target customer, identify underserved needs, define your value proposition, specify your minimum viable product feature set, create a prototype, and test it with customers, then iterate.

How is it different from The Lean Startup?

Olsen describes his book as a practical guide to applying Lean Startup ideas to product work, with specific tools for each step, from needs to prototype tests.