Strategy Cascade Kit: Town Halls That Reach the Front Line

The question on the loading dock

Picture a company-wide town hall. Two thousand people on a livestream. The CEO walks through 32 slides on the new strategy: fewer product lines, a push into service contracts, two distribution centers consolidated into one. Q&A runs eight minutes. The applause is polite.

At 6 a.m. the next day, a night-shift supervisor at one of the two distribution centers is asked by her team: “Does this mean us?” She does not know. She saw the slides at the same moment they did, on the same livestream. She says she will find out. By lunch the rumor is that the site closes in March. Nobody has decided that.

A strategy cascade is the sequence of conversations that carries a strategy from the top team to every team, each level translating it into what changes for the people in front of them. The town hall is one step in it, and not the most important. The step that decides whether the strategy lands is the team meeting run by a supervisor who was briefed first and can answer the question her team will actually ask.

This page is the kit for running that sequence: who is briefed in what order, a run sheet for the town hall, a talk track and session script for managers, and a log that brings the questions back up. The communicating strategy page makes the case for cascading through managers. This page is the equipment.

Nobody on the front line asks what the strategy is. They ask what changes on Tuesday.

Why the stage is the wrong place to cascade

The evidence points away from the big event. In Donald Sull, Charles Sull and James Yoder's research, across 69 survey items the single best predictor of strategic alignment was how consistently managers, from top executives to frontline supervisors, explained their team's priorities in terms of their unit and the company as a whole ¹. They also found that agreement on priorities fell from 51% within top teams to 22% among the senior executives who report to them ¹. Their advice is blunt: “Rather than hosting another town hall, top executives should focus first on their direct reports” ¹.

T.J. and Sandar Larkin made the same complaint about change communication in 1996. The usual advice to executives, they wrote, boils down to more: “more values, missions, and vision; more videos, publications, and meetings; more executive road shows.” Their verdict: “This communication is not working” ².

The mechanism is not that town halls are useless. It is that they cannot do the translation. A CEO cannot say what the strategy means for the night shift at one site, and the curse of knowledge makes it worse: executives who know the detail behind each abstraction tend to speak in sweeping, general language that people without that detail cannot act on ⁴. The supervisor can do the translation, but only if she hears the strategy before her team does, with enough of the reasoning to answer questions. The Army's 2019 mission command doctrine (ADP 6-0), written by an institution that has thought hard about passing intent down a hierarchy, asks commanders to deliver intent in person where possible, because face-to-face delivery “ensures shared understanding of what the commander wants by allowing immediate clarification of specific points,” and it sets the bar that soldiers “two echelons down” should be able to remember and understand it ³.

The kit: five pieces and a calendar

1. Week 0: Check the top team agreesAsk each top-team member to write down the priorities independently. If the lists differ, stop. Sull and colleagues found that two-thirds of top executives were on the same page in just 27% of the companies they studied ⁵. Cascading a disagreement multiplies it.
2. Week 1: Brief the level below the top teamEach executive, in person, with their own direct reports. The reasoning, not just the conclusion.
3. Week 2: Equip and rehearse managersSend the manager pack. Hold one 45-minute session where managers draft their talk track and try the hardest questions on each other.
4. Week 2: The town hallSame week, after the managers have been briefed. Never before.
5. Weeks 2 to 4: Team sessionsEvery manager runs the 30-minute session and logs the questions.
6. Week 5: Close the loopPublish one written note answering every logged question, including “not decided yet, answer by this date.”
7. Week 8: Test itAsk a sample of people at each level to list the priorities and say what changed for their team.

The town-hall run sheet

Forty-five minutes, and more than half of it for questions. The event's job is to show the leadership team agrees, explain the choice and the reasons, and tell everyone that their own manager will explain what it means for them, and when.

One rule for the leader: say what is not decided. “We have not decided which distribution center we will keep; we will decide by June, and you will hear it from your manager first” is a better answer than silence, and far better than a reassurance that later proves wrong.

The manager pack and the 30-minute team session

The manager pack is the most important piece of the kit. Its core is a talk track: a short set of points the manager writes in their own words, built on the template below. The tool on this page assembles one.

1. Minutes 0-5: What changed and the choiceFrom the talk track, in the manager's words. No company slides beyond the one-page strategy.
2. Minutes 5-15: What changes for us, and what does notThe heart of the session. Be concrete about this team's work.
3. Minutes 15-18: What is not decidedSay it plainly, with dates.
4. Minutes 18-28: QuestionsAnswer what you can. Log what you cannot, with a promise of when an answer comes back.
5. Minutes 28-30: The askOne or two things the team does differently from now. Write them down where the team will see them.

A filled-in talk track

Look at what the supervisor did not say. She did not promise the site stays. She did not repeat the strategy's slogan. She told her team the one thing that is certain (the pick list changes in April), the one thing that is not (the site), and the date when it will be. That is what the opening scene was missing.

Hard questions, honest answers

The pattern in every better answer is the same. Separate what is decided from what is not, and attach a date to the second. People can live with uncertainty that has an end date. They fill uncertainty without one with rumor, and the rumor is almost always worse.

When the cascade carries the wrong thing

The strongest objection to a kit like this is that it turns managers into mouthpieces. Hand a supervisor a talk track and an FAQ, and the team hears the company's script in a familiar voice. Front-line staff notice. A cascade that runs only downward also wastes what the front line knows: which slow-moving lines customers would miss, which promised service window the vans cannot make.

Both points are right, and the kit is built around them. The talk track is a template the manager fills in, not a script to read. The test in week 8 asks what changed for the team, which a memorized slogan cannot answer. And the question log is not a courtesy. It is the upward half of the cascade, the part hoshin kanri calls catchball. Read the logs as data. Fifty supervisors asking the same question means the strategy page has a hole. Ten saying a priority cannot be done with the current staffing means the plan does.

There is a harder case: the manager who disagrees with the strategy. Do not ask them to fake conviction; their team will see through it. Ask them to explain the choice and the reasons accurately, say that they raised concerns, and say how those were handled. A manager who says “I argued for keeping both sites, I lost, and here is why the decision went the other way” is more believable than one reading an FAQ. Then make sure the concern was actually heard. If many managers disagree, that is not a communication problem, and no kit will fix it.

Finally, test it. The strategic alignment check runs a version of the listing test Sull and colleagues used: ask people to list the priorities and score whether they can ¹. Add one question of your own: what changed for your team? If people can list the priorities but not answer that, the town hall worked and the cascade did not.

Before the town hall

• Each top-team member has written the same priorities, independently.
• Every direct report of the top team has been briefed in person, with the reasoning.
• Every people manager has the pack two days before the town hall and has drafted a talk track.
• The “not decided yet” list exists, with a date for each item.
• The town hall gives more than half its time to questions and ends with the date of the team sessions.
• The question log has an owner and a date for the written answer note.
• A week-8 test is in the calendar.

The supervisor on the loading dock did not need a better livestream. She needed to hear it a week earlier, with the reasons, the list of what was not decided and a date she could give her team. A strategy reaches the front line one conversation at a time, in the words of the person who runs the shift. Equip that person, and the town hall becomes what it should be: the trailer, not the film.

Questions

What is a strategy cascade?

A strategy cascade is the sequence of conversations that carries a strategy from the top team to every team, with each level translating it into what changes for the people it leads. It usually runs leader briefings first, then manager preparation, a town hall, team sessions and a written answer to the questions that come back up.

Should a strategy be announced at a town hall?

A town hall can show that the leadership team agrees and explain the choice, but it cannot say what the strategy means for each team. Brief managers before it, give more than half the time to questions, and end by saying when each team's own manager will meet them. The team session is where the cascade actually happens.

What should a manager say to their team about a new strategy?

What changed, the company's choice in their own words, what is being stopped, what changes for this team and what does not, what is not decided yet and when it will be, and one or two specific asks. Then take questions and log the ones that cannot be answered yet, with a date for the answer.

How do you know if a strategy cascade worked?

Test it about eight weeks later. Ask a sample of people at each level to list the company's priorities and to say what changed for their own team. If they can list the priorities but cannot say what changed, the announcement worked and the cascade did not.

Where to go next

• Communicating Strategy So People Can Act on It
• Strategy on a Page: A Template That Carries the Why
• Cascading Objectives
• Change Communication Strategy