Build on Durable Customer Needs
Anchor strategy in needs that persist while platforms and products change
- Difficulty
- Moderate
- Time to result
- ~months to results
- Steps
- 6
- Confidence
- 94%
Define strategy around stable customer desires rather than the current product or technical architecture. First identify what customers will continue to want—for example, reaching destinations, saving money, or receiving reliable service. Then separate that need from the mechanism currently satisfying it, because operating systems, distribution channels, and vehicle technologies can all shift. Treat an emerging platform as both a threat and a new way to serve the same durable demand. Experiment early, accept some cannibalization of the legacy business, and preserve flexibility by working with multiple technology suppliers until standards and winners become clearer. This approach provides continuity without complacency: the customer promise remains stable while the assets, partnerships, and delivery model evolve around it.
Origin
Rischer connected lessons from Microsoft, Amazon, and Lyft, citing Windows, the internet, and autonomous vehicles as successive platform shifts.
Core principles
- 01Persistent customer needs outlast individual technologies
- 02Platforms change even when the underlying job remains stable
- 03Durable demand provides a safer base for experimentation
- 04Companies must cannibalize themselves before a new platform does
- 05Multiple suppliers reduce dependence during an uncertain transition
How to run it
- 1
Define the durable need
State what customers will continue to seek regardless of current technology. Frame it as an outcome rather than a product category.
Pro tip Use plain language such as save money, reach a destination, or connect with other people.
Watch out A familiar product feature is not necessarily a durable need.
- 2
Separate need from mechanism
Identify which parts of the existing business are merely today's way of delivering the outcome. Mark assets and assumptions vulnerable to a platform change.
Pro tip Ask whether the customer would still want the outcome if the current interface or hardware vanished.
Watch out Protecting the mechanism can obscure better ways to deliver the need.
- 3
Map the platform shift
Assess the new technology's reliability, economics, adoption barriers, regulation, and infrastructure. Distinguish long-term direction from short-term deployment speed.
Pro tip Model an uneven transition rather than assuming an overnight replacement.
Watch out A technology can be inevitable in direction but slow and geographically uneven in practice.
- 4
Cannibalize deliberately
Invest in the emerging delivery model before it fully threatens the legacy business. Use existing customers, data, brand, and operations as transition advantages.
Pro tip Measure success by retained customer relevance, not protection of legacy revenue.
Watch out Waiting for certainty can leave the company in a Kodak-style trap.
- 5
Preserve supplier flexibility
Use multiple partners where technology and standards remain unsettled. Avoid becoming dependent on one platform before performance and economics mature.
Pro tip Build integration and operating capabilities that transfer among suppliers.
Watch out Premature lock-in can leave the business tied to a losing standard or disrupted supplier.
- 6
Scale with adoption evidence
Expand as customers demonstrate trust and infrastructure supports reliable service. Continue operating a hybrid model while demand or economics require it.
Pro tip Let customer usage and unit economics set the pace rather than technology hype.
Watch out Forcing a complete transition too early can reduce capacity and service quality.
In the wild
Lyft expects autonomous vehicles to become important because customers consistently value safe, reliable transportation. Rather than define itself around human-driven cars, it is combining rider demand, marketplace data, partnerships with autonomous developers, and its Flexdrive fleet-management capability while expecting human drivers to remain necessary for peak demand and service needs.
→ The company can participate in autonomous transportation without abandoning the current marketplace prematurely.
Netflix served the durable need for convenient entertainment first through DVDs by mail, then streaming, and later original content. It did not treat the delivery format that created its initial success as permanent.
→ The company remained relevant across successive distribution shifts.
Common mistakes
Defending the legacy format
Protecting current revenue can prevent investment in the platform customers will eventually prefer. The Kodak example illustrates the cost of avoiding self-cannibalization.
Mistaking direction for speed
A new platform may be the future while still requiring years of hybrid operation. Plans should account for infrastructure, regulation, supply, and adoption constraints.
Locking in too early
Depending on one supplier or standard during rapid technical change creates avoidable strategic risk. Preserve options until the ecosystem matures.
Is it for you?
Best for
It is best for established companies facing disruptive technologies, changing interfaces, or emerging infrastructure standards.
Not ideal for
It is not ideal for situations where the underlying customer need itself is disappearing or cannot be demonstrated.
From the transcript
“build your business is on things that don't tend to change, not things that are that are sort of ephemeral.”
“they were relentless, fearless about cannibalizing their own business to sort of, you know, get to the next thing.”
“you want to have multiple suppliers of that technology so you're not beholden to anyone.”
From the episode
BONUS: The Future of Ride-Hailing with Lyft CEO David Risher