Hybrid Prototype¶
Prototype — instantiates Conceptual Blending for Innovation
Builds the blend as a small working artifact or scenario so its coherence and usefulness can be tested in the world rather than argued on paper.
The Hybrid Prototype takes a blend that so far exists only as a description and materializes it — a rough artifact, a running mock-up, a service script acted out, a single-location pilot — precisely so its coherence and usefulness can be tested empirically rather than debated. Its defining move is embodiment: a blend can read as coherent on a canvas and still fall apart the moment someone tries to actually use it, because the friction between the two source logics only shows up in the doing. The prototype is deliberately minimal — the smallest build that exposes the blend's riskiest assumption — and it is for testing, not for shipping. What it uniquely contributes is contact with reality: it turns "does this hybrid hold together and help?" from an argument into an observation.
Example¶
A restaurant group has a blend on paper: combine a vending automat (self-serve, instant, mechanized) with a chef's tasting menu (curated sequence, high craft, guided pacing) into a "curated automat" where diners pull chef-designed courses from a wall of little glass doors, in a set order, at their own speed. It sounds elegant in the deck. Rather than build a restaurant, the team builds a hybrid prototype: one four-door cabinet in a corner of an existing venue, stocked with a four-course tasting sequence, run for three weekend services.
Reality talks back fast. The coherence question — can "instant self-serve" and "guided pacing" actually coexist? — surfaces a real clash: diners open all four doors at once and eat the courses out of sequence, collapsing the tasting-menu logic the blend depended on. The team learns the blend only coheres if the doors unlock in order, a mechanism the paper concept never mentioned. The usefulness question — do guests find this better than either a normal automat or a normal tasting menu? — gets a mixed but real answer: novelty draws them, but they miss a server's narration. The prototype thus does what no review could: it shows exactly where the two logics fight and whether the fight is worth resolving. (The historical Horn & Hardart Automat is the real automat lineage the concept riffs on.)[n1]
How it works¶
The prototype is built to interrogate, not to impress. First, isolate the riskiest blend assumption — the one place the two source logics most plausibly conflict — and design the build around exposing it (here, whether self-serve and guided pacing can coexist). Second, build the minimum embodiment that puts a real user in contact with that assumption: one cabinet, not a chain. Third, observe coherence in use: watch whether the blended logic holds when someone actually operates it, or whether it fractures into its parts. Fourth, observe usefulness: whether real users get value the source concepts couldn't give them. The discipline is that the prototype must be able to fail visibly — a build too polished or too padded to break tells you nothing, so the design centers the assumption most likely to collapse.
Tuning parameters¶
- Fidelity — a paper/role-play mock-up versus a working build. Higher fidelity tests coherence more honestly but costs more and risks over-investing before the concept is validated.
- Scope — probing one assumption versus embodying the whole blend. Narrow probes fail fast and cheap; whole-blend builds test integration but blur which part broke.
- Realism of use — colleagues simulating versus real users in a live setting. Real users surface genuine friction; simulations are cheaper but flatter the concept.
- Run length — a single session versus a multi-week pilot. Longer runs catch novelty-fade and operational drift; short runs catch first-contact breakage.
- Instrumentation — how much you measure versus merely watch. Heavy instrumentation sharpens the usefulness read but can slow iteration.
When it helps, and when it misleads¶
Its strength is empirical settlement: it ends paper arguments about whether a blend "works" by letting reality answer, and it catches the coherence failures — like out-of-order courses — that no amount of review foresees. It embodies the maker's principle that a rough working artifact teaches more than a polished specification.
Its failure mode is the prototype that can't fail: built too padded, too staffed, or too polished, it validates the concept by hiding exactly the friction it was meant to expose. A related misuse is reading novelty as usefulness — users are drawn to a strange hybrid at first contact, and mistaking that curiosity for durable value greenlights a blend that fades. The guarding discipline is to design the build around the riskiest assumption so it can break, and to test usefulness against a real alternative and over enough time that first-contact novelty wears off before the verdict is taken.
How it implements the components¶
This mechanism realizes the embodied-test face of the archetype:
blended_space— it renders the hybrid concept as a concrete, operable thing rather than a description.prototype_or_probe— the minimal build is itself the probe, designed to expose the blend's riskiest assumption in use.coherence_test— it observes empirically whether the two source logics actually cohere when someone operates the blend (do the courses stay in sequence?).usefulness_test— it checks against a real alternative whether users get value the source concepts couldn't provide.
It does not perform the upstream cross_space_mapping or selective_projection that produce the concept — that is Concept Blend Canvas's work — nor the analytic risk_review of imported hazards, which belongs to Blend Coherence Review; the prototype tests a blend by building it, not by analyzing or constructing it on paper.
Related¶
- Instantiates: Conceptual Blending for Innovation — supplies the empirical, build-and-observe route to testing a blend.
- Consumes: Concept Blend Canvas supplies the specified concept the prototype embodies.
- Sibling mechanisms: Concept Blend Canvas · Blend Coherence Review · Design Mashup Workshop · Cross-Domain Innovation Sprint · Business Model Pattern Mixing · Interdisciplinary Model Synthesis · Forced Connection Exercise · Metaphorical Blend Prompt
Editorial Notes¶
Form Classification¶
Form family: Experiment, Test & Rehearsal
Rationale: Hybrid Prototype operates as a bounded trial, probe, simulation, or rehearsal that generates evidence from performance because it builds the blend as a small working artifact or scenario so its coherence and usefulness can be tested in the world rather than argued on paper
Independent corroboration: The frozen evidence defines Hybrid Prototype as 'Builds the blend as a small working artifact or scenario so its coherence and usefulness can be tested in the world rather than argued on paper', so its operative form is Experiment, Test & Rehearsal.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Engineering & Design
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Building the smallest embodied artifact that exposes a concept's riskiest interaction is a canonical design-prototyping move.
Related originating lineages:
- Human-Computer Interaction — Experience prototyping materially tests whether users understand and accept the blended interaction.
- Innovation & Entrepreneurship — Retained as a formative lineage because the independent reviewer identified it as primary: Combining established and novel delivery modes in a testable artifact is a product-innovation and venture experimentation practice.
Review resolution: NASA’s engineering design process places prototyping and testing inside iterative product validation. Innovation practice supplies business and desirability experiments, but construction of mixed-fidelity technical prototypes is rooted in engineering design. The retained alternate domains identify independent or materially shaping provenance, not downstream reach alone. domain_reach=multi_domain because the mechanism has independent established use in several fields. The encyclopedia entry deliberately composes those lineages.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
- https://www.jpl.nasa.gov/edu/resources/image/engineering-design-process-flow-chart/ — NASA/JPL engineering design process showing iterative prototype construction and testing.
Notes¶
[n1] The Horn & Hardart Automat, which operated in Philadelphia and New York from the early twentieth century, served prepared dishes from coin-operated glass compartments — a real self-serve, mechanized dining format, and the historical source-space this example's blend riffs on. ↩