Project management practice

Stakeholder map example: connect influence to a delivery decision

Map stakeholder needs, decision rights and engagement actions using a fictional rollout. Move beyond a power-interest grid to a useful conversation plan.

Map a decision, not a personality

A stakeholder map is useful when it changes how you involve people. Record who is affected, what they need, what they can decide and what evidence they lack. Influence and interest are working hypotheses, not fixed personal labels.

Start with the next material delivery decision. An opening-date choice may affect operations, facilities, security, the installer and the sponsor in different ways. A person with little formal authority can still reveal a condition that makes the plan unusable.

Worked example: opening the new entrance

RoleNeed or concernDecision/inputEngagement action
Operations leadAvoid queues during morning arrivalAccept the temporary access processWalk through peak arrival before recommending go-live.
Security reviewerEvidence access rules workApprove security test evidenceBook evidence review before the acceptance milestone.
SponsorUnderstand cost/date trade-offAuthorise baseline changeSend options and latest useful decision date.
InstallerStable access and configurationConfirm installation durationValidate prerequisites and crew availability.

Turn a grid into a plan

A power-interest grid can help you prioritise, but it does not tell you what to say. Add an engagement objective, owner, channel and date. “Keep informed” becomes useful only when you know what the person needs to understand or do.

Check your assumptions with the person where possible. Do not infer resistance from a missed meeting. Ask whether the proposed timing, channel or decision framing is preventing useful input. Update the map when responsibilities or impacts change.

Copyable engagement row

Role / affected outcome:
Need, concern and evidence source:
Decision right or required contribution:
Current understanding / uncertainty:
Engagement objective:
Message or question / channel / owner / date:
Response and next action:
Review trigger:

Handle competing interests openly

If operations wants the original opening date and security needs another test, make the conflict explicit. Ask which acceptance condition is unresolved and whether a safe phased opening is possible. The map supports the conversation; it does not replace accountable approval.

Keep sensitive personal assessments out of shared templates. Record role-relevant needs and observable commitments instead of speculative judgements about individuals.

Method background

These sources provide general background. The worked examples and worksheets are original Response Shift teaching material; the organisations do not endorse this product.