the norman door and the design of understandable actions
the action begins before the hand moves
polished metal waits at the edge of a glass door. a hand closes around it, pulls, and meets resistance. the person pauses, reads the small sign, and pushes. a journey of several metres has acquired an unnecessary negotiation. the door has communicated one action while requiring another.
this is the problem commonly called a norman door, after don norman. it is a compact case study in usability because the intention is ordinary, the outcome is observable and the misleading clue is often visible. the useful lesson is broader than doors: a product must help a person discover what to do, recognise what happened and recover when their expectation was wrong.
possible action and visible explanation
an affordance concerns the relationship between an actor and an environment: what an action makes possible for that person. a signifier provides a perceivable clue. a handle may enable gripping and also suggest pulling, but those are different claims. a painted arrow can suggest movement without physically enabling it. confusing the two encourages designers to call every icon an affordance and overlook how the actual mechanism behaves.
a push plate works partly by reducing the invitation to grasp. a handle is sometimes needed for access, opening force or another condition, so removing it is not a universal solution. the aim is to align the information available to the user with the movement the mechanism requires. shape, position, labels and feedback should support the same understanding.
when an instruction belongs in the design
a common slogan suggests that good design needs no instructions. as a practical principle, that needs qualification. specialised instruments, unfamiliar operations and consequential actions may require teaching. the failure is avoidable contradiction, not the mere presence of a label. clear language can be part of a good interface, especially when a symbol alone would depend on cultural knowledge.
consider a hypothetical instrument with a button labelled start. does it start a measurement, a calibration or a motor? does a light mean the button was pressed or that the operation succeeded? a technically reliable control can still leave the user guessing. explaining the state is part of the work, rather than an optional layer added to its appearance.
testing the first encounter
observe the first action before explaining the prototype. give people a real task, including anything they must carry, read or attend to. record hesitation and the route to recovery as well as successful completion. someone may eventually open every door and still encounter a poorly designed sequence.
repeat the observation with different reach, grip and language requirements. a clue legible from an upright approach may disappear from a seated position. usability belongs to the relationship, so a successful test with one designer is evidence about that encounter rather than proof of universal understanding.
a worked design example
a hypothetical appliance has one button for two operations. a short press starts the normal cycle; holding it resets the configuration. its clean appearance conceals a significant difference. a person who presses uncertainly may perform an action they did not intend.
the team can separate the controls, require an explicit reset sequence or provide a clearly labelled alternative. those proposals solve different parts of the problem. adding a label to the existing button may improve recognition while leaving accidental activation possible. separating the operations can improve the mechanism while consuming more space.
a useful prototype review measures whether people discover the ordinary operation, recognise the consequential one and recover from a mistake. the decision should follow those observations and the importance of each action. the smallest visible interface is not necessarily the least demanding interface.
a practical exercise
photograph a confusing door or control. identify the intended action, the strongest visible clue and the first reasonable mistake. develop two revisions: one that changes the form and one that changes the information. test both without an introduction. compare first attempts, corrections and effort, then explain which revision resolves the contradiction with the least new work for the user. keep the explanation separate from your preference for its appearance.
the small pause at the threshold is useful evidence. it marks the place where the object has asked the person to finish its explanation.
a visual study
further reading and crosslinks
f/p industrial design and product development
connect the principle to research, prototyping and validation in a product development process.
f/p ux ui design for complex products and systems
extend the discussion through context of use, interaction sequences and user testing.
practical guide: choosing a UX and UI design agency
connect this topic to interface, interaction and user-experience partner selection.
planning a project in this area? discuss it with f/p design.
references
Don Norman: Signifiers, not affordances
image credits
1. Kopenhagen (DK), Christiansborg — 2017 — 1485.jpg
creator or credited source: Dietmar Rabich · CC BY-SA 4.0
image source and attribution record
scaled and JPEG encoded for Word; no creative alteration. the image retains the licence listed above.
2. Jackson Foundation Gallery door push-plate – geograph.org.uk – 7454792.jpg
creator or credited source: Elizabeth Scott · CC BY-SA 2.0
image source and attribution record
scaled and JPEG encoded for Word; no creative alteration. the image retains the licence listed above.
3. Door with both push and pull signs.jpg
creator or credited source: Robert S. Donovan from Adams, NY, USA · CC BY 2.0
image source and attribution record
scaled and JPEG encoded for Word; no creative alteration. the image retains the licence listed above.
,_Christiansborg_--_2017_--_1485.jpg){kind=link}
