Pivot or Persevere
A chapter summary from The Lean Startup by Eric Ries.
The pivot is the most-quoted concept from the book and the most often misused. Ries defines it precisely: a pivot is a structured course correction designed to test a new fundamental hypothesis about the product, strategy, or engine of growth — not a small tweak, not a rebrand, not a feature change. The pivot is the moment a team admits one big assumption was wrong and substitutes a new one.
Ries catalogs ten types of pivots. Zoom-in: a single feature becomes the whole product. Zoom-out: the whole product becomes one feature of a larger product. Customer segment: the product is right, the target customer was wrong. Customer need: the customer is right, the need we addressed was wrong. Platform pivot, business architecture pivot, value capture pivot, engine of growth pivot, channel pivot, technology pivot. Each is a different way of changing one fundamental variable while keeping the others stable.
The hard part is not identifying the right pivot; the hard part is being willing to pivot at all. Teams that have spent months on a hypothesis develop emotional investment in being right about it. The Lean Startup discipline is to make the pivot decision a regular scheduled question (every monthly or quarterly review, decide: pivot or persevere) so the decision is not deferred until the company is out of money.
The right pivot, taken at the right time, often turns a failing startup into a successful one. The wrong pivot, or the right pivot taken too late, is indistinguishable from a normal startup death.
A short summary — and that's the point. Read Stacks chapters are deliberately tight. The full The Lean Startup edition has the examples, the longer argument, and the moments worth re-reading. If this resonated, the Amazon link below buys the actual book and supports the author.
One chapter a week — curated, not algorithm-picked.
If this resonated, the free weekly Read Stacks email sends one curated 4-book stack with the chapter we'd open first. No spam, unsubscribe anytime.
From Read Stacks · Learn
If you just read a chapter summary…
You're using the navigation tool the way it was designed to be used. Two short essays on the meta-skill — what summaries actually preserve, and the six retention techniques that decide whether what you just read is still useful six months from now.
- Are book summaries actually useful, or am I just cheating?
Chapter summaries are a navigation tool, not a substitute. Used right, they help you read more books fully — by helping you avoid the wrong ones. Used wrong, they're a comfort blanket that lets you feel like you're reading without engaging with the material.
6 min read
- I read a lot of books but can't remember anything. What works?
Forgetting most of what you read is normal, not a personal failing — your brain wasn't designed to retain prose at the rate modern readers consume it. The practices that DO work share one thing: they force you to USE the material instead of just consuming it. Six specific techniques, each tested across decades.
7 min read