Your leadership team decided. Now the people who weren't in the room have to hear it.

Marco van Hout · 4 min read

Most cascades are designed as a broadcast: a deck travels down the org chart and gets thinner at every layer. Treat it as two designed sessions instead - managers first, teams second - each with a required output. Includes a runnable 75-minute manager session.

The offsite worked. The leadership team argued, converged, and left with a decision. Then someone says "comms will draft a deck for the managers" and the whole thing starts to die.

Cascades rarely fail because the message is wrong. They fail because the cascade is designed as a broadcast: a deck travels down the org chart and each layer forwards it a little thinner. A practitioner writing on cascading communication calls it a game of telephone: fidelity degrades at every relay, and by the third layer people are hearing a summary of a summary. The numbers back the felt experience. In an internal-comms industry survey, 56% of communicators named manager communication their top focus for 2026, yet only 4% believed managers are actually very effective at cascading messages. The same survey found employees trust their manager more than any other source. So the most trusted channel is also the one everyone admits is broken.

Here is the design flaw. The leadership team spent a full day metabolising the decision. They heard the objections, watched options die, and know why the losing option lost. The manager gets forty slides and a request to "share this with your team by Friday." She had zero minutes of that metabolising time. She cannot answer the first hard question, and her team can tell. Vendor research from an employee-comms platform (6,200+ employees surveyed across North America and the UK) found that 61-76% of employees miss critical updates despite regular communication, and that 70-77% of managers say they struggle to relay messages effectively. That is not a messaging problem. It is a session-design problem, and if your organisation is mid-AI-rollout, that manager layer is already saturated before your decision arrives.

Treat the cascade as two sessions, not one announcement

Design it the way you would design any workshop: two sessions, each with a required output.

Session one is for managers only, and it comes first, always. Its purpose is not to inform them. It is to let them metabolise the decision the way the leadership team did, compressed into 75 minutes. Its output: every manager leaves with a written, in-their-own-words answer to the three questions their team will ask. Usually those are some version of "why this, why now," "what changes for us specifically," and "what happens to the thing we were doing instead."

Session two is each manager running a working session with their own team. Its output: the team's list of what this decision means for their work, written by them, plus their unanswered questions routed back up. If a team session produces no questions, it was a broadcast wearing a session's clothes.

The manager session: 75 minutes, runnable as-is

  • 10:00-10:10 - A leadership team member states the decision and the two options that were rejected, and why. Ten minutes of presenting, no more. Output: the decision in one sentence on the wall.
  • 10:10-10:25 - Silent reading of a one-page decision brief (not the deck). Each manager writes their honest first reaction and their sharpest doubt on a card. Output: the doubts, visible.
  • 10:25-10:45 - Pressure round. Managers ask the leadership rep the questions they expect from their teams. Rule: the rep answers "we don't know yet" out loud where true; those go on a parking list with an owner and a date. Output: the parking list.
  • 10:45-11:05 - Pairs. Each manager drafts written answers to the three team questions, in their own words, for their specific team. Partners challenge anything that sounds like the deck. Output: three written answers per manager.
  • 11:05-11:15 - Rehearsal. Each manager states the decision in their own words to the room in under 60 seconds. If it comes out as slide-speak, they go again. Output: a version that survives contact.

Measure what landed, not what was sent

The Firstup research's core advice applies directly: replace send metrics with receipt metrics. "The deck went to all managers" measures nothing. Instead: every team session held within 10 working days of the manager session. Every parking-list question answered within that same window. And two weeks after the cascade, ask a sample of people at each layer to state the decision in their own words. If the answers at layer three still resemble the sentence on the wall, the cascade held.

If you are designing the manager session this week, build the timed agenda in Metodic Session Studio and adapt the block above to your own decision.

Sources

Design your own session

METODIC turns ideas like these into a complete session agenda with activities, timing, and materials — for workshops, meetings, offsites, and team sessions.

Try METODIC free