Every organisation has a strategy.
It has objectives. Initiatives. Milestones. Owners. A review cadence. A slide deck that gets updated quarterly.
It is a plan.
This is not an insult. Plans are useful. An organisation that could not produce one would be in serious trouble.
But a plan is not a strategy. The two words describe different cognitive operations applied to different conditions, and they fail in different directions.
The conflation is so common it has become invisible. Which is why strategies so regularly fail to survive contact with the conditions they were designed for.
The distinction is not semantic. It changes what you need to develop.
What a plan assumes
A plan specifies actions in sequence. Step one leads to step two leads to step three. It works when the environment cooperates: when the dependencies hold, the timeline is realistic, and conditions at step five resemble conditions at step one closely enough for the earlier decisions to still be valid.
Planning is exactly the right tool for that situation. If you are rolling out a software update across a known infrastructure, plan. If you are building a factory with a fixed budget and defined specifications, plan. These are execution problems. The environment is stable. The path is knowable.
The problem begins when the environment is not stable and the plan is applied anyway.
A plan is a bet that the environment will cooperate. Strategy is what you do when you know it won't.
The direction without the route
spent decades studying what strategists actually do, rather than what strategy textbooks prescribed. His finding: planning is programming. It translates an already-decided direction into a sequence of steps. Strategy is discovering. It forms a view about direction when the path cannot be specified in advance because the terrain ahead is genuinely unclear.
You plan when the path is knowable. You strategise when it is not. Strategy does not produce a sequence of steps. It produces a direction and the judgment to navigate toward it as conditions change.
This is why strategy is harder to teach through frameworks. A framework can be programmed into a plan. It cannot be programmed into the judgment required to navigate genuinely uncertain conditions.
Why planning gets called strategy
identified the mechanism precisely. Planning feels like strategic work. It requires analysis, debate, decisions about priorities. At the end, there is a document with structure and ownership. The organisation has acted.
The discomfort of genuine strategic commitment, to a direction without a guaranteed route, gets replaced by the tractable work of planning. Boards want evidence of direction. Teams want to know what to execute. A plan answers both needs. A genuine strategy commits to a direction while accepting that the route will be discovered, not specified. That commitment is harder to present and easier to dismiss.
So the plan becomes the strategy by default. And the default holds until conditions change and the plan no longer fits.
How the plan becomes the obstacle
named the condition in 1832: friction. The gap between the plan and the reality it encounters. Every plan is made on the basis of assumptions about conditions. The opponent's actions immediately begin to invalidate those assumptions. The formulation attributed to Moltke the Elder, his intellectual inheritor, is exact: no plan survives contact with the enemy.
Not because the plan was badly made. Because the enemy acts. Because conditions at step five no longer resemble the conditions under which step two was designed.
A plan in an uncertain environment does not simply underperform. It resists adaptation. It has committed people to a sequence of actions. Revising course means overriding a document that the organisation has reviewed, approved, and used to set expectations. The more detailed the plan, the more resistance it generates to the navigation it was supposed to enable.
You cannot plan in Go. You can only navigate.
The B in FusekiB
The name encodes the distinction. Strategy is movement from a current position toward a desired one. The B is the desired position. The orientation that makes navigation possible. Without it, movement is just activity.
What FusekiB develops is not the ability to produce a plan for reaching B. It is the capacity to navigate toward B when conditions change, when the path that made sense at move ten no longer fits the board at move thirty, when commitment has to be revised without being abandoned.
Go is the practice environment for this because planning breaks down in Go by design. Every stone changes the board. The opponent acts. The sequence that was right two moves ago may no longer be available. No plan survives the fourth move.
What survives is the judgment to read a changed position and decide what the situation now requires. That is the only thing that has ever been worth developing.