Insights ·
From slide to shop floor: why so many strategies gather dust in a drawer
Half the work starts after the recommendation. What separates a deployed strategy from a forgotten document.
Every organisation has lived this moment: the final readout is brilliant, the committee applauds, the document goes out as an attachment — and six months later, nothing has moved. The problem is almost never the quality of the analysis. It is that the strategy was designed as a deliverable, not as a starting point.
Where strategies go to die
Three causes come back, mission after mission.
The recommendation without an owner. A plan where no one personally carries each workstream is a plan that belongs to everyone — and therefore to no one. The question “who gets up tomorrow morning to do this?” should be asked before the last slide, not after.
The timeline without a sequence. Many roadmaps stack initiatives without saying what depends on what. Yet a transformation lives or dies in the order of things: which quick win funds the next step, which technical foundation must precede which use case, which team needs to succeed first to pull the others along.
The altitude gap. A strategy conceived at 30,000 feet always meets the ground: tools that don’t do what everyone assumed, teams already saturated, legitimate local exceptions. If nobody walked the floor during the framing, the landing is paid for at deployment.
Designing for execution
The alternative is not writing bigger documents, but changing the nature of the commitment: staying through implementation, alongside the teams.
It starts at the diagnostic — conducted in the field, without complacency, so the strategy inherits real constraints instead of discovering them later. It continues through the framing: every workstream has an owner, a first deliverable at ninety days, an observable success criterion. And it ends with what is too often forgotten: transferring the skills, so the organisation knows how to carry on without us.
One measure of success
A convincing document is not a result. A process that runs, a team that has changed the way it works, an indicator that has moved durably — those are results. It is the only measure that should count, for organisations and for those who advise them.
Recommendations that gather dust in a drawer all have one thing in common: they were delivered, never deployed.