Building a Stakeholder Map for Enterprise Campaigns Before Sign-Off
Enterprise campaigns get killed by stakeholders who weren't in the room at brief. A preventive playbook for project managers — including the silent-disagreement signals that surface late approvers.
The legal reviewer you didn't invite is the one who shifts your launch date
On enterprise creative work, the people most likely to block a launch are the ones least likely to attend the brief.
Enterprise campaigns die in approval rounds. The creative work gets done, the team is ready, and then a name appears in the routing — legal, brand governance, regional compliance, a senior leader's chief of staff — and the launch slides by two weeks. The people who triggered the slide weren't hiding. They were structurally absent from the brief, not invited because the project manager mapped stakeholders by who was already in the room.
This is the silent disagreement pattern in its enterprise creative form. The preventive intervention is not more meetings. It's a stakeholder map that identifies, at brief, who has approval authority three steps downstream of where the work happens today.
- Day 1Run the routing pre-mortemBefore brief, list every approval the campaign will need before it ships. Owned media, paid media, partner channels, executive sign-off, legal, brand. Each one is a stakeholder, even if a system handles the routing.
- Day 2Name the human behind each approvalFor every approval listed, name the specific person who will press the button — not the team or the system. If you can't name them, that is the first thing to fix, not the campaign.
- Day 3Pre-brief the late approversEach named approver gets a 15-minute pre-brief on direction. Not the asset — the direction. The goal is to surface objections at concept, not at final review.
- Day 4Lock the briefBrief includes the stakeholder map and the pre-brief notes. Anyone joining late gets pointed to the artifact, not invited to a re-brief.
The three stakeholder classes most often missed
On enterprise campaign work, three classes of stakeholders disappear from briefs and reappear at approval:
1. Legal and brand governance. They review at end-state. If they don't see direction at concept, they reject specifics at the worst possible time. 2. Regional or business unit owners. A global brand campaign that hasn't touched the regions before final review will lose two weeks per region in late conditioning. 3. Senior leader chiefs of staff. They prep their principal for the final review. If they're surprised by the work, the principal will be too — and surprises rarely produce approvals.
None of these are bad-faith actors. They're rational responses to being invited at end-state.
Stakeholder map review before brief
0 / 5- Every named approval gate has a specific human attached, not a function
- Legal, brand governance, and senior chiefs of staff each have a 15-minute pre-brief scheduled
- Regional or BU owners have either been pre-briefed or explicitly excluded with sign-off
- Anyone surfaced in pre-briefs as having concerns is named in the brief, with their concern logged
- The team has agreed on a default 'no new stakeholders after brief' rule, with named exceptions
When this fails
The technique fails in two situations. First, when the project manager treats pre-briefs as box-checking — running them but not actually surfacing or addressing direction concerns. The pre-brief is a listening exercise; conducted as a broadcast, it provides almost no protection. Second, when senior leadership routinely overrides stakeholder maps in approval rounds, adding new approvers late. That's a governance problem, not a stakeholder problem, and stakeholder mapping cannot fix it.
For the retrospective view of when this all goes wrong, see the same pattern in enterprise construction. The names differ; the structure is identical.