The Lean Product Playbook

Most product teams do not lack ideas. They lack a way to tell which idea deserves the next month of work. Olsen gives that way: a clear definition of product-market fit and a six-step process for testing it. If you have ever built something carefully and then watched people shrug, this book is aimed at that problem.

It gives you a map instead of a slogan

Lean Startup tells you to build, measure and learn. Olsen's point is that many people like the idea and still do not know how to apply it. He compares them to someone who joins a gym and then does not know which exercises to start with. The Product-Market Fit Pyramid is his answer. It splits fit into five layers, from target customer up to user experience, and treats each layer as a hypothesis you can check.

What changes in how you work

You stop starting with the feature list. You write down who the customer is, what they need and how well their current option serves them, and only then talk about what to build. Meetings change too. Instead of arguing for a feature, you ask which layer of the pyramid it tests. That is a calmer way to argue, because everyone can see which hypothesis is on the table.

Testing before building

The book is firm that building is the expensive way to learn. Olsen argues a landing page, mockups or a clickable prototype can teach you more per pound spent than a finished build. For a small business with a few people and a tight budget, that matters more than any framework. One month spent testing the wrong idea on paper costs far less than one spent coding it.

When to read it, and when to skip it

Read it before you commit to a new product, a big feature or a move into a new customer group. It also helps when growth has stalled and you need to find out which assumption broke. Olsen says the guidance suits software products best, and the book dates from 2015, so check that the tools it lists are still current. If you only need help with pricing or sales, other books fit better. Olsen says himself that business model and acquisition each deserve a book of their own.

How it connects to logging decisions

Every layer of the pyramid is a decision you can write down: this customer, these needs, this value proposition, this feature set. Write the hypothesis, the date and what would prove it wrong. Six months later you can see which bets paid off and why. That record is also the start of a repeatable playbook, because a process you have run three times is one you can hand to someone else.

Dan Olsen argues that products fail for one main reason. In his words, "The main reason products fail is because they don't meet customer needs in a way that is better than other alternatives." His fix is a framework, the Product-Market Fit Pyramid, and a six-step method for testing it, the Lean Product Process. The book then covers design, agile development and analytics, so it follows a product from the first idea to the numbers after launch.

Achieving Product-Market Fit with the Lean Product Process

Olsen uses Marc Andreessen's definition: "Product-market fit means being in a good market with a product that can satisfy that market." He then splits it into a pyramid. The bottom two layers, target customers and their underserved needs, make up the market side. The top three, value proposition, feature set and user experience, make up the product side. Each layer rests on the one below, so a mistake low down spoils everything above it. The Quicken story is his example: it launched into a market that already had 46 personal finance products and won by meeting needs the others missed.

Problem Space versus Solution Space

This chapter separates what customers need from how you might deliver it. His space pen story makes the point: a pen built for zero gravity cost a fortune, while the Russian space agency simply used pencils. Olsen argues for outside-in development, which starts with the customer rather than with what the team would like to build. He also deals with the Henry Ford line about faster horses, saying you should listen to customers about their problems, not ask them to design your solution.

Determine Your Target Customer

Step one is naming who you are building for. Olsen likens it to fishing, where your product is the bait and you only learn who bites once it is in the water. He covers segmenting by demographics, behaviour and needs, the difference between users and buyers, the technology adoption life cycle, and personas as a way to keep the customer in view.

Identify Underserved Customer Needs

Olsen uses needs and benefits interchangeably, and says a user goal is no different from a need. You test them in discovery interviews, using benefit ladders to find out why a need matters. His main tool is the importance versus satisfaction chart. The best opportunities are the needs customers rate as important and poorly met today. He also covers the Kano model, which separates the benefits customers expect from the ones that delight them.

Define Your Value Proposition

Now you decide which of those needs you will meet and how you will be better than the alternatives. Olsen repeats a definition of strategy as deciding what you will not do. You then compare your offer with competitors, benefit by benefit. The Cuil story shows the cost of a weak case against Google, and the Flip camera shows that a good position can erode as the market moves.

Specify Your Minimum Viable Product (MVP) Feature Set

Here you brainstorm features for each benefit, write them as user stories and break them into small pieces. You estimate effort in story points and prioritise by return on investment, which weighs value against effort. The result is an MVP candidate. It stays a candidate until customer tests show it works.

Create Your MVP Prototype

Olsen resolves the argument over what counts as an MVP by talking about MVP tests instead. His matrix sorts them into marketing and product, qualitative and quantitative. A landing page is a marketing test. A clickable prototype is a product test. He warns against treating an MVP as a product with limited functionality and nothing else: it should still be reliable, usable and delightful.

Apply the Principles of Great UX Design

A short guide to design for non-designers. Olsen uses an iceberg: conceptual design, information architecture, interaction design and visual design, with the visible visual layer sitting on top of the rest. He lists design principles, stresses that copy is part of the experience, and says most teams need more than one kind of design skill.

Test Your MVP with Customers

This is the practical chapter on user testing. Olsen recommends testing with one customer at a time, in person where you can, and allowing for a no-show rate of around 10 percent. He gives a session structure of warm-up, feedback and wrap-up, with open questions rather than closed ones. He also separates usability problems from the question of product-market fit, because a product can be easy to use and still not wanted.

Iterate and Pivot to Improve Product-Market Fit

After each wave of tests you note what share of users raised each issue, fix the most common ones and test again. Olsen reworks Eric Ries's loop as hypothesise, design, test and learn. If the real problem sits low in the pyramid, polish on the top layers will not help. A pivot is a change to a main hypothesis, such as a new target customer. The Flickr and Instagram stories show it working.

An End-to-End Lean Product Case Study

MarketingReport.com is walked through all six steps, with the test results shown. Olsen says the project took under two months and mostly used mockups, so it is the part to read if you want to see the process run from start to finish.

Build Your Product Using Agile Development

Once product-market fit looks good enough, you build. Olsen explains Scrum, with its sprints and backlog, and kanban, which limits the work in progress. He then covers quality assurance, test-driven development, continuous integration and continuous deployment.

Measure Your Key Metrics

After launch you can learn from behaviour as well as opinions. Olsen uses the AARRR framework: acquisition, activation, retention, revenue and referral. He argues for finding the metric that matters most right now, the one with the best return if you improve it, and for writing the equation of your business so you can see which variable to move.

Use Analytics to Optimize Your Product and Business

The final chapter of the method adds the Lean Product Analytics Process: define your metrics, set a baseline, judge each metric's upside, then design the best improvement and test it, ideally with an A/B test. A Friendster case study shows it applied to a viral loop. The chapter also warns about a local maximum, where small tweaks stop helping and you need a fresh approach.

What to do with it

• Write down your target customer, their top five needs and your value proposition on one page, and mark each as a hypothesis.
• Interview five customers about their needs and their current solution before you design anything.
• Plot the needs on an importance versus satisfaction chart and pick the one that is important and poorly served.
• Build the cheapest test you can, such as a landing page or a clickable mockup, and run it with real people.
• Track feedback by wave, fix the lowest layer first, and write down each decision and why you made it.