Definition
The user is the person a design is meant to serve. Context is the situation they are in while using it: their environment, physical state, available attention, urgency, prior knowledge, motivation, and what they were doing immediately before. Good design accounts for both, because nothing is ever used in a vacuum. The crucial move is to stop treating 'user' as a single abstract figure who resembles the designer. Real users arrive with different bodies, languages, devices, connection speeds, levels of expertise and reasons to care. A design that works for the median user and collapses at the edges has not solved the problem; it has solved the easiest part of it.
Why It Exists
Designers do not experience their own work the way anyone else does. They know where every control is, they built the mental model the interface assumes, they test on good hardware in good light without being interrupted, and they care about the product far more than any user ever will. This gap between the designer's experience and the user's is one of the most reliable sources of failure in the field, and it cannot be closed by trying harder to imagine. It is closed by watching. The whole apparatus of user research exists because introspection is an unreliable instrument for predicting other people's behavior, including for very good designers.
Examples
- →A food ordering app is often used one-handed, standing, with the other hand holding something, which changes where controls belong.
- →Emergency exit signage must be understood in smoke, in darkness and in panic, not only in a well-lit corridor.
- →A children's toy will be dropped, chewed and thrown in ways no laboratory prototype is ever tested for.
- →A payment screen used outdoors in bright sun needs far higher contrast than the same screen judged on a studio monitor.
History
Human factors and ergonomics became formal disciplines during and after the Second World War, when investigators found that many aircraft accidents attributed to pilot error were in fact caused by control and instrument layouts that invited mistakes. Identical-feeling levers placed side by side led pilots to retract the landing gear instead of the flaps, and the fix was a design change — shaped controls that could be told apart by touch — rather than more training. Researchers including Alphonse Chapanis documented this reasoning, and it produced a lasting reframing: when a competent person repeatedly makes the same mistake, the sensible explanation is the design, not the person.
In Modern Design
Contemporary UX practice formalizes user and context through research methods that get designers out of their own heads: contextual inquiry, where people are observed in their real environment; usability testing on representative tasks; journey mapping that records emotional and situational state as well as steps; and analytics that reveal where real behavior diverges from the assumed path. Accessibility standards extend the same logic to the full range of human variation in vision, hearing, motor control and cognition. Increasingly, teams also consider context of network and device — a slow connection on an aging phone is a context, and designing only for fast hardware quietly excludes a great many people.
Real-World Example
The OXO Good Grips kitchen line began in the late 1980s when Sam Farber noticed that his wife, who had arthritis, struggled with the thin metal handles standard on peelers and other tools. Rather than treating that as a niche medical requirement, the team designed for reduced hand strength as the baseline case, arriving at a thick, soft, oval handle with fins that stayed comfortable under pressure and grippy when wet. The tools sold broadly to people with no impairment at all, because a handle designed for a weak grip is simply a better handle. This is the inclusive design argument in a single object: designing for the edge improves the center.
Key Principles
- →A design succeeds or fails relative to a specific user in a specific context, never in the abstract.
- →Context includes environment, physical state, attention, urgency and prior knowledge.
- →The designer's own experience is a systematically unreliable model of the user's.
- →Repeated 'user error' by competent people is evidence about the design, not about the people.
- →Designing for the edges of human variation usually improves the experience at the center.
- →Device, connection and setting are part of context, not incidental details.
Why it matters
This is the idea that converts design from a matter of taste into a matter of evidence. Once you accept that quality is relative to user and context, 'I like it' stops being an argument and 'people in this situation succeeded at this task' starts being one. That shift is what makes design discussable across a team and defensible to a business. It also carries an ethical weight. Deciding who counts as the user is a decision about who the product is for, and every unexamined assumption — about literacy, language, device, ability, income — quietly excludes someone. Making that decision consciously is part of the work.
Then vs Now
Then
The maker and the user often shared a village, a trade and a set of conditions. A cooper knew exactly who would carry the barrel and over what ground, so context was absorbed without ever being studied.
Now
A single interface may be used across dozens of countries, languages, devices, network speeds and abilities. Context has to be deliberately researched and documented because none of it is available by default.
Try it yourself
Pick an app or object you use daily and list three contexts in which you have used it: in a hurry, in the dark, on a poor connection, while talking to someone, with cold hands. For each, note one way the design helped and one way it got in the way. Then run a simple observation. Watch one other person use something you know well, and resist the urge to help or explain. Record only what they do and where they hesitate. Almost everyone finds at least one moment where the other person's path bears no resemblance to the one they assumed was obvious.