The one‑page stakeholder plan you can use in 30 minutes
Stakeholder mapping tells you who matters. Alignment tells you how the decision should travel.
Then reality hits: you’re in motion, the calendar is full, and the programme starts to drift because nobody can remember what was agreed, who owes what, and what the trade‑off actually was.
That’s what this one‑page plan is for. It’s a working artefact for directors and C‑suite leaders: clear enough to use under pressure, specific enough to stop “polite sabotage”, and short enough that it actually gets updated.
A moment you’ll recognise
A director in a UK‑regulated organisation is running a change programme with multiple workstreams. The steering committee has “approved” the direction. The sponsor is broadly supportive.
Two weeks later, the programme is bleeding time through small, reasonable requests:
• Legal wants a wording change.
• Risk wants another review.
• Operations wants a phased rollout.
• Procurement wants to revisit a supplier assumption.
Nobody is openly blocking. But the decision is being dismantled by delay.
The director doesn’t need another stakeholder register. They need a one‑page plan that turns stakeholder complexity into named commitments.
What people get wrong
They build stakeholder plans as documentation. The plan becomes a record of who exists, not a tool for what happens next.
They also treat “stakeholder management” as a relationship exercise. At senior level, it’s a delivery discipline: decisions, trade‑offs, constraints, and ownership.
The one‑page stakeholder plan (copy this)
Keep it to one page. If it spills over, you’ve avoided prioritisation.
1. Decision (one sentence) Write the decision you need to move. Not the project name. The decision.
Example: “Approve the onboarding journey design for the next 90 days, including the assurance controls we will accept.”
1. Primary optimisation goal (pick one) For the next 90 days, are you optimising for speed, assurance, cost, or customer experience? One primary. A secondary is allowed, but only one primary.
2. The trade‑off (state it plainly) Write the trade‑off you are choosing.
Examples:
• “We will accept a slower customer journey to reduce regulatory exposure.”
• “We will accept higher cost to reduce operational fragility.”
1. Top stakeholders (six names, not thirty) List the six people who can accelerate, block, or reshape the decision. Include informal power.
2. For each stakeholder: three lines only For each of the six, write:
• Optimising for: what they are measured on (their incentive)
• Constraint: what would make this unacceptable (their non‑negotiable)
• Ask: what you need from them (a specific behaviour)
Make the “Ask” concrete:
• “Sign off by Tuesday” beats “support the programme.”
• “Back the trade‑off in the steering group” beats “be a sponsor.”
1. Risks (the ones that actually bite) List 3–5 stakeholder‑linked risks. Examples:
• Late‑stage reversals (“yes‑then‑block”)
• Quiet veto points (security, procurement, data protection)
• Reputational anxiety (fear of scrutiny)
• Capacity constraints (Ops can’t absorb more work)
2. Commitments (named, dated) Write 5–8 commitments with names and dates.
Example: “Risk (A. Patel) to confirm control threshold by Friday.”
1. Trigger to revisit (so you don’t re‑litigate) Write the trigger that forces a revisit.
Examples:
• “If conversion drops below X% for two weeks, we revisit.”
• “If Compliance identifies a material control gap, we pause.”
Why this works
It converts stakeholder complexity into a small set of visible commitments.
It also gives you a governance anchor. When someone reopens the debate through a “quick question”, you can point back to the decision, the trade‑off, and the trigger.
The explicit trade‑off
This plan sacrifices completeness for usability.
You will miss some names. That’s acceptable. The bigger risk is building something so detailed that nobody uses it — and the programme dies slowly through drift.
A closing script you can use today
When you meet a key stakeholder, close with:
“Given what you’re accountable for, what would make this unacceptable — and what would make you comfortable backing it?”
That question surfaces constraints early, while you still have room to design around them.
Leadership Insights: https://www.bapdglobal.com/leadership-insights Stakeholder Management: https://www.bapdglobal.com/leadership-insights-stakeholder-management