Undo/Redo

Undo/redo functionality allows users to reverse actions and recover from mistakes, enabling confident exploration and reducing error anxiety.

stellae.design

Design Principles

Undo/redo is the fundamental error recovery mechanism. It lets users reverse actions (undo) and re-apply them (redo), creating a safe environment for exploration. Without undo, every action feels risky. With it, users experiment freely. Implementation approaches: single-action undo (Cmd+Z), multi-level undo (history stack), undo via toast notification ('Deleted — Undo'), and time-based undo (Gmail's 'Undo Send' window).

Why It Matters

Undo and redo functionality gives users the freedom to explore, experiment, and recover from mistakes without fear of irreversible consequences. This principle directly supports Don Norman's heuristic of user control and freedom, which research consistently identifies as a key factor in perceived usability and user satisfaction. Without undo, users become cautious and hesitant, slowing down their workflow and avoiding features they are uncertain about.

Real-World Examples

Email client with send-undo grace period

An email client displays a toast notification with an undo button for five seconds after the user presses send, allowing them to cancel delivery during the grace period. This lightweight undo mechanism prevents a category of mistakes that causes real anxiety without requiring a complex versioning system. The feature has become so expected that its absence in competing clients is considered a significant drawback.

Design tool with full operation history

A vector design application maintains a scrollable history panel showing every operation performed on the canvas, from individual path edits to layer reordering. Users can click any point in the history to jump back to that state, and branching is supported so new edits from a past state do not destroy later work. This deep undo capability encourages creative experimentation without risk.

Counter-example

Admin panel with permanent delete and no undo

A content management system permanently deletes records when an admin clicks the delete button, with only a browser confirmation dialog as a safeguard. Accidental deletions require database restoration by engineering, costing hours of work and causing data gaps. The lack of soft-delete or undo functionality turns a routine administrative task into a high-stakes operation.

Role-Specific Guidance

Common Mistakes

• A common mistake is implementing undo only for text input while ignoring destructive actions like deletion, reordering, or configuration changes where recovery is most critical. Another error is providing undo without clear feedback about what was undone, leaving users uncertain about the current state of their work. Teams also frequently underestimate the complexity of undo in collaborative environments, where one user's undo can conflict with another user's concurrent edits.