UX Title Still Dominates Design Field, NN/g Survey Finds

What happened

A Nielsen Norman Group survey of 604 tech and design professionals has found that "UX" remains the default, most widely used term for the discipline, with no rival label coming close to displacing it. Proposed alternatives — including "product design," "service design" and other hybrid titles — continue to be used, but in a fragmented way, with no single term commanding anything close to consensus.

The research indicates that while practitioners have long debated whether "UX" adequately captures the scope of modern design work — spanning research, service design, content and product strategy — the profession has not converged on a replacement. Respondents cited "UX" most consistently across job titles, team names and self-description, even as many acknowledged the term's limitations.

Why it matters

Naming conventions might look like a semantic footnote, but they shape how organisations structure teams, allocate budgets and set expectations with customers and stakeholders. When a field can't agree on what to call itself, it becomes harder to standardise career paths, benchmark maturity across companies, or communicate the value of experience work to boards and clients who are outside the discipline.

For CX and service-design leaders, this matters because ambiguous terminology often maps directly onto ambiguous mandates. Teams labelled "UX" may be scoped narrowly to interface work even as they're asked to solve end-to-end service problems — a mismatch that can quietly limit influence, resourcing and impact.

By the numbers

• 604 tech and design professionals were surveyed by Nielsen Norman Group on naming conventions in the field.

The Renascence take

The persistence of "UX" as a catch-all label says less about branding fatigue and more about unresolved scope. The industry hasn't failed to find a better word — it has failed to agree on where the job actually starts and ends.

What most commentary on this misses is that the naming debate is a proxy for a deeper organisational problem: companies still treat experience work as an interface layer rather than a system-wide discipline spanning service design, operations and behavioral strategy. Renascence's view is that operators should stop waiting for the industry to settle on a title and instead define scope by outcomes — map the term used internally directly to the decisions that team is empowered to make, from journey redesign to policy change. If your "UX" team can't touch a broken refund process or an unclear pricing page, the label isn't the issue; the mandate is. Fix the mandate, and the name becomes a footnote rather than a source of friction.