Tool

Stakeholder Complexity Score

Eight questions that measure how complicated the human terrain around a decision really is, from veto holders to incentive conflicts, before the plan assumes a smooth path.

Score the decision as it must actually travel: through the approvers, functions and external parties who can shape or stall it. Fixed questions, fixed points, nothing stored.

Last reviewed 3 July 2026 · Free and ungated

Get independent perspectives

Put the stakeholder landscape to selected senior operators from the Global Board and receive a confidential report on where it will resist, before the timeline is public.

Get independent perspectives

How a client brief works · What you receive

Fixed questions · no AI · nothing stored

Run the scorecard

Answer for the specific decision, counting the stakeholders it actually has rather than the ones on the governance chart.

0–34 Manageable 35–64 Demanding 65–100 High complexity How our tools are scored
  1. Number of approvers How many people or bodies must formally say yes?
    • One approver, clearly identified
    • Two or three approvals, in a known sequence
    • Multiple approvals across bodies, with an unclear order
  2. Veto holders Who can block this without formally approving anything?
    • No one beyond the decision-maker can block it
    • One or two parties could block it, and they are engaged
    • Several parties hold effective vetoes, some unengaged or unknown
  3. Affected functions How widely does the outcome change how people work?
    • The outcome lands within one function
    • Two or three functions must change how they work
    • Most of the organisation is affected in some way
  4. External stakeholders Do parties outside the organisation have a say?
    • No external parties have a say
    • External parties are involved, with broadly aligned interests
    • Regulators, partners or investors can shape or stall it
  5. Incentive conflicts Does the likely outcome create winners and losers among the deciders?
    • Everyone gains, or nobody loses, from the likely outcome
    • Some parties lose ground, and know it
    • The decision creates clear winners and losers among the deciders themselves
  6. Past history between parties Is old friction shaping current positions?
    • The key parties have worked together without friction
    • Some old friction, acknowledged and managed
    • Unresolved history is shaping positions more than the merits are
  7. Communication constraints Can the decision be discussed openly with those affected?
    • The decision can be discussed openly with everyone affected
    • Some parties must be briefed late or partially
    • Confidentiality means key stakeholders cannot be told until it is done
  8. Timeline coupling Is this decision tied to the timing of other decisions?
    • This decision stands alone in time
    • Loosely linked to other initiatives, with slack between them
    • Hard-coupled to other decisions, so any delay cascades
Reading the score

What the result bands mean

0–34: Manageable

The human terrain around this decision is navigable: few approvers, no hidden vetoes, and interests that broadly point the same way. Complexity this low is worth confirming rather than celebrating, because the most common scoring error is counting only the stakeholders you already know about.

35–64: Demanding

This decision has enough moving human parts to fail on coordination alone, even if the underlying choice is right. In this band the danger is uneven attention: the loudest stakeholders get managed while the decisive ones, often the quiet veto holders, get a briefing pack and an assumption.

65–100: High complexity

The stakeholder landscape is itself the main risk to this decision: multiple vetoes, conflicting incentives, history between the parties, and a timeline lashed to other people's decisions. Plans of this shape rarely fail in one dramatic meeting. They dissolve across many small delays that each look reasonable.

Complexity belongs to the decision, not the organisation

The same organisation can pass one decision in a week and trap another for a year, because complexity lives in the specific combination of who must approve, who can block and whose incentives collide. Treating stakeholder management as a standard workstream misses this. A decision with three aligned approvers and a decision with three competing ones need entirely different plans, whatever the organisation chart says.

The costs a complexity score makes visible

Underestimating complexity has a familiar bill: launch dates set before the approval sequence was understood, sponsors spending credibility on rework, and compromises added late that trade away the value the decision was meant to create. Scoring the terrain before committing to dates is the cheap version of learning it afterwards.

Who should use it

  • Sponsors sizing the engagement effort before announcing a timeline.
  • Programme and PMO leads deciding how much governance a decision genuinely needs.
  • Executives inheriting a stalled decision and trying to see why it stalled.

Reading the score

Eight answers at 0, 5 or 10 points, normalised to 100, where higher means more human complexity between the decision and its outcome. A high score is not an argument against the decision. It is an argument against the current plan's assumptions about how easily it will pass.

Frequently asked questions

Is high stakeholder complexity a reason to abandon a decision?

Rarely. It is a reason to re-plan it: sequence the approvals deliberately, resolve the decisive conflicts early and stop promising dates that assume none of this exists. Some of the most valuable decisions are the high-complexity ones nobody else has managed to land.

How is this different from a stakeholder map we already maintain?

A map records who the stakeholders are. This score measures what their combination does to the decision: vetoes multiply with incentive conflicts and old history in ways a list does not show. Use the map as the input and the score as the health check.

The complexity comes from one difficult individual. Does the score help?

Score it anyway. One difficult stakeholder is usually manageable; the score reveals whether the difficulty really is one person or a structure of conflicting incentives that person happens to voice. The remedies for those two situations are entirely different.

The decision is sound. The path is the problem. Map it first.

Get independent perspectives