Three weeks after one of the best leadership presentations I’ve ever sat through, I was running listening sessions with frontline teams in four regions of the same company.

I kept waiting to recognize the message.

I never did.

The senior leadership of this global logistics company had done genuinely impressive work developing their change narrative. Clear rationale. Honest acknowledgment of difficulty. A compelling picture of what success looked like on the other side. When I watched the executive team deliver it, I remember thinking: this is going to land well.

What landed, three layers down and three weeks later, was something closer to: “there’s a restructuring, leadership isn’t telling us everything, and nobody knows what it means for us personally.” Fear. Rumor. A quiet but widespread sense of being managed rather than trusted.

The leaders hadn’t lied. The cascade had.

Here’s the thing about cascading communication that nobody wants to say plainly: it works beautifully for simple operational information and almost never for anything that actually matters. The moment your message carries nuance, context, trade-offs, or emotion, it will be transformed by every layer it passes through. Not because people are careless. Because human beings interpret information through their own context, filter it through their own concerns, and pass on the version that made sense to them. By the time it reaches the frontline, you’re not communicating anymore. You’re playing telephone with your strategy.

The senior team who built the message spent two days in a room together. They heard the debates. They understood the reasoning behind the decisions. They felt the weight of the trade-offs. That shared experience is what gave them genuine alignment.

Their direct reports got an hour. Their managers got thirty minutes and a slide deck. The frontline got a team briefing from someone who was themselves still processing the news.

You cannot transfer two days of context in thirty minutes. You can only transfer conclusions. And conclusions without context sound like directives. Directives without context generate resistance.

The organizations I’ve seen navigate this well have mostly given up on cascade as a primary vehicle for important communication. Instead they build in direct contact. The CEO doing small-group sessions across multiple locations over two weeks. Senior leaders hosting open Q&A where the real questions get asked, including the ones that are uncomfortable. Short, direct video messages that every employee sees in the same form, rather than a document that every manager translates differently.

It takes more time. It is also the only thing that actually works.

And there’s one more step that almost everyone skips: checking what was received, not just what was sent. Not “did everyone get the communication?” but genuinely testing comprehension. What did people hear? What are they worried about? What do they still not understand? That feedback loop is where you find out whether your message survived the journey, or whether you need to start again.

Communication is not a broadcast. It is a conversation that happens across time, through multiple filters, in contexts you cannot fully control.

Design it that way, or keep wondering why the organization never seems to get it.