Stakeholder Mapping: Lessons from the Battlefield

Change is a constant force. Whether it's in the corporate boardroom or the battlefield. While the stakes and the environment may differ, the principles of effective strategy remain the same.

One such principle is stakeholder mapping, which is essentially about identifying who holds the keys to success for a given project or initiative. It's an exercise in understanding power dynamics, vested interests, and interpersonal relationships. 

I learned the value of this technique whilst in the Army on combat tours in Afghanistan & Iraq. My role as a Joint Fires Officer put me at the intersection of strategy and execution on the battlefield. As a qualified JTAC (Joint Terminal Attack Controller), I was responsible for the precise coordination of various types of firepower, ranging from Artillery and Mortar Fires to Helicopter Gunships and Airstrike. 

Two objectives were paramount: first, minimize civilian casualties, and second, maximize the efficacy of each munition and asset deployed, because we didn't have room to waste resources.

You can see how important it was to have a good grasp of the concept of stakeholder mapping in order to be as effective as possible with our limited resources.

We started by targeting the obvious insurgents in order to take down the groups - the leaders and senior members. But, like a hydra with its head cut off, someone was always ready and waiting. It was a never-ending cycle of spending valuable time and resources on taking out one leader just for another one to step up in their place. A total waste of our efforts.

So, we tried another approach. We gathered our intel, watched how the groups interacted, and came up with a new plan. Instead of targeting the heads of the hydra, we went for the legs.

The 'legs' of the hydra were those individuals who had no formal authority but were often the communication conduit between disparate groups of operation cells. They were the powerhouse of the groups. Nothing was accomplished without them and it greatly reduced their ability to coordinate efforts on the battlefield when they were out of the picture.

This is where we can link the lessons learned on the battlefield, to the corporate boardroom.

The Traditional Paradigm

Change management often adheres to a traditional top-down model. The executives and senior leaders conceptualize the change, and then it trickles down through the layers of middle management until it reaches the front-line employees. This approach emphasizes the roles and responsibilities of leadership to envision, plan, and execute change. It has the benefit of a unified direction and clarity of purpose, which ideally should make implementation smoother.

The Limitations of the Top-Down Approach

However, the top-down model is not without its shortcomings. Much like how we struggled to see a change in the environment when we took out the heads of the insurgent groups, the corporate world often overlooks the complex web of interpersonal relationships and informal power structures at the ground level. These are the proverbial "boots on the ground" in the corporate world—your middle managers and front-line employees who must enact the change. Ignoring this dynamic is akin to building a house on a shaky foundation; it might look good on paper, but it won't withstand the pressures of reality.

Top-down Planning, Bottom-up Refinement

To remedy this, an effective approach is to combine top-down planning with bottom-up refinement. While the initial planning and vision should come from the top, the tactical execution and fine-tuning should be a collaborative effort involving those who are closest to the action. In this way, you get the best of both worlds: strategic alignment and practical viability.

The Risk of Malicious Compliance

Ignoring the bottom-up refinement phase can often lead to a phenomenon known as "malicious compliance." This happens when employees, particularly those who foresee the pitfalls or shortcomings of a proposed change, deliberately implement it without raising any concerns, effectively letting it fail. They do so either out of cynicism or because they believe their feedback will not be taken seriously. They can then point to their compliance as proof that they did their job, even as they watch the change initiative crumble. Malicious compliance is not just a failure of implementation; it's also a glaring symptom of a disengaged and disenfranchised workforce.

The Power of Informal Influence

In every organization, there exist individuals who, although lacking formal authority or an impressive job title, wield considerable influence over their peers and even superiors. Like the legs of the hydra, these people carry weight. Others turn to them for advice, their opinion is highly sought after, and they are natural leaders in their circles. They connect disparate groups and shape opinions.

Identifying these informal influencers is vital for effective change management because they can act in one of two capacities: as your strongest allies or as your most formidable obstacles. When you have them on your side, they can help sway opinions, calm fears, and facilitate a smooth transition. On the flip side, if they are opposed to the change, their influence can be a significant barrier, capable of sowing discord and resistance among team members.

Engaging with these informal influencers early in the change process can provide invaluable insights into how the change will be received, what concerns might arise, and how best to address them. Their support can serve as a catalyst for broader acceptance and successful implementation.

Stakeholder Mapping for Change Management

Stakeholder mapping can become unnecessarily complicated.

At its core, we are trying to understand four things:

  1. Who is affected?
    Identify the people and groups who will experience the consequences of the change, not simply those with formal responsibility for delivering it.
  2. Who has influence?
    Look beyond position and title. Who do people trust? Whose opinion carries weight? Who can accelerate the change, slow it down or quietly undermine it?
  3. How are they connected?
    Map the relationships between stakeholders. Information, trust and influence rarely follow the organisational chart neatly.
  4. How should they be engaged?
    Different stakeholders require different levels of context, involvement and communication. Treating everyone identically might be consistent. It isn't necessarily effective.

The objective isn't to create an impressive diagram. It's to understand the human terrain well enough to anticipate how the change is likely to move through it.

Communication: Sent Doesn't Mean Received

One of the easiest mistakes in change management is confusing communication with transmission.

  • The email was sent.
  • The presentation was delivered.
  • The announcement was made.
  • Therefore, everyone understands.

Not necessarily.

Communication has only worked when the intended message has been understood well enough for people to act on it.

That means leaders need to think beyond a single communication method. Some stakeholders need the strategic context. Others need to understand exactly what changes for them on Monday morning. Some need an opportunity to ask questions. Others need to see the new process demonstrated before it makes sense.

The responsibility isn't to make every communication endlessly elaborate. It is to ask: What does this person need to understand, and what is the most effective way of helping them understand it?

Sending the same information to everyone may be efficient. It doesn't guarantee understanding.

Understand What People Value

Stakeholder mapping becomes considerably more useful when we move beyond who has influence and start asking why. People don't interpret change in a vacuum. They assess it through their own priorities, experiences, relationships and values.

During deployments to Afghanistan and Iraq, we regularly worked alongside local defence forces whose language, culture and experiences were very different from ours.

There were plenty of things we didn't share. But there were also things we did. Family was often one of them. Finding that common ground didn't erase our differences. It gave us somewhere to begin. The same principle applies inside organisations.

A proposed change might be framed around efficiency at the executive level while the people implementing it care deeply about service quality, professional competence, team stability or autonomy.

Neither position is necessarily wrong. But if leaders communicate only through the values that matter to them, they shouldn't be surprised when the message fails to resonate elsewhere.

Understanding what matters to people doesn't mean manipulating it. It means recognising the perspective from which they are evaluating the change.

Resistance Is Information

Change resistance is often treated as something leaders need to overcome. Sometimes it is. Sometimes it is also telling us something.

People closest to the work may see consequences that weren't visible during planning. They may understand historical context the project team doesn't. They may have experienced three previous versions of the same initiative.

Or they may simply be uncertain about what the change means for them. That uncertainty can take several forms.

Competence: Will I still be good at my job when this changes?

Relevance: Will my skills or role still matter?

Control: Is this being done to me without any opportunity to influence it?

Trust: Do I believe the people leading this actually understand what they're changing?

These aren't always irrational objections to progress. They are data. That doesn't mean every concern should stop the change or every stakeholder gets veto power.

It means good leaders listen carefully enough to distinguish between resistance that needs to be managed and information that needs to be acted upon.

Ownership Changes Behaviour

There is a considerable difference between being informed about a change and having some meaningful involvement in it. This is where top-down planning and bottom-up refinement become important.

Senior leaders should establish strategic intent, boundaries and desired outcomes. But the people closest to implementation often know things senior leaders cannot.

  • Where will the process create friction?
  • Which assumption won't survive contact with reality?
  • What will customers notice?
  • What unintended consequence is already obvious from the frontline?

Giving people an opportunity to shape execution doesn't mean leadership abandons responsibility for the decision.

Consultation is not consensus.

It means using the knowledge already sitting inside the organisation before discovering it the expensive way. People are also more likely to take ownership of something they have been able to meaningfully influence.

Not because everyone needs to get their own way. Because participation changes the relationship people have with the outcome.

Stakeholder Mapping Isn't a One-Off Exercise

There is one final problem with stakeholder maps. They become outdated.

  • Influence changes.
  • Relationships change.
  • People leave.
  • New informal leaders emerge.

Someone who initially supported the change may become sceptical once implementation begins. Someone who resisted it may become one of its strongest advocates after seeing the benefits.

The stakeholder map created at the beginning of a project is therefore a starting point, not an artefact to be filed away after the planning workshop.

Keep watching.

  • Who are people listening to now?
  • Where is information travelling?
  • Where is friction emerging?
  • Has influence shifted?
  • What has the implementation taught us that the original map couldn't?

The organisation will keep moving while the change is happening. The map needs to move with it.

Conclusion

Stakeholder mapping isn't really about putting names into boxes. It's about understanding how an organisation actually works.

Formal authority matters, but so do informal influence, relationships, trust, values and the way information travels between people. That was the lesson on the battlefield.

Removing the most obvious person in charge didn't necessarily disrupt the system. Understanding the network around them did. The stakes in business are obviously very different. The principle isn't.

When leaders understand only the formal structure, they can miss the people and relationships that will ultimately determine whether a change gains momentum, encounters friction or quietly dies.

The organisational chart shows the structure. Stakeholder mapping helps reveal the system operating underneath it. That is often where change is really won or lost.




Drawn from lessons learned in the military, and in business, we make leadership principles tangible and relatable through real-world examples, personal anecdotes, and case studies.

© Copyright 2023 The Eighth Mile Consulting  |  Privacy