The Customer-Experience Technology Filter
Adopt technology only when it improves the customer's experience
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 6
- Confidence
- 98%
This filter evaluates technology from the customer's point of view rather than treating novelty as sufficient justification. Start with a concrete friction or unmet need, then ask whether the proposed feature makes the experience faster, easier, more relevant, or more consistent with the brand. Timing matters: an idea can fail when device adoption or adjacent capabilities are immature and succeed later when enabling conditions change. Complementary features can also create value together that they lacked separately, as stored value and mobile ordering did for Starbucks. Companies should measure traffic, conversion, repeat use, and customer satisfaction rather than celebrating technical sophistication. The output is technology that customers naturally embrace because it fits their lives, while features that merely introduce new steps or showcase technical capability are rejected.
Origin
Dan Levitan and the Acquired hosts contrasted an early failed mobile-ordering investment with Starbucks' later success combining stored value, order-ahead, loyalty, and convenient interfaces.
Core principles
- 01Technology is a means rather than the product goal
- 02Customer friction matters more than novelty
- 03Adoption depends on timing and enabling conditions
- 04Features become stronger when combined into a coherent experience
- 05Technology should reinforce the brand relationship
How to run it
- 1
Name the customer job
Describe the outcome customers seek and the friction in the current journey without mentioning a specific technology.
Pro tip Observe actual behavior rather than relying only on stated preferences.
Watch out A technology-first problem statement biases the decision.
- 2
Map the experience
Identify where customers wait, repeat information, switch contexts, or abandon the journey.
Pro tip Include the human interactions customers value and should retain.
Watch out Efficiency gains can damage the experience if they remove meaningful contact.
- 3
Test enabling conditions
Check device adoption, user habits, complementary features, operational readiness, and economics.
Pro tip Distinguish a permanently weak idea from a good idea whose timing is premature.
Watch out Do not interpret an early failed test as proof that the need will never exist.
- 4
Design a coherent feature set
Combine capabilities when their joint value is materially greater than their standalone value.
Pro tip Look for reinforcing combinations such as payment, loyalty, and ordering.
Watch out Bundling unrelated features can make the journey harder.
- 5
Run a customer-centered pilot
Test the experience in a constrained setting and measure usage, time saved, repeat behavior, and satisfaction.
Pro tip Compare the complete journey with the previous experience.
Watch out Technical completion is not evidence of customer value.
- 6
Scale or reject
Invest when the feature measurably strengthens customer experience and business outcomes; otherwise revise, defer, or stop it.
Pro tip Revisit deferred ideas when enabling conditions materially change.
Watch out Do not scale a feature solely because competitors have it.
In the wild
An earlier order-ahead company tested with several Starbucks locations but failed when smartphones were less prevalent and the feature set was insufficient. Later, Starbucks combined stored value, loyalty, and order-ahead into an experience that let customers receive coffee faster without abandoning the brand's human interaction.
→ Mobile order and pay became a compelling, widely sought retail capability.
A grocery chain tests voice replenishment only for frequently repeated purchases. It retains confirmation for substitutions and measures whether customers complete orders faster than through the app.
→ The grocer scales voice ordering for repeat staples while rejecting it for complex discovery purchases.
Common mistakes
Buying feeds and speeds
Selling technical specifications without understanding the retailer or consumer journey fails to establish customer relevance.
Adding technology hoops
A feature that requires extra steps without improving the outcome makes the experience worse despite being innovative.
Ignoring timing
Weak device penetration or missing complementary capabilities can cause a sound concept to fail prematurely.
Is it for you?
Best for
It is best for retailers and consumer companies evaluating digital features, partnerships, and new interfaces.
Not ideal for
It is not ideal for foundational infrastructure decisions whose primary benefits are operational resilience or regulatory compliance.
From the transcript
“Everything has to be in service of creating a superior customer experience.”
“And just doing tech or just doing mobile ordering for the technology aspects isn't gonna work.”
“Where we've had no luck is where tech companies think that, well, you know, these retailers just don't get it.”
From the episode
The Starbucks IPO with Dan Levitan
Dan Levitan