The framing problem
UX and UI are among the most misappropriated terms in the technology industry. They are used interchangeably by product managers, conflated by engineers, and — increasingly — treated as synonymous by organisations that should know better. For practitioners, this conflation is not merely a semantic nuisance. It has material consequences: misallocated budgets, under-resourced research phases, and interface decisions made in the absence of behavioural evidence.
Precision in language reflects precision in practice. User Experience design concerns itself with the structural and behavioural dimensions of a product — the logic of flows, the architecture of information, the conditions under which decisions are made. User Interface design operates at the perceptual layer — the visual grammar through which that structure is rendered legible, navigable, and compelling. Both are necessary. Neither is sufficient without the other.
UI craft: from visual to systemic
The UI discipline has undergone a structural transformation over the past decade. Where it once operated at the level of individual screens — colour choices, type treatments, icon families — it now operates primarily at the level of systems. The proliferation of design systems, component libraries, and token-based architectures has shifted the practitioner’s primary concern from “how does this look?” to “how does this scale?”
This is not a diminishment of the craft. It is a maturation. The practitioner who understands why a spacing token of 8px creates different cognitive rhythm than one of 12px, or who can articulate the accessibility implications of a 3.5:1 contrast ratio against WCAG AA, is operating at a level of rigour that purely aesthetic judgement cannot reach.
The research imperative
No aspect of UX practice is more consistently under-resourced than user research. This is, in part, a product of the discipline’s own success: as designers have become more embedded in product teams, the pressure to move quickly has compressed discovery phases. The consequence is a body of interface decisions built on inference rather than evidence.
The most effective practitioners treat research not as a phase but as a posture — a continuous orientation toward behavioural data that informs decisions at every stage of the product lifecycle. This requires both methodological fluency and organisational courage: the willingness to surface findings that complicate prevailing assumptions.