Announcing Change: The Cascade Method (and Why All-Hands Is Last)
Most companies announce change at all-hands first and brief managers afterwards. The result is managers caught flat-footed by their own teams.
On this page▾
- Cascade order: execs → senior managers → managers → ICs → all-hands.
- Each layer briefed before the next, with Q&A documented and shared up.
- All-hands is the last step, not the first.
- Cascade takes 3–7 days for most changes; do not compress to one day.
Imagine you are a manager. Your CEO announces a significant change at all-hands. You hear it for the first time alongside your team. Your direct report turns to you in the Q&A and asks what it means for them. You have nothing. Trust just took a hit — not in the CEO, in you. Multiply by every manager in the company. That is the cost of the default communication pattern, and it is avoidable.
The default that fails
Most companies default to all-hands-first because it is the fastest path from decision to announcement. It also flattens hierarchy, which feels good. The hidden cost is that it strips every manager of the ability to answer the questions their team will inevitably ask. The team's experience of the change is shaped not by the CEO's words but by the manager's inability to follow them up.
The cascade method
- 1Layer 1: senior executives1:1 brief from CEO. They become co-owners of the message before it leaves the room.
- 2Layer 2: senior managers (directors / heads)Briefed by their execs in small groups. Encouraged to surface objections privately.
- 3Layer 3: line managersBriefed by senior managers. Given the script, the FAQ, and 24 hours to absorb before talking to their teams.
- 4Layer 4: individual contributorsManager 1:1s, then team meetings. The change lands at the team level with a person they trust.
- 5Layer 5: all-handsPublic confirmation. Not new information. CEO takes hard questions live.
What you trade for what
- Fast (one event)
- Risk of leaks while drafting
- Managers caught flat-footed
- Team's first impression: anxiety
- Slower
- Same leak risk, distributed
- Managers are partners in the message
- Team's first impression: clarity from a trusted source
When all-hands first is correct
- Genuinely urgent operational news (a security breach, a regulatory enforcement) where speed beats sequence.
- News already public (a fundraise announced externally, a layoff that leaked).
- Very small companies (under ~30 people) where the cascade is one layer deep anyway.
If managers are sending their teams 'I just heard the same news you did' Slack messages after an all-hands, the cascade was skipped. That message should never be necessary.
Read next
All playbooksJohn Kotter found that most change efforts fail because steps are skipped. Here's the sequence, where most leaders break it, and the diagnostic to find which…
William Bridges drew the distinction every leader should know: change is external; transition is the internal psychological work.
A reduction in force is the most consequential communication any leadership team will run. Every word is remembered.