Pivot

What Pivot means in practice

A pivot changes a foundational assumption while keeping what the evidence supports. Adjusting onboarding or pricing is iteration; changing who you serve, what problem you solve, or how you make money is a pivot. Conflating the two makes the decision harder to reason about than it needs to be.

The signals justifying one are usually visible well before founders act. Retention that will not improve across successive cohorts, sales cycles that lengthen rather than compress, and customers using the product for something other than its intended purpose all indicate the current assumption is wrong. That last signal often points directly at the pivot worth making.

The discipline is retaining rather than restarting. A good pivot keeps the validated assets — customer relationships, domain knowledge, technology, distribution — and changes only what the evidence contradicts. Discarding everything is starting over, and loses the advantage the effort bought.

Worked example

A pivot driven by observed usage.

• Original product: team chat tool for game studios. Retention poor after four months.
• Observation: several studios used only the file-versioning feature, daily.
• Pivot: rebuild around asset version control for creative teams.
• Retained: the customer relationships, the domain understanding, and most of the underlying infrastructure.

Takeaway: The pivot followed evidence already present in usage data, and kept everything that had been validated — which is what separates a pivot from a restart.

Common mistakes

• Pivoting on impatience rather than evidence, before cohorts have had time to show a pattern.
• Discarding validated assets and effectively starting a new company.
• Calling routine iteration a pivot, which obscures whether a real assumption changed.
• Ignoring the clearest signal available — customers using the product for something unintended.

Related tool: Re-score a changed idea.

Related terms

• Product-Market Fit — Product-market fit is the point where a product satisfies a real, urgent demand well enough that customers adopt it, keep using it, and tell others — so growth starts pulling rather than being pushed.
• Cohort Analysis — Cohort analysis groups customers by when they joined and tracks each group's behaviour over time, revealing retention and revenue patterns that aggregate metrics hide.
• Problem-Solution Fit — Problem-solution fit is the stage at which you have confirmed a real, urgent problem exists and that your proposed solution genuinely addresses it — the milestone before product-market fit.
• Idea Validation — Idea validation is the process of gathering evidence that a business idea solves a real, urgent problem people will pay for — before committing significant time or money to building it.