Fewer than 25% of employees rate their manager as a well-calibrated communicator, according to research from Stanford Graduate School of Business. Francis Flynn and Chelsea Lide analyzed over 2,700 leadership assessments and found that leaders who miscalibrated were nearly ten times more likely to be criticized for undercommunicating than for overcommunicating. The data confirms what every experienced product manager suspects: the core problem with stakeholder communication isn’t disagreement. It’s that people don’t retain what you shared.
The VP who asks the same question you answered in last Tuesday’s update isn’t being dismissive. She’s carrying context from fourteen other products, three board prep sessions, and a reorg she hasn’t announced yet. Your update landed in a stream of information that looked, from her seat, roughly identical to everything else that arrived that day.
Product managers are uniquely exposed to this dynamic because of a cognitive bias psychologists call the curse of knowledge. You spend weeks in discovery calls, data analysis, and engineering trade-off discussions. By the time you present a recommendation, the reasoning feels obvious. You’ve internalized the customer quotes, the competitive moves, the technical constraints. Your stakeholder heard a one-sentence summary in a meeting where she was also thinking about a hiring freeze.
The Attention Math Working Against You
A typical VP or C-level executive sits in 12 to 15 hours of meetings per week across multiple product lines. Research on cognitive load and multitasking shows that high cognitive load reduces both accuracy and retention for information received from multiple sources. Your stakeholder isn’t choosing to forget your update. Their working memory is doing exactly what working memory does: dropping low-salience information to make room for whatever feels most urgent.
A useful frame: the average stakeholder retains roughly the equivalent of a Post-it note from any given update. Three to five words. “Migration delayed two weeks.” “Churn spiked in EMEA.” “New competitor launched.” That’s the resolution at which your carefully constructed status update gets stored. The reasoning, the trade-offs, the mitigations already underway: all of it drops away unless you design for repetition.
Matt LeMay calls this “the art of egregious overcommunication” in Product Management in Practice. The principle is blunt: the downside of undercommunicating is cavernous, while the worst case for overcommunicating is a few eye rolls. Most product managers instinctively do the opposite. They share context once, assume it landed, and then feel frustrated when stakeholders act as if they never heard it.
Three Practices That Account for Forgetting
Instead of treating stakeholder communication as a one-time information transfer, design it for the reality that your audience will forget most of what you share.
The three-sentence re-anchor. Start every stakeholder conversation (meeting, Slack thread, email) with three sentences that re-establish shared context. Not a full recap. Not “as I mentioned last week” (which reads as passive-aggressive to busy executives). Just the minimum context someone would need if they retained nothing from your last interaction.
“We’re in week three of the checkout redesign. Conversion on the new flow is running 4% above the control. The open question is whether to extend the test another two weeks or ship with current data.”
That takes ten seconds to say and saves fifteen minutes of confusion. It also protects you from the failure mode where a stakeholder makes a decision based on context from six weeks ago because nobody refreshed their mental model.
Separate the delta from the full picture. Most product managers write updates that blend new information with standing context, forcing the reader to parse the difference. A more effective structure puts the change first (what’s different since the last update) and the standing context second (as a reference block they can scan or skip). The stakeholder who has been tracking closely reads the first section and moves on. The one who missed the last two updates reads both. Neither feels like you’re wasting their time. This separation is the core idea behind writing stakeholder updates that executives actually read.
Anchor decisions, not information. Stakeholders remember decisions better than data. “We decided to cut the analytics dashboard from V1 and revisit in Q3” sticks because it’s a commitment with consequences. “Analytics dashboard usage is 12% below target and the engineering cost to maintain it is consuming 3 sprint points per cycle” evaporates because it requires the listener to synthesize the implication themselves. When you share information, follow it with the decision it implies or the decision you need. The information becomes context for the decision rather than free-floating data. The stakeholder decision brief is built on exactly this principle.
The Gap Runs Both Ways
Most PM communication advice focuses on outbound messaging: how you share context upward. But the curse of knowledge runs in both directions.
Your VP knows things about the company’s financial position, the board’s priorities, or an upcoming acquisition that shape how she evaluates your proposals. She assumes you understand constraints she hasn’t articulated because they feel obvious from her vantage point. When she pushes back on a roadmap item with a vague “I’m not sure the timing is right,” she may be referencing a budget discussion she can’t share directly.
Over twenty years in operations, I’ve watched this pattern repeat across dozens of organizations. The best product managers treat every ambiguous stakeholder response as a signal that there’s context they haven’t received. Instead of interpreting resistance as disagreement, they ask: “Is there something about the timing or the broader context that I should factor into this plan?” That question, asked without defensiveness, surfaces more useful information than any formal decision brief or alignment process.
Repetition Is the Strategy
The instinct to avoid repeating yourself is social, not strategic. In casual conversation, saying something twice signals that you think the listener wasn’t paying attention. In organizational communication, repetition is how important messages survive the noise floor.
Jeff Weiner, during his tenure as CEO of LinkedIn, described his approach to strategic communication as repeating the company’s priorities until he was tired of hearing himself say them. The point wasn’t that his leadership team was inattentive. The point was that messages need to land seven to ten times before they reliably stick across an organization.
You aren’t running a 16,000-person company, but the principle scales down perfectly. Your three most important product decisions this quarter should appear in some form in every update you send, every review you present, every 1-on-1 you attend. Not because your stakeholders don’t care. Because the research says they will forget, and designing for that reality is a better use of your energy than resenting it.