Product Pivot
A product pivot is a fundamental change to one part of a product's strategy, such as its target customer, the problem it solves, its business model or its growth channel, made because evidence shows the current approach is not working. Eric Ries, who popularized the term in The Lean Startup, describes it as a structured course correction designed to test a new fundamental hypothesis.
How a Product Pivot Works
In Ries's framing, the vision stays the same and the strategy for reaching it changes. A team runs experiments, tunes the product and watches whether its key metrics move toward the target. At regular intervals it makes a pivot-or-persevere decision: if the evidence shows steady progress, it keeps going; if repeated improvements are not moving the numbers, it changes a core part of the strategy.
A pivot keeps what has been learned and changes one major element. The Lean Startup names several types, including:
- Zoom-in pivot. One feature becomes the whole product.
- Zoom-out pivot. The product becomes one feature of a larger offering.
- Customer segment pivot. The product works, but for a different customer than planned.
- Customer need pivot. The customer is right, but a different problem matters more to them.
- Business architecture, value capture, engine of growth, channel, platform and technology pivots. Changes to how the product is sold, monetized, grown, distributed or built.
Each new direction is itself a hypothesis to test, not a final answer.
Why a Product Pivot Matters
The risk for most early products is not a dramatic failure but slow drift: modest results, endless tweaks and a strategy that never gets questioned until money or patience runs out. A deliberate pivot-or-persevere review forces the question while there is still time to act. It also separates a disciplined pivot, based on validation evidence, from simply chasing the latest idea.
A pivot has knock-on effects. Requirements, backlog items, roadmaps and any context given to AI coding agents were written for the old direction, and if they are not updated they keep pulling work back toward it. For a practical view of this problem, see keeping product context in sync after a pivot.
Product Pivot Example
A startup builds class-booking software for independent yoga studios. After six months, bookings through the tool stay flat, but usage data and interviews show that studio owners rely heavily on one secondary feature: automated reminders that chase members for unpaid class packs. Owners say it recovers money they used to lose. The team makes a zoom-in pivot: it rebuilds the product around payment recovery for small fitness businesses, keeps the reminder engine, drops most of the booking features, and sets new success metrics around recovered revenue. The vision of helping small studios run profitably does not change.
Product Pivot vs. Iteration
Iteration improves the product within the current strategy: better onboarding, a clearer pricing page, a faster workflow. A pivot changes one of the strategy's core assumptions, such as who the customer is or what problem is being solved. Many small iterations that fail to move the key metrics are often the signal that a pivot is needed. The product vision normally survives a pivot; the product strategy does not.