Strategic Planning Fails at the Handoff to Execution
Strategic plans in mid-market companies rarely fail because the thinking was wrong. They fail at the point where an intention has to become a commitment somebody can be held to. That handoff is a distinct piece of engineering, and almost nobody builds it.
An objective and a commitment are different objects
An objective describes a desired end state. A commitment names a person, a date, and a quantity of capacity that person will spend. Planning sessions produce the first in volume and the second almost never.
The gap is easy to miss because both fit on the same slide and use similar grammar. Growing into a new segment reads like a plan. Two named people spending a third of their week on that segment through the third quarter is a plan.
Anything that cannot be written in the second form has not been planned yet. It has been wished for, which is a legitimate first step and a poor final one.
The plan assumes capacity that is already spent
Most annual plans are built as though the organization starts the year empty. In practice every person is already fully consumed by the work that keeps revenue arriving this month.
New initiatives therefore arrive as an addition to a full load rather than as a reallocation from something else. The team accepts them because refusing looks like a lack of ambition. Then the initiative loses every scheduling conflict against the work that produces this quarter's invoices.
Run the arithmetic before the plan is approved rather than after. List what each contributing person currently spends their week on, then subtract what the plan requires. Where the subtraction produces a negative number, the plan is not a plan yet.
Naming what stops is the actual planning decision
The hard half of strategy is subtraction, and subtraction is what gets skipped. Adding an initiative is a pleasant meeting. Naming the activity that ends so the new one can exist is an unpleasant one.
Organizations avoid the unpleasant meeting by declaring both the old and the new important. The result is an initiative stack deeper than the capacity available to it, which converts a prioritization problem into a queueing problem nobody manages.
Work in progress limits solve this more reliably than better prioritization does. Cap the number of live strategic initiatives at a figure the organization can actually staff. Anything beyond the cap waits in a visible queue rather than proceeding at a quarter of the necessary intensity.
Cascading is not the same as allocating
The standard model pushes a corporate objective down through each layer until every team holds a version of it. That motion distributes language rather than resources, and language is not the scarce input.
Hoshin Kanri describes the corrective as catchball, meaning the objective travels down and the constraints travel back up before anything is fixed. The team receiving an objective states what it would need and what it would have to stop. Leadership then adjusts the objective, the resourcing, or both.
Skipping the return leg produces plans that were never agreed to by anyone required to deliver them. Coherence between the stated objective and the resourcing is what makes the cascade mean anything at all.
Plans get estimated from the inside and should not be
Teams estimate a new initiative by imagining how it will go. That method systematically produces optimistic numbers, because imagining a project surfaces the steps and not the interruptions.
The alternative is to look outward at comparable efforts already completed. What did the last three initiatives of similar scope actually take, measured from approval to operating? That figure is nearly always longer than the inside estimate and considerably more accurate.
Rigor here is cheap and unpopular. Keeping a simple record of how long past initiatives ran gives every future plan a reference point that does not depend on anyone's mood in the planning room.
Strategy is a portfolio of bets, so write the kill criteria
Some initiatives will not work, and the plan should say so in advance. A portfolio framing accepts that outcome rather than treating each failure as a discrete embarrassment requiring explanation.
Write the abandonment condition at approval, while the initiative is still unattached to anyone's reputation. What observable result by what date would mean this bet is not paying. Deciding that in advance costs nothing and later saves an argument nobody can win.
Without stated kill criteria, initiatives end by quiet starvation rather than by decision. Starvation is slower, consumes capacity the whole way down, and teaches the organization nothing usable.
The annual cycle is the wrong clock for most of the work
A twelve month planning horizon made sense when the operating environment moved slowly enough that a January estimate stayed useful in September. That condition has largely stopped holding for mid-market companies.
The practical repair is not continuous replanning, which produces churn and no direction. It is separating the parts of the plan that hold from the parts that need refreshing. Direction and resource envelopes hold for a year, while specific initiative sequencing holds for a quarter.
Consistency in that split is what allows a company to change tactics without relitigating strategy every time something moves. Continuity of direction and flexibility of sequencing are compatible once the two are separated on purpose.
Naming the frameworks that carry the handoff
Three named models do useful work here, and each fails in a specific way when applied without the others.
The OKR framework is built to make objectives measurable, and its common failure is producing measurable objectives nobody resourced. A key result without a capacity allocation behind it is a scoreboard rather than a plan, which is why teams report red for two quarters and change nothing.
Hoshin Kanri contributes the return leg described above, and its value is entirely in the negotiation rather than in the paperwork. Organizations that adopt the templates without the shared negotiation get a longer document and the same unresourced plan.
The Theory of Constraints supplies the sequencing rule that the other two lack. Where several initiatives depend on one constrained person, total completion time is set by that person and by nothing else. Running the initiatives in parallel simply delays all of them together.
Where the handoff actually breaks
Three failure points account for most of the distance between a good plan and a poor year, and all three are observable within a week of approval.
The first is an unnamed owner. An initiative assigned to a department rather than to a person has no one whose week changes on Monday, and a week that does not change produces no progress.
The second is an absent first action. Where the plan states an outcome without stating what specifically happens next, the initiative waits for someone to design that step and nobody has been asked to.
The third is a missing forum. Where progress has no scheduled place to be examined, review happens only when something has already gone visibly wrong. By then the useful decisions have expired.
Conditional rules for the planning cycle
Where an initiative has no named owner whose weekly schedule changes, remove it from the plan and hold it in the queue. An unowned initiative consumes attention in reviews while producing nothing.
Where two initiatives require the same scarce person, sequence them explicitly rather than running both. Parallel execution against a single constrained resource finishes later than deliberate sequencing does, and it finishes with worse quality.
Where an initiative has produced no observable movement across two consecutive review cycles, treat that as data about resourcing rather than about effort. The team is almost certainly working, and the work is almost certainly going somewhere else.
Governance of the plan is a rhythm, not a document
A plan is a set of live commitments and needs a cadence that keeps them live. The mechanism is small and most organizations already own the parts.
A standing forum meets on a fixed schedule. A visible list carries each initiative, its owner, its next observable step, and its kill criteria. Anything that misses two cycles gets an explicit decision to continue, resource differently, or stop.
Process architecture at this level is unglamorous and does most of the work. The systems that keep a plan alive are considerably duller than the ones that produce it.
Strategic fit is what makes the subtraction survivable
Cutting activity is only defensible when there is a clear account of what the organization is choosing to be. Without that account, every subtraction reads as arbitrary and gets quietly reversed by whoever was cut.
Strategic fit supplies the account. An activity that the chosen position requires stays even when it is expensive. An activity that made sense under a previous position leaves, and stakeholder value improves because the capacity moves to something the strategy actually needs.
Operational excellence in planning is mostly the discipline to state the position clearly enough that the subtractions follow from it rather than from a budget target.
Plans that respect capacity protect the people executing them
Capacity arithmetic is not an administrative nicety. A plan exceeding available capacity does not fail on paper first. It fails on people, who absorb the shortfall as longer weeks and a persistent sense of falling behind.
Human capital erodes quickly under a plan that was never achievable, and it erodes fastest among the people who tried hardest to deliver it. Servant leadership expressed here means doing the capacity arithmetic before asking anyone to commit.
Teams extend real effort to plans they believe are possible. Establishing that belief is a design task rather than a motivational one, and it starts with a plan that subtracts as honestly as it adds.
Watch the full explainer
Related
Further material on management consulting and operational structure from World Consulting Group: [www.worldconsultinggroup.com](https://www.worldconsultinggroup.com)