There’s a version of building something that looks very productive. You plan extensively. You design carefully. You build thoroughly. You launch — and then discover, usually too late, that you were solving a problem slightly differently to the one anyone actually had.
I’ve watched this happen. I’ve probably participated in it more than once. And that’s precisely why The Lean Startup hit so hard when I first read it. Eric Ries isn’t just writing about startups. He’s writing about the epistemology of building things — how you know if what you’re doing is working, before you’ve spent everything finding out.
This is the book that’s influenced me most. Here’s why.
Assumptions Are Everywhere. Most of Them Are Wrong.
Every idea — every product, every strategy, every initiative — is built on a stack of assumptions. We assume customers have this problem. We assume they’ll pay this price. We assume this feature is what they actually need. Ries calls these “leaps of faith,” and his central argument is that the job of a startup (or an intrapreneur, or frankly anyone building something new) is to convert those assumptions into knowledge as fast and cheaply as possible.
The word that matters there is cheaply. Because the traditional approach — build the whole thing, then find out — is the most expensive way to learn. It’s like writing an entire exam paper before checking whether you understood the question.
The MVP Wasn’t What I Expected
When I first encountered the Minimum Viable Product concept, I thought it meant “build a rough version.” It doesn’t. An MVP is the smallest thing you can build that generates validated learning. It doesn’t have to be a product at all.
The Dropbox story is a good illustration. Before building anything, Drew Houston made a three-minute video showing how the product would work. The waiting list went from 5,000 to 75,000 overnight. That was an MVP — not a line of code written, one critical assumption tested. Zappos did something similar: rather than building inventory and logistics infrastructure, Nick Swinmurn photographed shoes at local stores and listed them online. When someone bought a pair, he went to the store, bought them, and shipped them. Scrappy, slightly mad, and completely effective at answering the real question: will people buy shoes online?
The elegance of this is that both founders learned something real before committing real resources. The experiment was designed to answer a specific question, not to build a complete product.
Build-Measure-Learn Is a Loop, Not a Sequence
The framework at the heart of the book — Build, Measure, Learn — sounds linear but behaves as a cycle. You build the smallest thing that tests your most critical assumption. You measure what actually happens. You learn whether your assumption was right. Then you go around again, either improving the same direction or changing it entirely.
The speed of that loop is what separates fast-learning organisations from slow ones. Ries is almost obsessive about cycle time — not because speed is inherently virtuous, but because each loop through the cycle converts an assumption into knowledge. The faster you learn, the fewer expensive mistakes you make on the basis of things you only thought you knew.
There’s a concept in the book called innovation accounting — essentially, replacing vanity metrics (total sign-ups, page views, gross revenue) with actionable metrics that tell you whether the business is actually getting healthier. Vanity metrics feel good and prove nothing. Innovation accounting is uncomfortable and genuinely useful. The distinction matters more than most teams acknowledge.
Pivot or Persevere — The Hardest Decision in Building
One of the most practically valuable parts of the book is the framework around pivoting. A pivot isn’t failure — it’s a structured course correction based on what you’ve learned. Ries identifies several types: a customer segment pivot (same product, different customer), a platform pivot (feature becomes platform), a zoom-out pivot (what was the whole product becomes one feature of something bigger).
The hard part isn’t understanding the types. It’s having the honesty to recognise when the data is telling you to change direction rather than try harder in the same direction. This is where founder psychology becomes a real obstacle. Ries is thoughtful about this — the book doesn’t pretend pivoting is easy. But it makes a compelling case that the ability to pivot on evidence, rather than persist on hope, is one of the clearest separators between ventures that compound their learning and ones that run out of runway before they figure out what’s actually true.
It’s Not Just for Startups
The original is right that this book applies far beyond founding a company. I’ve seen Lean Startup thinking applied to product teams inside large enterprises, to new capability launches inside established businesses, and to personal projects where the “customer” is really just your future self.
The principle underneath all of it is the same: wherever you are building or changing something under conditions of uncertainty, you have assumptions that need testing. The question is whether you test them cheaply and early, or expensively and late.
Every initiative has a Build-Measure-Learn loop inside it, whether it’s labelled that way or not. The only choice is whether you run the loop deliberately.
When you last built or launched something — at what point did you first find out if the core assumption was right? And what would it have cost to find out earlier?
Let’s keep learning — together.
harish.balasubramanian 
Share your thoughts