What is stakeholder management?
Stakeholder management is the process of identifying, analysing, and systematically engaging the people who have an interest in — or influence over — your project. It encompasses everything from initial stakeholder mapping and communication planning to ongoing relationship management, conflict resolution, and expectation alignment throughout the project lifecycle.
Traditional definitions position stakeholder management as a structured, analytical discipline: map your stakeholders, assess their power and interest, design a communication plan, manage them accordingly. That framework is useful and necessary. But it only addresses half the challenge.
The other half — the half that actually determines whether most projects succeed or fail — is the human, political, and social dimension. As Henning Christiansen argues in Project Management: The Red Pill, the biggest challenges in project delivery almost never originate from the plan. They originate from the people surrounding the project, and specifically from the gap between what stakeholders say in the kickoff meeting and what they actually do for the next six months.
The core insight is this: a project is a social and political system first, and a technical system second. Managing stakeholders effectively requires understanding both dimensions — and knowing which is actually driving the outcomes at any given moment.
Why stakeholder management fails in practice
Picture a familiar scene. A project manager presents a clear, well-structured plan at kickoff. Key stakeholders nod approvingly. Six months later, the project is behind schedule, over budget, and mired in conflict. What happened?
Christiansen's answer is blunt: the politics behind the scenes. Many stakeholders carry hidden agendas into every project. Some use projects to strengthen their position with senior leadership. Others push tasks they find personally interesting — regardless of whether those tasks serve the project's actual purpose. Still others are simply protecting their status, their budget, or their team's relevance.
"Many times stakeholders have hidden agendas. Some individuals use the project to strengthen their position with their superior, while others pursue tasks they find personally interesting even if it means introducing objectives that do not serve the project's best interests."
— Henning Christiansen, Project Management: The Red Pill
These hidden motivations can quietly undermine even the best-planned projects. The key is learning to identify and address them before they derail your work. That starts with understanding what types of stakeholders you're actually dealing with.
The six stakeholder types every project manager encounters
Traditional stakeholder frameworks categorise stakeholders by power and interest — high power / high interest, low power / low interest, and so on. That matrix is a useful starting point. But it tells you nothing about how a stakeholder will actually behave under pressure. For that, you need a more human framework.
Christiansen's taxonomy of project players — developed around the concept of Monkey Poker, the social and political game that runs beneath the surface of every organisation — offers exactly that. Each type has a distinct set of motivations, behaviours, and risks for the project manager.
Monkey Poker is Christiansen's term for the social and political game that runs underneath the surface of every organisation. Players compete for recognition (the prize) while avoiding responsibility (the monkey). The game is played with bluffing, deception, and strategic positioning — and most people are playing it without even realising it. For a project manager, recognising that the game is happening is the first step toward managing it.
Stakeholder mapping: the traditional framework — and its limits
The standard approach to stakeholder management begins with a stakeholder map — a structured analysis of everyone who affects or is affected by the project. The most widely used framework plots stakeholders on a power/interest grid:
| Quadrant | Power | Interest | Traditional strategy | Reality check |
|---|---|---|---|---|
| Manage closely | High | High | Engage deeply, communicate frequently | Watch for Monkey Kings and Chameleons in senior positions |
| Keep satisfied | High | Low | Meet their needs, avoid surprises | Low interest can mask hidden agendas — don't assume neutrality |
| Keep informed | Low | High | Regular updates, involve in decisions | Honey Bees often live here — protect their focus and time |
| Monitor | Low | Low | Minimal effort, occasional check-in | Parrots live here — they amplify messages faster than you expect |
This grid is a sound analytical starting point. But the critical limitation is that it's static: it tells you where a stakeholder is, not how they'll behave when the project hits turbulence, when scope changes are proposed, or when credit is being distributed. For that, you need to layer the Christiansen typology on top.
For each stakeholder, document: What are their stated requirements and expectations? What type are they (Chameleon, Rooster, Honey Bee, etc.)? What level of political risk do they represent? What topics will trigger them? This gives you a communication strategy that actually matches the person you're dealing with.
The real goal of stakeholder management: aligned purpose
Traditional stakeholder management treats alignment as a communication problem: if you brief stakeholders frequently enough, clearly enough, in the right format, they'll stay aligned. That's true for Honey Bees. It's largely irrelevant for Chameleons, Roosters, and Monkey Kings — who are not misaligned because they lack information. They're misaligned because their personal goals are different from the project's goals.
Christiansen identifies three key stakeholders in any project: the organisation, the project team, and the customer. When all three agree on the project's purpose — not just its deliverables, but its underlying reason for existing — the project has a foundational strength that political interference struggles to erode.
"If all key stakeholders agree on the purpose then you have taken an important step toward ensuring the project's success. Finding this common ground means aligning different interests, expectations, and priorities into a shared direction."
— Henning Christiansen, Project Management: The Red Pill
When purpose alignment is absent — when one or more key stakeholders are not genuinely invested in the stated outcome — the consequences are predictable: scope creep, decision delays, budget overruns, and the slow replacement of project goals with individual agendas.
Using MoSCoW to lock stakeholder alignment
One of the most effective tools for establishing and testing stakeholder alignment is the MoSCoW method — a prioritisation framework that forces explicit agreement on what the project absolutely must deliver versus what it could deliver later.
The MoSCoW exercise itself is a stakeholder management tool — not just a planning tool. Where stakeholders disagree on priorities, those disagreements reveal the political fault lines in the project. A Chameleon who insists on upgrading a "Could have" to a "Must have" is not making a technical argument. They're positioning for credit. The project manager who documents these disagreements — including who holds which view and why — has the intelligence they need to manage what comes next.
The vision board as a stakeholder alignment engine
Beyond MoSCoW prioritisation, Christiansen proposes an underused tool for ongoing stakeholder alignment: the project vision board. Unlike a project charter or Gantt chart, the vision board communicates the project's purpose visually — using images, symbols, and minimal text to represent what success looks like, without getting lost in technical details.
The vision board serves several stakeholder management functions simultaneously:
- It creates a shared visual language for what the project is trying to achieve
- It acts as a constant, visible reminder of purpose during periods of conflict or pressure
- For Chameleons and Roosters, it works as what Christiansen calls a "magic wand" — linking their personal desire for recognition to the project's actual goals
- It flags misalignment early: where stakeholders disagree on how to prioritise elements of the vision board, those disagreements predict future conflict
When a vision board is physically present in meeting rooms and referenced regularly, its effect is partly subconscious. Stakeholders begin to associate the board's imagery with the project's core objectives. Over time, this creates an implicit alignment that makes it harder for individuals to justify decisions that contradict the shared vision — even if they'd otherwise try to push their own agenda.
Building a stakeholder communication plan
An effective stakeholder communication plan is not a broadcast schedule. It's a targeted strategy that matches the right information, at the right frequency, in the right format, to the right person — based on what actually motivates them and what they'll do with the information.
Managing politically difficult stakeholders
The standard stakeholder management advice — engage stakeholders early, communicate transparently, involve them in decisions — works well for straightforward stakeholders. For Chameleons, Roosters, and Monkey Kings, it needs significant adaptation.
Managing Chameleons
Chameleons are motivated by career advancement and personal recognition. The most effective approach is to give them a visible stake in the project's success — not by handing them control, but by positioning success as something they can share credit for. Christiansen's advice is counterintuitive: share the medals, even with those who may not fully deserve them. A Chameleon who feels credited is far less disruptive than one who feels ignored. At the same time, the project manager must ensure the Chameleon's public positioning doesn't reshape the project's actual direction.
Managing Roosters
Roosters are drawn to intellectually stimulating, high-visibility work. The danger is that they'll devote energy to the interesting parts of the project and neglect the critical but unglamorous work that actually determines delivery. The project manager's tool here is a well-defined model structure: when tasks are clearly scoped with explicit outputs and dependencies, the Rooster has less latitude to drift toward personally interesting tangents and away from project-critical work. Challenge their contributions where needed — but do it with facts and structure, not opinions.
Managing Monkey Kings
Monkey Kings are the most dangerous and the least manageable. They hold organisational power, rarely take sides until it serves them, and are immune to the usual approaches. The project manager cannot trump a Monkey King. What they can do is build sufficient project momentum — through purpose alignment, strong team cohesion, and documented facts — that disrupting the project becomes politically risky even for someone with the Monkey King's power. A well-documented, widely-supported project is a much harder target than a poorly-defined one.
When the Monkey King cuts your project budget without justification
One of Christiansen's most vivid examples: a Monkey King removes 1,500 hours from a project's budget — not because the project requires it, but to show a board of directors that they're in control. The project manager is still expected to deliver the same result. The options are limited, but the response is clear:
- Document the decision and its consequences in writing, immediately
- Ensure the project board understands the impact on scope, timeline, and quality
- Restructure the project plan to reflect the new reality — don't silently absorb an undeliverable commitment
- Focus on building political support from the stakeholders who do have an interest in genuine delivery
- Never try to publicly challenge or expose the Monkey King — it will not work and will leave you with the monkey
The recognition strategy: sharing credit strategically
One of the most practical and underappreciated stakeholder management tools is deliberate credit-sharing. Christiansen is explicit: the most effective thing a project manager can do — particularly with Chameleons and Roosters — is to share the medals, even with those who may not fully deserve them.
This is not about injustice or rewarding bad behaviour. It is about recognising the reality that, in most organisations, perceived contribution matters as much as actual contribution when it comes to political dynamics. A stakeholder who feels publicly credited is less incentivised to undermine the project. A stakeholder who feels ignored or sidelined is more dangerous than one who feels included.
At the same time — and this is the balance the Unicorn project manager must strike — credit-sharing cannot come at the cost of the Honey Bees. The people who actually do the work, who meet deadlines and solve problems without fanfare, deserve recognition too. Protecting and celebrating the Honey Bees is not just a matter of fairness. It signals to the team what behaviour is valued, and it builds the trust that sustains momentum through difficult phases.
Chameleons and Roosters are skilled at claiming credit for work they didn't do. If you allow this to happen systematically, you undermine the Honey Bees who carried the project — and signal to the team that politics beats performance. The project manager must be visible and deliberate about who actually contributed what, in ways the broader organisation can see.
Stakeholder management in Proglar
Proglar's project management system is designed to support the stakeholder management work that actually matters: clarity on project purpose, transparency on decisions and changes, and the documentation trails that give a project manager real leverage.
The vision board, MoSCoW prioritisation, and change request management features in Proglar are built specifically to support the kind of structured stakeholder alignment that Christiansen describes. As decisions change, scope evolves, and stakeholders push back, the project manager has a documented record of what was agreed, who pushed for what, and when — the foundation of informed, defensible stakeholder management.
Manage stakeholders with structure, not guesswork
Proglar gives your team a shared project vision, integrated change management, and the transparency that keeps stakeholders aligned and accountable. Try it free for 30 days.