Five principles.
Every diagnosis.
These are the first principles of experience design behind every ExSient engagement — the same ones my assistant reasons with when you describe what's off. Every problem I diagnose is explained through one of them, because experience problems repeat in patterns long before they repeat in symptoms.
Friction reveals intent mismatch.
Products encode assumptions — about what the user wants next, what they already know, and what order they think in. Users arrive with an intent shaped by their own situation. When the two align, the experience feels invisible. When they diverge, the user hesitates, backtracks, or leaves — and the analytics record it as drop-off. Friction isn't noise to be sanded off; it's the most honest signal an experience produces, because it marks the exact point where what you built and what the customer came to do stop being the same thing.
The pattern in the wild
A signup form asks for company size, industry, and use case before showing the product. The team's intent is qualification; the visitor's intent is evaluation. The mismatch shows up as abandonment no amount of form polish fixes — the friction is in the assumption, not the fields.
Read further in the library
Every metric hides a moment.
A metric is a compression: thousands of individual experiences reduced to one figure. The compression is useful for tracking direction, but it destroys the very information needed to act — who struggled, where, and why. Organizations manage what they can see, and dashboards make numbers visible while leaving moments invisible. Over time, teams optimize the number instead of the moment — which is how a score can improve while the experience quietly worsens.
The pattern in the wild
An NPS drop of four points triggers weeks of methodology debate. Reading two hundred verbatim comments takes an afternoon and reveals the actual moment: a new authentication step locking out long-tenured customers on shared devices. The metric started the conversation; only the moment could finish it.
Read further in the library
Journeys break at handoffs, not steps.
Each step of a journey usually has an owner who measures and improves it. The transitions between steps usually have no owner at all — and that is where context is dropped, promises are lost, and customers start over. Organizations are structured vertically while journeys run horizontally across them; every boundary between two owners is a place where the customer's context must be carried across by someone whose incentives stop at the boundary.
The pattern in the wild
Sales closes the deal with rich notes about the customer's constraints and goals. Onboarding starts with a blank template and asks the customer to explain their business again. Each team's dashboard is green; the customer experiences one journey with a crack down the middle.
Read further in the library
People act on mental models, not interfaces.
Every person arrives carrying a working theory of how things like this behave — assembled from other products, past experiences, and metaphors. They read your interface through that theory, and when the theory and the system disagree, the person follows the theory. Interfaces communicate a fraction of a system's actual behavior; the rest is filled in by belief. Teams who live inside the system forget this, and design for how it works instead of how it is believed to work.
The pattern in the wild
A banking app processes transfers instantly but shows a 'pending' state for compliance review. Customers believe pending means failed — everywhere else it does — so they send the transfer again. The duplicate-payment tickets are a mental-model collision, not a UI bug.
Read further in the library
Trust decays silently.
Customers rarely leave over one incident; they leave after a long sequence of small unmet expectations, each too minor to complain about. Every small letdown deducts from an account the customer never shows you. Nothing in the dashboard moves, because the customer is still transacting while they shop for alternatives. By the time the decay is measurable, it has been compounding for months. Silence is not satisfaction — it is often the sound of someone quietly recalibrating what they expect from you.
The pattern in the wild
A SaaS customer stops attending QBRs, stops filing feature requests, and logs in only to export data. Usage looks stable; engagement has gone quiet. The renewal conversation is a formality — the decision was made invisibly, one small disappointment at a time.
Read further in the library
Wondering which principle your problem lives under?
Describe what's off and I'll map it with you. Free, and you keep the map.
Free Experience Snapshot