The RACI Is a Map, Not a Strategy
Most project managers learn about stakeholder management through the RACI matrix — the tool that assigns Responsible, Accountable, Consulted, and Informed roles to individuals across a set of project activities. It's a useful discipline for clarifying who does what. But it has almost nothing to do with the actual challenge of stakeholder management.
Real stakeholder management is about understanding what people want, what they fear, how they make decisions, and how to create the conditions for collaboration and support. A RACI tells you who to put in the "Consulted" column for a deliverable sign-off. It tells you nothing about how to handle the department head who is actively hostile to your project, the board member whose support is essential but who never reads your reports, or the end-user group whose resistance will derail implementation if ignored.
This article is about the craft of stakeholder engagement — the things that actually make the difference between projects that move smoothly and projects that stall in a fog of misalignment and political friction.
Start With Genuine Stakeholder Analysis
The most valuable stakeholder analysis tool isn't the RACI — it's a power/interest grid combined with a honest assessment of each stakeholder's current position and trajectory.
For each significant stakeholder, you need to understand: How much power do they have to help or block this project? How much interest do they have in its outcome? What is their current disposition — are they a champion, a neutral party, a sceptic, or an active opponent? And — critically — is their position stable or moving?
A stakeholder who is currently neutral but has high power and is moving toward scepticism is a much higher priority than a low-power enthusiastic supporter. Stakeholder analysis should be dynamic, not a one-time exercise done during project initiation and then filed away.
Review your stakeholder map monthly. For each stakeholder with high power or high influence, note whether their position has shifted since last month and why. A stakeholder whose engagement is cooling is an early warning sign worth acting on before it becomes a problem.
Understand What Each Stakeholder Actually Wants
Stakeholders rarely tell you what they really want in meetings or in formal consultations. What they say in a requirements workshop and what they actually care about are often quite different things. Good stakeholder management requires investing time in understanding the person behind the role.
What does success look like for this individual — not for the project, but for them personally and professionally? What would make their life easier? What are they worried about? What is the political context they're operating in? A stakeholder who appears resistant to a system change may actually be worried about losing budget control, or looking incompetent in front of their team, or having promised their staff something that the project contradicts.
When you understand the underlying concern, you can address it. When you treat their resistance as obstruction to be overcome, you escalate conflict.
Tailor Your Communication, Don't Broadcast It
Most project communication is broadcast: a status report goes to a distribution list, a governance update goes to a standing meeting, a newsletter goes to all staff. Broadcast communication is necessary but not sufficient. For high-influence stakeholders, it needs to be supplemented with targeted, personalised communication.
This means knowing how each key stakeholder prefers to receive information — some want a one-page summary, others want the full data. Some want to be briefed before a governance meeting so they can prepare questions; others prefer to review outputs asynchronously. Some engage best in informal conversations; others need everything documented formally.
The investment of understanding and adapting to these preferences pays back many times over in the form of engagement, cooperation, and early warning when something is wrong.
Manage Upward as Well as Outward
One of the most underrated aspects of stakeholder management for project managers in SMEs is the upward dimension — managing the relationship with your project sponsor and the wider leadership team. Sponsors in SMEs are typically busy leaders with many competing priorities. If you only engage them when you need a decision or when something has gone wrong, you're missing an opportunity.
Regular, brief, informal check-ins with your sponsor — separate from formal governance — build the relationship, keep them contextually aware, and mean that when you need their intervention, they're already informed and onside. A sponsor who gets their first substantive briefing about a problem at a governance meeting is not a sponsor who can help you effectively.
Handle Resistance Constructively
Every significant project generates stakeholder resistance at some point. The instinctive response — to override it, escalate it, or ignore it — is almost always the wrong one. Resistance, when engaged with constructively, frequently surfaces legitimate concerns that improve the project outcome.
When you encounter resistance, the first step is to understand it rather than respond to it. What is the concern underneath the resistance? Is it a risk the project team hasn't adequately considered? Is it a communication failure — the stakeholder doesn't have the information they need? Is it a political dynamic that needs senior-level resolution?
Resistance that's engaged with respectfully and resolved often converts the resistant stakeholder into one of your strongest advocates. They've been heard, their concern was taken seriously, and the project is better for it. Resistance that's steamrolled becomes entrenched opposition that resurfaces at implementation.
Build the Stakeholder Dimension Into Your Project Plan
Stakeholder engagement should be treated as a workstream in its own right, with activities, milestones, and resources allocated to it. In practice, most project plans treat it as implicit — something that happens in the background alongside the real work. The result is that it gets deprioritised when pressure builds.
A stakeholder engagement plan doesn't need to be complex. It needs to identify the key stakeholders, their current position, the engagement objective for each, the activities planned, and the person responsible. Reviewed monthly at a minimum, it becomes a genuine management tool rather than a document that exists to tick a governance box.
If stakeholder management is a persistent challenge in your delivery environment, it's often a symptom of something structural — in the way your projects are set up, or in the culture around project governance. Our Outsourced PMO team works alongside SME leaders to build the engagement frameworks and disciplines that make delivery smoother. Let's talk about where the friction is for you.