Menu

UX

The real reason users drop off is not what you think

Drop-off is usually treated as a screen problem. It rarely starts where it shows up.

Why users usually leave because of the friction, uncertainty and doubt that build before the point where analytics says they dropped off.

28 November 20254 min read

In short

Why users usually leave because of the friction, uncertainty and doubt that build before the point where analytics says they dropped off.

What the data shows, and what it doesn't

Something on that screen must be wrong. The button is in the wrong place, the form is too long, the messaging isn't clear enough. Sometimes that's true. Often it isn't.

What the shows is where users leave. It doesn't show where they started to lose . That usually happens earlier. It slowly: a slightly unclear step, a decision that comes too soon, a piece of information they expected to see but didn't, a moment where the process starts to feel heavier than it should. None of those things look dramatic on their own, but together they change how someone feels about continuing. By the time they drop off, the decision has often already been made.

This is why tend to be more useful here than . The funnel gives you the exit. The recording gives you the four screens before it, where somebody scrolled back twice, hovered over a link they did not click, and read the same paragraph again.

By the time users drop off, the decision has often already been made.

How this shows up in different journeys

In travel, users browse comfortably until the experience starts introducing too much uncertainty around pricing, options, or what happens next. They don't leave at the first moment of doubt. They carry it until they reach a point where commitment is required, and then they stop.

In banking, the issue is often effort. A journey asks for more than feels reasonable, too early, or in a way that feels shaped by internal rather than user need. Users keep going until the balance tips and it no longer feels worth it.

In larger , especially where multiple teams or are involved, drop-off can come from fragmentation. Users don't trust what they're seeing because the experience feels inconsistent, or because the flow seems to change as they move through it. The abandonment point is visible, but the real problem is that confidence has been chipped away long before that.

The common thread across all three is that the journey asked for commitment before it had earned it. What differs is the currency being asked for: money in one, effort in another, in the third. The of carrying doubt until a threshold is the same.

Why the problem step is often the wrong focus

You can improve the screen where people leave and still see very little movement, because the issue is upstream. The experience has already created too much doubt, too much , or too little . The final step is just where it becomes measurable.

On some journeys, changing the end of the flow did almost nothing, but improving and earlier had a noticeable impact later, not because the final screen improved, but because users arrived there in a better state. They understood what they were doing, trusted what was happening, and felt more certain about continuing.

Testing this is straightforward if you are willing to be wrong. Change something meaningful several steps upstream and watch the exit point, not the step you touched. If the moves without the final screen changing at all, you have found where the problem actually lives.

Key takeaway

Drop-off usually becomes visible at one step, but the real cause is often built much earlier in the journey.

What drop-off is really telling you

A lot of comes down to . Whether the experience feels predictable, credible, and worth continuing with. Users keep moving when they feel in control. They leave when that starts to slip.

That loss of can come from vague pricing, hard-to-find information, a flow that introduces too much at once, or language that sounds internal rather than human. None of that shows up neatly in a dashboard. But users feel it straight away. is rarely a screen problem. It's usually a journey problem. Sometimes a product problem. Quite often a problem.

There is a practical list worth working through, because most failures are ordinary. Whether the total cost is visible before somebody is asked to commit, whether it is clear what happens next, whether the decision can be reversed, and whether anyone is reachable if it goes wrong.

Exit rarely help with this, for the same reason the does not. Somebody who left because doubt accumulated over four screens will report that the price was too high, because that was the last thing they were looking at when they decided.

Written by Andy Scott

Strategic design, UX and digital transformation thinking from real projects.

LET'S WORK TOGETHER

Ready to improve your product?

UX, research and product leadership for teams tackling complex digital services.

Previous feedback

I had a fantastic experience working with Andy. One of his most impressive achievements during our time at NHS HEE was masterminding a deeply complex information architecture for a new platform that brought together a large number of legacy websites.

Will Parkhouse

Senior Content Designer