Vizually
ArticleProject Lifecycle3 min read

7 Stakeholder Identification Mistakes That Wreck Mid-Size Campaign Projects

Seven specific stakeholder identification mistakes new project managers make on mid-size campaign projects — with corrective steps that work even mid-flight.

Vizually Team·
Initiation & Chartering

The seven names you missed and the seven days you'll lose

Most stakeholder lists on campaign projects are populated by who showed up, not by who matters. The two are rarely the same.
Vizually editorial

Mid-size companies are large enough that you don't know everyone, and small enough that there's no formal stakeholder mapping process. New campaign project managers fall into a predictable set of identification mistakes — none of them dramatic, all of them expensive at approval time. The seven below are listed in order of how often they appear in retrospectives.

Each one is paired with a corrective: what to do once the mistake has been made and you're already mid-project. The preventive version of all seven is captured in the enterprise preventive playbook; this article is for when you're past prevention.

  1. Mistake 1
    Treating the brief attendees as the stakeholder list
    If everyone in the brief room is in marketing, you have not identified stakeholders — you have identified your team. Fix: list every approval gate and name a human behind each one, then audit who's missing.
  2. Mistake 2
    Naming functions, not humans
    'Legal' is not a stakeholder. 'Priya, senior counsel' is. Functions don't have opinions; humans do. Fix: replace every function name in the register with a person's name and a contact path.
  3. Mistake 3
    Skipping the founder or CEO when the topic is sensitive
    On brand, pricing, partnerships, or anything public-facing, the CEO has a position whether or not you've asked. Fix: send a one-paragraph 'here's what we're doing' note before final review. Their reaction surfaces issues cheaply.
  4. Mistake 4
    Forgetting the salesperson with the loudest customer
    If a key account is the implicit reason for the campaign, the AE owns a stake. Skipping them means a parallel commitment forms that you'll have to absorb later. Fix: identify the top three named accounts that this campaign is really for, and pull their AEs into the brief.
  5. Mistake 5
    Treating freelancers and agency partners as vendors, not stakeholders
    External creatives have stakes in scope, timeline, and asset reuse rights — and they make decisions you'll inherit. Fix: include the agency lead in the stakeholder register with explicit decision authority captured.
  6. Mistake 6
    Missing the regional or BU owner
    On any campaign that runs in more than one region or BU, the local owner has a stake even if the campaign is centrally produced. Fix: pre-brief one named regional owner per region; absence of objection is captured as a positive yes, not assumed.
  7. Mistake 7
    Identifying stakeholders once and never updating
    The stakeholder list at brief is wrong by week three. People change roles. New programs collide. Fix: a 10-minute weekly stakeholder review by the PM — three questions: 'Who's new? Who's gone? Who's surprised us?'

Quick recovery actions, in order

0 / 5
  • List every name currently in the campaign approval routing
  • Add one column: 'when did this person first see direction?'
  • For anyone whose answer is 'final review,' schedule a 15-minute pre-brief this week, even if final review is days away
  • Flag any approval whose owner you cannot name — that's a governance problem, not a stakeholder problem
  • Update the stakeholder register and circulate a one-line note to the team about what's changed

These seven mistakes account for the large majority of stakeholder identification failures on mid-size campaign work. The pattern underneath them is consistent: stakeholder lists get built from who's present, not from who has authority. The corrective is just as consistent: replace presence with authority, function names with human names, and one-time identification with weekly review. None of these are difficult; they're discipline.

For the version of this work that prevents the mistakes from happening, see preventing silent disagreement on enterprise campaigns. For the same pattern in a different setting, see enterprise construction's late-arriving stakeholders.

More in
CategoryProject Lifecycle

Related reading

Articlethe preventive playbook for enterprise campaignsArticlethe same pattern in physical projectsArticlethe startup software wizard