Reading drop-offs without blaming a single screen

A steep drop after a form step can mean the form is hard — or that customers finished the same task elsewhere. In cross-channel service work, abandonment in one app often coincides with completion in another, or with a phone call that never gets linked back.

Pair quantitative drop-off counts with a short sample of real cases. Pull ten recent sessions or tickets around the same step and note whether the customer reappeared in another channel within a day. That habit prevents teams from redesigning a screen that was never the real end of the journey.

Agree on a shared definition of completion before comparing channels. If mobile counts a booking as complete at payment authorization and the desk system counts it at ticket print, your charts will disagree forever.

When you brief stakeholders, present drop-offs as questions with evidence, not as verdicts. That tone keeps product, support, and marketing aligned long enough to decide what to measure next.

Back to field notes