Your completion rate tells you what happened. It doesn’t tell you why.

A useful signal can still lead to the wrong conclusion.

A completion rate can tell you that 70% of people finished a journey and 30% did not. It can show a change over time, a difference between journeys or a point that deserves investigation.

What it cannot tell you on its own is why the remaining people did not complete.

That distinction sounds obvious. In practice, organisations often move from a behavioural signal directly to a product explanation: the form is too long, the interface is confusing, the new journey is worse, people need more guidance.

Any of those explanations might be true. The completion rate has not proved them.

The cause may sit somewhere else.

Someone may leave because they do not have the information being requested. They may be using the product in a difficult physical environment. A mandatory step may not fit their circumstances. Connectivity may fail. An accessibility barrier may prevent progress. They may need reassurance before continuing. Or the problem may originate in a process or communication that happened before they reached the interface.

If the organisation assumes the interface is the cause, it may redesign the interface while leaving the real barrier untouched.

Separate the symptom from the diagnosis.

A stronger starting point is to describe what the evidence shows without adding an explanation.

Observation: completion fell after the journey changed.

Interpretation: the new interface is harder to use.

The first may be supported by the data. The second is a hypothesis that needs evidence.

Keeping those two things separate creates room for other explanations and makes it easier to decide what should be investigated next.

Ask what would change the decision.

The answer is not always “do more research.” The organisation may already have useful evidence in support contacts, customer feedback, previous studies, accessibility findings, operational data or conversations with frontline teams.

The useful question is: what do we need to understand well enough to decide what to do next?

If knowing the cause would materially change the intervention, it is worth understanding. If it would not change the decision, further investigation may add little value.

Measure what happened. Investigate what it means.

Completion, drop-off, errors and support demand are valuable because they help reveal where attention may be needed.

They become more useful when they are treated as the beginning of a question rather than the end of one.

A symptom is not a diagnosis. And a metric is not an explanation.