Your Vision Is Not the Problem. Not Knowing When You've Reached It, Is.

Run a structured Ambition Setting Workshop where the team writes its own ambitions live, tested against the same readiness criteria, not a top-down mission statement handed down after the fact. Alignment built by having a small group draft a statement and present it to the rest rarely survives first contact with a budget conversation; alignment built by having the whole team write and stress-test the ambition together tends to hold, because everyone was in the room when the trade-offs got made.

Treat it as a thinking exercise, not a wordsmithing exercise, start from external research and internal interviews, not a blank page and a facilitator asking everyone to shout out adjectives. Most vision statements read the way they do because the process that produced them was really just an editing exercise on whatever the loudest voice in the room proposed first. Starting from evidence about the market and the organisation's own capability changes what gets written, not just how it's phrased.

A vision states direction; it does not need to be a plan. The plan belongs in the target state layer beneath it. Trying to make a vision statement do both jobs at once is why so many end up vague enough that every department can read its own agenda into it, a genuine vision should be specific enough to rule things out, even if it doesn't yet say exactly how those things get ruled out.

The target state is the measurable, 12-18 month milestone toward the vision, concrete, time-bound, and ambitious but achievable, unlike the vision itself, which describes a direction without a deadline attached. Where a vision might say the company will lead its category on sustainability, the target state says specifically what that looks like at month fifteen, in numbers a board can actually track, which is what turns a direction into something the organisation can be held accountable for.

Add a “vision state” layer describing concretely what success looks like, then a nearer-term target state as the first measurable milestone toward it. Most visions skip this step entirely and jump straight from a direction statement to a set of KPIs, which leaves a gap nobody can explain: what does achieving the vision actually look like, concretely, before you even get to measuring progress toward it? The vision state layer exists specifically to close that gap.

Run an Ambition Setting Workshop to translate it into 1-3 concrete, completable ambitions with recognition signals attached to each one. A vague vision isn't necessarily a badly written one; it's usually a vision that was never translated into anything specific enough to plan against. The workshop doesn't rewrite the vision itself, it builds the missing layer underneath it that tells the organisation what to actually do this year.

Define a target state, the same ambition, scoped to what's achievable and measurable within 12-18 months, rather than a generic annual goal loosely inspired by the long-term vision. The discipline here is scoping down without losing the connection upward: every target state should be traceable back to the specific vision-state element it's a milestone toward, so short-term work never quietly drifts away from the long-term direction it was supposed to serve.

Score it against 8 internal readiness dimensions and 5 confidence gates covering market growth, customer pull, operational feasibility, margin, and legal or compliance exposure, before committing to it publicly or building a budget around it. A target that clears all five gates is realistic in the sense that matters: the organisation actually has, or can build in time, what it takes to deliver it, not just that it sounds achievable in a planning session.

Work backward from the target state: what must this organisation be able to do, which roles and decision rights follow from that, and what does the organisation look like once it can actually do those things reliably. Most capability gaps only become visible once someone tries to answer this question specifically for the target state rather than for the strategy in the abstract, a strategy can sound complete while quietly assuming capabilities nobody has actually built yet.

Derive it directly from the validated target state, capabilities, roles, and decision rights follow from what the ambition requires, rather than being redesigned in the abstract or copied from whatever operating model looked fashionable at a conference. An operating model designed this way tends to be leaner too, since it only includes what the specific target state actually needs rather than every function a generic best-practice template happens to recommend.

Make the weighting between competing goals, growth versus margin, speed versus care, explicit at the ambition-setting stage, so it isn't re-decided weekly at department level by whoever has the most urgent deadline that particular week. Most departmental conflict isn't actually disagreement about the goals themselves; it's the absence of a stated priority between them, which forces every team to guess, and different teams tend to guess differently.

A two-hour session with decision-makers where ambitions are written live using the Vision-to-Action framework, informed by prior interviews and external research gathered in the weeks beforehand. Attendance should be limited to people with real decision authority over the ambitions being set, adding observers or delegates tends to dilute the ownership the workshop is specifically designed to create, since the people who wrote the ambition are the people who defend it afterward.

Run it through 5 confidence gates covering market growth, customer demand, operational feasibility, margin, and legal or compliance exposure before finalising it, not after it's already been announced internally or externally. An ambition that fails one gate isn't necessarily abandoned; it might simply need a longer timeline or a dependency resolved first, but that's a very different conversation to have before commitment than after.

Involve people beyond the boardroom in the interview phase, the shop floor often knows the real playing field better than leadership does, and their early involvement in shaping the ambition tends to produce far more durable buy-in than a rollout presentation after the fact. Buy-in built through participation in the diagnosis stage survives contact with implementation difficulty far better than buy-in built through a well-delivered announcement.

Every target and target state is built as a building block toward the vision, not a standalone goal that happens to point the same way by coincidence. The traceability has to be explicit and checkable, someone should be able to ask why a specific quarterly target exists and get a direct answer back to the vision state it serves, rather than a general sense that it's probably related.