An internal-facing persona archetype that represents a key stakeholder group — a product manager, a senior leader, a customer success manager — capturing their goals, communication style, risk tolerance, and typical objections. Stakeholder personas help designers tailor how they pitch and present work to each stakeholder type.
Common contexts
- Building a stakeholder persona for a risk-averse CFO reviewer before designing the format of a UX business case presentation
- Creating an archetype for a 'shipping velocity' product manager to anticipate and address their objections to adding a research phase to a sprint
- Mapping communication style differences between a technical lead and a marketing director to prepare two versions of the same design rationale
Use when
Build stakeholder personas when you regularly present to the same stakeholder types across multiple projects — the investment pays off when you can reuse the same communication strategy rather than rediscovering each person's priorities from scratch.
Avoid when
Don't create stakeholder personas as a way to manipulate decision-makers rather than inform them — using archetype knowledge to strategically withhold concerns or frame tradeoffs dishonestly undermines the trust that makes design influence sustainable.
Understanding a stakeholder's risk tolerance is more useful than understanding their preferences — a risk-averse executive needs evidence that change is safe before they can engage with whether it's good.
Real-world examples
- Salesforce creates stakeholder personas for their enterprise sales process (IT Admin, End User, Procurement Officer, C-Suite Sponsor), each with distinct pain points — ensuring their product UI and sales materials address all four audiences separately.
- A healthcare app team created a 'Dr Sarah' stakeholder persona representing time-pressed clinicians who would approve the app's hospital procurement, helping the design team prioritise clinical credibility signals alongside patient usability.
- The UK government's cross-department design community uses stakeholder personas to help product teams understand the civil servant decision-makers who approve digital service budgets, not just the citizens who use the services.