UI review pattern
Make consequential actions reversible
When recovery is practical, let people act and undo. Reserve a blocking confirmation for actions that cannot be safely reversed. The review has to look at the recovery, not only at the button that starts the action.
Use this pattern when
- The action changes meaningful state: it archives, moves, edits, sends, or removes something a person would notice was gone.
- A reliable undo or recovery path exists, and it restores the relevant data rather than a partial stand-in.
- A confirmation dialog on every attempt would interrupt a common workflow. If people are trained to dismiss the dialog, it is not protection.
Do not use it as cover for a destructive action that cannot be undone. If recovery is impossible, say so in the interface and confirm before the action. Calling that flow reversible because a toast appeared is the failure this pattern is meant to catch.
Review the whole state sequence
Inspect five states, in order. The default action, before anything is committed. The immediate feedback, so the person can tell the action happened. The undo affordance, including where it sits and how long it stays available. The expiration state, when undo is no longer offered and the action has stuck. The failure state, when recovery was attempted and did not work.
A polished initial screen is not this review. If the proposal only shows the happy path, send it back. The same standard applies if undo is easy to miss, if it expires without saying so, or if a failed recovery looks identical to a successful one.
Keep the promise honest
Do not label an action reversible unless recovery restores the relevant data and the person can tell that it succeeded. "Undo" that recreates an empty record, or that restores the item without the edits that were on it, is a different action and the label should say so. If only some fields come back, the interface has to say which ones.
Staged commitment is the other honest form. The person can assemble the change, see it, and back out before it sticks. That is still reversible only for as long as backing out is real. Once the stage commits, the review should show the new recovery path or admit there isn't one.
How to hold this against a real screen
In Try That UI, keep the current action as Current and put the proposed treatment on Proposed. If you need to judge the undo control itself, try it as an isolated component prototype in the review. The prototype does not add undo to your application, and a captured screen does not replay the live product. The pattern is the list of states to insist on before you keep the direction. Implementation stays in your code. The rest of the library is the pattern index, which currently publishes this note and no others.
Questions
When should a review demand undo instead of a confirmation dialog?
When the action is common and a reliable recovery path can restore the relevant state. Use a blocking confirmation when recovery is impossible or incomplete, not as a substitute for a missing undo.
What states does the review have to include?
The default action, the immediate feedback, the undo affordance, what happens when undo expires, and what the person sees if recovery fails. The resting state alone is not enough.
Does Try That UI add undo to my product?
No. This is a review pattern. You can compare the current action with a proposed recovery treatment in the workspace. Implementing undo still happens in your own code.
Create a free account