How to run a strategy day that actually produces something

The strategy away-day has a bad reputation, and mostly for good reason. A room full of people, a facilitator with a lot of coloured markers, and by four o'clock a wall covered in ideas that nobody is quite sure how to act on. The problem isn't the format. It's the preparation, and specifically the failure to agree on what question the day is actually trying to answer.

Start with one question, not a list of topics ¶

The most common mistake is treating a strategy day as a chance to cover everything that hasn't been discussed recently. Pricing, team structure, marketing, the new product idea, the client who's been difficult. Each of those is a real topic, but putting them all in the same room for the same day produces a kind of productive-feeling chaos that resolves into nothing.

A useful strategy day has one central question. Not a theme, not a focus area. A specific question with a yes/no or a ranked set of options as its answer. Everything else in the day serves that question.

The pre-work that most teams skip ¶

Before anyone gets in a room together, each person should spend thirty minutes writing down their current answer to the central question and the two or three assumptions that underpin it. Not a presentation, just a short note. This does two things: it surfaces the disagreements that exist before the day starts, and it gives the facilitator something real to work with.

At Amber Rocket, the pre-workshop briefing for the Pull It Apart workshop includes exactly this kind of individual preparation. It's the part that clients most often say made the biggest difference.

What to do with the outputs ¶

By the end of a well-run strategy day, you should have one clear decision or a ranked shortlist of options, a list of the assumptions that decision rests on, and a named person responsible for the next concrete action. If you have more than that, you probably tried to cover too much.

The written summary matters more than people expect. Not because anyone will read it carefully in six months, but because the act of writing it forces the group to agree on what was actually decided, which is often less settled than it felt in the room.

The test of a strategy day isn't how energised people feel at five o'clock. It's whether anything is different three weeks later.