CX Methods
Friction compounds until the customer quietly leaves
Each snag looks minor in isolation. Together they break trust, and a customer who stops trusting you leaves without a word.
Journeys rarely fail at one catastrophic step. They fail by accumulation: a forced download, a duplicate account, a reset loop, a lockout, then support that can't recover it. The damage is emotional and cumulative. After the first breach of trust, every remaining step feels risky.
An account setup that goes wrong rarely goes wrong once. A forced app download leads to duplicate-account confusion, which leads to password reset loops, then a security-question lockout, and finally a support call that cannot untangle any of it. Audit each step alone and every one looks minor. But the customer does not experience steps; they experience an arc: frustration, then distrust, then abandonment. After the first failure, they approach every remaining step braced for the next one, and even neutral moments start reading as hostile. What began as a simple task becomes a verdict on whether the brand can execute at all.
Why it matters to the business
The tolerance window is narrow. PwC's 'Experience Is Everything' research found 32% of customers will walk away from a brand they love after a single bad experience, and 92% would abandon a company after two or three negative interactions. The exit is usually silent: ThinkJar research found only 1 in 26 unhappy customers complains. A compounding-friction journey produces no ticket spike and no angry email, just a customer who never returns, invisible in every dashboard except revenue.
Behavioral science explains why the arc matters so much: people judge an experience by its worst moment and its ending, not its average. In a McKinsey behavioral-science pilot, resequencing a journey to put hard parts early and finish strong lifted satisfaction 7 percentage points against a control group.
How to use it
- Map your onboarding and recovery journeys as emotional arcs, not checklists; mark where trust is won or lost.
- Find compound-friction zones where one failure triggers the next, especially authentication, account setup, and billing, and break the chain.
- Design recovery into every vulnerable transition: a failed password reset should open an easier path, not a harder one.
- Test cumulative load by running usability sessions across the whole journey, not isolated screens.
- Put hard steps early and engineer a strong finish; the ending writes the memory.
Where teams get it wrong
Teams QA each step in isolation, and each step passes. No one owns the accumulation. The download works, the reset email sends, the lockout policy is technically secure, support followed the script, and the customer is gone. Per-step metrics can all be green while the journey is failing.
Ask your team
- Which of our journeys has the longest chain of dependent steps, and what happens to a customer who fails at step two?
- Do we test whole journeys end to end with real customers, or only individual screens?
- How would we know a customer abandoned us quietly? What signal would actually fire?
Customers don't experience steps. They experience the accumulation.
Apply this
Reading about friction compounds until the customer quietly leaves is one thing. Seeing where it applies in your journey is the useful part.