Delivery
The move that looks most like progress is usually the move that should come later.
Give a capable, action-oriented person a broken situation, and they will start fixing it. In almost every other context, this is exactly what you want. At the executive level, it is also the single most reliable way to make a bad situation worse.
The obvious first action — the one that presents itself most immediately, that feels most like progress — is almost always an intervention at the wrong point. The broken thing gets fixed, and the system it sits inside produces the same failure again, somewhere else, slightly later.
The First Move Fallacy
This pattern is consistent enough to deserve a name: the belief that the right first action is the one the situation most obviously seems to demand. The fallacy works by disguising itself as responsibility — acting immediately feels like exactly what a competent, decisive leader should do. But visibility is not the same as importance. Complex systems present their symptoms far from their causes, so the thing demanding attention is almost never co-located with the thing that needs to change.
When an intervention feels obvious and urgent, that feeling is itself the signal to slow down and ask whether the obvious move addresses the symptom or the cause.
What Delivery actually asks for
This includes diagnosing before acting on an inherited situation, keeping scope and risk trade-offs explicit rather than implicit, distinguishing a genuinely blocked team from a comfortably busy one, and measuring success by whether the business outcome landed — not just whether the project closed on time and on budget.
Where to start
- The next time an intervention feels obvious and urgent, pause and ask what the obvious move is actually treating — symptom or cause.
- Before committing to a fix, trace the visible problem one level further back. The First Move Fallacy is consistent and correctable once you know which direction it points.