Skip to content
UX Atlas
PrincipleExpert heuristicFoundational

Forgiveness

An interface people can explore without fear produces confident users and fewer support tickets.

Definition

A design principle holding that systems should tolerate exploration and error, making most actions reversible, most states recoverable, and consequences visible before they are permanent.

Expert heuristic. A review criterion developed by practitioners. Useful and widely taught, but evaluated by judgement rather than measurement.

On this page
  1. Definition
  2. Fear is a usability cost
  3. Mechanisms
  4. In practice
  5. Sources
  6. Continue from here

Fear is a usability cost

Users who are unsure whether an action is safe will avoid it. That shows up as unused features, as duplicate records created because someone was afraid to edit the original, and as support requests asking what a button does.

Forgiveness is what makes exploration a viable learning strategy. Without it, the only safe way to learn a product is documentation, and most people will not read it.

Mechanisms

  • Undo for anything reversible, available long enough to be used.
  • Version history for content, so an edit is never a loss.
  • Soft delete with a restore window rather than immediate destruction.
  • Autosave with visible drafts, so interruption costs nothing.
  • Preview before commit for anything with a wide effect.
  • Non-destructive defaults: duplicate rather than overwrite, add rather than replace.

In practice

Version history in collaborative editors

Documents

Full history plus named versions makes editing a shared document safe. Without it, teams create copies defensively and the single source of truth stops being single.

Draft and publish separation

Content management

Separating the editing state from the published state makes experimentation free. The user can be wrong in private, which is the point.

Sources

Where a source establishes something narrower than the popular reading of it, the note says so.

  • The Design of Everyday Things

    D. A. Norman, Basic Books, 1988, revised 2013

    Forgiveness is developed through Norman's treatment of error, constraints and recovery rather than as a single named chapter.

Continue from here

Each link says what the connection is, so you can tell a principle from an alternative from a thing people mix this up with.

Applies when you are designing

An AI Product

Why this works

The reasoning this entry rests on.

Applied through

Where this shows up as a concrete interface decision.

Practical example

A worked decision where this was the deciding factor.

Related concept

Connected closely enough to change how you apply this.