Most companies have a planning process. Annual planning, quarterly planning, some version of a strategy cycle. Leadership retreats, financial modeling, headcount debates. The output is a plan that everyone leaves the room aligned on.
Then execution starts. Within weeks — sometimes days — the plan starts to drift. Not because people aren't trying. Because the planning process has a structural flaw: it produces a document, not a system.
The break between planning and execution is where strategy goes to die.
What planning actually produces
Done well, a planning process produces:
- A set of goals for the period
- A budget to support those goals
- A high-level timeline for major milestones
- Headcount assignments to teams
What it does not produce, by default:
- Who owns each cross-functional dependency
- Decision principles for the cases the plan didn't anticipate
- A mechanism to check whether the plan is still valid as circumstances change
- Accountability for the gaps between planning assumptions and execution reality
The result: a plan that's accurate for the moment it was created and becomes less accurate every week after — with no built-in mechanism to update itself.
The five breaks
Goals without milestones. A 12-month goal with no quarterly waypoints isn't a plan — it's a hope. Teams don't know if they're on track until the end of the period, when there's nothing left to fix. The planning process produced a destination but not a map.
Budget assumptions that expire. Planning allocates resources based on a model of what the work looks like. By month two, the model is usually wrong — some initiatives took more effort than modeled, some less. The budget still reflects the old assumptions. Teams either overspend quietly or under-execute against plan. Nobody has a mechanism to reconcile this in real time.
Strategy that doesn't travel to function-specific plans. The company strategy lives in the executive team's document. Each function then interprets it independently. Marketing builds a marketing plan. Engineering builds an engineering plan. Sales builds a sales plan. These plans are often quietly inconsistent — different assumptions about market conditions, different timelines, different priorities — but the planning process has no mechanism to surface the inconsistencies until execution reveals them in the form of a conflict.
A plan that becomes a historical document. The plan was made at a two-day offsite in November, based on what was known in November. The operating rhythm for the next 12 months is weekly standups, monthly reviews, quarterly checkpoints. If that operating rhythm never asks "is our plan still valid?", the plan stops being a working document and becomes a relic. Teams keep executing toward a destination the company has already moved away from.
Decisions without records. During planning, tradeoffs get made: why this market over that one, why this initiative funded and not that one, what data was relied on. Most of that reasoning lives in the room where it was decided. Three months later, when a new lead joins or a team pivots, the context is gone. Teams execute on the output of decisions without the reasoning that would allow them to adapt when conditions change.
The core pattern
In each case, the break is the same: information or accountability that existed during planning doesn't survive the transition to execution. The plan was made in one context — the offsite, the spreadsheet, the leadership meeting — and execution happens in another — the weekly standup, the Slack channel, the 1:1.
The fix isn't better planning. It's planning that anticipates the break and builds infrastructure to bridge it: decision records, milestone check-ins tied to the operating rhythm, explicit ownership of cross-functional dependencies, and a process for updating the plan when underlying assumptions change.
That process doesn't need to be elaborate. Tiago Forte's concept of the weekly review — a scheduled moment to step back from execution and re-sync — applies at the organizational level. A monthly or quarterly moment where teams ask: is our plan still valid? What has changed? What should we update? Without that scheduled departure from execution mode, the plan slowly becomes fiction.
Why it keeps happening
Because planning feels complete. You have a document. You have alignment. You have sign-off. The natural move is to execute.
The companies that close this gap treat the planning process as incomplete until they've established: how will we know if this plan is still valid? Who owns each cross-functional dependency? What does a plan update look like and who can trigger one? Planning without those answers isn't a plan — it's a budget with goals attached.
