Nielsen User Control
Users often choose system functions by mistake and will need a clearly marked 'emergency exit' to leave the unwanted state without having to go through an extended dialogue. Support undo and redo.
$ prime install @community/principle-nielsen-user-control Projection
Always in _index.xml · the agent never has to ask for this.
NielsenUserControl [principle] v1.0.0
Nielsen Heuristic 3: users often choose system functions by mistake and need clearly marked emergency exits; undo and redo must be supported.
Users often choose system functions by mistake and will need a clearly marked 'emergency exit' to leave the unwanted state without having to go through an extended dialogue. Support undo and redo.
Loaded when retrieval picks the atom as adjacent / supporting.
NielsenUserControl [principle] v1.0.0
Nielsen Heuristic 3: users often choose system functions by mistake and need clearly marked emergency exits; undo and redo must be supported.
Users often choose system functions by mistake and will need a clearly marked 'emergency exit' to leave the unwanted state without having to go through an extended dialogue. Support undo and redo.
Attributed To
Jakob Nielsen, 1994
Applies To
- destructive actions: delete, archive, bulk operations
- multi-step wizards: back navigation must always be available
- modal dialogs: Escape key and explicit Cancel button required
- text editing: undo/redo history of sufficient depth
- navigation: browser Back button must work predictably
- settings changes: ability to revert to defaults or previous state
Counter Examples
- A 'Delete Account' flow that executes immediately on confirmation with no grace period or recovery email — data loss is irreversible.
- A checkout wizard where clicking Back resets the entire form, forcing users to re-enter all information they already provided.
- A long-running CLI operation with no interrupt mechanism — users must kill the process and restart from scratch.
Loaded when retrieval picks the atom as a focal / direct hit.
NielsenUserControl [principle] v1.0.0
Nielsen Heuristic 3: users often choose system functions by mistake and need clearly marked emergency exits; undo and redo must be supported.
Users often choose system functions by mistake and will need a clearly marked 'emergency exit' to leave the unwanted state without having to go through an extended dialogue. Support undo and redo.
Attributed To
Jakob Nielsen, 1994
Applies To
- destructive actions: delete, archive, bulk operations
- multi-step wizards: back navigation must always be available
- modal dialogs: Escape key and explicit Cancel button required
- text editing: undo/redo history of sufficient depth
- navigation: browser Back button must work predictably
- settings changes: ability to revert to defaults or previous state
Counter Examples
- A 'Delete Account' flow that executes immediately on confirmation with no grace period or recovery email — data loss is irreversible.
- A checkout wizard where clicking Back resets the entire form, forcing users to re-enter all information they already provided.
- A long-running CLI operation with no interrupt mechanism — users must kill the process and restart from scratch.
Sources
Examples
- Gmail's 'Undo Send' with a configurable 5–30 second cancellation window gives users a safety net after the most common email regret.
- Notion's Cmd+Z undo works across text edits, block moves, and property changes — users can safely explore without fear.
- VS Code's modal palette (Escape closes instantly) and every dialog having a Cancel button exemplify low-cost escape at every level.
Source
- Jakob Nielsen, 'Heuristic Evaluation', in Nielsen & Mack (eds.), Usability Inspection Methods (1994)
- https://www.nngroup.com/articles/ten-usability-heuristics/
Source
prime-system/examples/frontend-design/primes/compiled/@community/principle-nielsen-user-control/atom.yaml