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

The System of Progress

When Coffee and Kale Compete Alan Klement
system-of-progress interdependencies cascade-effects progress-helix customer-evolution

Key Principle

The System of Progress (SoP) is a cyclical framework mapping the interdependencies between customers, their Jobs to Be Done, and producers across four phases: (1) customer imagines a better life-situation, (2) customer searches for and chooses a solution, (3) customer uses the solution, (4) customer realizes the new life-situation -- which feeds back into phase 1. The cycle is not a flat loop but an expanding helix: each completed revolution lifts the customer to higher aspirations, surfacing struggles they did not previously have.

"You do not help customers make progress by optimizing parts of the system of progress individually. You improve the system by optimizing how those parts work together." -- Alan Klement, Chapter 11

The top hemisphere (phases 1-2) belongs entirely to the customer; producers cannot dictate what a JTBD is. The bottom hemisphere (phases 3-4) is where customer and producer interact. Customer preferences are not stable truths -- they are artifacts of the current system configuration. When any interdependency shifts, preferences cascade and change with it.

Why This Matters

The unit of analysis for innovation is the full cycle, not any single phase. A product can be excellent and still fail if the surrounding system -- discovery, purchase, onboarding, life-integration -- is broken. Teams that optimize their own slice without coordinating across the cycle produce what Klement calls parts-optimization failure: "A mediocre product that customers know about, can buy, and can use will beat out a perfect product that customers don't know about, can't buy, or can't use." (Chapter 11)

Because the helix is perpetual, every solved problem is a lead generator for the next product. Treating the customer relationship as terminal after purchase means a competitor captures the next aspiration. And because progress is path-dependent, two customers with identical demographics but different progress histories need entirely different things -- which is the causal argument for why demographic segmentation fails.

Good Examples

  • Beachway Therapy Center: The rehab product was unchanged; the system failure was at the recognition stage. Copywriter Joanna Wiebe rewrote the headline to "If you think you need rehab, you do" and the CTA to "Does my insurance cover this?" Result: 26% more leads at $20,000/month each. Fixing the interaction, not the product, drove profit. (Chapter 8)

  • Bob Moesta / Home Builder: Empty nesters said they wanted a smaller dining room and bigger second bedroom. Delivering those stated preferences produced tepid sales. The real friction was emotional inability to part with the family-size dining table. Fix: expanded the dining room, shrunk the bedroom, placed a large old-looking table in the demo. Result: 23% increase in sales -- by doing the opposite of what customers asked. (Chapter 8)

  • BananaDesk: Founder Tim Zenderman mapped four sequential stages of hostel growth (Survive, Control:Reservations, Control:Finance, Scale), each a distinct JTBD. Booking-site promotions are a good hire at Survive; direct marketing is a good hire at Scale. "If you look at just the functional need of these two stages, they seem similar: 'I need to sell beds.' But in both cases, the context around that 'need' is quite different." (Chapter 10)

Counterpoints

  • Parts-optimization trap: Engineering perfects the product, marketing perfects the campaign, no one coordinates across the cycle. Volume of data is mistaken for completeness: "Companies create ever-larger reports that contain a great deal of irrelevant data about customers -- reports that no one ends up reading." (Chapter 11)

  • Anchoring to stated preferences: Steve Ballmer knew exactly what customers wanted in 2007 -- low cost, physical keyboard -- and dismissed the iPhone: "Five hundred dollars! Fully subsidized! That is the most expensive phone in the world! And it doesn't appeal to business customers because it doesn't have a keyboard." Microsoft's smartphone share went from 12% to under 1% by 2016. (Chapter 12)

  • Ignoring fragile interdependencies: The author's FDT product was tightly coupled with Adobe Flash. When Flash entered irreversible decline, FDT revenue was guaranteed to follow regardless of product quality. Similarly, Kodak's cascade: digital cameras replaced film, smartphones replaced digital cameras, digital sharing replaced prints, then video replaced image sharing -- each stage a distinct disruption with distinct losers. (Chapter 11)

Key Quotes

"We must abandon the idea that customers have a laundry list of 'needs.' Instead, we should see customers as having only one need: to make progress within the systems they belong to." -- Alan Klement, Chapter 8

"Customers know only what the system tells them. This is something the customer does not understand, but you must." -- Alan Klement, Chapter 8

"How can people tell you what they want if they haven't seen it before? If we ask them what they want, we'll end up doing Swan Lake every year!" -- Mario D'Amico, Cirque du Soleil, Chapter 12

"I've stopped buying hair-conditioner sachets... I can't do anything without my phone." -- Lakshmi Kumari, earning $100/month, Chapter 11

Rules of Thumb

  • The leverage point for innovation often sits outside your product boundary. If churn is caused by a skill gap the customer has, no amount of product improvement fixes it.
  • Customer input is symptoms, not diagnosis. Empathy with symptoms does not produce a cure -- you must study the system.
  • Design for ongoing betterment ("become a better X"), not finite outcomes. Finite outcomes have a built-in expiration date; identity-level progress is open-ended.
  • Ask "What comes before?" -- the upstream struggle that creates your demand is often a larger, more profitable opportunity than the visible problem.
  • Monitor fragile interdependencies: distinguish which couplings in your system are robust (removing a hair strand) versus fragile (removing an organ). When the fragile element declines, your product declines with it.
  • Think of your business as delivering a combination of products that work together to forward the system of progress, not standalone P&Ls.
  • Reading continued usage as satisfaction is dangerous. A customer using your product alongside three workarounds is not a happy customer -- they are a switching risk.

Related References