A strategy is the choice of which problems you do and don't address, and why that choice is the right one at this moment. A plan is the translation of that choice into who does what, with which budget and at what time. The difference seems semantic, but in practice it's the reason management teams contradict each other without anyone realizing it: one person talks about the choice, the other about the execution, and both think they're talking about strategy.
At a service provider of roughly 120 employees, there's often a thirty-page strategic plan sitting on the shelf: growth targets, new market segments, a digitalization agenda, a culture program. Everything is in there, with deadlines and people responsible. What's missing is the answer to the question of why these five points made the list and the other twenty didn't. Without that underlying choice, it's not a strategy but an organized collection of initiatives. That only becomes visible the moment the market turns unfavorable and a choice has to be made about which initiative gets shelved — and no one remembers anymore which criterion applies.
The opposite happens just as often. A management team wholeheartedly agrees on the direction — for example: becoming less dependent on one large customer — but that direction has never been translated into hours, systems, or an adjusted commission model for the sales department. Everyone endorses the strategy in the meeting, but nothing changes in the agendas of the weeks that follow. The strategy then only exists as a sentence in the minutes, not as guidance.
The most difficult point is not the distinction between strategy and plan on paper, but the spread within the team about what the strategy actually is. At a manufacturing company of 200 people, the CFO could name the exact growth figure, while the COO had a completely different picture of which customer segments were given priority for it. Both had read the same plan document. That kind of spread between board members is exactly where a self-plot on five axes becomes useful: not to prove who's right, but to make visible where the interpretations diverge before that causes delays in execution. Anyone curious about what that looks like in their own situation can take the free mini-test: ten questions that give an indication of the pressure profile of their own strategy, without requiring an advisory conversation.
A plan has a longer shelf life than the assumptions it's based on, and that's where many management teams get stuck. The plan is executed as agreed, while the market, regulations, or competition have since moved on. How you recognize that a strategy has become outdated doesn't depend on the feeling that something is off, but on a concrete check between the picture from outside and the assumptions the plan still rests on. Companies that don't have a fixed moment for that usually only discover the difference when a customer, regulator, or competitor demonstrates it for them. What to do when the market changes faster than the plan is therefore a different question than whether the plan is on schedule — it's about whether the plan still addresses the right problem. More on that can be found at what you do when the market changes faster than your plan.
A strategic choice without a recorded reason can no longer be traced at the next change of leadership — and is then often mistakenly seen as an error, while the circumstances at the time of choosing may have been perfectly logical. Recording how you substantiated a strategic choice is therefore not just a matter of accountability, it's the only way to later assess whether the choice has become outdated or whether the execution is falling short. What that recording can look like is explained at how you record why you made a strategic choice. Also relevant is who needs to be in the room when that choice is reviewed: who needs to take part in a strategy review determines whether the spread between board members becomes visible before execution stalls, or only afterward.
The first step is not to rewrite the plan, but to check whether the current plan still reflects a choice that the entire team understands in the same way. That doesn't require a new process, just an honest comparison laid side by side. Once that picture exists, the question automatically shifts: from 'what is our strategy' to 'what does this mean for tomorrow's agendas, hours, and systems'. That translation step — from themes to tasks, hours, and responsibilities per person — is precisely where the werkscan at ftetoai.com is deployed, for anyone who wants to know what a decision agenda concretely means for who will do which work.
Stel uw vraag. Vaak zit de echte vraag een laag dieper — daar mag ik naar vragen.
Answers come from this site’s knowledge base. Not tailored advice, and not a scan of your company.