Most strategic roadmaps assume a straight line: budget approval → delivery.
Reality looks more like this: stakeholder drift, hidden dependencies, approvals that stall, suppliers that slip, and a team doing last-minute triage while leadership expects certainty.
When I audit a plan, I’m not looking for ambition. I’m looking for the quiet assumptions — the things the deck implies will “sort themselves out”.
So I run a simple Vulnerability Mapping protocol: Likelihood × Impact. Every deliverable goes into one of four buckets. The aim isn’t more task management. It’s to find where delivery is fragile before it becomes visible.
What it looks like: inconsistent stakeholder reporting, unclear sign-off routes, version chaos, repeated scrambles for assets and inputs.
What it does: it drains momentum and increases error rates. A tired team makes avoidable mistakes.
What to do: systematise. If it happens more than twice, it gets a checklist, a rule, or automation.
Example mapping: weekly status updates → no fixed format → decisions slip by a week.
What it looks like: vendor misalignment, missing resourcing, unclear decision rights, dependencies with no buffer, processes that haven’t been tested under real conditions.
What it does: it stops execution cold. When this breaks, the comms plan is irrelevant.
What to do: remediate before execution ramps. This is where most pre-delivery effort belongs.
Example mapping: launch messaging → legal review not booked → copy locked late → everything downstream compresses.
What it looks like: regulatory shifts, external events, reputational shocks, last-minute changes you can’t control.
What it does: it forces reactive decisions under pressure.
What to do: pre-decide your response. Draft the holding statement, align approvals, and define who makes the call.
Example mapping: press attention spikes → no approved lines → leadership goes off-message.
What it looks like: senior time spent debating low-impact details while high-impact risks remain unresolved.
What it does: opportunity cost. It steals time from the risks that actually decide outcomes.
What to do: label it and park it. Give the programme lead permission to deprioritise.
Example mapping: design tweaks → multiple exec opinions → two days lost → critical dependency untouched.
The result isn’t a longer to-do list. It’s a heat map of what will break first — and a prioritised plan to prevent it.
It allows a Director, Head of Comms, or Programme Lead to say:
“We’ve reduced friction, parked the noise, covered contingencies, and focused on the critical risks — so the strategic plan gives the business/policy objectives a real foundation.”
That’s the difference between a roadmap that reads well and one that survives reality.
