Strategic planning produces two different things, and most organisations only produce one. A strategy document describes a destination. A quarterly commitment assigns named people to specific work with a date attached. The second does not follow automatically from the first, and a plan that stops at the destination changes nothing about how the week is spent.
A Destination Is Not an Assignment
Almost every company has a vision statement. Very few have a working answer to the question of who is doing what about it before the quarter ends. The distance between those two states is where most strategic planning fails.
The vision statement is genuinely useful. It sets direction, filters opportunities, and gives people a way to judge whether a request belongs to the business. None of that is trivial and none of it survives contact with a busy operating week on its own.
What survives a busy week is an assignment. Assignments have owners, deadlines, and a defined finished state. A vision has none of those things and was never designed to.
The failure is not that companies write visions. The failure is that they treat the writing as the completed act. The document is signed off, circulated, and printed, and everyone returns to the work they were already doing.
There is a reason the writing feels like completion. Producing a strategy document is genuinely hard work, and the relief at finishing it is real. That relief is easily mistaken for arrival.
Anyone who has watched a leadership offsite end in applause has seen the effect. The energy in the room is authentic and it dissipates within about a fortnight. Nothing in the process was designed to convert that energy into scheduled work.
Why the Annual Plan Decays So Quickly
Annual planning assumes the operating environment holds still for a year. It rarely does. By the second quarter the assumptions behind the plan have usually shifted enough that the numbers no longer describe anything real.
What happens next is predictable. Nobody formally cancels the plan, because cancelling it would require admitting the planning process produced something disposable. Instead the plan quietly stops being referenced.
Meetings move on to whatever is urgent. The document remains on a shared drive, technically current and functionally dead. When the next planning cycle arrives, the same process runs again with new numbers and the same fate.
The deeper problem is the length of the feedback loop. A plan reviewed once a year gives the organisation a single opportunity to notice it was wrong. That is far too few chances to correct in a market that moves faster than the calendar.
Shortening that loop is the single highest-return change available to most leadership teams. It costs nothing beyond meeting discipline. It requires no new system and no consultant.
What a Quarterly Commitment Has That a Plan Does Not
A quarterly commitment is a short list of outcomes the company intends to achieve in the next three months. Each item has one owner. Each item has a definition of done that two reasonable people would judge identically.
That last property does most of the work. Vague commitments survive review because nobody can prove they were missed. Specific commitments cannot hide, which is why teams resist writing them and why writing them changes behaviour.
The list must also be short. A leadership team that commits to fifteen outcomes has committed to none of them, because the organisation will default to whatever is loudest rather than whatever was agreed. Three to five outcomes is the practical limit for most mid-market companies.
The case for running the business on quarterly execution cycles rather than annual plans rests on this compression. A shorter horizon forces sharper choices, and sharper choices are easier to assign.
Quarterly commitments also create a natural moment to kill work. Anything not on the list is explicitly not a priority for the next three months. Saying that out loud is uncomfortable, which is exactly why it needs a formal occasion.
The Translation Layer Nobody Owns
Between the strategy document and the quarterly list sits a translation step. Someone has to convert an ambition into a set of finite tasks that a specific team can complete. In most companies nobody is responsible for that step.
The executive who wrote the strategy considers the work finished at the document. The managers who receive it consider their job to be delivering the current operating plan. The translation falls into the gap between those two views and stays there.
Where a company does have someone doing this work, it is usually informal. A chief of staff, an operations lead, or a founder who happens to think in tasks. That arrangement functions until the person leaves, at which point the connection between strategy and execution disappears without anyone diagnosing why.
Making the translation layer explicit is the fix. One person owns the conversion of strategy into quarterly commitments. That person is accountable for the list existing, being specific, and being reviewed.
The role does not require authority over the work itself. It requires authority over the process that defines the work. Those are different powers and the second is far easier to grant.
Testing Whether a Vision Can Be Acted On
A vision statement can be tested without a workshop. Take the statement to three people at different levels of the company and ask each of them what it means for their next two weeks. Then compare the answers.
If the answers differ wildly, the statement is not directing anything. If the answers are all some version of keeping up the good work, the statement is decorative. Either result is diagnostic and neither requires a facilitator to interpret.
A second test is subtraction. Ask what the company has stopped doing because of the vision. A direction that has never eliminated an activity is not a direction, because it has never had to choose.
The third test is the hardest. Ask a manager what they would need to change if the vision were replaced with its opposite. If nothing meaningful would change, the vision was never load-bearing.
Building a strategic vision the team will actually execute means passing all three of those tests before the statement is circulated. Most statements are written to survive a board slide rather than a Tuesday.
What Changes When the Work Is Assigned
The first thing that changes is the quality of disagreement. Abstract strategy produces polite nodding, because nobody has to accept a cost. Assigned work produces argument, because the costs are now visible and personal.
That argument is the point. A leadership team that never argues during planning has not made a real choice, and the absence of conflict is a warning rather than a sign of alignment.
The second change is in how progress gets reported. Status against a vision is a narrative exercise. Status against a defined outcome with a date is binary, and binary reporting removes most of the room for optimistic framing.
The third change is slower and more valuable. Teams that repeatedly set and review specific commitments become better at estimating what they can actually deliver. That calibration compounds, and after several cycles a leadership team can forecast its own capacity with reasonable accuracy.
None of this requires new software. Most companies attempt to solve execution problems with tools, then discover the tool has faithfully recorded the same vagueness that existed before. A tracker inherits whatever specificity the commitments already had.
Most planning time is spent on the wrong half of the process. Days go into refining the document, choosing language, and building the presentation. Hours, sometimes minutes, go into deciding who does what next.
Reversing that ratio is the practical recommendation. The strategy document should be short enough to state in a paragraph, because anything longer will not be remembered and therefore will not be used.
The quarterly list deserves the remaining effort. Naming owners, defining what finished means, sequencing the dependencies, and agreeing what gets dropped to make room. That work is unglamorous and it is the part that determines whether anything moves.
The sequencing question deserves particular attention. Most quarterly lists fail not because the items were wrong but because two of them required the same scarce person in the same fortnight. Nobody checks for that collision until it happens.
Reviews should be frequent and brief. A monthly check on a quarterly list takes under an hour when the commitments are specific. It takes an afternoon when they are not, which is a reliable signal that the list needs rewriting rather than the meeting needing more time.
A vision that nobody can act on still has a use. It sounds good in a recruitment conversation and it fills a slide. What it does not do is change the order in which work gets done, and that ordering is the only mechanism by which a strategy ever becomes a result. The difference between a company that executes and one that plans is rarely ambition. It is whether somebody wrote down who was doing what, and then went back and checked.
Frequently Asked Questions
How often should a strategic plan be revisited?
The destination itself changes rarely and can be reviewed annually. The commitments underneath it should be rebuilt every quarter and checked monthly. That split keeps the direction stable while allowing the work to respond to what the market actually did. Companies that revisit the destination too often confuse motion with strategy.
What if the leadership team cannot agree on priorities?
Disagreement at this stage is useful information rather than an obstacle. It usually means the strategy was too abstract to force a choice, and the abstraction was hiding a genuine conflict of view. The resolution is to make the trade-off explicit by naming what will be given up. A decision that costs nobody anything was not a decision.
How many commitments should a quarter contain?
Three to five outcomes is the workable range for most small and mid-market companies. Longer lists do not increase output, because capacity is fixed and attention is scarcer than time. Anything beyond that range tends to be a wish list rather than a plan. The discipline is in what gets left off.
Does this replace annual budgeting?
No. Budgets serve a financial control function and follow their own cycle for good reasons. Quarterly commitments describe operational focus, which is a different question from how money is allocated. The two should inform each other without one being collapsed into the other.
Who should own the quarterly list?
One named person should own the existence and quality of the list, though not the delivery of every item on it. That is usually an operations leader, a chief of staff, or the founder in a smaller company. Splitting the ownership across a committee reliably produces a list that nobody maintains. The role is process authority rather than delivery authority.
What should happen when a commitment is missed?
The miss should be recorded plainly and examined for cause rather than blame. Most misses trace back to an unclear definition of done, an unfunded dependency, or a capacity assumption that was never tested. Fixing the pattern matters more than punishing the instance. Teams that treat misses as data improve their forecasting within a few cycles.
No comments:
Post a Comment