Interface Affordance Redesign¶
Design intervention — instantiates Mental Model Mismatch Repair
Changes the labels, defaults, previews, and status cues a system emits so it stops inviting the wrong expectation, repairing the system rather than blaming the user.
Interface Affordance Redesign repairs a mismatch by changing what the system communicates rather than what the person knows. It alters the labels, defaults, previews, constraints, and status cues so the interface stops teaching the wrong model in the first place — and it engineers the new cue to teach the right prediction instead. Its defining move is a locus commitment: when the diagnosis shows the system invited a reasonable false expectation, the fair and durable repair is to fix the system, not to instruct the user to try harder. So it lives entirely on the cue side: it neither retrains people nor rewrites reference text; it re-shapes the signals the artifact emits at the moment of action, so the correct model is the one the interface makes obvious.
Example¶
A smart thermostat is set to 68°F on a cold morning, and people crank it to 85 believing a higher setting heats the room faster — a "valve" model in which the number is a throttle rather than a target. The furnace has only one speed, so 85 just overshoots and wastes energy, then the room bakes. Interface Affordance Redesign commits to a system-side fix and re-engineers the cues to teach the target model: the display now shows current 68° → target 70° as two distinct numbers, a small "reaching set point…" progress indicator appears while heating, and turning the dial past a comfort band triggers a gentle "won't heat faster — just warmer" hint. The redesigned affordance makes the correct prediction — the number is a destination, not a throttle — the intuitive one. No manual, no training session; the cue itself now carries the model.
How it works¶
- Confirm the system taught the model. Take a diagnosis showing the wrong expectation was invited by a cue (not merely held by an untrained user) — the precondition that makes a system-side locus the right call.
- Locate the misleading affordance. Pin the specific label, default, preview, or status that suggests the false prediction.
- Re-engineer the cue to carry the correct model. Change the signal so the right expectation is the one it naturally teaches — a clearer label, a truthful default, a preview of the real outcome, a constraint that blocks the wrong read.
- Design out the invitation, not just the symptom. Ensure the new cue does not merely suppress one error while seeding another nearby.
Tuning parameters¶
- Cue strength — a subtle relabel versus a hard constraint or forced preview. Stronger cues correct more reliably but add friction and can feel patronizing.
- Default vs. signal — whether to change what the system does by default or only what it shows. Changing the default repairs the outcome even for people who never read the cue; changing the signal preserves choice.
- Reversibility affordance — how loudly the interface advertises undo/recovery, which lowers the cost of a wrong prediction without changing the prediction itself.
- Discoverability vs. clutter — how prominent to make the corrective cue; louder teaches faster but crowds the interface and dilutes other signals.
When it helps, and when it misleads¶
Its strength is durability and fairness: a fixed cue corrects everyone who meets it, forever, without depending on memory or training — it turns a hidden model into a visible signifier[n1] that announces what will happen. When the system created the false expectation, this is the locus that stops re-blaming users for the system's own ambiguity.
Its failure mode is the local patch over a deep model error: renaming one button or adding one hint can suppress a single wrong prediction while the underlying analogy stays intact, so the same broken model resurfaces one screen over. Its classic misuse is cue inflation — piling on warnings and confirmations until the interface is a wall of noise that trains people to click past everything, the mismatch included. The guarding discipline is to re-check adjacent predictions after the redesign (did fixing this cue leave the neighbors consistent?) and to prefer the smallest cue that carries the correct model over the loudest one.
How it implements the components¶
correction_locus_decision— its defining commitment: repair the system's cues rather than the person, chosen because the diagnosis showed the interface invited the false expectation.model_revision_path— the redesigned affordance encodes the corrected expectation ("the number is a target, not a throttle") directly into the signal, so the right model is the one the interface teaches.
It changes the cue but does not rewrite the reference text or surface hidden edge cases in prose (assumption_map) — that is its nearest twin Documentation Revision, which repairs the words rather than the affordances — and it does not itself prove the new cue transfers to a fresh scenario (expectation_validation, Simulation-Based Correction). It also assumes the mismatch is already diagnosed (mismatch_diagnosis, Incident Mental-Model Review).
Related¶
- Instantiates: Mental Model Mismatch Repair — Interface Affordance Redesign performs the system-side repair the archetype prefers when the system taught the wrong model.
- Consumes: User Journey Diagnostics or Incident Mental-Model Review — supplies the diagnosis identifying which cue invited the false expectation.
- Sibling mechanisms: Usability Testing · Incident Mental-Model Review · User Journey Diagnostics · Documentation Revision · Simulation-Based Correction · Training Feedback Loop · Expectation Audit
Editorial Notes¶
Form Classification¶
Form family: Intervention, Treatment & Transformation
Rationale: Interface Affordance Redesign operates as a direct treatment or transformation intended to change the target state or representation because it changes the labels, defaults, previews, and status cues a system emits so it stops inviting the wrong expectation, repairing the system rather than blaming the user
Independent corroboration: The frozen evidence defines Interface Affordance Redesign as 'Changes the labels, defaults, previews, and status cues a system emits so it stops inviting the wrong expectation, repairing the system rather than blaming the user', so its operative form is Intervention, Treatment & Transformation.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Human-Computer Interaction
Origin pattern: Convergent development
Present-day reach: Multi-domain
Rationale: Changing labels, defaults, previews, and signifiers to align action with accurate expectations is canonical interaction design.
Related originating lineages:
- Cognitive Science — Mental-model and perception-action research materially explains why misleading signifiers produce systematic error.
- Psychology — Mental-model and perception research materially explains expectation errors and corrective cues.
Review resolution: Both independent reviews place the primary lineage in human_computer_interaction. The queued differences (alternate_origin_disagreement, origin_mode_disagreement, domain_reach_disagreement) concern secondary metadata rather than primary provenance. The final retains cognitive_science, psychology only where a reviewer supplied a formative-lineage rationale; this does not convert downstream applicability into origin. origin_mode=convergent because the reviewers document independently established or materially co-developing traditions. domain_reach=multi_domain records application breadth separately from provenance.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] In Don Norman's vocabulary, a signifier is a perceivable cue that tells a person what action is possible and what will result — distinct from the underlying affordance. Affordance redesign works precisely by fixing the signifiers so the interface advertises the true outcome instead of an appealing false one. ↩