You Cannot Manage Stakeholders Like Resources

Program leaders create commitment through influence, credibility and governed choices, not by pretending that important stakeholders sit inside the program manager’s chain of command.

A program can have a clear charter, credible schedule and competent project teams and still lose momentum because one influential stakeholder withdraws support. The difficulty is that the people with the greatest ability to help or damage a program are often the least controllable. Sponsors, executives, functional leaders, regulators, suppliers, customers and affected groups may all influence outcomes without reporting to the program manager.

That changes the leadership problem. Resources can be assigned. Tasks can be delegated. Contracts can define obligations. Stakeholder commitment works differently. It has to be earned, renewed and sometimes renegotiated as the program changes.

The practical implication is significant: stakeholder engagement is not a softer version of task management. It is a core mechanism through which a program maintains the social and organisational conditions required to realise benefits.

The Strategic Context

Programs sit between strategic intent and operational reality. They coordinate projects, organisational change and transition to produce outcomes that individual components cannot deliver alone. That makes them especially exposed to competing interests.

The supplied Week 10 study material makes a useful distinction between stakeholder management and stakeholder engagement. At program level, the manager may have little direct authority over many people whose decisions matter. The emphasis therefore shifts from control to engagement: understanding interests, gaining support, managing expectations through communication and negotiation, identifying concerns before they become issues, and resolving those issues when they do emerge.

The 2005 AccountAbility, UNEP and Stakeholder Research Associates handbook pushes the idea further. It treats stakeholder engagement as something that can inform strategic decisions, improve learning, pool knowledge and resources, and strengthen the organisation’s ability to respond. Although the handbook was written primarily for corporate and sustainability contexts, its underlying logic is valuable for programs: engagement creates information and legitimacy that formal plans alone cannot provide.

This is why the stakeholder system should be considered part of program architecture, not an external communications layer.

What Leaders Commonly Misread

The first mistake is to equate stakeholder importance with hierarchical seniority. A powerful executive may have formal authority, but an operational expert, regulator, customer group or supplier may hold information, legitimacy or practical control that becomes decisive at a particular point.

The second mistake is to assume that a stakeholder register is a completed analysis. A register is only a starting point. The Week 10 material emphasises continuing review because stakeholders change, people move roles, organisations restructure, suppliers change ownership and executive attitudes shift. A static map can quickly become an outdated representation of influence.

The third mistake is to treat resistance as a communication failure. Sometimes it is. But resistance can also be rational. A business unit may be asked to absorb disruption without receiving enough benefit. A sponsor may see strategic assumptions weakening. An operational team may recognise implementation risks that the program has underestimated.

The fourth mistake is to believe that stakeholder engagement is about keeping everyone satisfied. It is not. Programs create trade-offs. Some interests will conflict. The leadership task is to understand those conflicts, make legitimate decisions and maintain enough trust that disagreement does not become destructive.

Related article: Stakeholder Maps Expire: Portfolio Influence Changes as Strategy Moves

Reframing the Issue

A better question than “How do we manage this stakeholder?” is:

What commitment, decision, information or behaviour does the program need from this stakeholder, and what does the stakeholder need in return to engage constructively?

That reframing moves the conversation away from labels such as supportive, neutral or resistant and toward a more useful exchange.

Stakeholder relationships can be analysed through at least five lenses:

Influence: What can this stakeholder enable, delay, change or stop?
Impact: How materially will the program affect them?
Interest: Which outcomes, risks or decisions matter to them?
Legitimacy: Why does their perspective deserve consideration?
Commitment: What level of participation is actually required for success?

These factors are dynamic. A stakeholder with low interest during design may become central during transition. A sponsor with high formal power may become disengaged if strategic attention moves elsewhere. A regulator may be distant until a threshold is crossed.

The program therefore needs a living stakeholder model rather than a one-off classification exercise.

Influence Is a System, Not a Personality Test

Traditional power-interest grids can be useful because they force teams to discuss relative influence and concern. Baker’s 2012 PMI conference paper also describes broader classification approaches that include legitimacy and urgency. But no matrix should be mistaken for reality.

The more valuable practice is the discussion behind the placement: What evidence supports our judgement? What could change it? What informal networks are we missing? What decision is approaching that will alter stakeholder importance?

A program team should also be cautious about circulating blunt classifications. The Week 10 notes correctly warn that such tools represent the team’s perception and can damage trust if stakeholders see themselves inaccurately or dismissively categorised.

The best stakeholder analysis therefore has two qualities: it is useful enough to guide action and humble enough to be revised.

Engagement Requires an Exchange of Value

Programs often approach engagement as a demand: approve this, attend this meeting, provide this resource, support this change.

That is incomplete.

A senior functional leader may support a program because it removes a constraint, protects service performance or advances a strategic priority. A customer group may participate because its concerns will genuinely shape design. A supplier may commit scarce expertise because decisions are timely and commercial expectations are clear.

The program manager needs to understand the exchange. Where the program repeatedly asks for attention without demonstrating relevance, stakeholders disengage. Where consultation occurs but decisions ignore all input without explanation, trust decays.

The AccountAbility handbook’s emphasis on responsiveness is useful here. Engagement has credibility only when the organisation can consider what it hears and explain what it will do as a result.

Decision Framework

For each critical stakeholder, use a five-part test.

Test	Leadership question
Outcome	What program outcome depends on this stakeholder?
Required commitment	What decision, behaviour, resource or support is needed?
Stakeholder interest	What value, risk or consequence matters to them?
Engagement strategy	What interaction is needed: inform, consult, involve, negotiate or govern jointly?
Evidence of commitment	What observable behaviour would demonstrate genuine support?

The last question matters. Attendance is not commitment. Positive language is not commitment. A stakeholder is committed when behaviour aligns with the agreed outcome: resources are made available, decisions are taken, risks are surfaced early, actions are owned and organisational changes are supported.

The framework also helps leaders decide where not to spend attention. Engagement should be proportional to strategic importance, impact and the required level of commitment.

From Strategy to Execution

Immediate action: identify the handful of stakeholders whose decisions could materially change program outcomes in the next 90 days. Review assumptions about their influence, interests and current commitment. Confirm what the program actually needs from each.

Medium-term capability: maintain a shared stakeholder register and engagement plan as working program assets. Involve the program team, not only the program manager, because different team members observe different relationships and weak signals. Connect stakeholder issues to risk, benefits, dependencies and change decisions rather than maintaining them in a separate communications silo.

Long-term positioning: build an organisational capability for influence without authority. Program leaders need political awareness, negotiation ability, judgement, listening skills and credibility across functions. These capabilities become increasingly valuable as transformation crosses organisational boundaries.

Related article: The Program Manager Must Stop Thinking Like a Project Manager

Signals to Monitor

Watch for a growing gap between formal endorsement and practical behaviour. Other warning signs include repeated non-attendance by decision-makers, delayed resource commitments, stakeholders learning about material changes indirectly, previously resolved issues reappearing, unexpected escalation outside the program, and engagement activity increasing while decisions remain stalled.

A particularly important signal is a change in the language of stakeholders. When discussion moves from “how will we deliver this?” to “why are we doing this?”, the issue may no longer be execution. Strategic legitimacy may be weakening.

Questions for the Leadership Team

Which program stakeholders can materially alter outcomes despite having no formal role in the program structure?
Where are we assuming support because someone approved the program months ago?
Which stakeholders carry the greatest impact from the change but the least formal power?
What commitments do we need over the next tranche, and what evidence will show that those commitments are real?
Where is stakeholder resistance signalling a genuine strategic or operational problem rather than poor communication?
Which relationships would become critical if the program changed direction?

Closing Perspective

Stakeholder engagement becomes more important as programs become more cross-functional, politically sensitive and dependent on organisational change. The program manager’s authority does not expand simply because the stakes are higher.

Strong program leadership accepts that constraint. It does not try to manage people as if they were schedulable resources. It builds the conditions in which influential people can understand the choice, challenge the assumptions, contribute knowledge and commit to the outcome.

Related article: Stakeholder Engagement Is a Decision System, Not a Communication Plan

References

University of South Australia, Week 10 Study Notes on Program Stakeholder Engagement, supplied course material based on PMI 2017.
Krick, T., Forstater, M., Monaghan, P. & Sillanpää, M. 2005, The Stakeholder Engagement Manual, Volume 2: The Practitioner’s Handbook on Stakeholder Engagement, AccountAbility, UNEP and Stakeholder Research Associates.
Baker, E. 2012, ‘Planning effective stakeholder management strategies to do the same thing!’, PMI Global Congress 2012—North America.