We assume important information cascades down the organisation. It doesn't happen by itself.
Two days of leadership work, real decisions, genuine alignment — and three weeks later most employees have heard nothing new. The message didn't fail in the room. It failed in the twenty metres between the leader's inbox and their team meeting.
What separates the leaders who do this well?
The strong ones: translate the message, make it relevant to their team, pass it on quickly, and follow up that people understood what it means for them.
The weaker ones: assume people have picked it up, don't see that they have a role in reinforcing it, and waver when the critical questions come — because they don't own the message well enough to defend it.
That last one is the real tell. A leader who can't handle the first hard question in their team meeting doesn't have a communication problem. They have an ownership problem, and it was created in the room you designed.
Why does this keep happening?
Because cascading is treated as distribution, and it's actually translation.
The session ends, the deck goes out, and everyone assumes the deck carries the meaning. It doesn't. What a decision means for a fifteen-person team in one country is not what it means in general, and the general version is the only one that ever gets sent.
Good cascading creates direction and reduces resistance. Weak cascading creates noise and misunderstanding — which is worse than silence, because now you have to correct it.
Design it into the session
Don't leave it to the last twenty minutes. Three things:
Give each leader a slot to write their own version. Thirty minutes, in the room, before anyone leaves. Not the corporate summary — their words, for their team, naming the two things that actually change for those specific people.
Have them say it out loud to a peer. Five minutes each. The peer plays the sceptic and asks the hardest question their team would ask. Wavering in front of one colleague is cheap; wavering in front of thirty people is not.
Fix the date before you leave the room. Not "in the coming weeks." A named arena, a date in the calendar, and preferably within a week — while the leader still remembers why it made sense.
Four things that make cascading land
- Pick a fixed arena, and do it verbally. Spoken beats written, because it builds trust and lets people ask.
- Deliver the core message at a point that helps the team, not when it suits the reporting cycle.
- Say concretely what your team should do — or think — about it. Information without an implication gets filed.
- Check that it was actually understood. Ask someone to say it back. It takes a minute and it's the only real verification available.
The uncomfortable part
One of a leader's most important jobs is not to discuss messages, or to receive them.
It's to carry them.
If your leadership gathering doesn't rehearse that, it produced alignment in twelve people and nothing else.