Why Experiences Fail at Scale
The metrics work until they don't. Experience-first systems decay when ownership becomes ambiguous.
You've seen the proof: experience-first improves velocity, reduces bugs, lifts retention. But watch a platform scale and the pattern flips. Suddenly experience-first feels expensive. Features ship, but customers don't renew. Teams move fast, but in different directions.
The problem isn't experience-first. It's that experience-first scales only when ambiguity is managed. And most platforms never make that management explicit.
Where the signal breaks
When your team is small, experience-first works because you are the system. You know what the platform is supposed to feel like. You know why decisions were made. You understand the tradeoffs. A new hire onboards and picks up the culture by osmosis. A customer request comes in and the team collectively understands whether it belongs in the product or not.
Scale that to 50 engineers, two time zones, and a dozen customer segments. Suddenly:
- One team builds a feature that optimizes for their own configuration but breaks another team's workflow.
- A product manager ships an experience that contradicts what the platform promised last quarter.
- A customer's demands cascade through the system because nobody's clear on who owns what.
- The UX that felt coherent at 10,000 users is incoherent at 100,000 because the underlying architecture never named its own rules.
You don't lose experience-first at scale. You lose clarity about what the experience is supposed to be, and who's responsible for maintaining it.
The renewal signal disappears
In your measurement post, you noted that retention and renewals lifted when teams aligned around experience-first. That's because customers could feel the coherence. The platform wasn't perfect, but it was predictable. They could run their business on it.
Watch what happens when scale introduces ambiguity:
- The product team sees a spike in "customization requests" (really: customers asking the platform to make sense).
- Support tickets shift from "how do I use this?" to "why does this work one way here and another way there?"
- Renewals decline not because features are missing, but because the platform feels like a collection of good ideas rather than a coherent system.
That's the cascade: ambiguity → incoherence → customer confusion → churn.
The framework that prevents it
The scaling problem isn't new, but it has a shape. You can design for it.
The insight is simple: experiences don't scale; frameworks for coherence scale. The question isn't "how do we give every team the freedom to optimize?" It's "how do we give every team the freedom to own their part while staying aligned to a coherent whole?"
That's what cascading experiences do. But to get there, you first need to name the problem your platform is solving — and then enshrine that at the design level, where it can't be overridden by good intentions.
The next post explores how to do that. It starts with a single move: designing backwards from the moment of value, rather than forwards from the feature.
Read: Moments, Experiences, Moments — Why Backwards Design Works