Why Do Stakeholders Say Nobody Told Them?
Two weeks before launch, a senior leader asks: "Wait, this affects the finance team too? Nobody told me that."
You have documentation showing that finance was included in the original scope deck. They were on the distribution list for updates. Their director was in the steering committee meetings.
But yet: surprise.
Why do stakeholders say nobody told them?
Getting information isn't the same as processing it.
Most stakeholders are on distribution lists for dozens of initiatives. They skim updates, attend meetings while checking email, and assume someone will flag anything that needs their attention.
They're not being negligent. They're being realistic about their capacity.
The problem emerges when you treat "they were informed" as equivalent to "they understand the implications."
Those aren't the same thing.
Why do stakeholders miss how a change affects them?
Stakeholders often understand the change but miss how it affects them specifically.
"We're implementing a new approval workflow" registers as someone else's problem until it becomes "you'll need to reallocate two people from your team for three months to support testing."
That implication was always in the plan. But it wasn't explicit enough to break through general awareness and create specific attention.
By the time it becomes explicit, it feels like new information even when it was technically disclosed months ago.
When does a stakeholder actually start paying attention?
Stakeholders pay attention when they need to make a decision.
Early in a change, they don't need to make decisions yet. So they track progress generally without engaging deeply.
Later, when decisions become urgent, they don't have the context to make them well. And there's no time to build that context from scratch.
This creates the "suddenly surprised" pattern: they were technically aware all along, but only started paying attention when it was too late to influence the outcome.
How do I keep stakeholders informed without more updates?
Effective stakeholder communication isn't about keeping people informed.
It's about:
Flagging implications before they become urgent
Matching information depth to decision timing
Distinguishing between "FYI" updates and "action required" escalations
Building context incrementally so decisions make sense when they arrive
This means different stakeholders need different information at different times, not just different versions of the same update.
Why do stakeholders get surprised by a project?
Stakeholders get surprised when:
Implications are buried in general updates instead of called out explicitly
The gap between "you should know about this" and "you need to act on this" is too long
Decision requirements arrive without sufficient context
Scope changes happen silently without resetting stakeholder understanding
None of these are communication failures in the traditional sense. They're coordination failures.
What should a stakeholder update contain?
Before your next stakeholder update, ask: "What decision will this person need to make, when will they need to make it, and what do they need to understand before that decision point arrives?"
Then design your stakeholder communication to build that understanding incrementally.
Don't wait until the decision is urgent to provide the context.
References & Related Reading:
1) Sweller, "Cognitive Load During Problem Solving" (Cognitive Science, 1988): https://onlinelibrary.wiley.com/doi/10.1207/s15516709cog1202_4
2) Newton's Stanford tapper-listener experiment (1990), summarized by Temple University: https://law.temple.edu/aer/2021/03/02/brain-lessons-tappers-and-the-curse-of-knowledge/
If you're planning how to announce a change, The DANCE System gives you 29 tools for planning and communicating it in five phases, from defining the scope to keeping it in place after launch.
Related Blog Posts:
Why do clear announcements still confuse people?
How do I announce what's changing and what's not?
What is the team asking that the announcement isn't answering?
