UX Maturity = the extent to which a company is "willing to do" and "able to do well" user-centered design. It does not measure how good a single design draft is, but measures the entire organization's capability and willingness toward user experience: whether research/design standards are good enough and consistent, whether people, tools, and processes are in place, whether leadership and culture can support it, and whether it can continue to be done well in the future.
NN/g updated this model in 2021, with two interlocking frameworks at its core:
(1) 6 Stages / Levels — a maturity map from "zero presence" to "organizational soul":Absent → Limited → Emergent → Structured → Integrated → User-Driven. It answers "what level are we at now, and where do we go next".
(2) 4 Factors — each stage is examined across four dimensions simultaneously:Strategy (senior decision-making before work starts), Culture (whether the organization understands and recognizes UX), Process (how research and design are conducted), Outcomes (whether the output is effective and whether it is measured). It answers "why we are stuck at this level, and which leg we need to strengthen".
Key reminder (third core axis):This is not a ladder that can only be climbed upward, but a Living System — it grows non-linearly, different teams progress at different rates, it can regress, and it relies on daily care rather than "checking in to level up". Using it as a ranking tool will almost certainly lead you astray.
The full text is divided into five parts: ① Foundation of the 4 factors (why these four legs) → ② Master table of the 6 stages (see everything in one view: characteristics / signals / typical patterns / advancement actions) → ③ Per-stage mindsets and counterexamples (the most common pitfalls at each level) → ④ Living system perspective (five pitfalls of ladder thinking vs five practices of living systems + four real cases) → ⑤ How to self-assess + how to advance.
I. Foundation: 4 Factors and Subfactors
Improving maturity is not as simple as "hiring a designer"; you need to grow simultaneously on all four legs. Each leg is broken down into several subfactors,and each subfactor contributes equally to its parent factor(no single one is more important); the four legs together determine overall maturity. This also serves as a diagnostic tool: when stuck, you can find weak points by checking each subfactor one by one.
| Factor (EN / CN) | One-sentence positioning | Subfactors (explained one by one) |
|---|---|---|
| Strategy | Senior decision-making and planning before work starts, which determines whether UX goals can be achieved | Vision: clear user-centered goals that guide internal decisions (e.g., annual goals, leadership strategic pillars) · Planning & Prioritization: whether UX work is seriously scheduled and prioritized · Budget: resources invested in UX (people + time) |
| Culture | The organization's understanding, recognition, and support of UX | Awareness: whether people inside and outside the organization know what UX is and what benefits it brings · Appreciation & Support: whether UX is respected and supported outside the UX team · Competency: whether UX skills are cultivated and defined within the organization (whether there are dedicated UX roles, recruitment practices) · Adaptability: whether strategy and practice are flexible and adjustable |
| Process | How all UX work is carried out (research / design / content) | Methods: whether user-centered techniques run through the product lifecycle (qualitative and quantitative research, iterative improvement) · Collaboration: whether the UX team collaborates with other departments · Consistency: whether there are shared systems / frameworks / tools that are used appropriately |
| Outcomes | The results produced by UX research and design, and whether they are measured, and whether it is being measured | Impact of Design: from the user's perspective, the quality and effectiveness of implemented designs · Measurement: whether there are mechanisms to track user-centered metrics |
Why emphasize "growing all four legs simultaneously": A common maturity pitfall is "limping forward" — for example, thinking you are very mature just because you have a design system (one leg of Process), while ignoring misaligned culture and lack of leadership buy-in. This is exactly the "mistaking tools for maturity" trap discussed later in the living system chapter.How to use: Treat these four factors as fixed agenda items in retrospectives (explore Strategy / Culture / Process / Outcomes each time), and you will continuously identify friction points.
II. Master Table of the 6 Levels
The table below is the core of the entire article. How to read it:First use "characteristics + visible signals" to locate which level you are at, then look at "advancement actions" to know what to do next. Note that higher stages are not necessarily better, nor are they an end point — see Chapter 4 on the living system perspective.
| Stage (EN / CN) | One-sentence characteristic | Signals you will see (behavioral level) | Quick sketch of four-factor status | Who commonly stays here | Core action to advance to the next stage |
|---|---|---|---|---|---|
| 1 Absent | "Zero presence" of UX — no one values it, no activities, and people even think they don't need it | Products are development-led; design exists only to "look pretty"; there is no time for research and testing in plans; people who bring up "users" are seen as wasting time | Almost all four dimensions are blank: no UX agenda in Strategy / ignorance or bias in Culture ("it's just making the interface pretty") / no Process / no Outcomes | Non-tech traditional industries, early-stage startups, long-established companies with traditional working methods | Awakening + education: share a UX article, host a lunch & learn, talk to a few users before making decisions, build alliances with influential internal stakeholders — the goal is to bring "users" into the company's language, not to build processes immediately |
| 2 Limited | UX is budding — there is awareness and action, but it is sporadic, scattered, and unstructured | A few individual designers/supervisors are pushing it; projects mention "do some research" "talk to users" but it is perfunctory; surveys/focus groups are passed off as user testing | Strategy: "focus on users" is mentioned in vision but is only a slogan, resources are ranked last (done with "leftover money") / Culture: people have heard of UX but understand it inconsistently / Process: specious practices (heuristic evaluation treated as research, executed by non-professionals) / Outcomes: there is output but metrics are superficial (only looking at click-through rate / time on page) | Most companies, with remaining departments still stuck at Stage 1 | Synchronize Culture + Process: communicate value to senior leadership in their language (tell cost-focused leaders "good UX reduces complaints", tell growth-focused leaders "good experience improves retention"); cultivate 2-3 allies instead of fighting alone; do 1-2 small projects but do them right and produce high-quality models(use user journey maps instead of brainstorming, usability testing instead of heuristic evaluation) |
| 3 Emergent | "Semi-mature" — there are people doing it full-time, several projects have positive feedback, but efforts are scattered, lack unified direction, and are the first to be cut when resources are tight | There are dedicated researchers; UX has been incorporated into the development process but only appears in mid-to-late stages, research is mostly post-hoc remediation; tools and design systems are scattered across teams | Strategy: vision mentions "user-centric" but lacks definition and executable strategy, short-term wins are prioritized / Culture: there are supporters but most people are wait-and-see, distrust qualitative research / Process: fragmented participation, collaboration gaps / Outcomes: improvements are visible but local, metrics are siloed by team | Large enterprises, especially in traditional industries such as finance and healthcare, are very likely to be stuck here long-term | Systematization + consensus culture: turn methods into processes all teams can follow (build design systems/research repositories, unify design principles, hold regular UX sync meetings, introduce DesignOps/ResearchOps); provide basic training for non-UX roles, build internal mentorship programs; use "small wins" from small pilots to exchange for resources |
| 4 Structured | UX shifts from "gaining support" to "formal institution" — there are professional teams, leadership recognition, rules for design to follow, and research runs through the whole process | There is a complete UX team, UX becomes part of company language; cross-departmental collaboration is frequent; design systems/Personas/workshops are used; UX participates in agile ceremonies | Strategy: vision includes "user-centered" but is insufficiently communicated, research is mostly "reactive", priorities are still ranked by business metrics / Culture: generally recognized but a few leaders hold reservations, some business lines have no UX, career paths are incomplete / Process: there are formal processes but "people know they should do it but don't do it right" / Outcomes: quality begins to be systematically tracked, metrics include usability and accessibility, but execution varies | Most well-functioning companies are at this level | Optimize the flexibility and scalability of the system(not building more rules): make all UX activities traceable back to the company vision; integrate horizontally to reduce duplication (unify knowledge bases/research archives); adaptive processes ("one system for multiple uses", allow business lines to flexibly adjust within a shared framework); strengthen career development and mentorship; use unified metrics (NPS/task success rate/usability improvements) so leadership continuously sees business value |
| 5 Integrated | UX becomes culture — people no longer discuss "whether to do it", but "how to do it better"; UX is a regular part of business and strategy | Product/R&D/Marketing/Customer Service all understand who users are and what they care about; UX does not belong to a single department, it is driven by conviction; DesignOps/ResearchOps continuously optimize | Strategy: Vision and metrics resonate, business goals and user goals mutually reinforce each other, planned investment in future UX growth / Culture: User awareness is a shared consensus, HR systems are mature (role standards / growth paths / competency models) / Process: Methods are mature and flexible, cross-disciplinary collaboration is the norm / Outcomes: Design value is proven with data, user metrics are closely tied to company direction and tracked regularly | The target state most companies should strive to reach(At this stage, UX effectively helps achieve business goals) | Moving from "user-centered" to "user-first": From outcome-oriented to meaning-oriented (making user goals a core input to business strategy, rather than an afterthought to NPS); letting the vision permeate every layer of decision-making; building a co-creation culture (non-UX roles also participate in research); driving continuous evolution through training, communities, and sharing sessions |
| 6 User-Driven | UX becomes the soul of the organization — not just methods and processes, but a value system and decision logic; user research drives strategy, investment, and innovation | User research must be conducted before any new project starts; no project launches without understanding users; sufficient and sustained budget (improving methods, external sharing); research findings, methods, and tools are shared across the entire organization | Strategy: From business-oriented to user-oriented, what to spend money on and what to do first are entirely determined by user research / Culture: UX is a "belief" rather than a "function," leaders rely on UX for decision-making, promotion criteria assess "whether user value is reflected" / Process: Fully operational yet dynamically evolving, standardized yet flexible / Outcomes: Producing the best design in the industry, imitated by peers, the standard for measuring UX = the standard for measuring company success | Very few companies reach this stage, and it is difficult to sustain long-term | The goal is no longer "advancing" but maintaining the peak: Repeatedly emphasizing user value, holding managers accountable for culture (incorporating it into performance reviews), publicly recognizing user-centric behaviors, regularly measuring "cultural temperature";Dropping back to Stage 5 is not considered failure— remember the height once reached, and work to get back there |
Stage 5 vs Stage 6 is the most critical dividing line in the entire model; be sure to distinguish them clearly:
- Stage 5: UX serves business goals(User satisfaction is a metric used to help the company make money) — this is a realistic and achievable ideal state.
- Stage 6: Business goals originate from user value(User needs come first, then business decisions) — this is the highest state, but very fragile: A technology company may have been fully user-centered 10 years ago; as the business grows, gets acquired, and leadership and culture change, when business metrics such as "conversion rate" replace user-centered thinking, it will fall back to Stage 4 or 3. Therefore, all effort at Stage 6 is focused on "preventing regression."
III. Per-stage Mindsets and Counterexamples (The Most Common Pitfalls at Each Level)
The main table shows "where to go," while this section shows "don't fool yourself at this level." Each stage has a specific cognitive trap.
| Stage | Mindset for this level (why) | Most common pitfalls / counterexamples |
|---|---|---|
| 1 Absent | Ignite awareness, don't overthrow the system— Make "users" part of the company's language through small actions | Even if some developers know UX is important and want to do it well, if the company does not provide methods, resources, or support, it is still Stage 1 (awareness ≠ capability); mistakenly believing "startups naturally understand users" — if founders lack awareness, budgets are tight, and roles are chaotic, UX will still be ignored |
| 2 Limited | From "doing UX" to "doing UX right"— Even if you only do one or two small projects, do them with high quality to become internal examples | Champion-led type: Driven by a powerful leader; stagnates as soon as she leaves / Checklist type: Treats UX as a checklist, thinks it's done after doing it once, methods become templates, and the philosophy is lost / Siloed type: One department saves itself but efforts cannot cross departmental walls |
| 3 Emergent | Build a culture that supports UX and accumulate momentum— Don't fall into the complacency of "we're already doing UX"; in reality, it's far from enough | Tiny central UX team: Too small, too many demands, daily priority conflicts / Distributed attempts: Local success but UX people are isolated from each other, methods are inconsistent, experience cannot be shared (stuck at "local optimum") / Well-meaning misapplication type: Others imitate UX processes but use methods incorrectly, producing poor results, which reinforces the bias that "UX is useless" |
| 4 Structured | From "doing well" to "doing better"— The key is not building more systems, but optimizing flexibility and scalability | Although processes are mature, there are still strategic-level problems: insufficient leadership support, unclear responsibilities, success metrics disconnected from UX, insufficient research and iteration, over-focus on large clients rather than overall strategy / Distributed UX: Integrates quickly but lacks communication between teams → reinventing the wheel, inconsistent interface styles / Consultancy type: Processes are complete but not flexible enough when dealing with special industries or difficulty accessing users |
| 5 Integrated | Make "users" the starting point of decision-making, not an appendage of metrics— This is already the ideal state for the vast majority of organizations | Over-focusing on the process itself while neglecting actual results; or the metrics leaders care about are "not user-centered enough" — user-centered design is respected, but the factors that truly drive the business are not sufficiently user-centered. The focus is on establishing user-centered outcome metrics at the highest level of the company / Small startup teams (Lean UX): High execution, but as scale grows, discipline loosens and regression is easy |
| 6 User-Driven | Maintaining is harder than climbing— Maintain momentum, spread values, educate new employees, prevent regression | Resource constraints, conflicting goals, and internal politics can all lead to regression / Nascent enterprises: UX culture is native, but rapid expansion dilutes the culture, and new hires from low-maturity organizations weaken belief / Small mature companies: Quick awakening through leadership, but a user-centered culture takes a long time to truly stabilize; otherwise, it is easy to regress |
IV. Living System Perspective: Not a Ladder, but a Living Ecosystem (Living System, Not a Ladder)
This is the most easily misused part of the entire model. The model is drawn as a six-level ladder, so many teams treat it as a "level-up game": only thinking about "clearing to the next stage," and becoming discouraged or defensive when they regress.This is wrong. NN/g emphasizes: UX maturity is more like an ecosystem that requires continuous nurturing —growth is nonlinear, different teams/domains progress at different speeds, and maturity depends on nurturing the overall environment(pay regular attention or processes will degrade, adjust to the environment, build resilience to handle reorganizations/budget cuts/leadership changes). True maturity is reflected in daily small adjustments, effective habits, and continuous alignment, not stage numbers.
Five pitfalls of ladder thinking vs five practices of living system thinking:
| Ladder thinking (wrong) | Living system thinking (right) |
|---|---|
| Pursuing numerical rankings (e.g., a Stage 2 team is single-mindedly focused on "moving up a level") | Use rhythm instead of milestones: Turn maturity reflection into a periodic activity (e.g., monthly reviews) |
| Treating "presence" as "integration" (Stage 3 teams mistake "having UX" for "being integrated") | Accept fluctuation as normal: Maturity rises and falls; there is no need to be overly anxious |
| Treating tools as maturity (Stage 3/4 has a design system but neglects cultural alignment) | The model is a reflection tool, not a ranking tool: Use the four factors to detect friction points and opportunities |
| Assuming maturity is permanent (Stage 5/6 stops maintenance leading to regression) | Celebrate sustainability: "What was effectively maintained" is more meaningful than "what stage you advanced to" |
| Over-assessment: frequent assessments without accompanying action, leading to team fatigue | —— |
Four real-world cases (practice of maturity mindset):
| Case | Situation | Lesson |
|---|---|---|
| Financial services company: Regression caused by leadership change | Originally stable at Stage 4; after senior leadership turnover, focus shifted to delivery speed and cost control, and UX was marginalized | Lacking organizational-level support and resilience, it is difficult to maintain maturity relying solely on the team's own efforts |
| Healthcare company: Illusion of stability masks stagnation | Had established research operations and a design system, appearing close to Stage 4 on the surface, but lacked reflection; processes became routine, and learning and optimization stagnated | Stability ≠ continuous growth; without reflection mechanisms, you will stay in place or even regress |
| Global SaaS company: Over-chasing upgrade scores | After being rated Stage 2, leadership wanted to quickly "move up a level"; the team did surface work (changing slides, performing rituals) while neglecting actual practice | Treating maturity as a goal leads to "doing it for others to see" rather than genuine improvement |
| Logistics technology company: Growth without formal support | At Stage 2, a UX lead introduced the four factors as a topic in retrospective meetings, sparking bottom-up change (shared design manuals, cross-departmental user discussions) | Growth is possible without organizational-level push, as long as someone is willing to initiate conversations and nurture the environment |
Overall mindset: Stop viewing UX maturity as a "task that must be completed," and instead treat it as a "system that requires continuous maintenance." The essence of maturity is not the stage number, but whether UX practices can continue to grow and serve users amid fluctuations. It relies on continuous reflection, proactive care, and the willingness to evolve with the times — like nurturing a healthy ecosystem, it depends not on a burst of effort, but on accumulation over time.
V. How to Self-Assess + How to Advance
Self-assessment (evaluating your company's maturity)— Don't ask just one person, don't look at only one type of evidence; use multiple methods to cross-verify:
| Method | What to look at |
|---|---|
| Interviews and observation | Actual processes, team collaboration, and the real use of UX methods (not what is written in documents, but what is actually being done) |
| Document and deliverable analysis | Whether design outcomes truly reflect user-centered principles |
| Cross-departmental questionnaire | Collect perceptions and practices of UX from employees at all levels and across departments |
Two self-assessment intensities; choose based on whether you have resources on hand:
- Not yet ready for a formal assessment(no time/budget/senior support): You can still use the model for reflection — ① observe signals (what positive/negative patterns exist in daily work) ② spark conversations (use the four factors as guiding topics in retrospectives) ③ record changes (which areas are gaining attention, which are being ignored). The logistics case was initiated bottom-up exactly this way.
- Have already completed a formal assessment: More important than the assessment itself is the continuous care afterward— ① observe whether things are "drifting" (which processes are degrading) ② be wary of "habit becoming second nature" (whether former strengths have become mechanical) ③ identify external changes (whether reorganizations/strategic changes have affected UX's status).
General rules for advancement (running through the sixth column of the main table): Lower levels (1→2→3) rely on awareness and culture to break through — making people first "willing to care"; middle level (3→4) relies on systematization— turning "whoever knows does it" into "processes all teams can follow"; higher levels (4→5→6) rely on flexibility, consensus, and cultural nurturing— no longer piling up rules, but letting the vision permeate every decision and making "understanding users" a collective responsibility.Advancement at every level emphasizes "trading small wins for resources, using real cases to demonstrate value," rather than achieving it all in one step.
Sourced from NNGroup Topics / Managing UX Teams - Managing UX Teams (UX Maturity subset, 9 articles). For usability methods and heuristic evaluation, see NNGroup Usability Testing and the Ten Usability Heuristics (Complete table of 10 heuristics · Complex application use cases · User pleasure hierarchy · Testing methods: 5-user rule/recruitment/remote/task scenarios/step-by-step tasks/attitude vs behavior/4-step analysis/small-sample errors/competitive evaluation); for interaction flow patterns, refer to Apple HIG Interaction Patterns (25 flow patterns · Onboarding/input/feedback/media/system collaboration). Stage posters PDF (UX_Maturity_Model_Poster / Stage 1-6 Poster A4) and original files are kept in sources.
Sources and related materials
- NNGroup Usability Testing and the Ten Usability Heuristics (Complete table of 10 heuristics · Complex application use cases · User pleasure hierarchy · Testing methods: 5-user rule/recruitment/remote/task scenarios/step-by-step tasks/attitude vs behavior/4-step analysis/small-sample errors/competitive evaluation)
- Apple HIG Interaction Patterns (25 flow patterns · Onboarding/input/feedback/media/system collaboration)