UX Glossary · S
Stakeholder
Anyone with an interest in the outcome, which usually includes people who will never use the product.
A stakeholder is anyone affected by, or able to affect, a project: executives, product managers, engineers, sales, support, legal, compliance, and the users themselves.
Why the word is worth keeping precise
Because “stakeholder” is frequently used to mean “the person who can veto this”, and that usage quietly removes users from the set. Keeping users inside the definition is a useful discipline, since their interest is usually the least represented in the room.
What stakeholder research gets you
Interviewing internal stakeholders early is cheap and disproportionately useful. It surfaces the constraints nobody documented: the regulation that rules out an approach, the contract that fixes a workflow, the previous attempt that failed and why, and the disagreements between departments that will otherwise be discovered halfway through.
It also identifies who has to agree for the work to ship. Discovering a veto holder late is one of the more expensive project failures, and it is entirely avoidable.
The conflict to expect
In enterprise and industrial products the buyer and the end user are different people with different incentives. The buyer evaluates a feature list; the user lives with the interface. A design that satisfies only the first sells and is resented.
In practice
Map who signs, who administers, who operates and who is affected. If those are four different people, the design has four audiences and one of them has no voice by default.