Strategy offsite

When to use it

A leadership team or whole department is setting direction, and the same three arguments have been circling for months without resolution. The usual offsite format (flip charts, breakout groups, a facilitator synthesizing overnight) has a structural problem: the most senior voice frames the question, the most confident voices fill the flip charts, and the synthesis is the facilitator's. This session makes the priorities arrive anonymously and the themes arrive from the group.

Do not use it as the whole offsite. It is one 90-minute block inside a day. It is very good at surfacing and prioritizing, and it is not a substitute for the decision conversation that follows.

The question

Strategy sessions fail on questions that are too abstract to answer from experience.

Seeds:

• What should we stop doing to make room for what matters next year?
• What is the constraint that will still be here in two years if we do not deal with it now?
• What do we believe about our customers that we have not tested recently?
• If we could only fix one thing before the next fiscal year, what should it be and why that one?

The question that fails: "What is our vision for the next five years?" It produces sentences nobody disagrees with and nobody can act on. If the client insists on a vision question, run it after this one, informed by what emerged.

Session settings

• Participants: cap at expected headcount plus five
• Anonymous participation: on
• Raffle: off
• Blind gather: on, this is what stops the senior voice anchoring
• Blind then reveal voting: on
• Shuffle order: on
• Access after finish: on

Run of show

Ends at: Evolve, with the chosen direction handed to the rest of the day; add Resolve as a closing segment only when this block closes the offsite rather than opening it.

Facilitator notes

The seniority problem is the reason to use this, so protect it. Ask the most senior person in the room to contribute in the silent phase and to say nothing until the themes are on the screen. Ask them in advance, privately, not in front of the group. Most will agree readily when the reason is explained, and the session is much better for it.

Expect the room to be smaller than the cap. A leadership team is often 12 to 25 people, which is below the design centre. It still works, but say honestly that vote margins at that size are directional rather than decisive, and lean on the themes and the discussion rather than on the numbers.

The clustering merges strategic opposites constantly. "Expand into the new segment" and "we are already spread too thin" are topically adjacent. Splitting that cluster in front of the room is often the moment the real disagreement finally becomes discussable, because it is now on the screen as two named things rather than a background tension.

Do not let the day end here. The output is a prioritized, group-authored set of themes. The decision still has to be made by whoever makes decisions. Say so, so nobody leaves thinking a vote happened.

What the group leaves with

The themes they named, what resonated most widely, where they disagreed, and the direction they chose for the next block. If the session closes with Resolve, they also leave with recorded endorsements and reservations on the priorities, which is more useful than false unanimity.

The failure mode

The group ratifies the leader's framing because the leader wrote the question. This is the quiet failure, and it looks like success: smooth session, high agreement, nothing new.

Prevent it in the question. If the client hands you a spark that contains the answer ("How do we accelerate our move into enterprise?"), rewrite it with them before the day ("What should determine where we focus next year?"). If you notice mid-session that every theme is a restatement of the brief, say so during Emerge and ask the room directly what is missing from the picture. That question, asked out loud, usually produces the thing everyone was avoiding.