A common trust building problem
Users quit complex flows midway
The short answer: show where they are and what's next. Here is how to recognise this problem in your funnel, why it happens, and how the best consumer apps design it away.
How to recognise it
- Multi-step completion far below simple-task completion
- Drop-offs at steps that introduce surprise asks
- No progress indicator or saved state anywhere
Why do users abandon multi-step flows?
In a long flow, users are continuously answering three questions: where am I, how much is left, and is anything ahead going to surprise me? A flow that answers none of them runs on faith, and faith runs out midway.
The surprises hurt most: a document demanded at step five, a card required where none was mentioned. One ambush teaches users to expect ambushes.
Abandonment mid-flow usually is not fatigue. It is uncertainty compounding until leaving feels safer than continuing.
How do you carry users through complex flows? Orientation at every step
Orient constantly: a progress marker that tells the truth, step names that say what each one wants, an honest “about two minutes left”.
Kill every surprise by moving it to the front: “you'll need your passport and ten minutes” before step one converts better than an ambush at step five, even though it looks scarier upfront.
Make leaving safe: save progress automatically and say so. “Your application is saved” converts abandoners into resumers; a flow that loses work converts them into ex-users.
And close each step with a small completion beat: progress acknowledged at every stage keeps the ledger positive the whole way through.
The building blocks that solve it
- Progressive Disclosure: One step at a time, each one named and expected.
- Success Moments: Every completed step acknowledged, not just the last.
Who does this well
Airbnb: Listing a home is a big task presented as small named phases, progress always visible, exit always safe.
Wise: Sending money abroad is a regulated, scary flow broken into plain steps that always say what is next and why.
Questions founders ask
Should we show how many steps remain?
Yes, honestly. Users budget effort against the remaining count, and an honest count builds exactly the trust a complex flow spends.
If the count is embarrassing, the flow is too long: fix the flow, not the label.
Where do users most need reassurance?
Just before every ask, and at every irreversible-looking moment.
A line of plain text at those points, what this is for, what happens next, prevents more abandonment than any redesign of the happy path.