Affordance Discovery Workshop¶
Ritual — instantiates Exaptive Function Redeployment
A facilitated session that mines an existing feature for latent affordances and turns the promising ones into explicit claims about new functions it could be redeployed to serve.
Redeployment starts with a hunch that something you already have could do a job it was never built for — the way a feather that kept a dinosaur warm turned out to afford flight. Affordance Discovery Workshop is the generative front-end that makes those hunches explicit and plural. In a facilitated session it strips a feature down to what it actually affords — its capabilities read independently of its intended purpose — and then does the move that defines it: it pairs each promising affordance with a named new function and an owner who would use it. The output is not a wistful list of possibilities but a short set of claims — "this feature could serve that function for those people" — concrete enough for another mechanism to test, bound, and govern. That commitment to a claimed function is what keeps the workshop on the redeployment side of the line, rather than merely cataloguing hidden capabilities.
Example¶
A platform team owns the company's feature-flag system — the switches that turn new code on for 1% of users, then 10%, then everyone. Someone suspects it could be good for more than gradual rollouts, so they run an Affordance Discovery Workshop. On the table is that one feature; in the room are people who have never touched it — an incident responder, a billing engineer, a support lead. First they map what the system affords, stripped of its purpose: it can gate any code path, instantly, for any slice of users, from a central console, with an audit log. Then they turn affordances into explicit new-function claims — an incident "kill switch" that disables a misbehaving feature in seconds without a deploy (owned by the responder); an entitlement gate that turns paid features on per customer tier (owned by billing).
Each surviving claim names the feature, the new function, and who would run it. The workshop's whole deliverable is exactly that: a handful of owned redeployment hypotheses and the affordance map behind them — passed downstream for someone else to bound, trial, and govern rather than acted on in the room.
How it works¶
The session runs divergent, then convergent, and the convergence is the point:
- Read affordances, not features. Describe what the thing can do with its intended use deliberately set aside — the capabilities an outsider would see. Bringing in people from other functions is what surfaces affordances the owners are blind to.
- Bind each affordance to a function and an owner. A free-floating capability is not yet a claim. The workshop forces the pairing: which new function, for whom, run by whom — the step that separates it from open-ended affordance-gazing.
- Triage to a few strong claims. Kill the clever-but-ownerless ideas; keep the ones a named person will carry forward. Fewer, sharper claims beat a long wish-list.
Tuning parameters¶
- Framing breadth — how far from the original purpose you invite ideas. Wide framing surfaces surprising exaptations but floods the room with noise; narrow keeps signal but misses the leaps.
- Participant mix — insiders who know the feature versus outsiders who see it fresh. Cross-domain guests catch affordances the owners have gone blind to, at the cost of context.
- Constraint timing — how early you let inherited-constraint worries into the room. Too early smothers good ideas; too late spends effort on claims that were doomed by lineage.
- Claim bar — how much a hunch must carry (a named owner, a plausible user) before it graduates from the wall. A higher bar yields fewer but load-bearing claims.
When it helps, and when it misleads¶
Its strength is cheap optionality: it finds value already sitting in the system and turns diffuse "we could maybe…" energy into owned, testable hypotheses — usually faster and cheaper than building anything new.
Its central failure mode is over-generation of plausible-but-false uses. A workshop is very good at manufacturing convincing stories about why an affordance is a hidden purpose, and some of those affordances are mere byproducts that will not bear a real function's weight — the design equivalent of mistaking a spandrel for an intended arch.[n1] Its classic misuse is being run to rubber-stamp a redeployment someone has already decided on, generating retrofit justification instead of options. The discipline that guards against both is to make every claim name a real owner and to route it to a bounded trial for falsification — never straight to rollout.
How it implements the components¶
Affordance Discovery Workshop fills the generative, front-of-pipeline components — the ones a divergent session can actually produce:
latent_affordance_map— the inventory of what the feature affords beyond its original use, read independently of purpose.new_function_claim— each surviving affordance committed to an explicit, owned proposal that the feature serve a specific new function.
It does not bound or inventory the feature, nor grade how well it fits — that is Feature Refunctioning Audit. It does not test its own claims (that is Bounded Co-option Trial) or check whether the new use collides with the old (Dual-Function Compatibility Test).
Related¶
- Instantiates: Exaptive Function Redeployment — the workshop supplies the new-function claims the rest of the redeployment tests and governs.
- Sibling mechanisms: Feature Refunctioning Audit · Bounded Co-option Trial · Adaptation Delta Mapping · Dual-Function Compatibility Test · Legacy Feature Wrapper · Origin-Context Constraint Review · Lineage-Preserving Documentation · Negative Transfer Red Team · Purpose-Built Replacement Gate · Repurposed-Feature Monitoring Dashboard · User Appropriation Review
Editorial Notes¶
Form Classification¶
Form family: Communication, Facilitation & Learning
Rationale: The mechanism is a facilitated session that mines an existing feature for latent affordances and turns the promising ones into explicit claims about new functions it could be redeployed to serve, so its operative form is communication, facilitation, or learning exposure.
Independent corroboration: The frozen evidence defines Affordance Discovery Workshop as 'A facilitated session that mines an existing feature for latent affordances and turns the promising ones into explicit claims about new functions it could be redeployed to serve', so its operative form is Communication, Facilitation & Learning.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Engineering & Design
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Facilitated generation of new use claims from an existing feature's capabilities is chiefly a design ideation and functional-reframing practice.
Related originating lineages:
- Biology & Ecology — Exaptation supplies the formative model of a feature acquiring a function it was not selected for.
- Human-Computer Interaction — Affordance analysis supplies the agent-relative inventory of possible actions rather than treating intended purpose as the feature's only capability.
- Innovation & Entrepreneurship — Naming a user, function, and owned test turns latent capability into an innovation hypothesis.
- Psychology — The affordance concept supplies the actor-relative inventory of possible actions.
Review resolution: Design facilitation supplies the workshop form, while biological exaptation, HCI and psychological affordance theory, and innovation hypothesis ownership materially form the redeployment procedure.
Attribution caveat: The mechanism intentionally combines affordance theory and biological exaptation inside a design workshop; no single source tradition fully contains it.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; medium confidence.
Notes¶
This is deliberately not generic affordance-surfacing. A workshop that stops at "here is what this could do" has produced an affordance map and nothing more; the redeployment-specific act is committing to a claimed new function with an owner — which is precisely what makes the downstream lineage, constraint, and governance work necessary. If the room never names a function, the session belongs to a different archetype.
[n1] In evolutionary biology a spandrel is a structural byproduct later pressed into a use it wasn't selected for; Gould and Lewontin used it to warn against "just-so stories" that assume every trait is an adaptation. The workshop faces the same trap — an affordance can be an incidental side effect, not a capacity that will hold a real function under load — which is why claims are graduated to trials, not beliefs. ↩