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.
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.
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. 2. 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) — more general patterns this builds on
-
Human action cycle is a kind of Perception Action Loop Prime
The proposed strict upward parent is
prime:perception_action_loop.
Hierarchy path (1) — routes to 1 parentless root
- Human action cycle → Perception Action Loop → Feedback
Neighborhood in Abstraction Space¶
Human action cycle sits in a crowded region of the domain-specific corpus (9th percentile for distinctiveness): several abstractions share nearly its structure, so a description that fits it tends to fit its neighbors too.
Family — Human–Computer Interaction & Interface Design (24 abstractions)
Nearest neighbors
- Natural user interface — 0.94
- User interface design — 0.93
- Task-focused interface — 0.93
- User interface plasticity — 0.93
- Dark pattern — 0.93
Computed from structural-signature embeddings · 2026-09-08