There’s a phrase that appears in almost every UX job description, almost every design principles deck, almost every product strategy doc written in the last decade. User-centered design.It has become so ubiquitous that it functions as wallpaper. Nobody argues against it. Nobody defines it. It’s the design industry’s equivalent of “we care about quality” — a claim so universal it communicates nothing.
This matters. Because underneath the buzzword is an idea that actually changed how products got made — and the dilution of that idea has real consequences for the designers who use it as a credential and the users who are supposed to benefit from it.
The original argument was specific and genuinely radical when it was made. Don Norman and colleagues, formalizing human-centered design in the 1980s and early 90s, were pushing back against a product culture that optimized for engineering elegance over usability — systems built around what was technically possible rather than what humans could actually use. The idea that you should study people first, understand their mental models, design to match them rather than correct them — that was a meaningful intervention against a specific failure mode.
What happened next is what happens to every idea that becomes institutional. It got simplified into a process, the process became a checklist, and the checklist became something you tick before you do what you were going to do anyway.
UCD focuses on an individual problem instead of looking at the bigger picture where there can be large and unanticipated side effects [2]. As Yolanda Martin, Head of Platform Design at Farfetch, put it plainly: “User-centered design is obsolete — it’s just not enough anymore.” The critique isn’t that studying users is wrong. It’s that centering the individual user as the unit of design ignores the system the user inhabits — the other stakeholders, the downstream effects, the business realities that shape what actually ships.
There’s also a more uncomfortable version of this critique.
By applying User-Centered Design methods we are not always challenging our assumptions — we are rather looking for their confirmation [3]. The research that gets commissioned tends to validate the direction that’s already been chosen. The users who get interviewed tend to be the ones easiest to reach, who look most like the team doing the research. The insights that get surfaced tend to be the ones that translate cleanly into features. Real user-centered practice would mean sitting with findings that contradict the roadmap. In practice, it often means marshaling evidence for decisions that were already made.
This is not a character failing — it’s a structural one. UX is most impactful when its principles shape every layer of the experience — the interface and what people see on screen, as well as the system behaviour and underlying logic [4]. But in most organisations, designers are brought in after the strategic decisions are made, handed a brief, and asked to validate rather than interrogate. Calling that “user-centered design” is technically accurate and functionally misleading.
The version of the phrase worth keeping is the one that treats it as a constraint, not a credential.
Not “we do user-centered design” — as though naming the practice is the same as practicing it. But “have we actually changed anything based on what we learned about users?” Not research as decoration. Not personas as posters on a wall. The harder version: decisions that went differently because someone talked to a real person and took what they said seriously enough to act on it — even when it was inconvenient.
Most portfolios that claim user-centered design are showing you the research artifacts. The interesting question is what the research changed. If the answer is nothing — if the wireframes were already done before the interviews happened, if the insight section of the case study reads like a confirmation of the brief — then what’s being claimed isn’t a practice. It’s a vocabulary.
The phrase isn’t the problem. The pretending is.
References