There is a distinction we rarely name clearly in UX, and it shapes almost everything we do.

The observer encounters a product: they see it, form an impression, and move on.

The user inhabits it - returning to it, forming habits around it, leaning on it to accomplish things that matter to them. These are not the same relationship, and designing as though they are is one of the quieter failures in the discipline.

Designing for the user rather than the observer is not simply about adding depth or rigour; it is about orienting the work toward the right relationship from the start. There are five patterns that make this distinction visible and concrete.

It's not all visual

Some of the most striking user experiences I have encountered are extraordinary to look at: art directed with real care, visually arresting, the kind of work that earns recognition on design portfolios and awards shortlists.

They are also, in many cases, genuinely frustrating to use. This tension is one we understand in principle but repeatedly underestimate in practice; the observer responds to how something looks, the user responds to how something works, and those two responses are not the same calibration.

This is not an argument against visual craft. Quite the opposite - visual design done well plays together with usability, amplifying it rather than competing with it.

The trap is treating visual quality as a proxy for user quality, assuming that what impresses at a glance will satisfy across repeated encounters. The observer is impressed once; the user returns to the same product day after day, and what they need from those repeated visits is something entirely different from what captivates at first sight.

Different folks, different strokes

One of the quiet traps in UX is designing for a generalised user: a composite that smooths over the real variation in how people think, move through interfaces, and make decisions.

It’s easy to see how this happens. We are looking for patterns that scale; we build user personas; we run research sessions and synthesise findings into coherent pictures of behaviour.

But somewhere in that process, the actual texture of individual difference tends to flatten.

What we need, beyond understanding how our users interact, is an understanding of how they think. Not just the surface-level behaviour - the clicks, the paths, the drop-off points - but the underlying thought structures that produce that behaviour: the mental models they carry into the product, the expectations formed by prior experience, the heuristics they apply when they are uncertain. Two users performing the same task may be doing so for entirely different cognitive reasons, and a design that serves one may quietly obstruct the other.

Know thyself

Consider an expert attending a talk in their specialist domain: decades of accumulated knowledge, a well-developed sense of what matters, a set of expectations about how the territory should be mapped. Now imagine that talk has been designed not for the specialist but for an adjacent audience - one that shares some interests but brings different assumptions, different language, a different relationship to the material. The expert finds it disorienting, possibly even alienating, not because the talk is bad but because it is calibrated for someone else.

This is what happens when we design from our own worldview rather than our user's. We carry our own expectations into every product decision, and without deliberate effort, those expectations become invisible assumptions: that a certain navigation pattern feels natural (because it feels natural to us), that a particular information hierarchy makes sense (because it makes sense to us), that users will respond to the same cues we do.

The antidote is not self-erasure; it is deliberate alignment - understanding our users well enough to build a design stance that genuinely reflects their modus operandi rather than ours.

Red bad, green good

Colour conventions sit so deep in our cognitive architecture that we rarely interrogate them: red signals danger, error, urgency; green signals safety, confirmation, go. These are not design choices we invented, they are inherited from traffic systems, safety protocols, and decades of interface convention, absorbed by users long before they encounter our products. Ignoring them is not a creative decision; it is a usability cost.

But the lesson cuts further than simply following convention. In healthcare applications using the NEWS scoring system, which aggregates vital signs like respiration rate and temperature to assess patient risk, the safest possible score is displayed in grey, not green. Green, in that context, signals a moderate level of concern.

A designer who imports the standard colour convention without understanding the domain model will build something that feels right to them and misleads the user.

It is the small calibrations, correctly made, that structure a user’s experience across every interaction; and precisely because colour is so powerful, it demands scrutiny rather than assumption.

This, not that

The deepest habit of observer-centric design is assumption: assuming we know how our users operate, assuming we know what they need, assuming our experience of the product tells us something reliable about theirs. The problem is not a lack of good intent; it is a structural one.

In most projects, designers do not share the demographic profile, the domain expertise, the daily context, or the emotional relationship to the problem that their users bring. We are not our users. We rarely are.

Empathy allows us to connect with users; separating the self from the design allows us to create for them. These are related but distinct moves. Connection is relational - it requires understanding, curiosity, real attention to the specifics of how someone else experiences the world. Separation is structural - it means building discipline into the design process that prevents our own assumptions from overriding what research and observation are actually telling us.

In Summary

The difference between designing for the user and designing for the observer is ultimately the difference between those two dispositions.

We carry our own worldview into the work, always. The question is not whether that worldview shapes our decisions, it does, and will continue to - but whether we build enough rigour into our process to ensure it shapes them helpfully rather than accidentally.