You Just Got a Decision from Your Boss: Here's How to Cascade It Without Creating "We vs. They"

TL;DR: In 8 minutes, you'll learn how to stop being the communication bottleneck between senior leadership and your team, own decisions as "we decided" instead of "they want this," and cascade strategic context that actually reaches your people.

You just left your boss's office. Or closed the Zoom. Or finished reading the email.

You have a decision to cascade to your team.

Maybe it is a new process. Maybe it is a budget cut. Maybe it is a change to how your team does their work.

Your boss explained the reasoning. You understand the business case. You might even agree with it.

Now you have to tell your team.

Here is where most managers make the fatal mistake.

They think their job is to pass the message. Relay the information. Be the messenger.

So they say: "Leadership has decided we need to do X."

Or: "They want us to start doing Y."

Or: "I know this is frustrating, but this came from above."

Every time you say "they," you just created a "we vs. they" culture.

Not because you are a bad manager. Because you are treating cascade communication like a relay race instead of an ownership transfer.

The Real Story: When "They Want This" Breaks Trust

A senior leader at a mid-size company rolled out a new documentation standard for engineering teams. The regulatory team was hammering them with questions because change documents were missing business context. Every gap triggered hours of follow-up.

The senior leader explained this to his managers. Staff meeting. One-on-ones. Full business case. The pattern he was seeing. The time they were wasting. The risk they were creating.

The managers heard it. They understood it. Then they went back to their teams and said some version of: "Leadership wants more detailed documentation."

That is it. Tactic. No strategy.

Three weeks later, an engineer was getting detailed feedback on a change document. Frustrated, they asked their skip-level: "Why are they making you dig this deep?"

The senior leader had to say: "They is me. Here is why."

But here is what surprised him. The engineer was not questioning his authority. They were trying to protect him from what they assumed was a bad decision being forced down from above.

The engineer's logic: "This leader does not normally ask for bureaucratic detail. He trusts us. He protects us from unnecessary process. Someone above him must be pushing this."

The strategic context never reached them.

Not because the senior leader did not communicate it. He did. To the managers.

Not because the managers were incompetent. They were not.

Because somewhere in the cascade, the WHY got stripped out. All that reached the team was the WHAT.

Why Communication Cascades Fail (Even When You Try)

Research on organizational communication reveals a harsh truth: cascades fail not because the concept doesn't work, but because they aren't built correctly Ragan.

Dr. Robert Carroll from the University of Texas explains: "The problem isn't that information moves through hierarchy—the problem is that we don't equip that hierarchy with what it needs to do the work effectively." Ragan

Three structural failures explain most cascade breakdowns:

The Translation Gap

Senior leaders speak in strategy: "We need to reduce operational risk and improve regulatory compliance."

Your team needs to hear operations: "Regulatory questions are eating 10+ hours a week because our docs are missing context. Here is exactly what to add."

You are supposed to translate. But nobody taught you how.

The Telephone Effect

Studies show that like the game of telephone, by the time the message returns to you it has changed significantly Processexcellencenetwork. Each layer of management filters, summarizes, or accidentally distorts.

You had ten other priorities when your boss explained this. You might have written down the decision but missed the nuance of the reasoning. Then you mentioned it once in your team meeting and moved on.

The Distance Problem

When you say "they want this," you are creating distance between yourself and the decision.

Your team hears: "My manager is just the messenger. The real decision-makers are disconnected from our work."

Even if you disagree with the decision, saying "they" makes it worse. Because now your team thinks: "Even our manager thinks this is stupid, but they are being forced to make us do it."

What Good Managers Do Differently (It's Not What You Think)

Here is what might surprise you: There is no such thing as perfect cascade communication.

Even the best managers have to repeat strategic context multiple times. Research shows that messages need to reach people 7 times, 7 ways before they actually stick Myhubintranet.

But good managers do two things that bad managers skip:

1. They Ask Enough Questions to Own the Decision

When your boss gives you a decision to cascade, you have a responsibility: Ask questions until you can deliver it as "we decided."

Not "they decided and I am telling you."

Not "leadership wants this."

"We decided. Here is why."

If you cannot say "we" with full conviction, you have not asked enough questions yet.

Go back to your boss. Get the full context. Understand the business case. Figure out why this matters. Ask:

What problem are we trying to solve?
What happens if we do not do this?
What are the trade-offs?
What did we consider and reject?
How will we measure success?

Keep asking until you understand the decision well enough to defend it as if it were yours.

Because once you cascade it, it is yours.

2. They Deliver It With Full Buy-In (Even If They Disagree)

Notice I did not say "only cascade decisions you agree with."

You will get decisions you disagree with. That is part of management.

But here is the key: Your team does not need to know you disagree. Your team needs strategic context delivered with conviction.

Research on manager communication shows that employees can sense when managers don't believe in decisions they're communicating Emergingrnleader. When you hedge, your team hears uncertainty. When you deflect to "they," your team hears distance.

The right way to cascade a decision you disagree with:

"We had a long discussion about this. There were different perspectives. Ultimately, we decided that [decision] because [business case]. Here is what it means for us and here is how we are going to make it work."

Not: "I do not love this, but leadership wants us to do it anyway."

That second version makes you feel better in the moment. You get to distance yourself from the unpopular decision. But it destroys trust in leadership and makes you look powerless.

The Framework: How to Cascade With Ownership

Here is the step-by-step for cascading a decision effectively:

Step 1: Before You Leave Your Boss's Office

Do not just nod and leave. Ask questions.

"Help me understand the business case I should give my team."
"I expect my team will be concerned about [X, Y, Z]. How should I address those?"
"What am I missing that would help me explain this better?"

Take notes. On the reasoning, not just the decision.

Step 2: Process It Yourself First

You cannot cascade conviction if you are still processing your own reaction.

Take 24 hours. Think through:

Do I understand why we made this call?
What concerns do I have that I need to raise back up?
How will this impact my team specifically?
What support will they need?

If you still have unanswered questions, go back to your boss before you face your team.

Step 3: Deliver It as "We Decided"

Bad version: "Leadership has decided we need to change our documentation process. They want more detail upfront."

Good version: "I want to talk about a change we are making to our documentation process. We have been getting hammered with regulatory follow-up questions—it is eating about 10 hours a week across the team. We looked at the pattern and realized our change docs answer the technical question but miss the regulatory context. So we decided to add more upfront detail in specific areas. Here is what that looks like for us."

Notice the difference:

"We" instead of "they"
Business problem stated clearly
Decision tied directly to the problem
Specific impact for this team

Step 4: Answer Questions With Context, Not Deflection

Your team will have questions. Concerns. Pushback.

Bad responses:

"I do not make the rules, I just enforce them."
"You will have to take that up with leadership."
"I know, but what can we do?"

Good responses:

"Good question. The trade-off we considered was [X]. We went with this because [Y]."
"I do not have a great answer for that. Let me find out and get back to you."
"I hear your concern. Here is what I can control and here is what I cannot."

Step 5: Repeat It 7 Times, 7 Ways

This is the part most managers skip.

You said it once in a team meeting. You think your job is done.

It is not.

Repeat the decision and the reasoning in:

Team meeting announcement
Follow-up email with written summary
One-on-ones with each person
Team Slack or chat
Visual reminder (posted procedure, updated documentation)
Pre-shift huddles or stand-ups
Monthly recap of changes

Different people absorb information differently. Some need to hear it. Some need to read it. Some need to discuss it. Some need to see it in action.

Your job is not to say it once. Your job is to make sure it reaches everyone.

What Happens When You Get This Wrong

When you say "they want this" instead of "we decided," here is what your team hears:

"My manager is powerless." If you are just passing messages from above, you are not a leader. You are a messenger. Your team stops bringing you problems because you cannot solve them.

"Leadership is disconnected." When decisions arrive without context, your team assumes the people making them do not understand the real work. Trust in senior leadership erodes.

"I should ask why." Your team starts questioning every decision. Not because they are difficult, but because they are trying to fill in the missing context you did not give them.

And here is the worst part: When your team does not trust the cascade, they bypass you. They go directly to your boss or your boss's boss to ask "who really wants this and why?"

That is a signal that you failed to cascade with ownership.

The Reality: Even When You Do It Right, You Still Repeat Yourself

Here is the hard truth: Even the best cascade communication requires repetition.

You will explain the decision. Your team will nod. Two days later, someone will ask a question that proves they did not absorb the context.

That is normal.

Do not get frustrated. Do not think "I already said this." Just say it again.

Because consistent, repeated messaging is what makes strategic context stick Myhubintranet.

Your boss explained this once to you in a staff meeting. You thought you got it. But you did not really internalize it until you had to explain it to your team.

Your team is the same way.

They will not really get it until they have to apply it. Or explain it to someone else. Or make a decision based on it.

Your job is to keep reinforcing the context until it becomes part of how they think.

Technical Visibility: Why This Matters More for Engineering Managers

If you manage technical teams, this cascade failure creates a specific problem.

Your work is already invisible to non-technical leaders. When you strip out strategic context from decisions, it makes the invisibility worse.

Your team hears: "Leadership wants better documentation."

What they think: "Leadership does not understand our work. They think we have extra time for bureaucracy."

What you should have said: "We are seeing a pattern where regulatory questions are creating rework. Better upfront documentation prevents that rework and protects us from compliance risk."

The difference between those two messages is massive.

One makes your team think leadership is clueless. The other makes your team understand the business value of their technical work.

Your job as a technical manager is to build the bridge between technical excellence and business impact. That means translating strategy into operations when cascading down, and translating operations into strategy when communicating up.

Monday Morning Action Plan

Before your next cascade:

Ask your boss for the full business case, not just the decision
Write down the reasoning in your own words
Identify the top 3 questions your team will ask
Get answers to those questions before you face your team

When you deliver the decision:

Use "we decided" instead of "they want"
State the business problem before the solution
Tie the decision directly to the problem
Explain what you considered and why you chose this

After you deliver:

Plan to repeat it 7 times, 7 ways over the next two weeks
Schedule one-on-ones to discuss individual concerns
Put it in writing so people can reference it
Check for understanding by asking "what questions do you have?"

If someone asks "who wants this?":

Stop and ask yourself: what strategic context did they not get?
Re-explain the business case, not just the decision
Do not get defensive—their question is valid feedback

The Bottom Line: Cascade Ownership, Not Messages

Your job is not to be a messenger.

Your job is to translate strategy into action, own decisions as "we," and repeat context until it sticks.

When you say "they want this," you create distance.

When you say "we decided this because," you create ownership.

The difference between those two phrases is the difference between a "we" culture and a "we vs. they" culture.

Choose wisely.

Have you ever had to cascade a decision you disagreed with? How did you handle it? Share your experience in the comments.

You're great at the work. Let's make you impossible to ignore.

Want help translating your technical work into business impact? Visit jessestaffordcoaching.com

Related Reading:

Search This Blog