Why Stakeholder Management Keeps Failing and What to Do About It
The lessons are not hidden. They appear in every post-mortem, guide, and conference talk on what went wrong. Yet the same failures persist.
Professor Herman Stein once observed, "The most consistent lesson from lessons learned is that lessons are not learned."
The stakeholder management body of knowledge is well developed. Project Management Institute, Association for Project Management, and International Organization for Standardization all convey the same fundamentals: identify stakeholders early, understand their interests and influence, communicate proactively, and engage continuously.
Project managers understand these principles. The problem is that under pressure, they collapse into checkbox activities. The gap is not knowledge; it is application.
Five places stakeholder management breaks down:
1.Stakeholder identification is done once, too late, and too narrowly.
Stakeholders are often defined as those with formal authority, such as sponsors, regulators, and approvers. However, influence does not always come with a title. Community members, landowners, informal leaders, and affected businesses can exert significant practical power over a project's outcome without any formal role.
Proper identification requires asking not only who has authority, but also who can delay, block, or render the project politically untenable. These stakeholders must be identified, understood, and engaged from the outset.
2.Resistance is treated as opposition rather than a signal.
When stakeholders push back, the instinct is often to respond defensively by explaining more, justifying harder, and presenting additional data. In reality, resistance is usually a symptom. It may reflect miscommunication, an unaddressed concern, or a grievance unrelated to the project that has found expression through it.
In industrial communities, people rarely object to the activity itself. They object when they feel uninformed, disregarded, or when specific concerns, such as insurance, roads, or water, are ignored. Treating resistance as opposition rather than feedback turns manageable friction into conflict.
3.The wrong people do the engaging.
Technical specialists are essential to delivery, but they are often not the right people to lead stakeholder engagement.
Rock engineers and geologists are trained to explain models, parameters, and data. That expertise matters, but a stakeholder concerned about their livelihood is not asking a technical question. They are asking a human one. Human concerns require responses from individuals who understand context, can communicate clearly, and have the authority to make commitments.
When senior leadership is absent, the message is clear that these stakeholders are not a priority. Having the right people in the room is critical to building trust and avoiding conflict.
4.Materials are prepared for the project team, not the audience.
This is one of the most avoidable failures in stakeholder engagement. A presentation designed for internal technical review is not suitable for an external audience. The data may be the same, but the framing, language, and emphasis must reflect the audience's perspective.
A worst-case modelling scenario may be appropriate for engineering purposes, but it can be alarming when presented to communities dependent on groundwater. The model is not wrong. The communication is.
Reviewing materials through the audience's eyes is not a communications nicety. It is basic risk management.
5.The stakes are higher than most teams realise.
Stakeholder management failure is rarely just a relationship issue. It is a project risk and potentially a business risk.
Environmental and regulatory approval processes in South Africa and globally include formal objection and appeal mechanisms. In mining, infrastructure, and development projects, affected parties can delay or derail approvals through legitimate channels.
Those you fail to engage are not just unhappy stakeholders. They represent a direct risk to your schedule and, in time-sensitive projects, your reason for proceeding.
Projects with narrow windows, where delays can erode or eliminate NPV, cannot treat stakeholder engagement as a compliance activity. It must be treated as a critical success factor.
What effective stakeholder management actually requires.
None of this is complex. It requires discipline.
- Start stakeholder identification at initiation but treat it as iterative across all phases. Analyse stakeholders during each planning cycle, define targeted engagement strategies, and monitor effectiveness so adjustments can be made early.
- Map informal power alongside formal authority. Look beyond who has a seat at the table to who can delay, block, or derail the project. Maintain ongoing engagement to understand priorities and concerns.
- Prepare for the room by reviewing your material from the audience's perspective. Identify unaddressed concerns and challenge your assumptions.
- Bring the right people to sensitive discussions. Align seniority and communication style to the context. Politically charged engagements require leaders who can address both human and technical dimensions.
- Engage continuously, not reactively. Trust is built through consistent contact. If stakeholders only hear from you when problems arise, every interaction becomes a warning. Ongoing engagement encourages early, manageable concerns.
The pattern will repeat unless something changes.
The frustrating reality of stakeholder management failure is its predictability. The same oversights appear across industries and geographies. The literature documents them clearly, and training reinforces them. Yet under pressure, the same shortcuts are taken.
Changing this requires more than awareness. It requires treating stakeholder engagement as a core discipline that is planned early, resourced properly, and held to the same level of rigour as the technical and financial workstreams it supports.
The next approval window, community meeting, or regulatory submission is an opportunity to get this right before it becomes a recovery exercise. The question is whether the project team will treat it that way.
Author:
Jacques Gouws (Principal Consultant)
