Affordance Discovery Prototype¶
Exploratory prototype — instantiates Legacy-Form Refashioning
A throwaway build whose only job is to find out what the new substrate can do — and which inherited constraints it can safely drop — before the real architecture freezes around old assumptions.
An Affordance Discovery Prototype is a deliberately disposable build, made before commitment, whose sole purpose is to learn what the new substrate can do that the old one could not — and to test which inherited constraints are real rather than merely copied — so the eventual architecture is not silently shaped by old-medium assumptions. Its defining property is that it produces knowledge, not a product: the output is a ranked backlog of affordance bets that were validated, killed, or deferred, and the throwaway itself is expected to be discarded. It answers the question the archetype most fears going unasked — what does this medium alone do well? — while there is still time to design around the answer.
Example¶
A city museum is building a virtual-reality version of a fragile antiquities gallery and is tempted to reproduce the physical gallery one-to-one: glass cases, roped-off vantage points, a printed plaque beside each object. Before committing the platform, a two-person team throws together three rough VR sketches whose only job is discovery. The first lets a visitor scale an amphora to the size of a room and walk inside it — impossible in glass. The second deliberately violates the old "one viewer at a time, do not touch, fixed vantage" constraints to see whether anything actually breaks when several visitors handle the same reconstructed object together; nothing does. The third tests whether the skeuomorphic wall-plaque is even wanted in VR, and finds visitors ignore it. None of these ships. The team writes up a ranked backlog — scale manipulation: high value, feasible; multi-user co-presence: high value, hard; floating plaque text: low value, drop — and only then designs the real exhibit around the winners.
How it works¶
- Build cheap and disposable. Each probe is low-fidelity and single-purpose, made to be thrown away; polish is a signal the team has drifted from discovery to production.
- Test the constraint, not just the feature. For each inherited constraint, build a probe that deliberately breaks it and watch whether anything of value is lost — separating real requirements from copied habits.
- Map what proved real. Catalogue which native affordances turned out to be genuine, valuable, and feasible on this substrate — and which were mirages.
- Rank into a backlog. Record every affordance bet as validated, killed, or deferred, so the architecture team inherits a prioritised menu rather than a pile of demos.
Tuning parameters¶
- Fidelity ceiling — how rough each probe is allowed to be. A hard ceiling protects disposability; raising it produces more convincing demos but invites the prototype to be promoted into production.
- Probe scope — one affordance per build versus bundled experiments. Isolated probes give clean signal; bundles are faster but confound which bet actually paid off.
- Kill criteria — how quickly a disproved affordance is dropped. Fast kills keep the backlog honest; slow ones let sunk effort masquerade as evidence.
- Exploration horizon — how far past the current release the backlog reaches. A long horizon surfaces future affordances but risks discovering things no near-term user needs.
When it helps, and when it misleads¶
Its strength is preventing premature architectural commitment: it buys cheap, early evidence about the substrate before the design hardens, so old assumptions do not quietly become load-bearing walls. Failure here is nearly free, which is the whole point.
Its failure mode is prototype creep — the disposable build is admired, then promoted to production, carrying its throwaway shortcuts into the foundation it was meant to inform. A second, subtler failure is discovering affordances that are possible but not wanted: novelty for its own sake, an amphora you can walk inside that no visitor cares to.[n1] The classic misuse is skipping the constraint-breaking probes and only demoing shiny new features, which leaves the inherited constraints untested and free to smuggle themselves into the architecture. The guarding discipline is to keep the build genuinely disposable and to validate value, not just possibility — every backlog entry records not "we could" but "users wanted, and it was feasible."
How it implements the components¶
affordance_experiment_backlog— its primary output: a living, ranked list of native-affordance bets, each marked validated, killed, or deferred, that the architecture team builds on.substrate_affordance_map— each probe fills in the map of what the new substrate can genuinely do that the old form could not.inherited_constraint_filter— every constraint-breaking probe tests whether an old-medium limit is a real requirement or a copied habit, filtering the inheritance before it hardens.
It does not ship a polished, public release that stabilises the winning affordances into supported features (native_affordance_activation) — that is Substrate-Native Showcase Release; the prototype discovers, the showcase activates. Nor does it keep the standing rationale for what was ultimately kept or dropped (lineage_and_rationale_record); that is Design Rationale Changelog.
Related¶
- Instantiates: Legacy-Form Refashioning — supplies the pre-commitment discovery that keeps old-medium assumptions from freezing the new architecture.
- Sibling mechanisms: Skeuomorphic Onboarding Interface · Side-by-Side Legacy / Native Mode · Legacy Pattern Deprecation Schedule · Format Crosswalk and Migration Guide · Substrate-Native Showcase Release · User Readiness Signal Panel · Design Rationale Changelog
Editorial Notes¶
Form Classification¶
Form family: Experiment, Test & Rehearsal
Rationale: The mechanism is a throwaway build whose only job is to find out what the new substrate can do — and which inherited constraints it can safely drop — before the real architecture freezes around old assumptions, so its operative form is an evidence-generating test, experiment, or rehearsal.
Independent corroboration: The frozen evidence defines Affordance Discovery Prototype as 'A throwaway build whose only job is to find out what the new substrate can do — and which inherited constraints it can safely drop — before the real architecture freezes around old assumptions', so its operative form is Experiment, Test & Rehearsal.
Nearest alternative: Interface, Display & Cue — The throwaway build is used specifically to discover capabilities before implementation, so it is an exploratory test rather than the final interface.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Engineering & Design
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Exploratory prototyping in design engineering builds disposable artifacts to discover a new material or medium's capabilities before architecture and requirements freeze.
Related originating lineages:
- Human-Computer Interaction — Experience prototyping tests which possible actions users perceive, value, and can successfully perform on the new substrate.
- Innovation & Entrepreneurship — Lean experimentation treats the prototype as a low-cost learning instrument whose output is validated or killed bets, not production code.
- Psychology — Ecological affordance theory distinguishes genuine agent-relative action possibilities from properties inherited only by label or analogy.
Review resolution: Disposable exploratory prototyping is engineering-led; HCI affordance testing, lean experimentation, and ecological psychology materially shape its knowledge-before-commitment purpose.
Attribution caveat: The throwaway knowledge-producing build is engineering-led, while the question it asks is framed by affordance theory and user research.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] Affordance — in the sense of J. J. Gibson and Donald Norman, the action possibilities a thing offers an agent. A discovery prototype exists to find the new substrate's genuine affordances rather than to reproduce the old medium's; the trap is mistaking a merely-possible action for one anyone actually wants. ↩