Eric Ries

Eric Ries studied computer science at Yale, dropped out to pursue a startup, returned to finish his degree, and then co-founded IMVU — a 3D avatar-based social network — in 2004. IMVU was not an immediate success, and the early failures led Ries to think systematically about why startups so often build things nobody wants. His answer, developed through practice and through mentorship from Steve Blank (whose Customer Development methodology was a direct influence), became the Lean Startup methodology, which he began articulating on a blog before condensing it into a book.

The Lean Startup (2011) applies concepts from lean manufacturing — specifically the Toyota Production System developed by Taiichi Ohno — to software product development and startups. The core argument is that most startups fail not because they can't build their product but because they build the wrong product: they spend months or years in development before discovering that customers don't want what they made. The solution Ries proposes is a Build-Measure-Learn feedback loop in which you release the smallest possible version of a product (a minimum viable product, or MVP) as quickly as possible, measure how real users interact with it, and use that data to decide whether to pivot (change direction) or persevere. The goal is validated learning — replacing assumptions about customers with data.

The book also introduced the concept of Innovation Accounting, a framework for measuring progress in conditions of extreme uncertainty where traditional financial metrics are meaningless. And it popularized the idea of the pivot: a structured course correction that preserves what has been learned while changing fundamental assumptions about the product, market, or business model.

The Lean Startup landed at a moment when Silicon Valley's product development culture was ready for a new framework. Agile software development had already pushed back against waterfall planning; the Lean Startup extended that logic to the entire business. The methodology spread fast — first through startups, then through corporate innovation labs, then into business schools and government agencies. Ries followed it with The Startup Way (2017), which addressed how large organizations can apply lean principles, drawing on his work advising companies including GE.

The methodology has been genuinely influential, and the core insight — that assumptions about customers should be tested rather than assumed — has improved how many product teams think. But the criticism is real and worth taking seriously. In practice, the MVP concept has frequently been used to justify shipping incomplete, low-quality products to users who didn't ask to be test subjects. The emphasis on speed can crowd out craft, and the framework's language of experimentation can become cover for an inability to commit to a vision. Ries has acknowledged versions of this criticism and argued that the methodology is often misapplied, but the gap between the book's idealized version of validated learning and what "lean" actually looks like inside companies is large.

His ideas are most useful at the stage where they were developed: early-stage startups with genuine uncertainty about product-market fit. The translation to large enterprises is messier than The Startup Way acknowledges, and the frameworks don't map cleanly onto domains where iteration speed is limited by regulatory, safety, or physical constraints. These are not fatal objections. The Lean Startup remains one of the most practically useful business books written in the past two decades, and the questions it asks — what are we actually learning, and how do we know? — are ones every product team should be asking.