Marcus Andrey Study
Ler em português Library

Framework · Measurement · 3 min read

UX maturity model

Nielsen Norman Group's six stages (Absent, Limited, Emergent, Structured, Integrated, User-driven), assessed across four factors, so you can place your organisation and pick the next factor to improve.

  1. 1 Absent
    Signs
    UX is ignored or doesn't exist
    For example
    Developers design screens as they build
  2. 2 Limited
    Signs
    Sporadic, unreliable UX that depends on individuals
    For example
    One designer, pulled in late
  3. 3 Emergent
    Signs
    Functional and promising, but inconsistent and inefficient
    For example
    Good work in some teams, no shared methods
  4. 4 Structured
    Signs
    Semi-systematic, effectiveness varies across teams
    For example
    Design system and research process, unevenly used
  5. 5 Integrated
    Signs
    Comprehensive, effective and pervasive
    For example
    UX metrics shape every roadmap
  6. 6 User-driven
    Signs
    Dedicated UX at all levels drives insight and outcomes
    For example
    User insight steers company strategy

Assess each stage across four factors: strategy, culture, process, outcomes.

Nielsen Norman Group's six stages of UX maturity, from Absent to User-driven.

Use it when

  • You are new in the role and need an evidence-based picture of where UX stands, instead of a gut feeling.
  • Your manager asks "How mature is our UX?" and you need a clear, honest answer.
  • You are setting yearly goals for the practice and need to choose where to invest first.

How to use it

  1. Form a hypothesis. In your first weeks, guess a stage per domain from what you see and hear. Write it down as a guess, for example "Emergent to Structured (3–4)". Output: a one-line hypothesis per domain.
  2. Run the baseline. Ask each designer and one product manager per domain to complete NN/g's free UX maturity quiz. Add 4–5 questions specific to your organisation, such as "Is there a UX request process?" or "Are usage metrics available?". Output: answers per domain. Allow two weeks.
  3. Score the four factors. For each domain, place strategy (leadership, planning, prioritisation, resourcing), culture (awareness, knowledge, growth of UX), process (methods, research, systematisation) and outcomes (UX goals, measurement, impact on decisions) on a stage. Output: a stage per factor per domain.
  4. Visualise it as a heatmap. Put domains in rows and factors in columns. Share it with your manager and product managers as a picture of the system, never of individuals. Output: a domain × factor heatmap.
  5. Choose one or two factors to move. Pick the factors that block the others most, often outcomes or process. Turn them into goals for the year. Output: one or two maturity goals with owners.
  6. Repeat every 6–12 months. Run the same baseline again and compare. Output: an updated heatmap and a short note on what changed.

Worked example

A fictional internal operations platform with 6 product teams. Before the baseline, the new lead writes down what they observe and places each factor.

Factor Signals you observe Placement
Strategy No UX goals in the product roadmap. Designers are funded per project, and each team decides alone whether it needs one. Limited (2)
Culture Product managers ask for designers early in most teams. Two teams still see UX as "making it look nice". Emergent (3)
Process A shared design system and component library exist, but research and critique happen in some teams only. Structured (4) in two teams, Emergent (3) elsewhere
Outcomes Nobody tracks task success or satisfaction. Launches are judged by delivery date. Limited (2)
How you'd place it
the organisation sits around Emergent (3) overall, with process ahead and strategy and outcomes behind. The lead treats this as a hypothesis, runs the baseline to confirm it, and picks outcomes as the first factor to move, for example by setting up Goals-Signals-Metrics for one core app.

Watch out for

  • Averaging into one number. "We are a 3" hides that process is at 4 and outcomes at 2. The gaps tell you where to act.
  • Scoring alone. Your own guess is a hypothesis. Without designers and product managers in the baseline, it is just your opinion.
  • Trying to jump stages. Moving a whole organisation up one stage usually takes years. Aim for one or two factors per year.
  • Turning it into a team ranking. A heatmap that shames one domain stops people answering honestly. Present it as the state of the system.

Template

Copy this into a doc or spreadsheet and fill one row per domain (stages 1–6).

Domain / team      | Strategy | Culture | Process | Outcomes | Notes
-------------------|----------|---------|---------|----------|------
                   |          |         |         |          |
                   |          |         |         |          |
                   |          |         |         |          |

Stages: 1 Absent · 2 Limited · 3 Emergent · 4 Structured · 5 Integrated · 6 User-driven
Hypothesis before baseline:
Factors to move this year (max 2):
Next baseline date:
Source
Nielsen Norman Group

"See on Amazon" links are affiliate links. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.

Saved only on this device.

↑ ↓ to move · Enter to open · Esc to close