How to Run a Strategic Planning Workshop

A strategic planning workshop is a facilitated session — usually a single day — where a leadership team turns a direction everyone vaguely agrees on into a written plan with named owners, measurable targets and a date attached to each one.

That definition is doing a lot of work, so here is the blunt version. Most planning workshops fail before anyone enters the room, because the team arrives without the inputs the session needs and spends the first four hours inventing them badly. This guide is mostly about avoiding that.

What a planning workshop is actually for

A good session produces four artefacts. If you leave without them, you had a discussion, not a planning workshop:

1. One agreed measure of success for the year — the number everything else serves.
2. Three to five priorities that plausibly move it. Not twelve.
3. A named owner for each priority. One human, not a committee or a department.
4. A first set of measures at company and team level, with the individual level at least sketched.

Everything in the agenda below exists to produce one of those four things. If an activity doesn't, cut it — that is the test that keeps a day from turning into a two-day offsite.

Before the workshop: the part teams skip

Here is the pattern we see most often. A team books an offsite, arrives enthusiastic, and discovers around 11am that they don't agree on what the company is actually for. The rest of the day becomes an unplanned mission-statement exercise, and the plan gets written in the last forty minutes by whoever is still concentrating.

You can avoid that entirely. Four inputs need to exist in writing before the day, and the facilitator's real job is making sure they do:

Circulate all four at least five days ahead and ask people to read them before they arrive. Not the morning of. If someone hasn't read the pack, they will re-litigate its contents in the room and cost you an hour.

The readiness test. If you cannot answer "what is the one number we are trying to move this year, and can ten people in the company name it?" — you are not ready to plan. You are ready to have the conversation that precedes planning, which is a different session with a different agenda.

Who should be in the room

Between six and twelve people. Below six you lack the perspectives; above twelve you no longer have a working session, you have an audience, and the quiet people stop talking.

Include everyone who owns a function and will own a priority. Exclude anyone attending for visibility rather than contribution — their presence changes what people are willing to say.

Someone must facilitate, and it should not be the CEO. A CEO who facilitates cannot advocate, and a CEO who advocates cannot facilitate — attempting both means the loudest disagreement in the room goes unresolved because the person holding the pen has a stake in it. Use a Chief of Staff, an ops lead, or an outsider.

The one-day agenda

Timings assume a 9:00 start and a genuinely protected day. Phones out of the room.

9:00 — Where we actually are (45 min)

Finance walks the numbers. The COO walks last year's commitments against what shipped. No discussion of next year yet — the only goal is a shared, unflinching picture of the present.

Facilitator's job: stop this becoming a defence. When someone starts justifying a miss, note it for later and move on. You are establishing facts, not assigning blame.

9:45 — What did we learn (45 min)

Small groups of three. Each group answers two questions on paper: what worked that we should do more of, and what did we keep doing that we should stop. Report back in three minutes per group.

The stop list matters more than the start list, and it is the one every team under-invests in. Capacity for new priorities comes from somewhere.

10:30 — Break (15 min)

Real break. Do not run through it.

10:45 — The one number (60 min)

The most important hour of the day. The team agrees the single measure that defines a successful year.

Run it as: individual silent writing (5 min) → each person reads theirs aloud with no debate (10 min) → cluster the suggestions on a wall (15 min) → discuss and converge (30 min).

The silent-writing-first structure is not ceremony. Without it, the first person to speak anchors everyone else, and you get a number that reflects seniority rather than judgement.

Expect genuine conflict here. That is the point — this disagreement exists inside your company whether or not you surface it, and the only choice is whether it gets resolved in a room with everyone present or quietly in a dozen separate decisions over the next year.

11:45 — Candidate priorities (45 min)

With the number agreed, ask: what would have to be true for this to move?

Generate freely — every candidate goes on the wall. No filtering yet. Do not let anyone volunteer an owner at this stage; ownership offered too early stops the group evaluating the idea on merit.

12:30 — Lunch (45 min)

13:15 — Cut to three to five (60 min)

The hardest hour. Score every candidate on two axes only: impact on the number and effort to deliver. Two axes, not five — a scoring rubric with more dimensions produces a spreadsheet argument, not a decision.

Then cut. Out loud, explicitly, and with the cut list written down and kept. A priority list that nobody argued about is not a priority list — it is a wish list, because nothing was traded away to make room.

Sanity check before you move on: could the team deliver all of these and keep the lights on? If the honest answer is no, cut another one now, not in March.

14:15 — Owners and measures (75 min)

For each surviving priority, agree in the room:

• One owner. A person. If two people own it, nobody owns it.
• A measure that will be unambiguously true or false at year end.
• A first checkpoint — a date in the next 90 days by which something visible exists.

Then cascade one level: for each priority, what does each team need to be measuring for this to be on track? You will not finish the cascade today, and you shouldn't try. Getting company level agreed and team level sketched is a good day's work; individual measures and job descriptions follow in the two weeks after.

15:30 — Break (15 min)

15:45 — Pre-mortem (45 min)

Ask the room to imagine it is twelve months from now and the plan failed. Then: why?

This one exercise is worth the whole afternoon. It surfaces objections that politeness suppressed all day, because it is socially much easier to describe a hypothetical failure than to object to a colleague's plan in front of the CEO. Capture every cause named. The top two or three become risks with owners.

16:30 — Commitments and close (30 min)

Read the plan back aloud: the number, the priorities, the owners, the checkpoints. Out loud, in front of everyone — ambiguity survives a document and dies in a room.

Agree three things before anyone leaves: who writes it up (and by when — 48 hours, while it is fresh), how it gets communicated to the wider company, and when you review it (quarterly, dates in calendars now).

The week after, where plans usually die

The workshop is the easy part. What kills plans is the fortnight afterwards, when the energy fades and nothing structural changes.

Three things need to happen within two weeks:

1. The plan is written and circulated. One page. If it needs more than one page to communicate, it isn't decided yet.
2. The cascade completes. Company measures exist; team measures exist; individual measures and job descriptions reflect them. This is the step almost everyone skips, and it is precisely the step that determines whether the plan reaches anyone's Tuesday.
3. The first checkpoint is in calendars. Not "in Q1" — a date.

A plan that ends at company level is a poster. A plan that reaches individual measures is an operating system.

How long should it take?

One day, if your inputs are ready. Two days if you also need to agree direction from scratch — but be honest that day one is then a direction workshop, not a planning one.

Half-day sessions do not work for annual planning. You can agree the number or the priorities in half a day. You cannot do both, and doing one without the other produces a plan with no arithmetic behind it.

Common ways it goes wrong

• The CEO facilitates. Covered above; the most common and most costly error.
• Too many people. Above twelve, quiet people stop contributing and you lose exactly the perspectives you invited them for.
• No stop list. New priorities land on a team already at capacity, and the plan fails quietly in February.
• Owners assigned to departments. "Marketing owns this" means nobody owns it.
• Measures nobody can compute. If it needs a bespoke analysis to check, it will not be checked.
• No cascade. The plan stays a leadership artefact and never becomes work.

What to do next

If your inputs are ready, use the agenda template and exercises to run the session yourself. If you are running the shorter annual planning meeting rather than a full offsite, the annual planning meeting agenda is a tighter structure built for two to three hours.

And if the readiness test above went badly — no agreed number, no KPI structure, job descriptions that don't match what people actually do — that gap is the thing to fix first. It is also the thing we built our free workshop around.