Activity-centered design¶

An interaction-design approach that organizes a product around the coherent activity users must accomplish rather than around isolated preferences or interface features.

Version: v1 · 2026-09-08 · History
Domain-specific #: 3199
Origin domain: interaction design
Subdomain: interaction design

Core Idea¶

Designers study goals, actions, tools, division of labor, context, and task sequence, then shape system support so the whole activity becomes more effective and intelligible. Mapping dependencies among actions reveals missing transitions and coordination burdens, allowing the artifact to scaffold the work structure shared across user variants. 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.

The load-bearing residual is not the broad topic of interaction design. It is the domain-specific identity determined by the target activity and goal, actors, actions, context, tools, dependencies, and success conditions are explicit and design decisions trace to them.

Scope of Application¶

Activity-centered design belongs to interaction design and is useful where the analyst can specify the typed interaction design carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets, then evaluate the target activity and goal, actors, actions, context, tools, dependencies, and success conditions are explicit and design decisions trace to them. The scope is broad within that domain but bounded by the need for the target activity and goal, actors, actions, context, tools, dependencies, and success conditions are explicit and design decisions trace to them. The entry records a descriptive analytical identity; practical use requires the governing domain's evidence, standards, and safety obligations.

Clarity¶

The abstraction clarifies a crowded vocabulary by making the target activity and goal, actors, actions, context, tools, dependencies, and success conditions are explicit and design decisions trace to them the center of the account. A claim should name the carrier, the governing operation or relation, the applicable assumptions, and the recognition test. A bare label is insufficient because the name Activity-centered design can be used for a formal identity, an implementation, or a neighboring result unless carrier and convention are stated.

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 Activity-centered design. Activity-centered design 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 interaction design 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 target activity and goal, actors, actions, context, tools, dependencies, and success conditions are explicit and design decisions trace to them independently of one notation or implementation.

Knowledge Transfer¶

Knowledge transfers strongly among subfields of interaction design because they reuse the typed interaction design carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets, Mapping dependencies among actions reveals missing transitions and coordination burdens, allowing the artifact to scaffold the work structure shared across user variants., and type the carrier, state every parameter and convention in the definition, test that the target activity and goal, actors, actions, context, tools, dependencies, and success conditions are explicit and design decisions trace to them, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases.

Relationships to Other Abstractions¶

Current abstraction Activity-centered design Domain-specific

Parents (1) — more general patterns this builds on

Activity-centered design is a kind of Task Interdependence Prime

The proposed strict upward parent is prime:task_interdependence.

Hierarchy paths (2) — routes to 2 parentless roots

Activity-centered design → Task Interdependence → Dependency

Show alternative path (1)

Neighborhood in Abstraction Space¶

Activity-centered design sits in a crowded region of the domain-specific corpus (13^th 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

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