Marcus Andrey Study
Ler em português Library

Framework · Influence & change · 3 min read

Kotter 8 steps

John Kotter's eight steps for leading organisational change, from creating urgency to anchoring the change in culture, adapted to building a UX practice.

  1. 1Urgency

    Share evidence of inconsistency, duplicated work and user pain.

    e.g. Five different date pickers
  2. 2Coalition

    Designers plus two or three influential product managers or dev leads.

    e.g. The PMs who feel it most
  3. 3Vision

    A shared picture of the practice you want, co-created.

    e.g. "One way to do common things"
  4. 4Communicate

    Show & tell, wiki, repeated in every forum.

    e.g. A slot in every show & tell
  1. 5Obstacles

    Remove what blocks people: tools, access, time for practice work.

    e.g. Library access for all teams
  2. 6Quick wins

    Visible early results that build credibility.

    e.g. First shared pattern in use
  3. 7Sustain

    Use the credibility to expand: more teams, a contribution model.

    e.g. Teams add their own patterns
  4. 8Anchor

    Make it normal through rituals, onboarding and the career ladder.

    e.g. Part of every designer's onboarding
John Kotter's eight steps for leading change, adapted to building a UX practice.

Use it when

  • You are introducing a design system, a shared critique ritual or a new research practice across several teams.
  • You are planning a tool migration and want more than a training session and a deadline.
  • You want to retell a past change, such as a tool migration, as a clear leadership story.

How to use it

  1. Create urgency with evidence. Share concrete signs of the problem: inconsistency, duplicated work, user pain. Use screenshots, numbers and user clips, not opinions. Output: a short evidence pack that makes "doing nothing" feel costly.
  2. Build a guiding coalition and form the vision. Bring your designers together with two or three influential product managers or dev leads. Co-create a shared picture of the practice you want, for example a practice model like the one in Design your UX practice. Output: a named coalition and a vision you can say in two sentences.
  3. Communicate the vision, everywhere, often. Use show & tell, the wiki and every forum you have. Repeat it more than feels necessary. Output: a communication plan with recurring slots.
  4. Remove obstacles. Find what stops people: missing tools, no access, no time for practice work. Fix the biggest one yourself or with your manager. Output: a list of obstacles with owners.
  5. Generate short-term wins, then sustain. Plan an early, visible win, such as a first cross-team critique or the first shared pattern. Celebrate it, then use the credibility to expand: more teams, a contribution model. Output: one win within the first months, and a plan for the next teams.
  6. Anchor it in culture. Make the change the normal way of working: rituals, onboarding for new people, and expectations in the career ladder. Output: the change written into onboarding and role expectations.

Worked example

A UX lead on an internal operations platform with 6 product teams introduces a shared design system. The table below shows the adapted steps.

Step What the lead did
1. Create urgency Showed five different date pickers across products, and support tickets caused by them.
2. Build a guiding coalition Two senior designers, the frontend lead and two product managers who felt the pain most.
3. Form a vision "One way to do common things, so teams spend time on real problems." Co-created in a workshop.
4. Communicate the vision A slot in every monthly show & tell, a wiki page, repeated in planning meetings.
5. Remove obstacles Got the design tool library set up for all teams and agreed time for contribution work.
6. Generate short-term wins A shared table component used by two teams, with fewer support tickets. Presented in show & tell.
7. Sustain acceleration Three more teams adopted it; a contribution model let them add patterns.
8. Anchor in culture Design-system use became part of onboarding and of the designer career ladder.

Watch out for

  • Skipping urgency. If people don't feel the problem, the vision sounds like extra work. Start with evidence.
  • A coalition of only designers. Without product and engineering leads, the change stays a "design thing". Include people with influence outside UX.
  • Declaring victory too early. One successful pilot is a short-term win, not the finish. Keep going until it is in onboarding and the career ladder.
  • Ignoring the individual. Kotter works at the organisation level. Use ADKAR to see where each person is stuck.

Template

Use this to plan a change, or to retell one you led.

Change:

1. Urgency          Evidence I will show:
2. Coalition        Who (incl. 2-3 non-designers):
3. Vision           In two sentences:
4. Communicate      Where and how often:
5. Obstacles        Top 3, with owners:
6. Short-term win   What, by when, how we'll show it:
7. Sustain          Next teams / contribution model:
8. Anchor           Rituals / onboarding / career ladder:
Source
John Kotter

"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