How to tell whether to pivot or keep going

The Reddit version is painfully concrete: founders asking whether to pivot after spending serious money with no revenue, whether no users means the product is wrong, or how many pivots it usually takes before product-market fit. The emotional shape is always the same: quitting feels premature, continuing feels expensive, and every data point can be explained both ways.

The hard part isn’t the abandoning. It’s that both persistence and pivoting are correct strategies, depending on something you can’t directly observe: whether your problems are puzzles or anomalies.

Borrow the vocabulary from science

Thomas Kuhn’s The Structure of Scientific Revolutions describes how science handles exactly this dilemma. Most of the time, scientists do “normal science”: they work inside a framework — a paradigm — and treat unexpected results as puzzles to be solved, not as evidence against the framework. This is rational. Most anomalies dissolve under harder work. A field that abandoned its framework at the first contrary result would never get anywhere.

But sometimes the framework itself is wrong, and Kuhn’s account of how that announces itself is the most practically useful idea in the book. A paradigm in crisis has a recognizable signature. Anomalies persist through repeated, competent attempts to resolve them. They strike the core rather than the periphery—Mercury’s orbit challenged Newtonian mechanics at a central point. And patches multiply. Ptolemaic astronomers kept the earth at the center by adding epicycles, circles on circles that saved individual observations while the framework’s elegance and predictive power drained away. The system still “worked” because every discrepancy received a fix. It was also becoming less capable of explaining why the fixes were necessary.

The translation to your situation

Swap “paradigm” for your strategy, architecture, research program, or business thesis, and Kuhn’s triage becomes operational. Examine the last few months of problems and fixes. Do the same problems return after competent attempts to resolve them? Do they attack the central thesis—whether users want the product, the architecture scales, or the channel converts—rather than an edge? Is the cost of each fix rising through exceptions, special cases, and one-off accommodations?

One yes means: keep working, this is normal science. Three yeses means you’re not in a rough patch; you’re in a crisis, and further patching is denial with a work ethic.

Why you’ll see it too late

Daniel Kahneman’s Thinking, Fast and Slow explains why this diagnosis arrives later than it should. WYSIATI: you build a coherent story from the evidence in front of you, and the story “we’re almost there” is always coherent, because every individual patch did fix something. Sunk costs and loss aversion: abandoning the approach converts paper losses into realized ones, and losses loom twice as large as gains. The inside view: your sense of progress is built from your effort, which is vivid, rather than from the reference class of similar efforts, which is damning.

The countermeasures are procedural. Run the outside view: of teams whose fix-lists looked like yours, how many were actually “almost there”? Run a premortem: it’s a year from now, you stayed the course, and it failed — write the history. If the history writes itself, believe it. And set tripwires in advance — “if churn hasn’t moved by Q3, we reconsider the thesis” — because the decision you can’t trust is the one you’ll make in the moment, with sunk costs whispering.

The crucial asymmetry: don’t quit into a vacuum

Here Kuhn issues a warning to eager pivoters: “the decision to reject one paradigm is always simultaneously the decision to accept another.” Scientists never abandon a framework merely because it has problems — working without a framework isn’t science, it’s chaos. They switch when a candidate exists that resolves the crisis-provoking anomalies and explains the old successes too.

That’s your bar for a pivot. Not “this is hard” — everything is hard — but: a specific alternative exists that explains both why your old approach won what it won, and why it keeps failing where it fails. A pivot without that is just quitting with extra steps; you’ll re-enter the pre-paradigm fog and burn months relearning what the old approach already knew.

The next move is a crisis review with a candidate alternative

Inventory the last quarter’s important problems, the attempted fixes, and whether each problem returned. Mark which failures strike the central thesis and whether patch cost is rising. If only one condition appears, persistence is still reasonable: normal work inside a useful framework includes resolving anomalies. If all three recur, stop treating each item as an isolated execution miss and name the strategic crisis.

Run the premortem and outside view before deciding. Then require a candidate alternative to explain both the current anomalies and the genuine successes of the old approach. Compare the two on specific observations, not enthusiasm for change. A pivot earns commitment when it produces a more coherent account and a testable path; persistence earns commitment when the old model still resolves anomalies without escalating special pleading.

Set the next tripwire before acting: the observation and date that will force another review. Kuhn’s deepest comfort is that crisis is not failure. Anomalies are raw material for a better thesis. The teams that die are often the ones that keep adding epicycles until the ability to choose has disappeared.

The decision is credible when the same evidence standard can justify staying or changing.