Date:
Author:
in2o Team
001
The handover that never happens
A strategy is usually signed off in a room that does not contain the people who will deliver it. The document leaves that room complete on its own terms — a direction, a set of pillars, a target — and arrives at the teams as an interpretation exercise. Everyone agrees with it, and everyone reads it differently.
What is missing is not commitment. It is a translation layer: the step where a pillar becomes a named initiative with a scope, an owner, a first milestone, and a decision it is allowed to make on its own. Without that step, a strategy stays a description of a destination rather than an instruction for the next ninety days.
002
Translate direction into decisions
The most useful question to ask of any strategic pillar is: what does this let us stop doing? A direction that only adds is a wish list. A direction that also removes is a plan.
From there the work becomes concrete. Each pillar produces a small number of initiatives; each initiative names the decision it exists to make, the evidence it needs to make it, and the point at which it will be either scaled or closed. This is what turns a strategy into a portfolio you can manage — one where stopping something is a sign the strategy is working, not a sign it is failing.
003
Give the work an owner and a rhythm
Initiatives fail quietly when ownership is spread across a committee. Someone has to be accountable for the outcome rather than the activity, and they need enough authority to change the approach without renegotiating the mandate.
Rhythm matters as much as ownership. A monthly forum that reviews progress against decisions — rather than against a Gantt chart — surfaces problems while they are still cheap to fix. The agenda is short: what did we learn, what changed as a result, and what do we need a decision on today. Meetings that only report status do not move work; meetings that resolve blockers do.
004
Measure the change, not the activity
Most transformation dashboards measure effort: workshops held, systems launched, people trained. These are inputs. They tell you the machine is running, not that it is producing anything.
The alternative is to define, at the start, the one or two things that will be observably different for a beneficiary, an employee or a budget line if the initiative works — and to measure them from the beginning, including before the change lands. A baseline taken after launch is not a baseline. Naming the difference in advance has a useful side effect too: an initiative that cannot name one rarely survives the conversation.
