Sit in enough design critiques and you start to notice a pattern. Teams describe work as "user-centered" the same way they describe it as "scalable" or "intuitive." Almost like it's a as a property the work has, not a method the team followed. The phrase has become shorthand for a general orientation toward doing good work, and like most shorthand, it has stopped meaning what it once did.

The trouble runs deeper than overuse. "User-centered design" makes a specific claim: that the practice is organized around the people who will use what gets built. The first word undermines that claim before the sentence is finished.

"User" is a relationship to a product, not a description of a person.

A user is someone defined by their function relative to your system. Strip away the product and now what, are they still a "user?" There's no such thing as a user in the absence of the thing being used. Compare that to words that name actual people: patient, parent, small business owner, commuter, first-generation college student, etc. Each of those carries history, competing demands, an existence outside the moment of interaction. "User" carries none of that. It starts from the artifact and works outward, which is the opposite of the orientation "user-centered" claims to represent.

The words a field uses to frame its work shape how that work gets done. A team designing for "users" is designing for a function. A team designing for patients managing a chronic condition is designing for people with specific histories, fears, and competing demands on their attention. The research questions shift. So do the assumptions that seem reasonable, and what the team decides it means to understand them.

The abstraction is also what makes "user-centered" so easy to claim without doing. Because "users" are already to some degree removed from real people, it becomes possible to believe you understand them through proxies: analytics dashboards, behavioral data, patterns assumed from similar products. These tools have real value, sure. They also make it possible to feel like you've done the work when you've done something that looks like it before.

Practiced this way, user-centered design becomes a credential or a check-box rather than an orientation. The phrase signals that human considerations were part of the process, which is important. Whether any actual humans were part of it is a separate question that the language doesn't force you to ask. You can describe your product as user-centered while having no direct contact with the people it's built for, and nothing in the phrase pushes back on that. Organizations exploit this gap constantly, sometimes cynically, often without realizing it.

Attempts to replace "user-centered" with "human-centered" or "people-centered" solve part of the problem and introduce others. Those terms are still abstractions, still properties claimed rather than earned. The more useful intervention is a habit of forcing specificity before the design work begins, or in some cases adjusting as you learn more.

Name the actual person. Not "users" but the specific population: parents navigating a school district's benefits system, contractors invoicing a client for the first time, patients deciding whether to fill a prescription they can't afford. When you name them, the design questions shift. The research you need shifts. The assumptions that felt obvious become things you have to verify. "User" smooths over all of that friction, and that friction is where the real design work happens.

The takeaway for practitioners: The next time you catch yourself describing your audience as "users," slow down long enough to name them, these don't have to be fully baked personas by any means. If you can't, that's a signal worth paying attention to.

The phrase isn't going anywhere. The field has too much invested in it, and it does real work in conversations where you need to establish a shared orientation quickly. But there's a difference between using "user-centered" as shorthand and hiding behind it, and that difference lives in whether you can name the actual people when the shorthand isn't enough.

Most of the time, the work reveals which one you've been doing.