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

v1 · 2026-08-30 · History

Domain-specific #

2086

Origin domain

human computer interaction

Subdomain

interaction techniques

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.

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:

1. 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. 2. Task equivalence enables comparison. Competing techniques can be compared fairly only when they support the same operational task under comparable conditions. 3. 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) — more general patterns this builds on

• Interaction Technique is part of Coordination Prime

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

Children (1) — more specific cases that build on this

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

  Interaction Technique is the proposed immediate parent.

Hierarchy paths (5) — routes to 4 parentless roots

• Interaction Technique → Coordination → Concurrency

Show alternative paths (4)

Neighborhood in Abstraction Space

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

Family — Unclustered & Miscellaneous (1565 abstractions)

Nearest neighbors

• User interface — 0.82
• Human action cycle — 0.79
• Object–Action Interface — 0.77
• Interaction Flow Modeling Language — 0.75
• Switch access scanning — 0.74

Computed from structural-signature embeddings · 2026-09-08