Stakeholder and sponsorship

Transformation is a political process as well as a technical one. Mapping who can affect the outcome — and who can stop it — is part of the assessment, not an optional extra.

Stakeholder map

Every engagement maintains a stakeholder map covering:

• Name and role — who they are, and what they own.
• Department — where they sit, including Legal, Finance, HR and Sales.
• Influence — high, medium or low: their ability to change the outcome.
• Interest — high, medium or low: how much the outcome affects them.
• Disposition — champion, supporter, neutral, sceptic, blocker.
• Concerns — the specific thing they are worried about losing.
• Engagement approach — who talks to them, how often, about what.

Name	Role	Dept	Influence	Interest	Disposition	Primary concern	Approach

Reading the map

• High influence, high interest — manage closely. These people decide.
• High influence, low interest — keep satisfied. They can block without noticing.
• Low influence, high interest — keep informed. They are often the people who know where the process actually breaks.
• Low influence, low interest — monitor.

A common failure is to over-consult the low-influence, high-interest group (usually engineers) and under-engage the high-influence, low-interest group (usually finance and legal) until a late-stage objection appears.

Executive sponsorship

An executive sponsor is the person with enough authority to remove blockers and enough stake to persist when the programme becomes inconvenient.

Responsibilities

Strategic alignment

Ties the transformation to the organisation's stated objectives, and can explain the link without notes.

Decision authority

Chairs the steering forum and makes decisions there. Escalation that never reaches a decision is not sponsorship.

Resource commitment

Secures budget, headcount and the time of the people the programme depends on.

Blocker removal

Intervenes across departmental boundaries where the delivery team has no authority.

Visible commitment

Uses the new process and the new metrics in their own forums; does not exempt their own team.

Accountability

Owns the outcome publicly, including when it is behind schedule.

Selecting a sponsor

Good sponsors have three attributes: authority over the resources the programme needs, stake in the outcome that outlasts a quarter, and availability for a regular cadence. A CTO who delegates attendance is less useful than a COO who attends.

Avoid sponsors whose role is nominally relevant but whose actual authority is limited — they become a bottleneck that appears to be a decision point.

Cadence

Forum	Frequency	Attendees	Decision scope
Steering committee	Monthly	Sponsor, department heads, delivery lead	Scope, budget, sequencing, escalations
Delivery review	Weekly	Delivery lead, workstream owners	Blockers, risks, plan adjustments
Department working group	Fortnightly	Department representative, change lead	How the change lands in that department

Resistance

Resistance is usually rational. Someone is protecting a control, a commitment or a reputation, and the design has not addressed it.

Signal	Likely cause	Response
"We've tried this before"	Previous failure with no closure	Acknowledge it explicitly; publish evidence of the difference in approach
"It's not compliant"	A real control that the new process does not satisfy	Bring risk and compliance into the design; encode the control as policy
"We don't have time"	Competing delivery commitments	Sequence the change against the delivery calendar; reduce scope rather than add parallel work
"That's not our job"	Role boundaries and accountability	Redefine roles explicitly, with the people affected
Silence in workshops, objection afterwards	Not enough involvement in design	Involve earlier, and give real decision weight

Related standards

• Organisational change
• Workshops and interviews
• Stakeholder map template
• Executive sponsorship plan