Eric Ries AMA: 7 things founders miss from Lean Startup

Eric Ries' AMA on The Lean Startup and Incorruptible — 7 insights founders misapply daily. Real answers, no fluff. Built for operators who ship.

Black and wooden letter board with humorous text against a pink wall.

Most founders think they're running lean. They're not. They've borrowed the vocabulary — MVP, pivot, validated learning — and left the discipline behind. Eric Ries' Reddit AMA on The Lean Startup and his new book Incorruptible surfaced exactly where that gap lives. Here's what operators actually need to pull from it.

Table of Contents

What Ries Actually Said in the AMA

The AMA ran on r/IAmA and pulled thousands of upvotes — rare for a business author thread. The signal-to-noise ratio was higher than most founder podcasts because the questions came from operators with live problems, not journalists fishing for soundbites.

Three themes dominated: (1) how Lean Startup principles hold up in an AI-saturated market, (2) what Incorruptible is actually about beyond the title, and (3) whether the MVP framework is broken now that shipping costs have collapsed.

Ries' consistent answer: the framework isn't broken, but the execution almost always is. Teams treat lean as a speed hack when it's a learning discipline. That distinction matters more now, not less — because cheap shipping means teams can waste money faster than ever on the wrong experiments.

This connects to a broader pattern worth tracking: as AI tooling lowers the cost of building, the real constraint shifts to institutional decision-making — exactly what Incorruptible targets.

The MVP Mistake 80% of Teams Make

The minimum viable product is not a product. It's an experiment with a specific question attached.

Ries has said this for 15 years. Teams still ignore it. The mistake: building a stripped-down version of your full vision and calling it an MVP. That's a beta. An MVP asks: "What is the riskiest assumption in our business model, and what is the cheapest way to test it?"

Dropbox's MVP was a demo video — no product, no code, just a 3-minute explainer. It generated 75,000 signups overnight. The question it answered: "Do people want this?" Cost: near zero. If Ries' framework had been applied literally (build a working product first), Dropbox would have spent 18 months building something the market might have rejected.

The 2025 version of this mistake is AI wrappers. Teams spend 3 months building a GPT-4 interface, launch to silence, and call it a pivot. The riskiest assumption was never "can we build this" — it was "will anyone pay for this specific workflow." A Typeform survey and 10 sales calls would have answered that in a week.

Before you spec your next feature, write the assumption it tests at the top of the doc. If you can't name the assumption, you're not building an MVP — you're building inventory.

Pivot Vs. Persevere — the Decision Most Founders Botch

A pivot is a structured course correction, not a rebrand triggered by a bad quarter.

Ries defines it precisely: change the strategy, hold the vision. Instagram pivoted from Burbn (a check-in app) to photo sharing — same vision of social connection, different vehicle. What most founders call a pivot is actually a vision change driven by panic, which is just starting over with less runway.

The structured pivot review Ries recommends: schedule it quarterly, bring your cohort data, and answer three questions before the meeting ends — (1) What did we learn this quarter? (2) What assumption did that invalidate? (3) What's the minimum change to our strategy that addresses it?

Skipping this structure is why VC relationships deteriorate after Series A — investors can't distinguish disciplined pivots from founder panic if you haven't documented the learning that drove the change.

Vanity Metrics are Still Eating Your Growth in 2025

Total registered users is not a business metric. Neither is monthly website traffic, LinkedIn impressions, or app downloads.

Ries coined "vanity metrics" in 2011. In 2025, the problem is worse because dashboards are prettier and the vanity numbers are easier to generate with AI content and paid distribution. A SaaS team can hit 10,000 signups in a month with a viral LinkedIn post and have zero activated users. The dashboard looks great. The business is dying.

Actionable metrics have three properties: they're comparative (this cohort vs. last), they're accessible (your team can act on them this week), and they're auditable (you can trace them to individual user behavior). Activation rate, revenue per cohort, and churn by acquisition channel meet all three. Total signups meet none.

For Indian SaaS teams specifically: CAC from paid vs. organic, activation rate within 7 days, and MRR by cohort month are the three numbers that predict whether you have a business. Everything else is noise. Tools like doableclaw.com surface exactly which metrics your funnel is hiding — it scans your site and shows where drop-off is happening by stage, not just total volume.

What Incorruptible Adds That Lean Startup Didn't Cover

Lean Startup solved the early-stage problem: how do you build something people want without burning all your capital. Incorruptible tackles what happens after product-market fit — when the organization starts optimizing for its own survival instead of its mission.

Ries' argument: every institution eventually develops immune responses to change. The metrics that drove growth become the metrics that protect incumbents. Teams start gaming KPIs instead of serving customers. This isn't a culture problem — it's a structural one. The incentives corrupt the mission.

The practical implication for founders: the same discipline that keeps early-stage teams honest (falsifiable hypotheses, short feedback loops, customer evidence over internal opinion) has to be institutionalized before you scale, not after. Once you have 50+ people, the organizational immune system is already forming. By 200 people, it's calcified.

This is also why the build-fast-and-figure-it-out ethos breaks down at scale. Speed without accountability structures produces exactly the institutional corruption Ries is diagnosing. The companies that stay sharp at 500 employees are the ones that kept the learning loop mandatory, not optional.

How to Run a Real Build-Measure-Learn Loop

The loop runs in one direction: Learn → Build → Measure → Learn. Most teams run it backwards.

Here's what backwards looks like: build a feature, ship it, look at the data, tell a story about what it means. That's not learning — that's rationalization. Real learning starts with a written hypothesis ("We believe that adding a progress bar to onboarding will increase 7-day activation by 15% because users currently don't know what step they're on"), defines success criteria before launch, and kills the feature if the data doesn't confirm the hypothesis.

The "Measure" phase is where most teams cheat. They look at aggregate data instead of cohort data. They measure the wrong moment (total signups instead of activated users). They measure too early (checking results after 3 days when the behavior takes 14 days to manifest).

Three rules for a clean loop: (1) Write the hypothesis before any code is written. (2) Define the metric and the threshold before launch. (3) Set a review date and honor it — no extending the experiment because the results are inconvenient.

If you're running multiple experiments simultaneously without a structured log, you're not running experiments — you're shipping features and hoping. A structured audit of your funnel often reveals that 60-70% of recent "experiments" had no hypothesis attached and no success criteria defined.

Conclusion

The Lean Startup framework isn't broken — your implementation of it probably is. Write the hypothesis before you build. Measure cohort behavior, not vanity aggregates. And read Incorruptible before you hit 50 people, not after the culture has already calcified. Want to find where your funnel is leaking right now? Run a free audit at doableclaw.com — takes 2 minutes, no signup required.


5 Questions Founders Actually Ask

Is Lean Startup still relevant when AI can ship an MVP in a day?
More relevant, not less. When shipping costs collapse, the bottleneck shifts entirely to learning quality. You can now waste 10x more money, faster, on the wrong experiments. The discipline of writing hypotheses before building matters more when building is cheap.
What's the minimum team size where Incorruptible's warnings apply?
Ries points to the 30-50 person mark as where institutional immune responses start forming. Before that, the founder's direct presence keeps the learning loop honest. After 50, you need structural mechanisms — not culture decks.
How do you know when to pivot vs. when to give the strategy more time?
The answer is in your cohort data, not your gut. If early cohorts are improving month-over-month, give it time. If cohort behavior is flat or declining despite product changes, the strategy isn't working. Set a specific metric threshold before the review — don't decide in the room.
What's the biggest misapplication of Lean Startup Ries called out in the AMA?
Using "MVP" as an excuse to ship low-quality work. An MVP is low-fidelity on purpose — to test a specific assumption cheaply. It's not permission to ship a broken product and call it lean. The fidelity should match the question, not your sprint capacity.
Does Lean Startup apply to non-tech businesses?
Yes. The framework is about uncertainty, not software. Any business operating under high uncertainty about what customers want benefits from short feedback loops and falsifiable hypotheses. A ₹50L restaurant concept, a D2C skincare brand, a B2B services firm — all of them can run Build-Measure-Learn loops before committing capital.

Find the exact growth leak in your business — in 2 minutes.

Paste your URL. Our AI agent crawls your site, diagnoses what's broken, and ships a step-by-step fix plan. Free, no signup.

Run free audit