There’s a specific, uncomfortable spot many capable people find themselves in: sending frequent, detailed updates to senior leadership out of genuine diligence, only to sense that those updates are being skimmed, ignored, or quietly resented for taking up time. The instinct behind over-reporting is usually good — a genuine desire to keep leadership informed and demonstrate diligence. The execution, though, often misses what leadership actually needs, which is considerably less than what a conscientious person instinctively wants to provide.
Why More Information Isn’t the Same as Better Communication
Senior leaders are, almost by definition, managing a wider span of attention than anyone reporting to them — more projects, more people, more competing priorities. An update calibrated for someone with deep, ongoing context on a specific project is usually miscalibrated for someone managing a dozen other things simultaneously. Communicating up well means adjusting not just the tone but the actual density and framing of information, not simply sending the same detailed update you’d give a close collaborator.
What Leadership Actually Needs to Know
The headline first, always. A senior leader scanning an update needs the actual state of things — on track, at risk, off track — immediately, not buried at the end of a detailed narrative. Leading with the headline respects the reality that most updates get read quickly, not studied carefully.
What’s changed since the last update, not a full restatement of everything. Repeating unchanged context in every update trains a reader to skim past your updates entirely, since most of the content is redundant with what they already know. Focusing specifically on what’s new since the last communication keeps each update genuinely worth reading.
Risks and decisions needed, clearly flagged. Leadership generally wants visibility into what could go wrong and what requires their input, more than a comprehensive account of what’s going smoothly. Burying a genuine risk or a needed decision inside an otherwise routine update risks it being missed entirely.
A level of detail matched to what they’d actually act on. If a piece of information wouldn’t change what a senior leader does next, it likely doesn’t need to be in the update at all — interesting detail and actionable information are different things, and calibrating toward the latter respects their limited attention.
How to Calibrate Frequency
Match frequency to genuine volatility, not habit. A stable, low-risk project may only need a brief update every few weeks; a genuinely volatile situation may warrant more frequent contact. Sending the same cadence regardless of actual risk level trains leadership to expect noise rather than signal from your updates.
Ask directly what cadence and format leadership actually prefers. Different leaders have different preferences — some want a brief weekly bullet list, others prefer a monthly deeper dive with real-time flags only for genuine emergencies. Asking directly, rather than guessing, avoids the common trap of calibrating to your own instincts rather than their actual needs.
Reserve unscheduled contact for things that genuinely can’t wait. If every update, regardless of urgency, arrives through the same unscheduled channel, leadership loses the ability to distinguish a routine note from something genuinely urgent. Protecting unscheduled contact for things that truly warrant it keeps that channel meaningful.
Why Under-Communicating Is Also a Genuine Risk
It’s worth being clear that the goal isn’t minimal communication — it’s well-calibrated communication. A leader genuinely surprised by a problem that had been developing for weeks, with no earlier flag, has a legitimate complaint, and “I didn’t want to bother you” is rarely a satisfying explanation after the fact. The skill isn’t reducing communication uniformly; it’s directing more of it toward what’s genuinely decision-relevant and less toward routine detail that doesn’t actually change anything for the reader.
Framing Bad News Well
Lead with the issue, not a long build-up. Burying bad news at the end of an otherwise positive-sounding update, hoping the surrounding context will soften it, tends to read as evasive once the reader reaches it — leading clearly with what’s actually wrong, then following with context and a plan, reads as more credible and more respectful of their time.
Pair a problem with your recommended response, not just the problem alone. Flagging an issue without any accompanying thinking about what to do about it puts the entire burden of the next step on the reader. Even a tentative recommendation gives them something to react to, rather than a blank problem to solve from scratch.
Don’t wait for certainty before flagging a developing risk. A risk flagged early, while it’s still manageable, is considerably more useful to leadership than the same risk reported only once it’s become a fully realised problem — waiting for complete certainty before raising a concern often means raising it too late to matter.
Building Genuine Trust Over Time, Not Just Sending Good Updates
A single well-calibrated update is useful; a consistent pattern of well-calibrated updates over time is what actually builds genuine trust with senior leadership. Leaders remember whether previous updates turned out to be accurate — whether a status marked “on track” genuinely stayed on track, whether a flagged risk turned out to be a real one worth the attention it received. This track record, built up over many updates, is what eventually earns the kind of credibility where a leader takes your word at face value rather than feeling the need to dig deeper themselves. Protecting this credibility means resisting the temptation to consistently mark things more positively than they genuinely are, even when a less rosy update feels uncomfortable to send.
Adjusting Your Approach for Different Leaders
Not every senior leader wants the same thing, and assuming a single, universal template for “communicating up” misses genuine, important variation between individuals. Some leaders are detail-oriented and want to see the underlying data; others want only the synthesised conclusion and trust you to have done the analysis. Some prefer written updates they can read at their own pace; others prefer a brief verbal check-in where they can ask follow-up questions directly. Paying attention to how a specific leader actually engages with your updates — and adjusting accordingly, rather than applying one fixed approach regardless of the audience — is part of what separates genuinely skilled upward communication from a well-intentioned but poorly calibrated default.
A Practical Scenario
A project lead has been sending his executive sponsor detailed weekly updates covering every workstream in depth, assuming this demonstrates diligence and keeps her genuinely informed. After noticing the updates seem to go largely unread, he asks her directly what she actually finds useful, and learns she mainly wants a brief, three-line headline on overall status, with detail only on anything genuinely at risk or requiring her input.
He restructures accordingly: a short headline update each week, with a longer, detailed version available on request rather than sent by default, and immediate, unscheduled contact reserved specifically for genuine risks that can’t wait for the next regular update. His sponsor’s engagement with his updates improves noticeably — not because he’s communicating less overall, but because what he’s sending is now genuinely calibrated to what she actually needs to act on.
Common Mistakes
Sending the same level of detail to senior leadership as you would to a close collaborator. This misjudges how much context and attention a senior leader, managing a much wider span, actually has available for any single update.
Repeating unchanged context in every update rather than focusing on what’s new. This trains a reader to skim past your updates entirely, since much of the content is redundant with what they already know.
Burying a genuine risk or decision inside an otherwise routine, positive-sounding update. This risks it being missed entirely by a reader scanning quickly for the headline.
Waiting for complete certainty before flagging a developing risk. By the time certainty arrives, the risk has often become considerably harder to address than it would have been if flagged earlier.
Action Steps
- Ask a senior stakeholder directly what cadence and format of update they actually find useful, rather than assuming based on your own instincts.
- Restructure your next update to lead with a clear headline, followed by what’s changed since the last update, rather than a full restatement.
- Identify any genuine risk currently buried within a routine update, and give it clear, separate visibility instead.
- The next time you need to flag bad news, lead with the issue directly and pair it with your recommended next step.
- Review your recent communication frequency against actual project volatility, and adjust if you’ve been sending the same cadence regardless of genuine risk level.
Key Takeaways
- Senior leaders generally need less detail and more calibrated framing than a close collaborator would, given the wider span of attention they’re managing.
- Leading with the headline, and focusing on what’s changed rather than a full restatement, keeps each update genuinely worth reading.
- Communication frequency should match actual volatility and risk, not habit, and should be confirmed directly with the stakeholder rather than assumed.
- Under-communicating is as much a genuine risk as over-communicating — the goal is calibration, not minimalism.
- Flagging a developing risk early, paired with a recommended response, is considerably more useful to leadership than waiting for certainty or presenting a problem without any accompanying thinking.
Conclusion
Communicating up well isn’t about sending more information to demonstrate diligence — it’s about calibrating what you send to what a senior leader, managing a wide span of competing priorities, can actually absorb and act on. Leading with the headline, focusing on genuine change and risk, and confirming preferred cadence directly all build a communication pattern leadership actually reads and trusts, rather than one that quietly gets skimmed past regardless of how much genuine effort went into producing it.
Frequently Asked Questions
How can I tell if I’m over-communicating with senior leadership?
Signs include updates that go consistently unread or unacknowledged, or direct feedback that your communications feel repetitive — asking the stakeholder directly what they find useful is the most reliable way to check.
Is it better to under-communicate than to risk overwhelming a busy leader?
No — under-communicating carries its own genuine risk, since a leader surprised by a problem that had been developing without any earlier flag has a legitimate complaint. The goal is calibration, not minimal contact.
How should I decide what counts as genuinely urgent enough for unscheduled contact?
Reserve unscheduled contact for things that genuinely can’t wait for the next regular update — protecting this channel for true urgency keeps it meaningful rather than diluted by routine content.
What’s the best way to structure a brief status update?
A clear headline on overall status, followed by what’s changed since the last update, and any risks or decisions needed — in that order, so a reader scanning quickly gets the most important information first.
Should bad news be delivered differently than routine updates?
Yes — lead directly with the issue rather than burying it after positive context, and pair it with your recommended next step, since this reads as more credible and more respectful of the reader’s time than an evasive build-up.
How do I know what cadence and format a specific leader actually prefers?
Ask them directly — different leaders have genuinely different preferences, and confirming this explicitly avoids the common trap of calibrating updates to your own instincts rather than their actual needs.
How does communicating up build genuine trust over time, not just in a single update?
A consistent track record of accurate, well-calibrated updates — where a status marked “on track” genuinely stayed on track — is what eventually earns a leader’s trust at face value, rather than any single well-written update alone.
Should I use the same communication approach for every senior leader I report to?
No — leaders vary genuinely in how they prefer to engage, from detail-oriented data reviews to brief, synthesised verbal check-ins, and adjusting your approach to the specific person improves how well your communication actually lands.
What should I do if I’ve been over-communicating for a long time and want to reset the pattern?
Name the change directly rather than simply going quiet without explanation — telling leadership you’re shifting to a more focused update format, and why, prevents the reduced frequency from being misread as reduced diligence.