Just Start with Experiment-Driven Development
Building products without talking to customers is like navigating without a map. You might get somewhere, but probably not where you intended. Experiment-driven development is the practice of systematically testing assumptions before committing resources, reducing the risk of building something nobody wants.
The field sits at the intersection of product management, lean startup thinking, and user research. At its core is a simple idea: instead of debating opinions in a conference room, go find evidence. Run small experiments. Talk to real users. Let data guide your decisions. The companies that do this well ship fewer features but create more value.
The challenge for newcomers is that the landscape can feel fragmented. Some books focus on the strategic framework, others on specific experiment techniques, and others on building a sustainable discovery practice within a team. The best starting point is Teresa Torres’s “Continuous Discovery Habits,” which gives you a structured, repeatable approach to weaving customer discovery into your weekly workflow. For a comprehensive toolkit of specific experiments, David J. Bland and Alexander Osterwalder’s “Testing Business Ideas” is an excellent companion. And for the foundational philosophy that started it all, Eric Ries’s “The Lean Startup” remains essential reading.
Start here
Continuous Discovery Habits
Teresa Torres · 237 pages · 2021 · Easy
Themes: product discovery, customer interviews, opportunity mapping, assumption testing, product management
The most practical and actionable guide to building a sustainable product discovery practice. Teresa Torres has spent over a decade coaching product teams at companies ranging from early-stage startups to Fortune 500 enterprises, and this book distills that experience into a clear, repeatable framework.
Why Start Here
Most product teams know they should talk to customers more often. The problem is not motivation, it is structure. Torres solves this by introducing the concept of continuous discovery: at minimum, weekly touchpoints with customers, conducted by the team building the product, in pursuit of a desired outcome. That simple definition reframes discovery from a phase you do before building to a habit you maintain alongside building.
The book introduces the Opportunity Solution Tree, a visual framework for mapping the gap between business outcomes and customer needs. This tool alone is worth the price of admission. It helps teams move beyond feature requests and opinion-driven roadmaps toward a shared understanding of the problem space.
Torres also covers practical techniques for customer interviewing, assumption mapping, and designing small experiments to test ideas before committing engineering time. The writing is clear and grounded in real examples, never theoretical hand-waving.
What to Expect
A focused, well-structured read at 237 pages. Torres writes in plain language and assumes no prior experience with formal product discovery methods. Each chapter builds on the previous one, and the frameworks are immediately applicable. You will finish the book with a concrete plan for how to integrate discovery into your team’s weekly rhythm. Published in 2021, it reflects modern product practices and remote-friendly workflows.
Alternatives
David J. Bland & Alexander Osterwalder · 368 pages · 2019 · Easy
A visual, hands-on field guide packed with 44 specific experiments you can run to test whether your business idea will actually work. David J. Bland and Alexander Osterwalder created this as a companion to the Business Model Canvas and Value Proposition Canvas, giving teams a practical toolkit for reducing risk through rapid experimentation.
Why Consider This One
Where “Continuous Discovery Habits” teaches you the mindset and weekly practice of discovery, “Testing Business Ideas” gives you the experiment library. Need to test whether customers have the problem you think they have? There is an experiment for that. Need to validate willingness to pay? There is one for that too. The book organizes experiments by what you are trying to learn: desirability, feasibility, or viability.
Each experiment card follows the same format: a description of what it tests, the strength of evidence it produces, the time and cost involved, and practical setup instructions. This makes the book work as both a cover-to-cover read and a reference you grab when planning your next test.
The visual design is excellent. Like the other Strategyzer books, it uses full-color illustrations, diagrams, and a layout that makes complex concepts scannable. If you work in a dual-track agile environment where discovery runs alongside delivery, this book fits naturally into that workflow.
What to Expect
At 368 pages, it is substantial, but the visual format means it reads faster than a traditional text-heavy book. Bland and Osterwalder assume some familiarity with business model thinking, though you do not need to have read their earlier books. The experiment cards are the real value, and you will return to them repeatedly as you plan validation cycles.
Eric Ries · 336 pages · 2011 · Easy
The book that launched the modern product experimentation movement. Eric Ries drew on his experience as a startup founder and his study of lean manufacturing to propose a radical idea: startups should treat their product development as a series of scientific experiments rather than executing a grand plan.
Why Consider This One
“The Lean Startup” introduced concepts that are now part of the standard product vocabulary: the minimum viable product (MVP), the build-measure-learn feedback loop, the pivot, and validated learning. Even if you have absorbed these ideas secondhand, reading the original gives you the reasoning behind them and the case studies that make them concrete.
Ries argues that the biggest waste in product development is building something nobody wants. His solution is to shorten the feedback loop dramatically. Instead of spending months building a complete product, launch the smallest possible version, measure how customers actually behave, and learn whether your assumptions hold up. Then decide: persevere with the current strategy or pivot to a new one.
The book is broad in scope, covering everything from how to define and measure progress in uncertain environments to how established companies can apply startup thinking to innovation projects. It reads more like a manifesto than a tactical handbook, which is both its strength and its limitation.
What to Expect
At 336 pages, it is a comfortable read with a conversational tone. Ries uses stories from his own startups and from companies like Intuit, Dropbox, and Zappos to illustrate each principle. Published in 2011, some of the specific examples feel dated, but the underlying framework remains as relevant as ever. If you want the “why” behind experiment-driven development, this is where to find it. For the “how,” pair it with Torres or Bland and Osterwalder.