We often think about UX flows as:
Before → Action → Done
But users don’t necessarily experience “Done” as the end.
Think about watching a movie on VHS.
You reached the end of the movie, but you still had one more thing to do: rewind the tape.
The experience wasn’t complete until the tape was ready for the next person.
Digital products have similar moments.
A user completes a purchase.
A form is submitted.
A file is uploaded.
A booking is confirmed.
A task is completed.
And then comes the question:
What happens next?
The hidden problem with “Done”
A flow can successfully complete the intended task and still leave the user uncertain.
They might wonder:
- Where am I now?
- What changed?
- Is anything still processing?
- What should I do next?
That means the task may be complete, but the experience isn’t necessarily clear.
Design the transition
Instead of thinking only about:
Before → Action → Done
Think about:
Before → Action → Feedback → Next State
The interface should communicate what happened, what state the system is currently in, and what the user can do next.
This connects directly to the UX principle of Visibility of System Status.
Users need to understand what the system is doing, especially after they take an action:
Action → Feedback → Current State → Next Step
Ask the “After” questions
Before shipping a flow, ask:
Did the user get confirmation?
Is the current system state clear?
Is anything still processing?
Is the next step obvious?
Can the user safely leave?
Can they recover if something goes wrong?
Is the experience ready for the next interaction?
These questions force us to design beyond the click.
The real UX lesson
A successful interaction isn’t just about getting users to complete a task.
It’s also about helping them understand what happened and what comes next.
So the next time you design a success state, don’t stop at:
“Success!”
Ask:
“Okay… now what?”
Because the best flows don’t just get users to the finish line.
They know what happens next.
Comments