Because saying yes to everything isn’t serving the organization. It’s serving the request.
Most internal communications professionals are trained to deliver.
A request comes in. A message needs to go out. A stakeholder needs something communicated. The IC professional produces it — professionally, on time, to specification.
That’s execution. And execution is a real and valuable skill.
But execution is not the whole job.
There are specific situations in which the IC professional’s responsibility to the organization — to the employees who will receive the communication and to the organizational outcomes that communication is supposed to serve — requires something harder than delivery.
It requires pushback.
Not obstruction. Not refusal. Not the kind of territorial defensiveness that makes IC functions difficult to work with.
Deliberate, evidence-based, professionally framed resistance to communication that will damage rather than build the organizational clarity, trust, and alignment that the IC function exists to protect.
This article names those situations — and gives IC professionals the language to navigate them.
Why IC professionals avoid pushing back
The pressure against pushback is real and comes from every direction simultaneously.
Organizational hierarchy creates pressure. The person requesting the communication is almost always more senior than the IC professional producing it. Pushing back on a VP’s communication request requires a specific kind of professional confidence — the confidence to say, in effect, “I have expertise in this domain that your seniority doesn’t override.”
Relationship pressure creates more. IC professionals work with the same stakeholders repeatedly. Saying no — or even saying “I have concerns” — creates friction in relationships that the IC professional depends on to do their job effectively. The short-term cost of pushback feels immediate and concrete. The long-term cost of not pushing back feels abstract until the communication damages something.
Role ambiguity creates the most. In many organizations, the IC function’s role is not clearly defined as a strategic one. When IC is positioned as a service function — when the job is understood as producing what’s requested rather than advising on what should be produced — pushback feels outside the scope of the role rather than central to it.
All of these pressures push toward compliance. And compliance, in situations where pushback is genuinely warranted, produces communication that damages organizational trust, credibility, and alignment in ways that take far longer to repair than the pushback would have taken to resolve.
The eight situations that warrant pushback
1. When the communication manages perception rather than creates understanding
The clearest signal that pushback is warranted is communication designed primarily to make leadership look good rather than to help employees understand what’s happening.
The signals are recognizable. Language that is unusually polished. Framing that emphasizes positives without proportionate acknowledgment of difficulty. Rationale that explains why the decision was good without addressing the legitimate concerns employees will have about it. A tone that doesn’t match the reality employees are experiencing.
This kind of communication doesn’t just fail to land. It actively damages trust — because employees can detect managed perception. They’ve received enough of it to have developed sophisticated pattern recognition for what it signals: that the communication was designed for the sender’s comfort rather than the audience’s understanding.
When IC produces this communication without pushback, the function becomes complicit in the trust erosion it’s supposed to prevent. The pushback isn’t “I won’t produce this.” It’s “this communication is designed to manage perception rather than create understanding — and here’s what that will cost us, and here’s what I’d propose instead.”
2. When the timing serves the sender rather than the audience
Timing requests that serve organizational politics, leadership preferences, or project schedules without regard for audience readiness are one of the most common situations warranting IC pushback.
The announcement that needs to go out before the weekend because the executive team is traveling next week. The communication that needs to be sent immediately because a decision was made and leadership wants it communicated before the informal network gets there first. The message that’s being rushed because a stakeholder is uncomfortable with the uncertainty rather than because the audience is ready for the information.
Each of these timing decisions prioritizes the sender’s situation over the audience’s readiness. And communication that arrives before the audience is ready to receive it — before they have the context to understand it, before they can act on it, before the emotional conditions exist for it to land constructively — consistently produces worse outcomes than communication that waits for the right moment.
IC’s professional responsibility includes naming this dynamic explicitly when it’s occurring — and making the case, with specific evidence about audience readiness, for timing that serves communication effectiveness rather than sender convenience. (For the full framework on timing decisions, read When to Communicate Early During Change — and When to Wait.)
3. When the narrative is inconsistent with what has been previously communicated
When a new communication contradicts, significantly shifts, or is materially inconsistent with what employees have previously been told — without acknowledging that shift — IC should push back before it goes out.
Narrative inconsistency is one of the fastest trust destroyers available. Employees who receive communication that contradicts previous communication don’t conclude that the situation has evolved. They conclude that one of the messages wasn’t fully truthful. And that conclusion doesn’t apply only to the inconsistent message. It applies retroactively to everything that came before it and prospectively to everything that comes after.
IC professionals who have been tracking the organizational narrative — who know what has been communicated, to whom, and when — are often the only people in the room who can identify when a new communication is inconsistent with the existing one. That knowledge is the basis for a specific and valuable form of pushback: “This communication is inconsistent with what we told people in March, and sending it without acknowledging that shift will produce a trust problem. Here’s how I’d propose we address the inconsistency.” (For how narrative consistency connects to organizational trust, read Why Leaders Lose Credibility.)
4. When the communication is premature
When a decision hasn’t been fully made but communication is being requested that implies it has — or when information is being communicated before the implications have been worked through enough to be communicable accurately — premature communication creates expectations that reality will subsequently fail to meet.
The cost of that gap — between what was communicated and what actually happens — is paid entirely in organizational trust. And it compounds: every subsequent communication is received in the shadow of the previous premature one.
IC pushback in this situation is specific: “This communication implies a decision that hasn’t been fully made. When that decision changes — and there’s significant risk that it will — we will have damaged our credibility with this audience. I’d recommend waiting until X, or framing this as a decision in progress rather than a concluded one.”
5. When the volume is creating signal fatigue
When the cumulative volume of communication is creating the conditions for signal fatigue — when the organization is receiving more messages than it can meaningfully process, when important signals are being lost in the noise of less important ones, when the sheer frequency of communication is training employees to ignore official channels — adding another message is not serving the communication objective. It’s compounding the problem.
IC professionals are often the only people with visibility across the full communication landscape — who can see that this stakeholder’s “urgent” message is the fourteenth communication employees have received this week on unrelated topics, and that the fourteenth message is not going to land any better than the thirteenth.
Pushback here is framed as resource allocation: “Adding this communication to the current environment is unlikely to produce the outcome you’re looking for, because the audience is already saturated. Here’s what I’d recommend instead — either delaying until the communication environment has space, or finding a way to consolidate this with other messages that are already scheduled.” (For why signal fatigue matters, read Change Communications: Why Clarity Matters More Than Volume.)
6. When the communication doesn’t answer the questions employees are actually asking
When a communication has been designed to answer the questions leadership wants answered rather than the questions employees are actually asking — when it addresses the organizational rationale without addressing the personal implications, when it explains what is happening without explaining what it means for the people receiving it — it will produce the confusion and informal speculation that IC exists to prevent.
This is perhaps the most common form of communication that warrants IC pushback — and the most frequently missed, because it requires the IC professional to represent an audience that isn’t in the room. The stakeholder who requested the communication is in the room. The employees who will receive it are not. Pushback here requires the IC professional to be the proxy for the audience — to say explicitly: “This communication answers the questions we have about this decision. It doesn’t answer the questions employees will have. Here are those questions, and here’s what I’d propose we add.”
7. When the communication asks employees to do something they haven’t been equipped to do
When a communication announces an expectation — a behavior change, a new process, a new requirement — without providing the information, tools, or support that would make compliance possible, it creates the conditions for failure rather than success.
Communication that announces a requirement without enabling it damages both the specific objective and the broader credibility of organizational communication. Employees who receive a directive they can’t follow — not because they’re unwilling but because they genuinely don’t know how — experience the gap between the announcement and the enablement as organizational dysfunction.
IC pushback here is practical: “This communication announces an expectation that employees aren’t currently equipped to meet. Before this goes out, we need X. Otherwise we’re setting people up to fail and ourselves up to manage the fallout.”
8. When the communication contains information that isn’t accurate
The clearest and least negotiable situation for IC pushback is when a communication contains information that the IC professional has reason to believe is inaccurate — information that doesn’t reflect the current state, commitments that haven’t been confirmed, timelines that are aspirational rather than realistic.
This is the professional boundary that matters most — and the one IC professionals are sometimes most reluctant to assert, because it requires directly challenging a stakeholder’s claim.
The framing is straightforward: “I want to flag that this communication includes information I believe to be inaccurate — specifically X. If we send this and the information turns out to be wrong, the credibility damage will be significant and will affect future communications. I’d like to verify this before it goes out.”
That’s not obstruction. That’s professional responsibility. (For how inaccurate communication affects organizational trust, read How Leaders Accidentally Create Confusion.)
How to push back effectively
Knowing when to push back is one skill. Knowing how to do it in a way that is heard rather than dismissed — that strengthens rather than damages the IC professional’s organizational standing — is a different one.
Lead with the organizational consequence, not the professional objection.
The least effective pushback is “I don’t think we should send this.” The most effective is “If we send this, here’s what will happen and here’s what it will cost us.” The difference is that the first positions the IC professional as an obstacle. The second positions them as an advisor with specific knowledge about communication outcomes that the stakeholder may not have.
Be specific about the risk.
Vague concerns are easy to dismiss. Specific, evidence-based concerns about specific outcomes are harder to ignore. “This communication will produce confusion because it doesn’t answer the question employees are actually asking” is more actionable — and more persuasive — than “I’m not sure this is the right approach.”
Come with an alternative, not just an objection.
The IC professional who pushes back without an alternative leaves the stakeholder with a problem and no solution. The one who pushes back with a specific recommendation — “here’s what I’d propose instead, and here’s why I believe it will produce a better outcome” — positions themselves as a partner rather than a gatekeeper.
Choose the moment carefully.
Pushback in a large meeting where the stakeholder is exposed is more likely to produce defensiveness than reconsideration. Pushback in a one-on-one conversation, or in a written note before the meeting, gives the stakeholder room to adjust without losing face. The goal is a better communication outcome, not a public correction.
Know when to escalate.
When pushback on a specific communication doesn’t produce a satisfactory outcome — when the communication goes out despite legitimate concerns — the IC professional’s responsibility may extend to flagging the pattern to a more senior level. Not every disagreement warrants escalation. But a pattern of communication that is consistently damaging organizational trust, and that individual pushback hasn’t been able to address, is a pattern that the IC professional is professionally obligated to surface. (For how this connects to the IC professional’s strategic role, read The Real Job of a Communications Leader.)
What effective pushback looks like in practice
I worked with a senior IC professional preparing for a conversation with a senior leader who wanted to send an all-staff communication about a restructure outcome before the affected employees had been individually notified.
The leader’s rationale was that the all-staff communication would prevent speculation and ensure everyone received consistent information simultaneously.
The IC professional’s concern was that sending an all-staff message about role changes before the affected individuals had been informed — before they’d had a conversation with their manager, before they knew specifically what the change meant for them — would produce exactly the kind of shock and betrayal that the most careful restructure communication is designed to prevent. People would learn that their role was changing by reading about it in an email alongside their colleagues.
The pushback was framed around organizational consequence: “If we send this before individual notifications are complete, we will have communicated a life-affecting change to some employees through an all-staff email rather than through a personal conversation. The trust damage from that experience will be very difficult to repair — and it will affect how these employees receive every communication we send for the foreseeable future. I’d strongly recommend a sequencing approach where individual notifications happen first, followed by an all-staff communication that can reference those conversations.”
The leader agreed. The sequencing was adjusted. The restructure communication was received with significantly more trust than previous restructures had produced — including from employees whose roles were directly affected.
The pushback didn’t obstruct the communication. It protected the outcome the communication was supposed to produce.
That’s what effective IC pushback is.
Final thought
IC professionals are not message execution services.
They are organizational communication advisors — professionals with specific expertise in how communication produces or fails to produce understanding, trust, and alignment. That expertise carries responsibility.
The responsibility to deliver well. And the responsibility to push back when delivery without pushback would damage the outcomes the function exists to protect.
Saying yes to everything isn’t serving the organization.
It’s serving the request.
The IC professional who has the knowledge, the evidence, and the professional courage to say “I have concerns about this, and here’s specifically why” — and who can frame that concern in terms of organizational outcomes rather than personal preference — is the one doing the real job.
Not just executing. Protecting.
FAQs: When IC should push back on leadership
Eight specific situations warrant IC pushback: when communication manages perception rather than creates understanding, when timing serves the sender rather than the audience, when the narrative is inconsistent with previous communication, when the communication is premature, when volume is creating signal fatigue, when the communication doesn’t answer the questions employees are actually asking, when it asks employees to do something they haven’t been equipped to do, and when it contains information that isn’t accurate.
By leading with organizational consequence rather than professional objection. Not “I don’t think we should send this” but “if we send this, here’s what will happen and here’s what it will cost.” Specific, evidence-based concerns about specific outcomes are significantly more persuasive than vague discomfort. And coming with a specific alternative — not just an objection — positions the IC professional as a strategic partner rather than a gatekeeper.
Three sources of pressure converge simultaneously: organizational hierarchy (the requester is almost always more senior), relationship pressure (friction in important working relationships feels immediately costly), and role ambiguity (when IC is positioned as a service function, pushback feels outside the scope of the role). All three push toward compliance — which, in situations where pushback is warranted, produces communication that damages organizational trust in ways that take much longer to repair than the pushback would have taken to resolve.
Pushback is evidence-based professional advice about the likely consequences of a specific communication decision — framed around organizational outcomes and accompanied by an alternative recommendation. Obstruction is resistance without rationale, designed to prevent rather than improve. The IC professional who pushes back on a timing decision because it will produce anxiety before action is possible is doing their job. The IC professional who consistently delays communications for reasons that serve their own preferences is not.
Yes — this is the clearest and least negotiable professional boundary available. When a communication contains information the IC professional has reason to believe is inaccurate, their professional responsibility is to flag it explicitly before it goes out. The framing is straightforward: “I want to flag that this contains information I believe to be inaccurate — specifically X. If we send this and the information turns out to be wrong, the credibility damage will be significant.” That’s professional responsibility, not obstruction.
When a pattern of communication is consistently damaging organizational trust and individual pushback hasn’t produced a satisfactory outcome. Not every disagreement warrants escalation — most can and should be resolved through direct conversation with the stakeholder. But a persistent pattern of communications that are undermining organizational credibility, and that direct pushback hasn’t been able to address, is a pattern the IC professional is professionally obligated to surface at a more senior level.
Directly. The IC professional who only executes what’s requested is a skilled operator. The one who also advises on what should be produced — and is willing to push back when what’s been requested will damage rather than serve the organizational outcomes communication is supposed to produce — is a strategic partner. That distinction is what separates IC functions that are valued as strategic contributors from those that are seen as support functions. The pushback is part of the value.
Ana Magana is a change management and communications strategist based in Calgary, Alberta. She helps IC professionals develop the professional confidence and strategic positioning to do the full job — not just the execution part.
Ready to position your IC function as a strategic partner? Work with Ana →
Related reading: The Real Job of a Communications Leader → The IC Pyramid: What to Send, When, and How → Change Communications: Why Clarity Matters More Than Volume →