Library
When Coffee and Kale Compete · 6 of 11
When Coffee and Kale Compete
Entrepreneurship CRITICAL

The Forces of Progress

forces-of-progress push-pull demand-generation demand-reduction anxiety inertia

Key Principle

Four emotional forces govern whether a customer acts or stays put. Two generate demand: push (dissatisfaction with the status quo) and pull (attraction toward a better life and a specific solution). Two reduce demand: anxiety (uncertainty about choosing or using the new product) and inertia (accumulated habits and investments that resist change). The customer experiences all four simultaneously; the net effect determines action or inaction.

Push and pull are interdependent -- neither alone produces demand. Push without pull leaves the customer dissatisfied but directionless. Pull without push has no urgency behind it: "There is no demand -- and therefore no JTBD -- unless push and pull work together." (Chapter 7)

Both anxiety and inertia subdivide into choice (blocks adoption) and use (blocks retention). Anxiety-in-choice is "will this work for me?" while anxiety-in-use is "will the next use satisfy me?" Inertia-in-choice is switching cost; inertia-in-use is habit regression pulling the customer back to old routines.

Why This Matters

Most innovators focus exclusively on demand generation -- building features that push and pull -- while treating demand-reduction forces as background noise. This creates a systematic blind spot: products that should win on paper but fail because anxiety or inertia were never addressed. Whether a customer stays put due to anxiety or buys a rival product, the revenue impact is identical.

The four-force model also explains why multiple competing products coexist for the same job. Different push contexts steer customers toward different solutions. An entrepreneur with a vague problem waits for Mark Cuban at a conference; an entrepreneur with an urgent, specific problem pays a premium for a direct call on Clarity. Same job, different push context, different product choice. Without the forces framework, teams misread this as irrational behavior rather than predictable variation.

Good Examples

  • Tesla vs. Tata Nano: Tata invested $400M in the Nano, a stripped-down car for Indian families. Massive push existed, but removing features (no stereo, no A/C, safety problems) destroyed pull. Only 18,531 annual sales by 2015. Tesla inverted this -- built pull first at the premium end, then moved downmarket. Result: 325,000 preorders in week one for the Model 3, a car nobody had driven. "If your product doesn't help customers make progress, price doesn't matter." (Chapter 7)

  • YourGrocer's habit problem: Customers churned not because supermarkets were better, but because the old habit of not planning meals persisted after adoption. Morgan needed to help customers build new planning habits -- inertia-in-use, not inertia-in-choice. Automated reorder emails ("reorder an entire box with one click") replaced the supermarket-visit habit loop. (Chapter 6)

  • Microsoft Excel: Solved inertia-in-choice by importing and exporting Lotus 1-2-3 files -- pure switching-cost elimination at the decision point. (Chapter 7)

Counterpoints

  • Godrej chotuKool: Guided by disruptive innovation theory, Godrej built a low-cost refrigerator for low-income Indians before talking to customers. Sold 15,000 units in a test market of ~114.2 million people. By 2016, completely repositioned as a luxury portable cooler -- total reversal of target customer, use case, and price. Solution-first thinking prescribed the product category before the forces were investigated. (Chapter 7)

  • Treating all anxiety as one thing: Clarity's founder discovered customers knew calls delivered progress but didn't know how to prep for the next one -- anxiety-in-use, not anxiety-in-choice. Optimizing onboarding alone misses the retention-blocking force entirely. (Chapter 7)

  • Investigating forces in the wrong order: Teams start by asking "why aren't people buying our product?" (anxiety/inertia) before confirming "do people want progress here at all?" (push/pull). This inverts cause and effect -- debugging conversion before validating demand. (Chapter 6)

Key Quotes

"The forces of progress are the emotional forces that generate and shape customers' demand for a product." -- Alan Klement, Chapter 6

"There is no demand -- and therefore no JTBD -- unless push and pull work together." -- Alan Klement, Chapter 7

"I ferociously attack inertia forces -- like habit -- as I would any competing product." -- Alan Klement, Chapter 7

"Forces that reduce or block demand should be investigated and managed with the same enthusiasm as demand generation." -- Alan Klement, Chapter 7

Rules of Thumb

  • Always investigate push and pull (product-independent forces) before anxiety and inertia (product-specific forces). If you reverse the order, you cannot distinguish "no demand exists" from "demand exists but our product blocks it."
  • Treat anxiety and inertia as competitors, not friction. Design against them with the same rigor you use against rival products.
  • When multiple solutions coexist for the same job, map the variation in push contexts rather than assuming customers are irrational.
  • Distinguish choice-stage forces from use-stage forces. Solving onboarding anxiety does not solve retention anxiety; eliminating switching costs does not eliminate habit regression.
  • Innovation design is organ transplant: the customer wants the product, but one small blocking force can trigger rejection. Demand-generation and demand-reduction require separate, parallel strategies.

Related References