Pivotconcept

hypothesis-testingcore-conceptiterationlearning
1 min read · Edit on Pyrite

Definition

A pivot is the decision to change one or more components of a business model hypothesis based on evidence from customer contact. In Blank's Customer Development framework, pivoting occurs when Customer Validation fails — when the evidence shows that the current business model will not work as hypothesized. Rather than pushing forward with a broken model, the startup returns to Customer Discovery with revised hypotheses.

Origins

The term "pivot" in its startup usage was popularized by Eric Ries in the Lean Startup methodology, but the concept originates in Blank's Customer Development process. The Customer Development loop between Discovery and Validation is explicitly designed to produce pivots: if Validation fails, you do not proceed to Creation — you return to Discovery with new hypotheses. Blank's framework made the pivot a planned, systematic part of the startup process rather than a crisis response.

Types of Pivots

Pivots can affect any component of the business model:

  • Customer segment pivot: Different customers than expected
  • Value proposition pivot: Different problem or solution than expected
  • Channel pivot: Different route to customers
  • Revenue model pivot: Different pricing or monetization
  • Technology pivot: Different underlying technology
  • Platform pivot: Change from application to platform or vice versa
  • The Pivot vs. Failure Distinction

    A key contribution of Customer Development is reframing failed hypotheses as learning rather than failure. In the traditional startup model, discovering that customers do not want your product is a crisis. In Customer Development, it is expected — most hypotheses are wrong. The pivot is the mechanism for acting on that learning without abandoning the venture entirely.

    Significance

    The pivot concept transformed startup culture by normalizing iteration and hypothesis revision. Before Customer Development, changing direction was seen as admitting failure. After Customer Development, it became a sign of learning discipline — evidence that the startup was testing hypotheses rather than executing assumptions.

    Sources: "The Four Steps to the Epiphany" (Blank, 2003), "The Lean Startup" (Ries, 2011)