A strategy everyone agreed with and nobody executed

The offsite went well. The analysis was sound, the slides were clear, and when the room was asked whether everyone was aligned, nobody objected. Six months later the strategy exists as a document and not as a set of decisions anyone has made differently.

This is usually diagnosed as a communication failure and treated with more communication — a roadshow, a cascade, a one-pager. It rarely works, because the problem is not that people did not hear the strategy. It is that the strategy never asked anyone to give anything up.

Agreement is cheap when nothing is scarce

A strategy discussed in a planning meeting costs nothing to agree with. Everyone can support "we will move upmarket" and "we will improve delivery quality" and "we will grow the mid-market channel" simultaneously, because in a meeting those are not competing — they are all just good.

They start competing the moment there is one engineer, one quarter, or one budget. That is where a strategy is actually made, and it is the conversation the offsite structurally avoided.

So the room leaves aligned on words and unaligned on trade-offs. Each person goes back and interprets the strategy in the direction of their own constraints, entirely in good faith, and six months of divergence follows.

What has to happen in the room instead

The mechanism is scarcity. Put the group in a situation where resources are genuinely limited, commitments are binding, and the consequences of over-committing arrive before the session ends.

Three things then become visible that a planning meeting hides:

Which priority actually wins. Not which is listed first, but which one people fund when they cannot fund both. Groups are frequently surprised by their own answer.

Who was never consulted. Decisions get made without the person holding the relevant information, not out of disregard but because the clock is running. This is the exact mechanism by which strategies get executed badly, and it is visible in round two.

What over-commitment costs. A promise made at minute five that cannot be honoured by minute forty is not an abstraction. Teams watch it happen to their own structure.

The debrief question then writes itself: what did we fund when we could not fund both, and is that the same answer we have been giving in the plan?

The four ways a strategy quietly stops

Worth naming before a session, because the group will recognise at least one of these in themselves within the first round, and the recognition is what the day trades on.

Everything was a priority. Seven initiatives, all important, none resourced to completion. The organisation is busy and nothing finishes. This is the most common failure and the hardest to admit, because every individual item is defensible.

The trade-off was made further down. Nobody at the top chose between quality and speed, so a team lead chose, on a Tuesday, under pressure, without knowing they were setting policy. They usually chose reasonably. They just chose differently from the team next door.

The measure drifted from the intent. A number was picked to represent the strategy and then the number became the strategy. The organisation optimises the proxy and the thing it stood for gets worse.

Nobody owned the interface. The strategy needed two functions to change together. Each changed its own half. The join was nobody's, and that is where it failed.

A session cannot fix any of these directly. What it does is make which one you have unmistakable, in a room containing the people who can act on it.

Who needs to be there

The people who control the resources, and the people who spend them. Sessions with only the first group produce agreement that changes nothing on the ground; sessions with only the second produce a clear-eyed account of the problem delivered to nobody with authority.

That usually means a leadership team plus one layer down — roughly twelve to twenty-five people, in three to five teams. Big enough that teams genuinely compete for scarce resources, small enough that a single debrief can reach a decision.

One test worth applying to the invitation list: if the session produces the recommendation to stop doing something, is the person who could stop it in the room? If not, move the date.

Turning a session into execution

A session produces clarity that decays. Three things convert it, and all three have to be agreed before anyone leaves the room.

One thing that stops. Strategies fail through addition. If the session does not produce something the organisation will stop doing, it has produced a wish list. Name it, name who tells the people affected, name when.

A decision right that moves. The session will have surfaced at least one decision that is being made too far from the information. Move it, in writing, on the day.

A number that gets watched. Not a dashboard — one number, already tracked, that the strategy should move. Agree what it is and when it gets looked at, which is the difference between a strategy and a document about one.

Where sessions do not help

When the strategy is genuinely unclear at the top. A session with a leadership team that has not decided will surface the disagreement, which is valuable, but it is a strategy meeting, not an execution one. Run it as that and say so.

When the constraint is capability, not alignment. If the organisation agrees on the strategy and cannot do it, the answer is hiring or building, not a workshop. A session will make this obvious, which is useful exactly once.

When the people in the room cannot change anything. Execution sessions for groups without budget or authority produce well-informed frustration.

Where HDX fits

Rooted is built on exactly this trade-off. Teams buy materials, promise revenue and build a structure that has to carry what they committed to — and the leaves are weighted, so an ambitious promise at minute two is a physical load on a branch at minute thirty. Profit is revenue minus costs minus penalties, and a structure that cannot hold what was promised says so in front of the room. The surprise reopening of the market in round two is the most argued-about moment of most debriefs, because it is a real opportunity arriving at the worst possible time, which is what opportunities do.

Where the execution problem is cross-functional rather than structural — different groups pulling the same strategy in different directions — Falcon Eye runs it as competing villages with scarce resources and genuine negotiation, which surfaces who is optimising for their own village at the system's expense.

Worth reading alongside: measuring behaviour change for setting up the number before the session rather than after, and what a simulation costs a corporate buyer if you are building the business case.

---

If a strategy everyone agreed with is not being executed, tell us what the room needs to decide.