Mockup¶
Core Idea¶
Mockup names a portable design move: materialize enough of a proposal for people to perceive and respond to it before the cost of final commitment. The relevant fidelity is question-relative. Full scale may matter for reach and circulation, while a reduced scale may suffice for massing, and a static screen may suffice for visual hierarchy.
The mockup's incompleteness is deliberate, not a defect hidden from view. It becomes informative when represented properties and omissions are explicit and feedback can revise the target. A mockup may overlap a prototype, model, simulation, or demonstration, but none is synonymous with this selective precommitment role.
How would you explain it like I'm…
The Cardboard Try-Out
Pretend Version First
Just-Enough Design Preview
Structural Signature¶
Sig role-phrases:
- Proposed target — Supplies the not-yet-final artifact, environment, interface, or arrangement being represented. It is referent. Counterfactual: A freestanding model with no design target is not a mockup of that target.
- Selective representation — Materializes only the properties under present examination. It is carrier. Counterfactual: Attempting complete replication defeats the economical selectivity central to mockups.
- Fidelity choice — Sets scale, material, finish, behavior, and detail relative to the evaluation question. It is design variable. Counterfactual: High visual fidelity cannot answer a load-performance question if mechanics are absent.
- Precommitment stage — Places the representation before or between costly design commitments. It is temporal role. Counterfactual: A finished production sample used only as merchandise is no longer serving this role.
- Stakeholder encounter — Enables viewing, fitting, handling, navigating, or communicating about the proposal. It is interaction. Counterfactual: A representation nobody can evaluate provides no mockup function.
- Feedback-to-revision loop — Converts reactions or measurements into changes to the proposed target. It is output. Counterfactual: Demonstration without any evaluative or communicative purpose is a display replica instead.
What It Is Not¶
- It is not necessarily miniature, physical, realistic, or fully functional.
- It is not a guarantee that the final artifact will perform as displayed.
- It is not merely an illustration with no evaluative encounter.
- It is not inferior to a prototype; the two answer different questions and can overlap.
- Closest near-miss. A prototype tests whether or how a system works; a mockup can test what it looks like, fits like, or communicates while omitting the operative mechanism, though one artifact may serve both roles.
Scope of Application¶
- Architecture and construction. Tests massing, circulation, fit, sightlines, and client understanding before building.
- Product and industrial design. Examines dimensions, ergonomics, surface, assembly access, or consumer response.
- Garment making. Uses toile or muslin to revise pattern fit before cutting final material.
- Software and service design. Stages screens, journeys, and interactions without production infrastructure.
- Education and public communication. Makes a proposed system or arrangement inspectable for explanation and discussion.
Clarity¶
Name the target, decision, represented properties, omitted properties, scale, fidelity, audience, and revision path. Fidelity is not one vertical score: visual, spatial, behavioral, material, and data fidelity can differ, so each must be evaluated against the question the mockup is meant to answer.
Manages Complexity¶
A mockup compresses an expensive possible future into a manipulable present representation. By separating target, fidelity dimensions, stakeholder task, and revision, it prevents teams from demanding full implementation before learning about form or use—and from trusting a visually impressive shell as evidence about hidden performance.
Abstract Reasoning¶
- Frame the decision that must be made before commitment.
- Select only the target properties that can inform that decision.
- Choose scale and media that make those properties perceptible to the intended stakeholders.
- Mark omissions so observers do not infer unsupported functionality.
- Elicit behavior, measurements, and criticism, then trace each finding to a proposed revision.
- Retire or refocus the mockup when the decision advances to another fidelity layer.
Knowledge Transfer¶
The transferable cargo is selective representation before commitment: target, evaluation question, fidelity vector, stakeholder encounter, and revision loop. It travels literally across buildings, garments, products, vehicles, interfaces, services, and instruction because none requires the same substrate; it stops at retrospective replicas or full-performance qualification whose learning object is no longer selective representation.
Examples¶
Canonical¶
A full-size cardboard room interior reproduces wall, door, and equipment positions so users can test reach and circulation before construction, while omitting final materials and services.
Mapped back: target → room; selection → geometry; fidelity → full scale; encounter → walk-through; revision → layout.
Applied / In Practice¶
A garment toile uses inexpensive cloth to test pattern fit, while a clickable interface mockup stages screen appearance and navigation without production back-end behavior.
Mapped back: garment cargo → fit; interface cargo → visual interaction; omitted → final fabric or system.
Applied / In Practice¶
A flight article built with production systems for qualification primarily tests full engineering performance; calling it a mockup obscures the changed fidelity and commitment.
Mapped back: functionality → production; purpose → qualification.
Structural Tensions¶
T1 — Speed And Disposability versus Representational Credibility. Cheap construction invites revision but can make stakeholders respond to artifacts of low fidelity rather than the design.
Diagnostic: Is each omitted or simplified property irrelevant to the present question?
T2 — Focused Question versus Stakeholder Overinterpretation. Selective fidelity clarifies one decision while viewers may treat the representation as a promise about everything.
Diagnostic: Which properties are represented, simulated, or explicitly out of scope?
T3 — Persuasion versus Evaluation. A polished mockup can recruit support even when it exposes little disconfirming evidence.
Diagnostic: Is the encounter structured to discover defects or merely to showcase a proposal?
Structural–Framed Character¶
Mockup is a hybrid near the middle of the structural–framed spectrum. Its structural part is selective representation: only the properties under examination are materialized, at a fidelity set by the question being asked. The framed layer is the design practice around it, with a proposed target, a stage before costly commitment, and people who perceive and respond.
Design vocabulary such as fidelity, prototype, and precommitment partly travels with it. As a concept it is evaluatively neutral, and it is not an inferior prototype but a tool for a different question. Its origin in architectural design is a professional practice rather than an institution of norms, which earns a partial institutional mark. It cannot be defined without designers, a proposal, and an audience whose feedback can revise the target, so it sits at the framed pole on that diagnostic. Applying it across design fields reads as recognition, while extending it outside design recasts the material. A full-scale room built to test reach and circulation, a reduced-scale model for judging massing, and a static screen used to assess visual hierarchy are all mockups. The diagnostics therefore place it near the middle, on the mixed-framed side.
Structural Core vs. Domain Accent¶
The substrate-independent core is a proposal represented selectively so consequential properties can be encountered before commitment. Domain accents determine what counts as fit or function, which media are credible, how stakeholders participate, and when a mockup becomes a prototype, sample, or demonstrator.
Instantiates / Related Primes¶
-
Parent — Design Prototyping (strict subsumption). Mockup is a kind of early design model used for examination and feedback, distinguished by selective fidelity and no requirement of full function.
-
Related — representation, simulation, scale model, feedback, affordance, and counterfactual testing. These supply relations or reasoning operations that mockups can employ without replacing the prime.
Relationships to Other Abstractions¶
Current abstraction Mockup Prime
Parents (1) — more general patterns this builds on
-
Mockup is a kind of Design Prototyping Prime
Mockup is a strict kind of Design Prototyping: A selective precommitment representation of a proposed artifact or arrangement used to examine appearance, fit, spatial relation, interaction, communication, or use without implementing full final functionality.A mockup is a strict kind of design prototyping: an early model used to examine a proposed design, narrowed by deliberate selectivity and no requirement of full functionality.
Hierarchy paths (2) — routes to 2 parentless roots
- Mockup → Design Prototyping → Iteration
Neighborhood in Abstraction Space¶
Mockup sits among the more crowded primes in the catalog (6th percentile for distinctiveness): several abstractions describe nearly the same structure, so a description that fits it will tend to fit its neighbors too — transporting it usually means disambiguating within this family rather than landing on it exactly.
Family — Inquiry, Evidence & Evaluative Standards (21 primes)
Nearest neighbors
- Replica — 0.81
- Crew — 0.77
- Argument — 0.77
- Analytic Reasoning — 0.76
- Perfection — 0.76
Computed from structural-signature embeddings · 2026-10-08
Not to Be Confused With¶
- Design Prototyping. Tell: The parent includes early models for testing broadly; mockup specifies deliberate partial representation, often of appearance, fit, or interaction.
- Prototype. Tell: A prototype's defining question is whether a mechanism or system works; a mockup may remain nonfunctional.
- Scale model. Tell: Scale describes size relation, while a mockup can be full-size or digital and is defined by design-evaluation use.
- Simulation. Tell: A simulation executes a behavioral model; a mockup may instead stage static form or embodied interaction.
- Demonstrator. Tell: A demonstrator may communicate an established capability, whereas a mockup represents a proposal before commitment.
Solution Archetypes¶
No catalogued solution archetypes reference this prime yet.
References¶
- Frozen Wikipedia discovery revision: https://en.wikipedia.org/wiki/Mockup (revision 1345715455).
- Preserved source candidate: http://news.softpedia.com/news/KSC-Gets-Orion-Mock-Up-for-Testing-103300.shtml
- Preserved source candidate: http://www.interaction-design.org/encyclopedia/mock-ups.html
- Preserved source candidate: https://apps.dtic.mil/sti/pdfs/ADA490527.pdf
- Preserved source candidate: https://northhouse.org/blog/trial-and-error-working-with-mockups
- Preserved source candidate: https://historicalsewing.com/working-with-mockups
- Preserved source candidate: https://graflick.com/
- Preserved source candidate: http://www.cpsc.gov/LIBRARY/FOIA/meetings/mtg08/smoldering7_14.pdf
- Preserved source candidate: https://web.archive.org/web/20081207033307/http://www.cpsc.gov/library/foia/meetings/mtg08/smoldering7_14.pdf
The frozen Wikipedia revision is discovery provenance. The retained source set was reviewed for identity, formal or operational relation, and scope. The encyclopedia's structural synthesis is bounded to those claims; a thin authority surface is recorded as a nonblocking source-strengthening repair rather than concealed.