.avif)
.avif)
Ask five people on a team what the company's top priority is this quarter, and you'll usually get three different answers and possibly some blank stares. This happens a few months after a perfectly good offsite where leadership actually agreed on the plan. Somewhere between that room and the rest of the org, the plan got lost. Not because it was wrong. Because nobody managed the handoff.
I've built cascades that looked sharp on the slide and were forgotten by week six. I've also walked into teams still working from a plan someone above them wrote three offsites ago, chasing priorities nobody upstream cares about anymore. Both are the same failure from opposite ends. And figuring out which side of it you're on, and fixing it, is one of the clearest ways to tell a Chief of Staff who's operating strategically from one who's still just executing someone else's plan.
Writing a good strategy is one skill. Getting it to survive contact with the rest of the company is a completely different one, and it's the one nobody trains you on.
Four things usually break it.
First, the plan gets diluted instead of carried. It goes from the offsite to a recap doc to a slide to a manager's verbal summary in the team all-hands, and by the third or fourth handoff nobody can trace their own goals back to the actual reasoning behind them. Once that thread snaps, people stop aligning to the strategy and start aligning to whatever their manager happened to emphasize that week. The fix isn't a cleaner slide or more slides for that matter. It's giving every layer direct access to the real reasoning, not a summary of it, and leaving room for people to push back on it before they're asked to execute against it.
Second, ownership gets bolted on after the plan is already built. Most teams write the priorities first and figure out who's accountable for what afterward. That's backwards. Skip the people who'll actually own the outcome and you'll find out in month three, when the numbers stall, that they never agreed those were the right goals in the first place. Bring second-line owners into the room while the plan is still being shaped, even informally, and the cascade lands on people who already have a stake in it.
Third, and this is the one almost nobody staffs: no one owns keeping the plan current. A strategy isn't something you publish once. It needs someone checking, every month or so, whether the priorities still hold, whether something upstream has quietly changed what teams below should be doing, whether two groups are now working against each other because nobody reconciled their plans. Where the cascade actually survives a full year, that job has a name attached to it, and it's usually the Chief of Staff's.
Fourth, the plan loses the fight for attention. A strategy mentioned once at the offsite and never again is, functionally, not a strategy. It's a slide. The ones that stick get repeated constantly, in 1:1s, in review meetings, in the shorthand people use to make tradeoff calls. That repetition doesn't happen on its own. Someone has to keep pushing it back into the room, usually the CoS, because the exec team is busy putting out whatever fire is loudest that day.
If you're the one building the next cascade, the fix for all four is roughly the same move: treat it as a conversation you're running for months, not a document you hand off once. Get the right people in early. Share the reasoning, not just the conclusion. Assign the ongoing upkeep to a real person on day one. And say it again next month, because a plan stated once is a plan that's dead by the next quarter.
This work is slower than shipping the deck and moving on. This is why most people skip it, and exactly why the ones who don't are the ones who end up running the next planning cycle instead of just attending it.
