Stakeholder persona

A stakeholder persona is a persona for someone other than the end user: a typical member of a group inside or around the organisation who affects, or is affected by, the product. The sales lead who has to demo it, the compliance officer who has to sign off, the support agent who will field the complaints.

Why bother

Products fail on the way to users as often as in front of them. A feature that delights customers but cannot be explained by the sales team, audited by compliance or supported by the help desk will not survive. A stakeholder persona makes those people’s needs concrete enough to design for.

It also changes the tone of internal conversations. “Legal will object” is a vague threat. “Priya reviews forty contracts a week, needs to see the change history in one place and gets blamed if an old version is sent” is a design requirement.

Stakeholder persona versus stakeholder profile

A stakeholder profile describes a specific, named person or team: their goals, their influence, their concerns. A stakeholder persona describes a type, built from several people, so it can be reused. Use the profile when you must manage a particular relationship, the persona when you design for a role.

Common mistake

Inventing these from stereotypes (“the sceptical engineer”). They deserve the same evidence as user personas: a few short conversations with real people in those roles are enough to ground one.