Module 10 of 12 · 8 min read
Stakeholders, Influence & Change
Map your stakeholders, influence decisions without formal authority, say no well, and lead change with Kotter and ADKAR.
Why it matters
A UX lead's authority is mostly informal. Even with a title, you can't order product managers, IT leads or business owners around. You influence them. Most of what you want to change (standards, priorities, research time, a design system) depends on people who don't report to you.
New leads often fall into one of these traps:
- Waiting for permission. You assume the title will do the work. It won't.
- Arguing on UX's terms. You talk about consistency and usability while your stakeholders think in cost, risk and deadlines.
- Deciding in the meeting. You bring a proposal to a big meeting cold, and someone senior kills it in two minutes.
- Yes to everything. You promise capacity you don't have, and lose trust when you can't deliver.
This module gives you the tools to avoid all four.
1. Stakeholder mapping
Power × Interest grid
| Low interest | High interest | |
|---|---|---|
| High power | Keep satisfied: concise updates, ask for input on big decisions | Manage closely: regular 1:1s, co-create |
| Low power | Monitor | Keep informed: show & tell, newsletters |
Go deeper for key stakeholders
For each high-power stakeholder, write:
- What are they measured on? (their KPIs)
- What keeps them up at night?
- What do they currently think of UX? (ally / neutral / sceptic)
- What do they need from UX?
- What do you need from them?
- Preferred communication style (data? stories? short emails? face-to-face?)
Stakeholder interview starter (first 30 days)
- What does your team/domain need to achieve this year?
- Where do our tools help or hurt that today?
- What has your experience with UX been so far, good and bad?
- If UX could fix one thing for you in the next 6 months, what would it be?
- How would you like to work with UX? How often, in what format?
- Who else should I talk to?
2. Influence without authority
Cohen & Bradford: influence is exchange
People help you when they get something they value. Find their "currencies":
| Currency | Example |
|---|---|
| Task/results | "This reduces the support tickets your team handles" |
| Position/visibility | "Let's present this improvement to the steering group together" |
| Relationship | Regular check-ins, genuine interest in their problems |
| Personal | Recognition, learning, saving them time |
| Inspiration | Connection to a bigger mission (a better working day for the people who use your tools) |
Cialdini's principles (ethical use)
- Reciprocity: help first (tools, templates, workshops, office hours).
- Social proof: "Team A already uses it, and here are their results."
- Authority: cite evidence (NN/g, usability data, your own tests).
- Consistency: link to commitments they've already made ("you said error reduction is a goal for next year…").
- Liking: relationships built before you need them.
The pre-meeting (meeting before the meeting)
Decisions are rarely made in the meeting. Before any important proposal:
- Talk 1:1 with key stakeholders.
- Share the draft, ask for input, incorporate it.
- Walk into the meeting with no surprises and with allies.
This is a very introvert-friendly influence technique (see module 03).
3. Articulating design decisions (Tom Greever)
Frame decisions in the stakeholder's terms:
- Listen to the concern fully. Ask "why" to find the underlying need.
- Restate it: "So the worry is that users won't find the export?"
- Respond with: the goal → the decision → the reasoning → the evidence.
- Agree on next steps or a test.
Useful phrases
- "Can you help me understand what problem that solves?"
- "What would success look like for you here?"
- "We have two options with different trade-offs. Here's what we gain and lose with each."
- "I recommend A because… If we choose B, we should be aware that…"
- "Can we test both with five users this week and decide with data?"
4. Saying no (or "not yet") well
Formula: Acknowledge → Explain the constraint → Offer options → Let them choose the trade-off.
"I understand this is urgent for your release. Right now, all three designers are committed to the booking flow and the billing redesign. I see three options: we start in two weeks; we pause the billing work, which delays it by a month; or we provide design-system guidance and office hours so your developers can build it with our components and a design review. Which works best for you?"
Never just "no." Never a yes you can't deliver: don't promise capacity you don't have.
5. When business decisions conflict with UX recommendations
- Understand the business rationale. It may be legitimate (regulation, cost, deadline).
- Make the risk explicit, ideally quantified: errors, task time, support load.
- Propose mitigations: phased approach, MVP + follow-up, measure after launch.
- Escalate only if user/compliance risk is high, and do it transparently.
- Disagree and commit: once decided, support the decision and measure the outcome.
- Document the decision (decision log) so learning is possible later.
6. Communicating with senior management
- Lead with the answer (Minto Pyramid / BLUF — Bottom Line Up Front).
- One page, one ask. What decision or support do you need?
- Outcomes over outputs: "Reduced booking errors by X%", not "Redesigned 14 screens."
- Three-part status: Done / Next / Need from you.
- Numbers + one human story (a 30-second clip of a user struggling persuades more than a chart).
Executive summary template
Recommendation: [what you want them to approve]
Why now: [problem + cost of inaction, 2 lines]
What we'll do: [3 bullets]
Impact: [measurable outcome]
What we need: [budget / people / decision]
Risks & mitigations: [2 bullets]
7. Leading change
Kotter's 8 steps (adapted to a UX practice)
| Step | UX lead application |
|---|---|
| 1. Create urgency | Share evidence of inconsistency, duplicated work, user pain |
| 2. Build a guiding coalition | Designers + 2–3 influential product managers/dev leads |
| 3. Form a vision | A shared picture of the practice you want (for example a practice model like the one in Design your UX practice), co-created |
| 4. Communicate the vision | Show & tell, wiki, repeated in every forum |
| 5. Remove obstacles | Tools, access, time for practice work |
| 6. Generate short-term wins | Cross-team critique, first shared pattern |
| 7. Sustain acceleration | More teams, contribution model |
| 8. Anchor in culture | Rituals, onboarding, career ladder |
ADKAR (Prosci): individual change
Awareness → Desire → Knowledge → Ability → Reinforcement. Use it to diagnose where someone is stuck. Resistance to the design system might be a Knowledge gap (training) or a Desire gap (they see no benefit), and those need different fixes.
A tooling migration maps onto both models. Say your team moves to a new design tool. Told as a change story: urgency (friction with the old tool), coalition (a pilot team), quick win (a shared library working in the pilot within a few months), knowledge (hands-on workshops), reinforcement (the new tool becomes the standard way of working). Practise telling your own changes this way.
8. Facilitation
Full toolkit with techniques, ready-to-run agendas and remote tips: 11 — Workshop techniques.
Workshops are the lead's main tool for alignment.
- Always have: goal, agenda, roles, outputs, decision method.
- Use silent individual work before group discussion (avoids loudest-voice bias; good for introverts).
- Useful formats: affinity mapping, dot voting, 2×2 prioritisation, "How Might We," Lightning Decision Jam, Lean Coffee for retros.
- End with: decisions made, owners, next steps, written summary within 24h.
9. Practice
Evidence to collect
Keep proof in your leadership log (see 12-Month Learning Plan):
- A decision you influenced without authority: before/after, who you persuaded and how.
- A "no, but…" you handled well.
Talking about it
Sooner or later someone will ask you, "Tell me about a time you influenced a decision without formal authority", whether it's your manager in a promotion conversation, a peer lead, or a hiring panel. Prepare one story and structure it like this:
- Situation: the decision, and why you had no authority over it.
- Stakeholders: who mattered, and what they cared about (their currencies).
- What you did: the pre-meetings, the evidence, the options you offered.
- Result: what was decided, and what changed for users or the business.
- Lesson: what you'd do differently.
With your own manager, use the Done / Next / Need from you status from §6 so they can see your influence work, not just your design work.
Read / watch
Library → Influence & stakeholders: Articulating Design Decisions (Greever), Influence Without Authority (Cohen & Bradford), Leading Change (Kotter), Influence (Cialdini), NN/g stakeholder mapping & workshop facilitation articles.
Check yourself
Answer out loud, then open the section to compare.
- What's the saying-no formula? → answer
- Someone is stuck at Knowledge in ADKAR. What do you do? → answer
- How do you structure a message to senior management? → answer
Connections
← Module 9: UX Maturity & Measurement · UX Lead Course · Module 11: Workshop Techniques →
Related
- Module 11: Workshop Techniques: full facilitation toolkit
- Module 3: Personal Leadership Presence: speaking up & the pre-meeting
- Module 6: UX Strategy & Vision: speak in business outcomes
- Module 9: UX Maturity & Measurement: ROI arguments
Hubs: Frameworks index