
Show Notes
The Strategy Arrived After The Decision
---
Some strategies are instruments for deciding. Others are instruments for explaining.
The difficulty is that both look exactly the same once they have been turned into slides.
The decision may have happened weeks earlier. In a corridor. Over lunch. On a phone call nobody minuted.
---
Then came the strategy. Forty-two pages of it. Rigorous. Polished. Pointing exactly where it was always going to point.
The board approved it. Nobody asked about the lunch.
---
This episode examines Reverse Strategy — a strategy written to explain a decision already made, organised after the conclusion rather than before it.
Sometimes that is harmless. Sometimes instinct is faster than analysis. Sometimes the most important reasoning happened in a conversation that was never written down.
---
The problem begins when the explanation is mistaken for the reasoning.
Because then the organisation examines the framework while the actual decision-making event remains entirely outside the frame.
---
The portable question — worth carrying into every strategy presentation you will ever sit in: "Which came first — the strategy or the decision it supports?"
The decision arrived from instinct. The strategy arrived from PowerPoint.
Field Note #054.
More from Engineering the Intelligent Enterprise
The presentation was beautiful. The premise was untested.
Indifference is easy to spot in a poorly made product. The harder failures to diagnose are the ones caused by devotion.
On the quiet agreement between those who produce numbers and those who read them.
The room achieved consensus. The project achieved nothing. — Why do initiatives that receive unanimous approval on Tuesday afternoon stall completely by Friday morning?