Paper prototyping¶
A low-fidelity interface-design method in which hand-made screens and a human-simulated interaction expose usability problems before implementation.
Core Idea¶
Designers represent interface states with paper, cards, or sketches; a facilitator changes the visible state in response to participant actions while observers record breakdowns and expectations. Cheap editable artifacts lower commitment, human simulation supplies system responses, and early user interaction turns observed confusion into rapid design revisions. 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 human computer interaction. It is the domain-specific identity determined by the artifact remains deliberately low fidelity, participants act on it as an interface, system responses are simulated consistently, and observations inform redesign rather than product performance claims.
Scope of Application¶
Paper prototyping 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 artifact remains deliberately low fidelity, participants act on it as an interface, system responses are simulated consistently, and observations inform redesign rather than product performance claims. The scope is broad within that domain but bounded by the need for the artifact remains deliberately low fidelity, participants act on it as an interface, system responses are simulated consistently, and observations inform redesign rather than product performance claims. 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 artifact remains deliberately low fidelity, participants act on it as an interface, system responses are simulated consistently, and observations inform redesign rather than product performance claims 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 Paper prototyping 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 Paper prototyping. Paper prototyping 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 artifact remains deliberately low fidelity, participants act on it as an interface, system responses are simulated consistently, and observations inform redesign rather than product performance claims 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, Cheap editable artifacts lower commitment, human simulation supplies system responses, and early user interaction turns observed confusion into rapid design revisions., and type the carrier, state every parameter and convention in the definition, test that the artifact remains deliberately low fidelity, participants act on it as an interface, system responses are simulated consistently, and observations inform redesign rather than product performance claims, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases.
Relationships to Other Abstractions¶
Current abstraction Paper prototyping Domain-specific
Parents (1) — more general patterns this builds on
-
Paper prototyping is a kind of Design Prototyping Prime
The proposed strict upward parent is
prime:design_prototyping.
Hierarchy paths (2) — routes to 2 parentless roots
- Paper prototyping → Design Prototyping → Iteration
- Paper prototyping → Design Prototyping → Approximation → Representation → Abstraction
Neighborhood in Abstraction Space¶
Paper prototyping sits in a crowded region of the domain-specific corpus (8th 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
- User interface design — 0.94
- Natural user interface — 0.94
- Task-focused interface — 0.94
- User interface plasticity — 0.93
- User modeling — 0.93
Computed from structural-signature embeddings · 2026-09-08