# 09B What Happens After a Click

A button label describes an action, but the behavior after the click determines whether the interface actually keeps that promise.
If a button says save, the user expects the information to remain available after leaving the page and returning later.
The application should therefore explain whether the action succeeded, failed, or is still waiting for a response from another service.
A silent delay can make people click again because they cannot tell whether their first request was received or ignored.
The description of the workflow should include this waiting state and explain when another action becomes safe or useful.
We also need to think about cancellation, because a user may change their mind before a long operation has finished.
Can the user close the dialog, continue reading, or return later without creating duplicate work or losing important input?
These questions connect interaction design with the state that the application maintains behind the visible controls and messages.
I prefer an explanation that follows one real example, from the initial input to the final confirmation and the next available action.
That example gives both the developer and the reviewer a common reference when they discuss whether the whole process works correctly.
The same description can guide a later review.