Unskinned Prototype Review¶
Workflow — instantiates Material Literalness Foregrounding
Reviews an object, interface, or system before cosmetic skinning so teams can inspect structure, affordances, and material constraints directly.
An Unskinned Prototype Review is a review gate held deliberately before the cosmetic skin goes on, so stakeholders judge structure, flow, affordances, and constraints on the bare substrate instead of reacting to color and polish. Its defining move is that it is a timed inspection workflow — it inspects and gates, it does not fabricate exposed structure or keep production marks. By fixing the review at the pre-skin moment and forbidding aesthetic feedback there, it forces the question "does the underlying thing actually work?" to be answered before a persuasive surface can smuggle it past everyone.
Example¶
A team is building a banking app's money-transfer flow. Historically the review meetings collapse into arguments about button color while the actual flow goes unexamined — because a polished mock triggers the aesthetic-usability effect,[n1] and a screen that looks finished is assumed to work. The team institutes an unskinned review: the flow is shown in grey wireframes, no brand color, no illustration, and the only questions permitted are structural — are the states honest, are the affordances real, are the constraints respected? Stripped of its skin, the flow reveals that the "confirm" screen hides the transfer fee until after the user submits — an honesty defect the polished version would have sailed straight past. Only once the unskinned review passes does visual design begin. The gate did its job by refusing to let the surface answer for the structure.
How it works¶
The workflow schedules the review at the pre-skin stage and strips the artifact to substrate — wireframe, grey-box, bare states. It then constrains the review question to structure, affordance, and constraint, explicitly deferring aesthetic feedback to a later stage, and it checks that even the stripped version preserves the safety and orientation states users depend on. Its output is a pass-or-revise verdict on the structure, not a built artifact — which is what marks it off from mechanisms that expose or retain physical material; a review gate inspects and decides, it does not make.
Tuning parameters¶
- Skinlessness depth — pure wireframe versus a low-color grey-box; barer forms remove more bias but are harder for some reviewers to read.
- Question scope — how strictly aesthetic feedback is deferred; a hard ban focuses the review but frustrates reviewers who think visually.
- Gate strength — advisory checkpoint versus a hard gate that blocks skinning until structure passes.
- State-honesty probing — how aggressively the review hunts for hidden or dishonest system states behind the bare screens.
When it helps, and when it misleads¶
Its strength is separation of concerns: it splits "does it work" from "does it look good," catching structural and affordance defects that a skin would mask. Its failure mode is that some material truths only appear once skinned — real contrast, legibility, and touch-target size — so an unskinned review can pass a flow that then fails at full fidelity; teams can also mistake the grey-box for the finished thing and under-invest in the skin. The classic misuse is wielding wireframe review to permanently avoid visual quality. The discipline is to treat the gate as a sequencing device, not a rejection of finish, and to re-check the honesty-critical states again at full fidelity before shipping.
How it implements the components¶
substrate_visibility_field— the review makes the bare structure and system states inspectable at the exact moment before a skin would hide them.intrinsic_affordance_alignment— its core question is whether the affordances and states are honest and match what the system can actually do.protective_use_boundary— it checks that even the stripped-down version keeps the safety and orientation information users need.
It does not fabricate visible structure or keep production marks (process_trace_exposure, patina_and_aging_policy) — a review gate inspects but does not make; retained marks on a finished object are Process Mark Retention.
Related¶
- Instantiates: Material Literalness Foregrounding — it forces the substrate to be judged before a cosmetic surface can speak for it.
- Consumes: Raw Material Exposure Specification supplies the ruling on which structure the review should hold open for inspection.
- Sibling mechanisms: Raw Material Exposure Specification · Exposed Joinery or Structure · Finish and Coating Minimization · Material Sample or Cutaway Panel · Literal Data Mark Encoding · Process Mark Retention · Scale Mockup and Tactile Review
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Unskinned Prototype Review operates as a bounded evaluation of existing evidence or work that produces a finding or disposition because it reviews an object, interface, or system before cosmetic skinning so teams can inspect structure, affordances, and material constraints directly.
Independent corroboration: The frozen evidence defines Unskinned Prototype Review as 'Reviews an object, interface, or system before cosmetic skinning so teams can inspect structure, affordances, and material constraints directly', so its operative form is Assessment, Review & Assurance.
Nearest alternative: Protocol, Workflow & Routine — Unskinned Prototype Review includes features of a repeatable ordered procedure or handoff sequence that coordinates action, but its defining operation is a bounded evaluation of existing evidence or work that produces a finding or disposition.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Engineering & Design
Origin pattern: Convergent development
Present-day reach: Multi-domain
Rationale: NASA Systems Engineering Handbook documents that systems engineering uses prototypes, design reviews, verification gates, margins, and feedback to expose risk before commitment. This is direct, mechanism-specific evidence for engineering design as the best-evidenced historical home of the operation—Reviews an object, interface, or system before cosmetic skinning so teams can inspect structure, affordances, and material constraints directly.—rather than evidence merely that the operation is useful there. The retained alternates record genuine adjacent lineages; later portability is represented separately by domain_reach=multi_domain.
Related originating lineages:
- Art & Aesthetics — Visual art, composition, and design practice supplies a parallel or contributing lineage for the mechanism's defining operation: reviews an object, interface, or system before cosmetic skinning so teams can inspect structure, affordances, and material constraints directly.
- Human-Computer Interaction — Human-computer interaction and interface design supplies a parallel or contributing lineage for the mechanism's defining operation: reviews an object, interface, or system before cosmetic skinning so teams can inspect structure, affordances, and material constraints directly.
- Organizational & Management Science — Organizational Management supplies a historically relevant adjacent lineage or formative practice for the operation—Reviews an object, interface, or system before cosmetic skinning so teams can inspect structure, affordances, and material constraints directly.—but the adjudicated evidence more directly locates the defining lineage in engineering design.
- Systems Thinking & Cybernetics — Systems science's feedback, boundaries, control, and regulation tradition contributes a separate formative lineage to the mechanism's unskinned prototype review logic.
Review resolution: The blind reviewers disagree on primary lineage (organizational_management versus engineering_design). The defining operation is: Reviews an object, interface, or system before cosmetic skinning so teams can inspect structure, affordances, and material constraints directly. The researched NASA Systems Engineering Handbook establishes that systems engineering uses prototypes, design reviews, verification gates, margins, and feedback to expose risk before commitment. That source therefore supports engineering design as the historical origin. organizational management remains in the uncapped alternates where it contributes a formative practice, but application or governance is not itself proof of origin. origin_mode=convergent records lineage construction; domain_reach=multi_domain separately records later applicability.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; medium confidence.
Sources consulted:
Notes¶
[n1] The aesthetic-usability effect — people (reviewers included) perceive more attractive designs as more usable, which biases judgment toward polish and away from underlying structure. ↩