Stakeholder engagement roles, and who holds each one

Roles as accountability

Most guides list stakeholder roles as job titles: sponsor, project manager, team, customer, supplier, regulator. That list describes who the stakeholders are. It does not describe who does the engaging, or who each conversation is for. I set out that first classification in internal versus external stakeholders.

This article is about the working roles inside engagement itself. There are 5, and they attach to decisions rather than org charts: sponsor, delivery lead, subject expert, affected user, decision-maker. One person can hold several at once. What breaks engagement is a role nobody holds, not a person missing from the list.

Where the role names come from

The vocabulary comes from programme management. UK government guidance gives every programme a Senior Responsible Owner: a single named person accountable for delivery. Methods such as 'Managing Successful Programmes' extend the idea with roles like the business change manager, who owns the benefits after delivery.

The names matter less than the property they encode: one accountable person per concern. The 5 roles below are my working set for a small digital project, and they keep that property.

The responsibility matrix

Role	What they own	What they need from engagement	What goes wrong when nobody holds it
Sponsor	The outcome, the resources and final accountability	Early warning, framed decisions, no surprises	Escalation has nowhere to land, and the loudest stakeholder sets the priorities
Delivery lead	The engagement work: register, cadence, conversations	A clear mandate, protected time, access to the sponsor	Engagement becomes everyone's task, which makes it nobody's
Subject expert	The substance the decision depends on	Early questions, and permission to say the difficult thing	Decisions rest on confident guesswork
Affected user	The lived experience of the change	A real route for input, and evidence that input changed something	The programme meets its mistakes at launch
Decision-maker	The decision, and the resources it commits	Options with costs, and trade-offs stated plainly	Engagement becomes a survey nobody acts on

One person, several hats

On a small project the sponsor is often the decision-maker for most decisions, and the delivery lead holds the subject-expert role for anything technical. That is workable, provided you know which hat a conversation is wearing. A sponsor hearing options as decision-maker needs different material from a sponsor being briefed as sponsor.

The pairing to watch is decision-maker and affected user in the same person. Someone who both makes the decision and lives with it will rarely stress-test it, and the people who only live with it lose their representative. If your structure forces that pairing, add an outside subject expert whose job is to argue the alternative.

When engagement stalls, it escalates to the sponsor, because that is the role with the authority to change things.

Put the names in the register

Add a role column to your stakeholder register: which of the 5 roles this person holds in the engagement. The register itself is described in what a stakeholder engagement framework is. Read the column downwards: every role needs at least one name. Engaging stakeholders: the key to successful projects covers the relationship habits that make the roles work, and stakeholder engagement versus a communication plan separates the engagement work from the updates people receive.

Put a name against each of the 5 roles

Write the 5 roles down the side of a page and put a name next to each for your current project. Use your own name where you hold more than one. The role left with no name is where your engagement will fail first.