Every CEO, CHRO, chief of staff, strategy director and head of internal communications I meet in the weeks after a strategy cascade, a manager summit or a run of divisional town halls asks a version of the same question, usually not out loud: did it land? The briefings ran, the town halls happened, and the survey said most people understood the strategy. Yet six or eight weeks on, the same senior leader will quietly admit they are not sure anything has actually changed. That gap, between a good comprehension score and a real shift in what people prioritise, is a measurement problem, not a communication one. I am usually brought in by someone who has already run the cascade, wanting to know whether it worked before the next board update, not after. What follows is the test I use. It takes about four minutes.
Alignment Is Not Agreement, and It Is Not Comprehension
Alignment gets confused with two things it is not. It is not agreement: a manager can privately dislike a priority and still align their team’s work to it well. It is not comprehension either: a manager can describe a strategy accurately, in the right order, and change nothing their team does on a Monday. Alignment is subtraction. It exists when a team can name what it is no longer doing because of this strategy, and what one team has stopped does not contradict what the team next to it has stopped. That is a harder bar, and the only one that tells you whether the strategy changed behaviour rather than vocabulary.
It matters most at the middle management layer, because that is where the strategy stops being a story and becomes a trade-off inside a real team’s real week. Senior leaders decided what the organisation will not do; middle managers have to decide what that means their own team will not do. Until that translation happens, the strategy has arrived as words and stalled before becoming a decision.
Why the Understanding Survey Tells You Nothing
The standard instrument here is a survey question along the lines of “I understand our strategic priorities,” and it almost always comes back strong, for reasons that have nothing to do with whether the strategy has taken hold. Saying you do not understand your strategy is socially expensive, so people round up, and understanding the words is genuinely easy besides. None of that tells you whether a single decision, on a single team, has changed. The pattern repeats often enough to predict: a strong comprehension score, followed by a meeting eight weeks later where nobody in the room can name anything that visibly changed. The survey did not lie. It measured the wrong layer of the problem.
The Four-Minute Stop List Test
Here is the exercise, small enough to run inside a leadership meeting already on the calendar, with no consultant or platform required. Bring your middle management cohort into one room. Give each person a piece of paper and one question: what is the one thing your team will stop doing this quarter because of the new strategy? Not slow down, not deprioritise gently. Stop. Give them ninety seconds, no discussion, no comparing notes, and collect the answers.
In a group of twelve managers, this is roughly what comes back, consistently enough to plan for. Two or three write nothing, or something too vague to count. Three or four describe something already stopped for reasons that predate the strategy, a project that was winding down anyway, a report nobody read. And somewhere in the pile, two answers directly contradict each other: one manager stopping the very activity another has just started, both convinced they are executing the same priority correctly. That is the alignment picture, gathered in four minutes.
What Contradictory Answers Are Telling You
The blanks are the easier read: a team that has stopped nothing has not received a strategy, it has received a request to keep doing everything it already did, with more energy and new language attached. The contradictions are the expensive ones, precisely because nobody is arguing. Two managers who each believe they are executing the same priority correctly, while doing incompatible things, will not raise a hand and ask for clarification. Open disagreement gets resolved because someone notices it; two confident, incompatible interpretations sit quietly for months.
The generous read, and the one I hold to, is that this rarely happens because a manager was careless. It happens because the reasoning behind the priority never reached them, only the language did, and language without reasoning can be read correctly in more than one direction. That is not a discipline failure; it is what happens when a decision arrives as a conclusion instead of as reasoning someone can apply to a situation its authors never anticipated.
Line of Sight Runs Both Ways
Line of sight is usually described in one direction: can a person trace their own week back to the strategy? Necessary, but not the whole test. The version I use runs both ways. Downward: can someone explain how this week’s work connects to a stated priority? Upward, and this is the direction leadership teams tend to skip: can a senior leader trace the strategy down to somebody’s actual week and recognise it there? If a leader cannot see their own priority in what a frontline team stopped doing, line of sight has not been achieved either, however well any one person can recite the strategy.
This is also where translating strategy into team-level priorities becomes visible as work rather than an assumption. It is not automatic: it is a judgement call, made under time pressure, by someone who was not in the room where the trade-off was decided, and the stop list is the fastest way to see whether it actually happened.
What to Do With an Amber Result
Say this plainly: amber is the normal result, not a sign the cascade failed. A clean, unanimous, contradiction-free set of answers eight weeks out would be the surprise. What matters is what you do with amber.
For the blanks, do not scold. Build the stop list together with that manager, from the strategy’s own reasoning; a manager who cannot generate one alone usually never received the reasoning in the first place. For the contradictions, put both managers in a room with whoever owns the priority, and resolve it as a genuine trade-off conversation, not a scorekeeping exercise. The output is not a winner, it is one shared answer both can take back to their own teams in their own words. Then close the loop: within 48 hours, each manager should be able to point to something that visibly changed. A diagnosis with no visible follow-up is just a more elaborate survey.
How Often to Re-Run the Test
Not quarterly. Turn this into a KPI and managers will learn to game it exactly as they already game the comprehension survey. Run it once, four to eight weeks after the cascade, while a blank answer is still diagnostic rather than an accepted state of affairs, and again after anything that genuinely shifts what a priority asks of a function: a mid-year adjustment, a divisional leadership change. Otherwise, once or twice a year catches drift before it hardens into habit. Anyone can say they understand a strategy in four seconds; naming the one thing they actually stopped doing because of it takes real thought.
Before You Get to This Point
The stop list is a diagnostic, not a cure. If it comes back amber across most of a cohort, the fix usually sits earlier, in what managers were given before they were sent to lead their teams. I have written separately about what a cascade briefing needs to hand managers beyond the messages on the slide: a briefing built on reasoning is the biggest lever on whether the list comes back clean. This article is the test; that one is the prevention. For the fuller argument on why strategies lose their edges as they travel, see the main piece on getting a strategy cascade to arrive intact. And for the research case behind treating line of sight as a two-way measure, see Boswell, Bingham and Colvin’s work on aligning employees through line of sight, published in Business Horizons and available through the Harvard Business Review store.
If you have a cascade behind you and a comprehension score that does not match what you are seeing in the business, this test costs four minutes and an uncomfortable half hour after. If you are preparing for a cascade that has not happened yet, or want an outside voice to run it honestly with a team that knows each other too well to challenge one another, that is worth arranging before the briefings go out. Get in touch about running it with your leadership group.
I work with executive teams and divisional leadership groups on Execution Intelligence™, the discipline of turning a decision into something an organisation can be seen doing. A good share of the rooms I am in have already run a cascade and want an honest read on whether it hit the mark, before the next board update rather than after it.
