---
slug: pivot
type: concept
summary: "A structured change of strategy made on validated learning: one of ten named types, not a synonym for any change of direction."
created: 2026-05-26
updated: 2026-05-29
related:
  lean-startup-loop:

    relation: enabled-by
    note: "The build-measure-learn loop produces the validated learning that a pivot acts on; the loop's persevere-or-pivot step is where the decision is made."
  product-market-fit:
    relation: related
    note: "A pivot is a search move toward product-market fit when the current path is not converging on it."
  false-positive-trap:
    relation: related
    note: "A niche signal misread as broad demand is the classic trigger for a customer-segment pivot that should have come sooner."
  chasm:

    relation: related
    note: "Stalling at the early-adopter band rather than crossing into the mainstream is a signal that a customer-segment or customer-need pivot is due."
  knightian-uncertainty:
    relation: related
    note: "Pivoting is the rational response to conditions that cannot be priced in advance, because the only way to learn the answer is to run the experiment and read the result."
  minimum-viable-product:
    relation: related
    note: "The MVP is the instrument whose results tell a team whether to persevere on the current hypothesis or pivot to a new one."
---

# Pivot

*A structured change of strategy made in response to validated learning — one of ten named types, not a synonym for any change of direction.*

> **Concept**
>
> Vocabulary that names a phenomenon.

The word is everywhere, and it means almost nothing as people use it. A team that rewrites its landing page says it pivoted. A team that abandons its market, keeps its technology, and chases an entirely different customer also says it pivoted. When one word covers both, it carries no information, and a board hears "we're pivoting" without knowing whether the founders changed a headline or bet the company. Eric Ries gave the term a precise meaning, and the precision is the whole value: a pivot is a *structured* course correction, made on evidence, that changes one element of the strategy while keeping a foot on everything the team has already validated.

## What It Is

A pivot is a change to one component of a startup's strategy (its customer, its problem, its product, its technology, its revenue mechanism, or its growth engine) made because evidence has invalidated the current hypothesis and pointed at a better one. Ries, in *The Lean Startup* (2011), defined it as a structured course correction designed to test a new fundamental hypothesis about the product, strategy, and engine of growth. Two words in that definition do the work. *Structured*: a pivot is a deliberate move from one testable bet to another, not a panic or a drift. *Hypothesis*: a pivot changes what the team is trying to prove, which means it can be run as another turn of the [build-measure-learn loop](lean-startup-loop.md) rather than as a restart from zero.

The other half of the definition is what a pivot *keeps*. A team that has spent eighteen months learning a market doesn't throw that learning away when it changes its product; it changes the product precisely because of what it learned. The art is holding the validated parts of the strategy while replacing the invalidated one. This is the line between a pivot and a reset: a pivot is anchored to something proven, a reset starts over.

Ries named ten types, and the names matter because they tell a team (and its investors) exactly what is changing:

| Pivot type | What changes | What stays |
|---|---|---|
| **Zoom-in** | A single feature becomes the whole product | The validated value, narrowed |
| **Zoom-out** | The whole product becomes one feature of a larger product | The validated value, broadened |
| **Customer-segment** | The buyer changes; the product is roughly intact | The product, the problem it solves |
| **Customer-need** | The problem changes; the same customer has a bigger one | The customer relationship |
| **Platform** | An application becomes a platform, or the reverse | The underlying technology |
| **Business-architecture** | High-margin/low-volume flips to low-margin/high-volume, or the reverse | The product and market |
| **Value-capture** | The way the company monetizes changes | The product and its users |
| **Engine-of-growth** | The growth model changes (viral, paid, sticky) | The product and market |
| **Channel** | The path to the customer changes | The product and the customer |
| **Technology** | The same solution is delivered through a new technology | The customer, the problem, the value |

Naming the type converts a vague announcement into a specific claim. "We're doing a customer-segment pivot" tells everyone the product survives and the buyer changes. "We're doing a zoom-in" tells them the team found that one feature was carrying all the value. The bare word "pivot" hides which of these is happening, and the hiding is usually the problem.

## Why It Matters

Most startups change direction at least once, and many that build something durable arrive at it only after they do. Founder surveys put the share that pivot at some point well above half; the more useful finding is that a change of direction is the normal path to a working business, not a sign of failure. Slack, Instagram, Twitter, and Shopify all reached the products they're known for through a pivot from the thing they started building. Treating a pivot as an admission of defeat gets the causality backwards. The defeat is refusing to pivot when the evidence says the current path is dead.

The decision is hard because it sits on top of [Knightian uncertainty](knightian-uncertainty.md): a founder can't calculate the odds that the next bet pays off, because the only way to learn them is to run the experiment. So the question is never "will the pivot work." It's "has the current hypothesis been falsified clearly enough that continuing to test it is the worse bet." That's a judgment about evidence, and a precise vocabulary for the move makes the judgment legible to the people who have to back it.

The three audiences read a pivot from different seats. A founder reads it as a survival decision under a clock set by the [runway](runway.md): every month spent persevering on a falsified hypothesis is a month not spent testing the next one. An investor reads the *type* as a signal about how much of the original thesis survives: a value-capture pivot preserves most of the diligence, a customer-segment pivot resets the market analysis, and a technology pivot can invalidate the reason they invested. An early employee reads a pivot as a re-pricing of their bet, because the company they joined and the company after the pivot can be materially different wagers on materially different markets.

## How to Recognize It

The skill is distinguishing a warranted pivot from two failure modes that flank it: pivoting on noise, and refusing to pivot on a clear signal. A change of direction earns the name "pivot" when it meets three tests.

- **It follows invalidated learning, not a bad week.** The trigger is evidence that the current hypothesis is false: retention that decays to zero, a sales cycle that never closes, a market that turns out too small, gathered across enough cycles to rule out variance. A single lost deal is noise; a quarter of flat retention across every cohort is a signal.
- **It changes one named element and holds the rest.** A team that can say "we're keeping the technology and changing the customer" is pivoting. A team changing the customer, the product, the model, and the technology at once isn't pivoting; it's starting a new company under the old name, and it should be honest about that.
- **It produces a new testable hypothesis.** The point of a pivot is to get back into the loop with a sharper bet. If the change doesn't yield a clear "if this is true, we'll see X" statement, it's a flail, not a pivot.

> **⚠️ Warning**
>
> The most expensive mistake is not the wrong pivot. It's the pivot that comes too late. Founders systematically over-persevere, because abandoning a hypothesis feels like abandoning the dream, and because sunk cost makes the last eighteen months argue for the next eighteen. Set the persevere-or-pivot decision on a calendar, tie it to a metric defined *before* the data arrives, and make the call against that metric rather than against the mood in the room.

The opposite trap is the serial pivot: a team that changes direction every time the data gets uncomfortable, never staying with a hypothesis long enough to test it properly. A pivot is a structured move between hypotheses; thrashing between half-tested bets is the absence of structure wearing the word as a costume.

## How It Plays Out

Instagram is the cleanest public example of a zoom-in. The founders started with Burbn, a location check-in app with a crowded feature set: check-ins, plans, points, and photo sharing among them. Usage data showed people ignored most of it and came back for one thing: posting and filtering photos. Kevin Systrom and Mike Krieger stripped the app down to that single feature, relaunched as Instagram in 2010, and crossed a million users in under three months. The pivot kept what the data had validated and discarded everything it hadn't. They didn't change customer or technology; they narrowed the product to the one feature carrying the value.

Slack is the customer-need-meets-zoom-out story. Tiny Speck set out to build a game, Glitch, and built an internal chat tool to coordinate the work. The game failed; the chat tool was the thing the team itself couldn't stop using. The company kept almost nothing of the original product and almost all of the underlying technology and team, then pointed it at a problem every company has rather than the narrow audience for one game. Naming the move precisely, recognizing that the value lived in the communication layer rather than the game, was what let the founders raise on it instead of winding down.

The quiet inverse plays out far more often and never makes a case study: a team that should pivot and won't. Retention is decaying, the design partners who loved the early product aren't representative of anyone else, and the honest read is that the team has early-adopter enthusiasm rather than [product-market fit](product-market-fit.md), the shape of the [False Positive Trap](false-positive-trap.md). A customer-segment pivot is available and obvious in hindsight. But the founders have a seed round raised on the original story, a sales team hired to scale it, and a deep aversion to telling investors the thesis was wrong. They persevere until the runway runs out. The pivot they needed was named, available, and refused.

## Consequences

Holding a precise definition changes what a team does with the word, and what its backers hear when they use it.

**Benefits.** A named pivot is a legible decision. The founder can defend it as "the evidence falsified hypothesis A; hypothesis B is the smallest change that fits what we learned," which is a far stronger position than "things weren't working, so we're trying something new." Naming the type tells investors exactly how much of their original bet survives, which is the difference between a follow-on conversation and a markdown. And the discipline of naming forces the team to identify what it's *keeping*, the validated learning the pivot is anchored to, which is the part that turns a change of direction into a faster second bet rather than a slower restart.

**Liabilities.** The vocabulary can launder a failure as a strategy: a team with no idea what to do next can call its confusion a pivot and buy itself cover for another quarter. Precision is the guard against this: a real pivot names the invalidated hypothesis and the new one, and a team that can't name either isn't pivoting. The encouraging statistics also flatter the move. The often-cited figures that most pivoting startups go on to find a viable model are survivorship-prone, because the companies that pivoted and then died don't answer surveys, and "viable" is defined generously. A pivot improves the odds relative to persevering on a dead hypothesis; it doesn't make the next bet safe. And every pivot resets the clock with the team and with investors: credibility, morale, and trust are spent each time, which is exactly why the move should be reserved for a falsified hypothesis and given a precise name when it's made.

## Sources

- Eric Ries, *[The Lean Startup](https://openlibrary.org/works/OL16086010W)* (2011) — defines the pivot as a structured course correction and sets out the ten-type taxonomy used here.
- Steve Blank, *[The Four Steps to the Epiphany](https://openlibrary.org/works/OL8844576W)* (2005) — the customer-development foundation underneath the loop that produces the validated learning a pivot acts on, and the origin of the "search, then execute" framing.
- Marc Andreessen, ["The Pmarca Guide to Startups, part 4: The only thing that matters"](https://pmarchive.com/guide_to_startups_part4.html) (2007) — the product-market-fit framing that a search-stage pivot aims to reach.
- The Instagram-from-Burbn and Slack-from-Glitch pivots are documented in contemporaneous reporting and in the founders' own public accounts of how each product reached its eventual form.

---

- [Next: Scrappy Distribution for Bootstrappers](scrappy-distribution-bootstrappers.md)
- [Previous: The Cold Start Problem](cold-start-problem.md)