Annual planning works in year one. Everything is new — the company is different, the team is fresh, the market assumptions haven't been tested yet. The plan feels real because it was built from scratch.
By year two, something shifts. The planning process runs again, but the output looks remarkably like last year's output. The numbers are different. The objectives have been nudged. But the shape is the same, the bets are the same, and the underlying assumptions — about what the company is, what it's competing for, who its customer is — haven't been meaningfully interrogated.
Why year-two plans look like year-one plans
Three forces push annual plans toward repetition.
Sunk cost of last year's structure. Last year's plan built organizational muscle memory. Teams know how to work within it. Managers have been hired into roles it defines. Changing the shape of the plan means changing the shape of the organization — which is harder than updating the numbers.
Planning cycles reward familiarity. Annual planning is a process that produces a document on a deadline. The incentive is to produce the document, not to interrogate the assumptions. Novel ideas slow the process. Familiar plans move faster.
Strategy drift is invisible in the short term. The difference between last year's strategy and this year's reality doesn't announce itself. It accumulates quietly — in customer conversations that don't fit the model, in competitive moves that the plan doesn't account for, in team capabilities that have changed since the plan was written.
Three things that should invalidate a plan mid-year
- A meaningful market shift. If the competitive landscape, regulatory environment, or customer behavior has changed materially, last year's assumptions are wrong. The plan built on those assumptions is wrong too.
- A team or capability change. If you've hired significantly, lost a key person, or discovered a new capability, the plan's resource assumptions don't hold. Running the same plan with different people produces different results.
- Resource reality. Most annual plans are written with optimistic resourcing assumptions. By Q2, the actual bandwidth available rarely matches the planned bandwidth. A plan that ignores this isn't a plan — it's a wish list.
What to do instead
Don't replace annual planning. Add quarterly recalibration checkpoints. Once per quarter, ask: have any of our core assumptions changed? If yes, which objectives are affected? What do we update?
The annual plan provides direction. The quarterly checkpoint provides correction. Together they produce something closer to an actual strategy than an annual plan alone can.
When goals and work are traceable — when you can see mid-year what work is attached to which objectives — recalibration becomes a fifteen-minute conversation rather than a two-week planning cycle.