Prototype Representation¶
Artifact — instantiates Representation Fit Selection
Uses a physical, digital, procedural, or role-play prototype to represent behavior, affordance, timing, or user interaction that text or charts would miss.
Prototype Representation represents a situation by building a thing someone can act on — a mock-up, a clickable flow, a role-played procedure — because behavior, affordance, and timing only reveal themselves when a real person interacts with a real (if rough) artifact. Its defining move is to choose the operable prototype precisely when the task-relevant structure is interaction that cannot be reasoned about on paper: whether a user will discover the button, how the wait feels, where a hand hesitates. Fit is judged not by a reader's comprehension but by what real users do when they touch it. This is what separates it from every static form in the family — the representation is validated by behavior, not by inspection.
Example¶
A grocery chain is designing a new self-checkout kiosk, and the specs look airtight: a requirements list of every screen, a flowchart of the scan-bag-pay sequence, an architecture diagram of the payment integration. On paper the flow is obviously correct. Prototype Representation is the insistence that "obvious on paper" tells you nothing about whether a hurried shopper with a toddler and a full basket can actually use it. The team builds a rough working kiosk — real screen, real scanner, a foam dummy for the bagging area — and puts a dozen ordinary shoppers in front of it with no instructions. Within minutes the interaction structure that no diagram exposed comes out: people don't see the "produce lookup" prompt because their eyes are on the bag; the "unexpected item in bagging area" timing is so tight it fires while they're still setting down the last item; left-handed users reach across the scanner. The prototype represents exactly the affordance-and-timing behavior a text spec omits. The team is disciplined about its distortions too — the foam bagging area doesn't weigh like real groceries, so weight-sensor behavior is explicitly out of scope for this round — and it watches how real users, not designers, interpret each cue.
How it works¶
The method builds the roughest artifact that still exercises the interaction in question, then puts real users in front of it and watches what they do — treating each session as a validation case that either confirms the design supports the intended behavior or exposes where it breaks. It is explicit about the prototype's own distortions: a prototype represents some aspects vividly (layout, sequence, discoverability) while faking or omitting others (real load, real data, real stakes), so the method names what is faithful and what is scaffolding, keeping conclusions inside the faithful zone. And it centers the actual user's interpretation — the point is what a first-time user perceives and does, not what the designer intended them to perceive.
Tuning parameters¶
- Fidelity — how close the prototype is to the real thing; higher fidelity surfaces more real behavior but costs more to build and makes users reluctant to critique a polished-looking artifact.
- Interaction scope — which behaviors the prototype is built to exercise; a narrow scope tests one thing cleanly but leaves interactions between features unseen.
- User realism — how representative the test participants are of true end users; realistic users surface real confusion but are harder to recruit than colleagues.
- Scaffolding disclosure — how explicitly the faked parts are marked out-of-scope; clear disclosure prevents over-reading but requires admitting what the prototype cannot show.
When it helps, and when it misleads¶
Prototype Representation helps whenever a design reads fine but its real risk lives in interaction, affordance, or timing that no static artifact can surface — it substitutes observed behavior for confident-but-untested reasoning.[n1]
Its failure mode is mistaking the prototype for the product: reading behavior off scaffolded parts as if they were real, or letting a high-fidelity mock-up's polish suppress the honest criticism a rough one invites. The classic misuse is the demo dressed as a test — a prototype built to impress stakeholders rather than to be broken by users, which produces applause instead of findings. The guarding discipline is explicit scaffolding disclosure plus genuinely representative users: name what the prototype fakes, keep conclusions inside what it faithfully represents, and let real users, not the design team, drive it.
How it implements the components¶
distortion_check— it names which aspects the prototype represents faithfully and which are scaffolded or faked, bounding what may be concluded.interpretation_context— it centers what real, representative users perceive and do, not the designer's intended reading.validation_case— each user session is a case that confirms or breaks the design's support for the intended behavior.
It builds an operable artifact tested by behavior and does not reason about which static form to draw — candidate_representation, preserved_feature, and representation_selection_rule belong to Diagram Model Choice, its nearest artifact twin, which picks a diagram genre to read rather than a prototype to operate.
Related¶
- Instantiates: Representation Fit Selection — a prototype instantiates the archetype only when chosen because interaction behavior is the task-relevant structure and validated against real users.
- Sibling mechanisms: Dashboard View Design · Diagram Model Choice · Graph–Table Comparison · Map–List Choice · Mathematical Model Selection · Multi-View Model · Narrative Representation · Schema Selection
Editorial Notes¶
Form Classification¶
Form family: Experiment, Test & Rehearsal
Rationale: Prototype Representation operates as an active test, trial, simulation, drill, or rehearsal that generates evidence through a deliberate attempt or perturbation because it uses a physical, digital, procedural, or role-play prototype to represent behavior, affordance, timing, or user interaction that text or charts would miss.
Independent corroboration: The frozen evidence defines Prototype Representation as 'Uses a physical, digital, procedural, or role-play prototype to represent behavior, affordance, timing, or user interaction that text or charts would miss', so its operative form is Experiment, Test & Rehearsal.
Nearest alternative: Representation, Specification & Plan — Prototype Representation includes features of a static representation, map, specification, schema, or prospective plan that externalizes information, but its defining operation is an active test, trial, simulation, drill, or rehearsal that generates evidence through a deliberate attempt or perturbation.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Engineering & Design
Origin pattern: Convergent development
Present-day reach: Universal
Rationale: Physical and procedural prototypes as representations of future behavior are foundational engineering-design methods.
Related originating lineages:
- Human-Computer Interaction — HCI materially shaped digital and interaction prototypes for testing affordance and timing.
- Performing Arts & Theatre Studies — Role-play and enacted simulation supplied an independent representational practice for procedural experiences.
Review resolution: Both blind reviewers agree on engineering_design as the primary origin. Explicit reconciliation resolves reported_ambiguity, domain_reach_disagreement. The merged alternate lineages retain only domains the reviewers identified as materially formative; domain_reach=universal records later applicability separately from origin breadth.
Attribution caveat: The page deliberately unifies several representational media that did not arise from one discipline. The entry deliberately unifies several historically distinct prototype media.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; medium confidence.
Notes¶
[n1] Affordance — the perceivable possibilities for action an object offers a user, a concept from perceptual psychology (James Gibson) brought into design by Donald Norman. Whether an affordance is actually perceived is discoverable only by watching people interact, which is exactly what a prototype represents. ↩