process & strategy
Stakeholder management
What is stakeholder management in UX?
Stakeholder management is the work of identifying everyone with an interest in or influence over a project - clients, executives, engineers, marketing, legal, and the users themselves - and engaging each appropriately so the work can succeed. For designers it's often the difference between good design that ships and good design that dies in a meeting, because the best solution still needs buy-in.
Also known as: stakeholder management, managing stakeholders, stakeholder mapping
Prefer to watch?
Watch the recap 1:22
The demo
Here are four people with a stake in your project. Drop each onto the power/interest grid and the right way to engage them appears. Same project; very different handling for each.
What this demo shows (text version)
A power/interest grid is shown, and you place four stakeholders into it: a CEO (high power, low day-to-day interest), a lead engineer (high power, high interest), a keen support agent (low power, high interest) and a distant partner (low power, low interest). As each lands in a quadrant, the demo gives the matching engagement strategy: manage closely, keep satisfied, keep informed, or monitor lightly - showing that how you engage someone depends on their influence and interest.
That's stakeholder management: identifying everyone with an interest in or influence over a project and engaging each appropriately, so good design actually ships rather than dying in a meeting. The power/interest grid tailors the approach; beyond it, involve people early for ownership, speak their language, lead with user evidence - and don't forget the user is a stakeholder too.
Great design that nobody buys into doesn't ship - so managing stakeholders is part of the job, not a distraction from it. Start by mapping who has a stake, then sort them by influence and interest: a classic power/interest grid tells you how to engage each. High power + high interest → manage closely (involve them, co-create). High power + low interest → keep satisfied (don't blindside them). Low power + high interest → keep informed (they're allies and advocates). Low power + low interest → monitor lightly. Beyond the grid: involve people early so they feel ownership (the IKEA effect), communicate in their language (business outcomes, not design jargon), back decisions with user evidence, and remember the user is the stakeholder most often missing from the room. Bring people along, and good design survives contact with the organisation.
Plot a stakeholder by how much power and how much interest they have, and the right approach falls out: manage the powerful-and-interested closely, keep the powerful-but-disengaged satisfied, keep the interested-but-junior informed, lightly monitor the rest. That's stakeholder management - and it's why good design ships or dies. The best solution still needs the right people brought along, in their language, with evidence.
Stakeholders are anyone affected by or able to affect a project: executives and budget-holders, product and engineering, marketing, sales, legal and compliance, support, partners - and, crucially, the end users, who are stakeholders too and the ones most often absent from decisions. The first step is identifying them all; the second is understanding each one's goals, concerns, influence and level of interest.
A power/interest grid is the classic tool for tailoring engagement. High influence and high interest: manage closely - involve them, collaborate, keep them bought in. High influence but low interest: keep them satisfied and informed enough that they don't derail things, without over-burdening them. Low influence but high interest: keep them informed and engaged - they make good advocates and sources of insight. Low on both: monitor with minimal effort. Engagement is matched to position, not one-size-fits-all.
The deeper craft is relational. Involve stakeholders early so they feel ownership of the outcome (the IKEA effect makes co-created decisions stick), communicate in their terms - business value, risk, outcomes - rather than design jargon, and ground design arguments in user research and evidence rather than opinion (which also defuses the "I don't like the blue" critique). Managing stakeholders well is how good design survives organisational reality; ignoring it is how strong work quietly fails to ship.