The gulf of execution and evaluation
Two gaps: working out how to act, and working out what happened after acting.
The gulf of execution is the distance between what a person intends and the actions the system offers. The gulf of evaluation is the distance between the state the system is in and what the person can tell about it from the display. Good design narrows both, through affordance: A visual cue that tells you what an element will do if you act on it. and signifiers on the execution side and through feedback and visible state on the evaluation side.
How it shows up in software
Execution gulf problems look like: the user knows what they want and cannot find the control, or the control exists under a name they would never search for. Evaluation gulf problems look like: the action completed and nothing on screen says so, or a save happened and the person cannot tell whether it stuck. Most bug reports that read as confusion are one of these two.
Using it well
- Name controls after the user's intent rather than the system's implementation, so searching for the intent finds the control.
- Acknowledge every action within a few hundred milliseconds, even if the work is still running, so the evaluation gulf never opens.
- Show state in the place the state lives: saved status in the document, sync status on the file, permission on the record.
- Diagnose a usability complaint by asking which gulf it is. The fixes are different: discoverability and labelling on one side, feedback and visible state on the other.
Where it turns manipulative
- Widening the execution gulf on purpose for paths you dislike, such as burying account deletion under an unrelated label.
- Leaving the evaluation gulf open on a charge or a data sharing change, so the person cannot easily tell what the system did on their behalf.
- Faking feedback: a progress bar that does not track real progress, or a success state shown before the operation has actually succeeded.
Where you have seen it
Google Docs
A persistent indicator states whether all changes are saved, closing the evaluation gulf on a background operation.
macOS Finder
Dragging a file shows the file moving with the pointer and the destination folder highlighting, so intent and system state stay visible during the action.
Linear
Actions apply instantly with an undo toast, so the result is visible immediately and reversible without a confirmation step.
What the research says
- Hutchins, Hollan and Norman, 1985Mixed evidence
Introduced the gulfs to explain why direct manipulation interfaces feel easier: they shorten the semantic and articulatory distance on both the input and output sides.
An analytical framework rather than an experimental result. Its value is as vocabulary for diagnosing a problem, not as a measured effect.
- Norman, 1988Mixed evidence
The Design of Everyday Things developed the gulfs alongside affordances, signifiers, mapping and feedback into a general account of usable design.
Widely adopted in practice. The concept of affordance was later revised by Norman himself because the original usage had drifted.
Grades are a judgement about the evidence, not about how useful the idea is. Plenty of contested effects are still worth knowing, as long as you do not cite them as settled.