Prework can improve a strategy workshop or quietly ruin it. Ask department heads to prepare their strategies too early and they will arrive ready to defend positions. Ask them to bring nothing and the workshop may spend half a day reconstructing information that could have been prepared in advance. The better purpose of prework is to improve what participants can see before they begin advocating what the organization should do.
What useful prework sounds like
Imagine Sales submits a slide saying, “We should expand into the mid-market.” Finance sends another saying margins in that segment are deteriorating. Operations reports that smaller accounts generate more service exceptions than expected. Three departments have already moved from evidence to conclusions, and the workshop has not started.
The facilitator can send the material back with a different instruction: give us the signal, its source, what assumption it may challenge, and one question leadership should be willing to answer. Sales may then bring a pattern of inquiries from a new buyer group. Finance may bring contribution-margin data. Operations may bring exception rates. The recommendations can remain in the background until the leadership team has looked at the same field of evidence.
This does not make participants neutral. People will still have preferences. The design simply makes it harder for a polished departmental answer to masquerade as the problem itself.
Collect signals, not sales pitches
A strategy signal is selected evidence that may change how leaders understand the situation. It can come from customers, performance data, operating failures, competitor moves, regulation, technology, talent, economics, resource constraints, or repeated decisions that no longer make sense.
The prework question is not “What is your strategy?” It is “What are you seeing that the leadership team should understand before it chooses?” That difference reduces the pressure to arrive with polished answers.
Use a Signal Pack
Ask each participant to bring a small number of signals under four headings: What changed? What pattern are you seeing? What assumption may no longer be safe? What question should leadership be willing to answer?
Keep the pack deliberately short. If people submit fifty slides, the workshop becomes a reporting session. Require enough evidence to make the signal credible, but not enough decoration to turn it into a departmental campaign.
A useful prework discipline is to ask people to distinguish what they observed from what they think it means. “Three major customers requested shorter lead times” is different from “We need more automation.” The first is a signal. The second is already a proposed response.
This separation does not forbid recommendations. It delays advocacy long enough for the leadership team to compare signals and build a shared diagnosis.
Handle sensitive signals carefully
Some of the most important information may involve failed initiatives, customer complaints, leadership tension, or an operating practice people are reluctant to name publicly. Pre-workshop interviews can help surface these issues and decide how they should enter the session without exposing individuals unnecessarily.
The facilitator’s job is to protect candor without turning private comments into surprise ammunition. If an issue matters strategically, design a fair way for the group to examine the pattern rather than reveal who complained about whom.
Give participants a small evidence burden and a clear reason for it. Ask for two or three signals they believe the leadership team should understand, the source of each signal, what assumption it may challenge, and one question it raises. This is enough to prepare thinking without encouraging a fifty-slide defense.
Where possible, ask participants to submit signals early enough for the facilitator to look for contradictions. If Sales sees demand expanding while Finance sees margin collapsing, that tension may deserve a deliberate place in the workshop rather than emerging by accident.
Do not reject them. Separate the recommendation from the evidence beneath it. Ask, “What are you seeing that makes this recommendation seem necessary?” Then bring the evidence into the shared field and hold the proposed action lightly until the diagnosis is clearer.
This is an important facilitation posture. People are allowed to have preferences; the process simply prevents those preferences from becoming facts before the group has examined the situation.
Prework is also where the facilitator begins seeing the shape of the discussion. Look for repeated signals, contradictory interpretations, missing evidence, and issues that several people mention privately but nobody has named collectively. These patterns help determine what deserves workshop time and what can be clarified before the session.
Do not turn this into a secret diagnosis made by the facilitator. The purpose is to design better questions and a fairer evidence field, not to enter the workshop with a hidden answer.
A two-hour strategy decision may need a concise data pack and a few customer signals. A major where-to-play decision may require deeper market and economic evidence. Match preparation to the size and reversibility of the choice.
Too little preparation forces participants to guess. Too much preparation can overwhelm the workshop and create false confidence simply because the deck is thick. Select evidence because it could change the decision.
What good prework changes
Good prework changes the first hour of the workshop. Participants begin with evidence and questions rather than long presentations. The same signal can be examined by several functions, and assumptions become visible before positions harden.
The next step is to turn those signals into a working diagnosis. Use the Strategic Mirror to help the leadership team see the pattern together.
Replace “prepare your strategy” with a short Signal Pack built around evidence, assumptions, tensions, and questions. Then use the Strategic Mirror to build a shared diagnosis before the leadership team starts advocating solutions.