Human action cycle¶

A seven-stage human-computer interaction model linking goal formation, intention and action specification, execution, perception, interpretation and evaluation across the gulfs of execution and evaluation.

Version: v2 · 2026-09-19 · History
Domain-specific #: 4920
Domain group: Professional & Organizational Practice
Origin domain: Human-Computer Interaction (HCI)

Core Idea¶

Norman's action cycle diagnoses interface breakdowns by asking whether users can discover available actions, map intentions to controls, perceive system state, interpret feedback and judge progress toward a goal. A user forms a goal, converts it into an intention and action sequence, executes through the interface, observes the resulting state, interprets its meaning and compares it with the goal, then iterates or stops. The abstraction is therefore identified by a declared carrier, a transformation or constraint over that carrier, and an invariant that tells an analyst whether the named structure is genuinely present.

How would you explain it like I'm…

Want, Do, Look, Check

When you want something from a toy or a tablet, you first figure out what to press, then you press it, then you look to see what happened. If you can't find the button, or you can't tell whether it worked, you get stuck. The Human action cycle is a way to spot exactly where you got stuck.

The Doing-and-Checking Loop

The Human action cycle describes the loop a person goes through when using a machine or app. First you decide on a goal, then you plan what to do and press the buttons. Next you look at what the machine shows, figure out what it means, and check whether you got what you wanted. If not, you go around the loop again. Designers use it to find the exact step where people get stuck, like not knowing which button to press or not understanding what the screen is telling them.

Norman's Execution–Evaluation Cycle

Don Norman's Human action cycle breaks using an interface into a loop. You form a goal, turn it into an intention and a sequence of actions, and carry them out. Then you perceive the system's new state, interpret it, and compare it with your goal. Then you either repeat the loop or stop. Its main use is diagnosis. Each step is a place where an interface can fail. A 'gulf of execution' is when users can't discover the available actions or map what they want onto the controls. A 'gulf of evaluation' is when they can't perceive or interpret the feedback well enough to judge their progress. This is more specific than 'good usability' in general. To apply it properly you have to spell out the user, the task, the controls, the feedback, and how success is judged.

Norman's Human action cycle models interaction as an iterative loop with execution and evaluation stages. On the execution side: goal formation, intention, action specification, and execution through the interface. On the evaluation side: perceiving system state, interpreting it, and comparing it against an evaluation criterion derived from the goal. Analysts use it to locate breakdowns. Can users discover the available actions (affordances and constraints)? Can they map intentions onto controls? Is the system's response perceivable? Can the feedback be interpreted correctly? Failures cluster into the gulf of execution and the gulf of evaluation. A valid analysis makes every element explicit: the user, task and context, goal, intention, action specification, affordances and constraints, system response, feedback, interpretation, evaluation criterion, iteration, and accessibility. If these are left vague, the analysis becomes a loose talk about 'user experience' rather than a test of whether the cycle's structure is actually present. It also helps to keep three questions separate: what must be true, what evidence supports the claim, and what inferences then follow.

Scope of Application¶

Human action cycle belongs to human computer interaction and is useful where the analyst can specify the typed human computer interaction carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets, then evaluate the user, task and context, goal, intention, action specification and execution, interface affordances and constraints, system response, perceivable feedback, interpretation, evaluation criterion, cycle iteration, gulf-of-execution and gulf-of-evaluation failures, and accessibility are explicit. The scope is broad within that domain but bounded by the need for the user, task and context, goal, intention, action specification and execution, interface affordances and constraints, system response, perceivable feedback, interpretation, evaluation criterion, cycle iteration, gulf-of-execution and gulf-of-evaluation failures, and accessibility are explicit.

Clarity¶

The abstraction clarifies a crowded vocabulary by making the user, task and context, goal, intention, action specification and execution, interface affordances and constraints, system response, perceivable feedback, interpretation, evaluation criterion, cycle iteration, gulf-of-execution and gulf-of-evaluation failures, and accessibility are explicit the center of the account. A claim should name the carrier, the governing operation or relation, the applicable assumptions, and the recognition test.

Manages Complexity¶

Without the abstraction, an analyst must reason directly over many local details: the carrier roles, admissibility assumptions, competing conventions, derived invariants, boundary cases, and proof or validation obligations specific to Human action cycle. Human action cycle compresses them into the roles in the structural signature. That compression permits comparison across instances without erasing the variables that determine validity. It also exposes which details may be varied safely and which are constitutive.

Abstract Reasoning¶

Identify the carrier. State what the elements, states, objects, or observations are: the typed human computer interaction carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets. Reject examples whose alleged carrier belongs to a different problem.
Lock the constitutive rule. Express the user, task and context, goal, intention, action specification and execution, interface affordances and constraints, system response, perceivable feedback, interpretation, evaluation criterion, cycle iteration, gulf-of-execution and gulf-of-evaluation failures, and accessibility are explicit independently of one notation or implementation.

Knowledge Transfer¶

Knowledge transfers strongly among subfields of human computer interaction because they reuse the typed human computer interaction carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets, A user forms a goal, converts it into an intention and action sequence, executes through the interface, observes the resulting state, interprets its meaning and compares it with the goal, then iterates or stops., and type the carrier, state every parameter and convention in the definition, test that the user, task and context, goal, intention, action specification and execution, interface affordances and constraints, system response, perceivable feedback, interpretation, evaluation criterion, cycle iteration, gulf-of-execution and gulf-of-evaluation failures, and accessibility are explicit, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases.

Relationships to Other Abstractions¶

Current abstraction Human action cycle Domain-specific

Parents (1) — outgoing typed relations

Human action cycle is a kind of Perception Action Loop Prime

It remains its own entry because its identity is fixed by the user, task and context, goal, intention, action specification and execution, interface affordances and constraints, system response, perceivable feedback, interpretation, evaluation criterion, cycle iteration, gulf-of-execution and gulf-of-evaluation failures, and accessibility.

Hierarchy path (1) — routes to 1 parentless root

Human action cycle → is a kind of Perception Action Loop → is a kind of Feedback

Neighborhood in Abstraction Space¶

Human action cycle sits in a crowded region of the domain-specific corpus (5^th percentile for distinctiveness): several abstractions share nearly its structure, so a description that fits it tends to fit its neighbors too.

Family — Interface & Interaction Design Methods (20 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-10-25