Object–Action Interface¶
Model a user's task objects and actions as corresponding interface hierarchies in which a visible object is selected first and the interface then exposes actions applicable to it.
Core Idea¶
An object–action interface organizes interaction around the user's domain objects: select or reveal an object first, then expose the actions that are meaningful for that object. The deeper model pairs a hierarchy of task objects and task actions with a comprehensible hierarchy of interface objects and interface actions. The mapping lets users transfer knowledge of the work domain into predictions about the interface instead of memorizing command syntax.
Shneiderman's direct-manipulation account supplies the closely related requirements of continuous object representation, physical action, rapid feedback, and reversible operations. The object–action model adds an explicit analysis of the task and interface hierarchies that make those representations coherent.
Scope of Application¶
The model applies to document editors, file managers, design tools, dashboards, visual programming, and domain applications where users recognize durable work objects. Hutchins, Hollan, and Norman explain directness through the semantic distance between user intentions and interface mechanisms, a criterion that also tests whether an object–action mapping is genuinely comprehensible.
Clarity¶
Document the task objects and actions separately from widgets and commands. Show the mapping between the two hierarchies; define selection state, action availability, feedback, cancellation, and undo; and test whether users identify the same objects the design assumes. “Object first” is a design consequence, not a substitute for task analysis.
Manages Complexity¶
Hierarchical decomposition prevents a large command vocabulary from appearing as one undifferentiated list. Object context narrows the available actions, and visible state reduces recall. Consistent mappings let a learned operation transfer across similar objects.
Abstract Reasoning¶
- Observe representative users performing real tasks.
- Identify their domain objects, actions, goals, and vocabulary.
- Decompose complex objects and actions into usable hierarchies.
- Create interface representations that preserve important task relations.
- Make the current object and its state perceptible.
- Offer only actions whose preconditions are satisfied, while preserving discoverability.
- Provide immediate outcome and error feedback.
- Support reversal, recovery, and safe exploration.
- Measure whether the mapping reduces gulf of execution and evaluation.
Knowledge Transfer¶
The portable pattern is bind available operations to a visible selected entity through a hierarchy that mirrors the user's task model. It transfers to API resource actions and contextual tools. The proposed immediate parent is Interaction Technique.
Relationships to Other Abstractions¶
Current abstraction Object–Action Interface Domain-specific
Parents (1) — outgoing typed relations
-
Object–Action Interface is a kind of Interaction Technique Domain-specific
Interaction Technique is the broader abstraction this entry instantiates.
Hierarchy paths (5) — routes to 4 parentless roots
- Object–Action Interface → is a kind of Interaction Technique → includes Coordination → presupposes Concurrency
- Object–Action Interface → is a kind of Interaction Technique → includes Coordination → presupposes Dependency
- Object–Action Interface → is a kind of Interaction Technique → includes Coordination → presupposes Task Interdependence → is a kind of Dependency
- Object–Action Interface → is a kind of Interaction Technique → includes Coordination → is a decomposition of Mobilization → presupposes Latent Realizable Capacity
- Object–Action Interface → is a kind of Interaction Technique → includes Coordination → presupposes Task Interdependence → is a decomposition of Network
Neighborhood in Abstraction Space¶
Object–Action Interface sits in a sparse region of the domain-specific corpus (96th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.
Family — Unclustered & Miscellaneous (2769 abstractions)
Nearest neighbors
- User interface — 0.78
- Desktop Metaphor — 0.78
- ACT-R — 0.77
- Interaction Technique — 0.77
- Human action cycle — 0.76
Computed from structural-signature embeddings · 2026-10-25