UI review pattern

Make consequential actions reversible

When recovery is practical, let people act and undo. Reserve blocking confirmation for actions that cannot be safely reversed.

Use this pattern when

• The action changes meaningful state.
• A reliable undo or recovery path exists.
• Repeated confirmation would interrupt a common workflow.

Review the complete state sequence

Inspect the default action, immediate feedback, undo affordance, expiration state, and failure recovery. A polished initial state is not enough.

Keep the promise honest

Do not label an action reversible unless recovery restores the relevant data and the user can tell that it succeeded.