Most programme failures are not technical failures. In our experience working with mid-market organizations across manufacturing, professional services, and distribution, the root cause of stalled or abandoned transformation programmes is almost always stakeholder-related: a CFO who publicly endorsed the initiative but quietly withdrew budget protection at a critical juncture; an operations director whose team withheld data during the design phase because they feared headcount implications; an IT vice-president who raised legitimate integration concerns in month one and was never meaningfully answered, becoming a persistent voice of dissent. The power-interest matrix — that familiar two-by-two — does not help you navigate any of these situations. It tells you who to keep informed and who to manage closely. It does not tell you how, and it does not account for the fact that stakeholders move.

Why the power-interest matrix is insufficient

The power-interest matrix, originally popularized by Aubrey Mendelow in the 1980s, remains a legitimate tool for initial stakeholder identification. Place stakeholders on two axes — their power to affect the programme and their interest in it — and you get a usable segmentation: monitor, keep informed, keep satisfied, manage closely. For a two-month project with a defined deliverable and a stable cast of characters, this is often enough.

Complex multi-stakeholder programmes are different in three important ways. First, they span enough time that stakeholder positions shift — a VP of IT who was a passive supporter in month two becomes an active blocker in month six when they realize the system integration will fall on their team. Second, they cut across organizational boundaries where formal authority does not map to actual influence — the most powerful voice in a mid-market leadership team is often a tenured operational manager with no direct reports on the programme who is trusted implicitly by the CEO. Third, they involve real stakes: budget reallocation, role changes, reporting structure modifications, or process redesign that creates genuine winners and losers. A static map cannot capture any of this.

The framework described in this post does not replace the power-interest matrix. It layers three additional disciplines on top of it: dynamic stakeholder profiling, influence pathway mapping, and resistance typology. Together, these give programme managers and sponsors a working model of their stakeholder environment rather than a snapshot taken at kickoff.

Dynamic stakeholder profiling

Static stakeholder analysis assumes that a stakeholder’s position, interest level, and attitude toward the programme are fixed properties that can be assessed once and referenced throughout. This is rarely true for programmes lasting longer than a quarter. Dynamic profiling treats each stakeholder as having a current state — their present attitude, their stated and unstated concerns, their level of engagement — and requires that current state to be formally reviewed at defined programme milestones.

In practice, this means building a stakeholder profile card for each key stakeholder that captures:

• Role and formal authority: Their position, budget control, and decision rights relevant to the programme.
• Current posture: Champion, supporter, neutral, cautious, resistant, or actively opposed — assessed at the last review date.
• Stated concerns: What they have said in meetings, workshops, or one-on-ones about the programme.
• Unstated concerns (inferred): What their behaviour suggests they are concerned about, even if they have not articulated it. This requires programme leadership to observe attendance patterns, escalation behaviour, resourcing decisions, and communication choices.
• What a win looks like for them: The personal or functional outcome that would make this programme a success from their perspective. This is often not the same as the programme’s stated objectives.
• Last meaningful engagement date: Not the last time they were sent an update, but the last time a substantive, two-way conversation occurred.
• Owner: The person on the programme team responsible for maintaining the relationship and keeping the profile current.

Profile cards should be reviewed formally at each phase gate and informally whenever there is a significant programme event — a scope change, a schedule slip, a leadership change in the business, or a budget challenge. In our experience, quarterly review is the minimum cadence for programmes lasting more than six months. Organizations that treat the stakeholder map as a document produced during initiation and archived thereafter are systematically surprised by resistance that was visible in retrospect.

Influence pathway mapping

Formal org charts describe authority. Influence pathway mapping describes how decisions actually get made and how opinions actually spread through an organization. In mid-market companies with 200 to 1,500 employees, these two things diverge significantly. A long-tenured plant manager with no seat at the executive table may have more influence over whether a new ERP system is adopted on the shop floor than the VP of Operations who formally sponsored the initiative. A finance director who has been at the company for fifteen years may be the de facto advisor the CEO calls before any significant commitment.

Mapping influence pathways requires you to answer four questions for each key stakeholder:

1. Who do they consult before forming a view on a significant decision? These are the people who shape their private opinion before they express a public one.
2. Who do they influence? If their posture shifts, whose posture is likely to follow — and how quickly?
3. Where does their credibility come from? Technical expertise, organizational longevity, relationship with the CEO, control of a critical resource? Understanding this tells you what kind of engagement will be persuasive to them.
4. What are their informal communication channels? Do they form views in one-on-ones with the CEO, in functional leadership meetings, in corridor conversations with peers, or through their direct team’s feedback?

Once influence pathways are mapped, programme teams can identify two things: influence multipliers (stakeholders whose shift from neutral to supportive would move multiple others) and influence blockers (stakeholders whose persistent resistance gives permission to others to disengage). In most mid-market programmes, there are two or three stakeholders who function as multipliers. Getting meaningful engagement from them is worth more than communication campaigns directed at the full stakeholder population.

Resistance typology: diagnosing what is actually blocking you

Resistance is not a uniform phenomenon. In our experience, stakeholder resistance in programme contexts falls into three distinct categories, each with a different cause and a different appropriate response. Treating all resistance the same way — typically with more communication — is a reliable way to make it worse.

The diagnostic question that distinguishes these three types is: if the concern they are raising were fully resolved, would their resistance diminish? For loss aversion and genuine scepticism, the answer is usually yes. For political positioning, the answer is usually no — the stated concern is not the actual concern, and resolving it will reveal a different objection.

This distinction matters because the response to political positioning requires sponsor-level intervention and governance decisions, not better communication. Programme managers who treat political resistance as a communication problem spend months producing materials and facilitating workshops that do not move the dial, because they are solving the wrong problem.

Engagement tactics by resistance type

Once resistance is correctly diagnosed, engagement tactics can be matched to root cause.

For loss aversion, the most effective approach is direct acknowledgement. Name the specific concern explicitly in a private conversation — do not wait for the stakeholder to raise it. Explain what is and is not known about the impact on their function. Where mitigation is possible, commit to it in specific terms. Where it is not, be honest. Stakeholders who are treated honestly about real impacts are more likely to remain workable partners than those who sense they are being managed around a difficult truth. Wherever possible, give them a meaningful role in designing the transition for their area — ownership of the solution reduces the sense of loss.

For genuine scepticism, the effective approach is engagement on substance. Arrange dedicated working sessions to go through their specific concerns in detail. If they have prior experience with a similar programme that failed, take that experience seriously and explain specifically what is different in this case — or, if it is not different, acknowledge the risk and describe how it is being managed. Genuine sceptics are often the most valuable stakeholders in a programme because they identify real risks before they become real problems. They should be treated as a resource, not a problem. Involving them formally in design or assurance activities turns adversarial energy into constructive contribution.

For political positioning, the programme manager typically cannot resolve the issue and should not attempt to. This requires the programme sponsor to engage peer-to-peer with the resistant stakeholder, with clarity about what the programme’s mandate is and what decisions are not available for negotiation. In some cases, the right answer is to restructure governance to remove the source of the political conflict — clarifying decision rights, adjusting reporting lines for the programme, or explicitly delineating which decisions belong to the programme team and which remain with functional leadership. This is difficult work and requires organizational authority that most programme managers do not have independently.

Stakeholder engagement planning template

The following template operationalizes the framework above. It is designed to be maintained as a live document throughout the programme, with a designated owner for each stakeholder relationship and a defined review cadence.

Three disciplines make this template useful rather than decorative. First, the relationship owner field must name a specific person — not “the programme team” — who is accountable for that relationship. Second, the next action field must contain a specific action with a specific date, not a general intention. Third, the template must be reviewed in programme governance meetings at defined intervals, with posture changes and new concerns surfaced as standing agenda items rather than ad hoc updates.

Organizations that treat stakeholder engagement as a communication plan — a calendar of town halls, email updates, and intranet posts — find that it produces awareness without commitment. The template above is designed to produce relationships, not broadcasts.

Frequently asked questions

How often should we formally update our stakeholder map on a multi-year programme?

At a minimum, at each phase gate and following any significant programme event — a scope change, schedule shift, sponsor change, or major organizational development in the business. For programmes with high political complexity or rapid organizational change, monthly reviews of the stakeholder engagement plan are appropriate. The goal is to ensure that your understanding of the stakeholder environment reflects current reality, not the situation that existed at programme initiation. In our experience, the gap between the two is usually significant by month four of any complex programme.

What do we do when the programme sponsor is not willing to intervene in political conflicts?

This is one of the most common and most consequential challenges in programme management. A sponsor who is unwilling to use their authority to resolve political conflicts between stakeholders is not adequately sponsoring the programme. The honest answer is that this requires a direct, private conversation between the programme manager and the sponsor about what programme sponsorship requires — not just visible endorsement, but active intervention when political dynamics threaten delivery. If the sponsor is genuinely unwilling or unable to play that role, the programme’s risk profile should be formally escalated and documented, because political conflicts that are not resolved at the sponsor level rarely resolve themselves.

How do we handle a stakeholder who is genuinely resistant and who holds significant decision authority?

First, correctly diagnose the type of resistance. If it is loss aversion or genuine scepticism, there is almost always a path to a working relationship if you engage honestly and specifically with the underlying concern. If it is political positioning, the resolution requires governance action, not engagement. If the stakeholder holds sufficient authority to block the programme and their resistance is politically motivated, the programme sponsor needs to make a decision about programme scope, mandate, or governance structure. Attempting to work around a highly resistant, high-authority stakeholder through communication activities is not a viable strategy for programmes with meaningful organizational impact.

Is it appropriate to map informal influence pathways? It feels like organizational politics.

Understanding how influence moves through your organization is not the same as manipulating it. Programme teams that refuse to acknowledge informal influence structures do not make their programmes less political — they make themselves less effective. Influence pathway mapping is a diagnostic discipline that helps you direct engagement effort where it will have the most effect. The alternative — treating all stakeholders as equal regardless of their actual influence — produces engagement programmes that are administratively complete and operationally ineffective.

When should we bring in external support for stakeholder management?

External support adds most value in three situations: when the programme manager lacks the organizational seniority to have credible conversations with senior stakeholders; when the political dynamics are sufficiently complex that an objective external view of the stakeholder environment is valuable; or when the organization lacks internal capacity to maintain the discipline of structured stakeholder engagement alongside programme delivery. In our experience with mid-market deployments, the decision to bring in external support is typically made too late — after resistance has hardened rather than before it has formed.

Stakeholder Management That Works: A Framework for Complex Multi-Stakeholder Programmes

Most senior operations directors, CFOs, and VPs leading complex programmes underestimate how quickly a static stakeholder map becomes a liability rather than an asset. This post offers a practical framework — dynamic profiling, influence pathway mapping, and resistance typology — that gives programme teams an accurate, actionable model of their stakeholder environment throughout delivery.