Interaction Technique¶

Couple user action, input sensing, software interpretation, state change, and perceptible feedback into a repeatable way of accomplishing one elementary interactive task.

Version: v2 · 2026-09-19 · History
Domain-specific #: 2086
Domain group: Professional & Organizational Practice
Origin domain: Human-Computer Interaction (HCI)
Subdomain: Interaction Techniques → Human-Computer Interaction (HCI)
Aliases: User interface technique, Input technique

Core Idea¶

An interaction technique is the task-level coupling by which a person acts on a computer system and receives enough feedback to accomplish an elementary interactive task. It joins an intended task, one or more physical actions, sensing through input devices, software interpretation, a change or query in application state, and perceptible output. Clicking a toolbar control, dragging an object, choosing from a marking menu, steering a pointer, pinching to zoom, speaking a command, or selecting an object with a ray in virtual reality are techniques when each defines a repeatable action–interpretation–feedback relation.

How would you explain it like I'm…

Press, Slide, See It Move

An interaction technique is a way you tell a computer to do something and see that it worked. Like dragging a picture on a tablet: you press, slide your finger, and the picture follows you, then you let go to drop it. The tablet is just the gadget; the press-slide-let-go move with the picture following is the technique.

Action-and-Feedback Recipes

An interaction technique is a repeatable way of doing one small job on a computer, like moving, picking, or zooming. It includes what you do with your body, how the device senses it, how the software understands it, what changes, and what you see or hear back. A mouse is a device, not a technique, and 'delete' is a command, not a technique. But deleting with a keyboard shortcut, a menu, a swipe, or by saying it out loud are four different techniques for the same command. Designers compare techniques to see which is faster, easier to learn, or less error-prone.

Input–Output Task Coupling

In human-computer interaction, an interaction technique is the repeatable coupling between a user's physical action, the system's interpretation of it, and the feedback that lets the user complete an elementary task. It sits between hardware and function. A mouse is an input device, and 'delete' is a command, but 'drag with the button held, see the object move, release to drop' is a technique. One task can be done with many techniques: shortcut, menu, gesture, or voice. One device can also support many techniques. Defining techniques at this level lets designers compare their speed, errors, accessibility, and learning cost separately from what the application is for. Examples range from clicking a toolbar button to pinch-zooming or pointing a ray at objects in virtual reality.

An interaction technique is the task-level coupling through which a user acts on a system and receives sufficient feedback to complete an elementary interactive task. It binds an intended task, one or more physical actions, sensing by input devices, software interpretation, a resulting change or query in application state, and perceptible output into a repeatable action–interpretation–feedback relation. Examples include clicking a toolbar control, dragging an object, using a marking menu, pinch-to-zoom, spoken commands, and ray-casting selection in virtual reality. The technique is distinct from the device (a mouse) and from the function (delete), since one function can be reached by several techniques and one device can host many. HCI texts accordingly describe it as a programmatic coupling of input and output processing for an elementary task. This level of description supports comparison of competing techniques on mapping, feedback, performance, error exposure, accessibility, and learnability. Instrumental interaction extends the idea by modeling techniques as instruments mediating between users and domain objects, generalizing direct manipulation beyond standard WIMP interfaces.

Scope of Application¶

The construct is native to human–computer interaction, computer graphics, interaction design, visualization, virtual and augmented reality, mobile interaction, accessibility engineering, and input-device research. It is especially useful where researchers propose or compare ways of pointing, selecting, navigating, positioning, entering symbols, choosing commands, or manipulating objects.

Scope is set by the elementary task and the human–system control loop. A technique may span hardware and software and may be implemented across many products. It may also be specialized to a device, body capability, environment, or application domain. A speech technique for issuing vehicle commands remains an HCI technique even though automotive safety constrains its design.

Clarity¶

To identify an interaction technique, ask five questions. What elementary task is supported? What action can the user deliberately perform? How is that action sensed and interpreted? What state or object does the interpretation affect? What feedback lets the user predict, monitor, and correct the result? If one role is missing, the candidate may instead be a device, command, presentation, task description, or isolated algorithm.

Manages Complexity¶

Interaction systems combine device physics, event streams, software state, user intention, perception, motor control, and learning. Treating each product as an indivisible interface makes comparison and reuse difficult. The interaction-technique abstraction compresses this complexity into a functional unit with explicit roles. Researchers can hold a task constant, vary a technique, and measure performance. Designers can hold a device constant and explore alternative mappings or hold a technique concept constant across device implementations.

Abstract Reasoning¶

The structure licenses several inferences:

Device substitution does not guarantee technique preservation. If a new sensor changes action vocabulary, precision, latency, or feedback, the human control relation may change even when the command is unchanged.
Task equivalence enables comparison. Competing techniques can be compared fairly only when they support the same operational task under comparable conditions.
Feedback is constitutive. Removing feedback can break the closed-loop technique by preventing correction or confirmation.

Knowledge Transfer¶

Within HCI, the abstraction transfers across desktop, mobile, wearable, tangible, immersive, automotive, assistive, and ubiquitous systems. Task labels and actions vary, but the action–sensing–interpretation–state–feedback loop remains recognizable. Taxonomies developed for pointing or manipulation can guide a new platform while still requiring platform-specific evaluation.

Transfer is strongest when the elementary task persists. A selection technique can migrate from mouse to pen or gaze, with its control-display relation and confirmation adapted.

Relationships to Other Abstractions¶

Current abstraction Interaction Technique Domain-specific

Parents (1) — outgoing typed relations

Interaction Technique includes Coordination Prime

aligns human action, software interpretation, and system response toward a task.

Children (1) — abstractions linked here by typed relations

Object–Action Interface Domain-specific is a kind of Interaction Technique

Interaction Technique is the broader abstraction this entry instantiates.

Hierarchy paths (5) — routes to 4 parentless roots

Interaction Technique → includes Coordination → presupposes Concurrency

Show alternative paths (4)

Neighborhood in Abstraction Space¶

Interaction Technique sits in a sparse region of the domain-specific corpus (97^th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.

Family — Unclustered & Miscellaneous (2769 abstractions)

Nearest neighbors

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