Mockup

Version

v3 · 2026-09-28 · History

Prime #

1592

Domain group

Applied Sciences & Engineering

Origin domain

Architecture & Urban Planning

Subdomains

Architecture and Construction, Design Prototyping → Architecture & Urban Planning

Also from

Engineering & Design (beyond software), Human-Computer Interaction (HCI)

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

Before building a real treehouse, you could make one out of a cardboard box to see if you like the door and the window. It isn't finished and it can't hold you up in a tree, but that's okay. It's just enough to look at, talk about, and change your mind before building the real one.

Pretend Version First

A Mockup is a pretend version of something you're planning, made just real enough for people to see it and react before you build the final thing. If you're planning a poster, you might sketch it on paper first to see if the words are big enough. It's supposed to be incomplete — you only make the parts that matter for the question you're asking. Everyone should know what's pretend and what's real about it. Then people's reactions can change the plan while changing it is still cheap.

Just-Enough Design Preview

A Mockup is a way of making enough of a proposal real that people can see and respond to it before anyone commits to the final version. How realistic it needs to be depends on the question: a full-size cardboard kitchen tests whether people can move around; a small model can test overall shape; a flat screen image can test whether the layout draws the eye to the right places. Its incompleteness is intentional and should be out in the open, not a flaw hidden from viewers. A mockup is useful when it's clear what it represents and what it leaves out, and when feedback can actually change the design. It overlaps with prototypes, models, simulations, and demos, but it's defined by this specific role: selective, cheap commitment used to learn before the expensive commitment.

 

A mockup is a portable design move: materialize enough of a proposal that people can perceive and respond to it before the cost of final commitment is incurred. Its fidelity is question-relative rather than uniformly high or low. Full scale may matter when the question concerns reach and circulation, reduced scale may suffice for massing, and a static screen may suffice for visual hierarchy. Its incompleteness is deliberate and declared, not a defect hidden from view; the mockup becomes informative only when which properties are represented and which are omitted is explicit. It must also be embedded in a loop where feedback can actually revise the target design; a mockup no one can act on is just a display. It overlaps with prototypes (which often test function), models, simulations, and demonstrations, but it is defined by this selective precommitment role rather than by its medium or fidelity.

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. Inclusion test: Require a proposed target, an intentionally selective representation, an evaluation or communication question, and use before final commitment. Exclusion test: Exclude finished artifacts, decorative miniatures with no design relation, simulations with no represented proposal, and functional prototypes when their defining purpose is mechanism validation rather than selective form or use inspection. Nearest boundary: 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. Exit condition: The identity changes when the representation ceases to stand in for a proposal under review or when full final functionality becomes the decisive object of testing. Common misclassifications: 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. Nearest named distinctions: Design Prototyping: The parent includes early models for testing broadly; mockup specifies deliberate partial representation, often of appearance, fit, or interaction. Prototype: A prototype's defining question is whether a mechanism or system works; a mockup may remain nonfunctional. Scale model: Scale describes size relation, while a mockup can be full-size or digital and is defined by design-evaluation use. Simulation: A simulation executes a behavioral model; a mockup may instead stage static form or embodied interaction. Demonstrator: A demonstrator may communicate an established capability, whereas a mockup represents a proposal before commitment.

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

1. Frame the decision that must be made before commitment.
2. Select only the target properties that can inform that decision.
3. Choose scale and media that make those properties perceptible to the intended stakeholders.
4. Mark omissions so observers do not infer unsupported functionality.
5. Elicit behavior, measurements, and criticism, then trace each finding to a proposed revision.
6. 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.

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.

Hierarchy paths (2) — routes to 2 parentless roots

• Mockup → Design Prototyping → Iteration

Show alternative path (1)