Executive Summary
- Bain has found leadership teams shift, on average, only about 2% of budget to new priorities after a strategy reset, most of the plan stays theoretical.
- The planning to action gap isn’t a discipline problem, it’s a design problem: the plan was never built a place in the calendar that already exists.
- Business-as-usual isn’t resistant, it’s just better resourced, and it will win every time the new plan doesn’t get its own calendar slot, owner and reporting rhythm.
- The Calendar Test, three questions asked before kickoff, tells you whether a priority was designed to survive the year or just announced into it.
- The earliest warning sign is meetings meant to carry the plan getting shortened or merged “just this once,” well before the numbers move.
How much of your FY budget will actually move to new priorities by December? Bain once put that exact question to a room of executives after a major strategy reset. The honest average answer was two percent.
I open with that number because it names something most leadership teams already feel but rarely say out loud. Everyone nodded at the plan in February. By June, almost none of the actual resourcing has moved to match it, and that gap between the decision and the resourcing is the planning to action gap, one of the main reasons why annual plans fail even when the strategy day itself was sharp.
If you’re a COO watching quarterly numbers drift from the plan, a transformation lead explaining to the board why momentum stalled, or a CHRO fielding “what actually changed” questions six months after kickoff, this is for you. It isn’t about whether the plan was good. It’s about what happens to a good plan once it meets a calendar that was never built to hold it.
What is the Planning to Action Gap?
The planning to action gap is the distance between the priorities a leadership team agrees to in the room and the resourcing, time, budget, attention, that actually moves to match them once the year gets busy.
It shows up as a plan that’s still technically true and functionally dead: nobody has rejected it, nobody has cancelled it, and almost nothing has moved because of it. That gap is rarely caused by a bad decision. It’s caused by a good decision that was never given anywhere to live once the room emptied.
Why Does the Plan Fade By Q2 Even When Everyone Agreed?
Agreement was never the hard part. Getting a room of smart, senior people to nod at a well-argued plan is one of the easier things a leadership team does all year. What’s hard is the following Monday, when the plan has to compete for oxygen against everything that already has a claim on people’s time.
Business-as-usual isn’t lazy or resistant, it’s just better resourced. It has standing meetings with a chair, reports that generate themselves, and muscle memory nobody has to think about. McKinsey once asked nearly 1,500 executives how well their time matched their strategic priorities, and only 52 percent said it largely did. The new plan starts the year with none of that infrastructure behind it. It has a PDF and good intentions.
So when the two compete for the same hours, business-as-usual wins almost every time, not because anyone chose it over the plan, but because it was already built and the plan wasn’t. That’s not a motivation failure, it’s a structural mismatch. Most teams respond to the symptom, low energy around the plan, rather than the cause, a plan with no infrastructure of its own.
Is it a Discipline Problem or a Design Problem?
It’s tempting to read the fade-out as a discipline problem: people didn’t hold themselves accountable, leaders got distracted. The familiar response is more reminders, a stricter tracker, a sterner tone at the next leadership meeting, and it rarely works.
Discipline assumes will was the missing ingredient. But a leadership team walking out of a strategy day is rarely short on will, it’s short on a structure that makes the plan easier to keep doing than to quietly let slide. That’s a design problem, not a character one, and turning strategy into action depends on getting the design right before the year gets busy.
The Calendar Test
The Calendar Test is three questions, asked before a priority is signed off, that tell you whether it was designed to survive the year or just announced into it.
For every priority on the plan, before kickoff, I ask:
- Where does this live in the calendar that already exists?
- Who owns it, specifically, not “the leadership team” but one named person?
- What gets reported, to whom, on what cadence, using what one number that tells you if it’s real?
Skip those questions before the confetti settles on kickoff day, and you haven’t built a plan, you’ve built a wish with a launch date.
How to Use the Calendar Test
Run it in the same room the plan gets signed off in, not as a follow-up exercise once everyone’s back at their desks. Take each priority through the three questions above, out loud, and write the answers down where the whole leadership team can see them. A priority that can’t get a straight answer to any one of the three hasn’t actually been designed yet, it’s only been announced.
This matters most in the first few weeks of the year, while there’s still room in the calendar to give a priority a genuine slot. Wait until March to ask where something lives in the calendar, and the calendar has already filled back up with everything that was there last year.
Example: Designing a Priority to Survive Contact With the Calendar
Take a fairly ordinary FY priority: improve customer retention. It’s announced well, everyone nods, and on the usual pattern it would be competing for oxygen against business-as-usual within a fortnight. This is a composite, built from the pattern I see across FY plans, not one client’s specific rollout.
Run it through the Calendar Test before kickoff, not after. Where does it live in the calendar that already exists? Retention gets a standing fortnightly slot in the leadership meeting, not a mention whenever there’s time. Who owns it, specifically? One named GM, not “the customer team.” What gets reported, on what cadence, using what one number? Renewal rate, reported every fortnight, not folded into a quarterly business review three months later.
Six months on, this priority is still recognisable, not because retention was easier to deliver than the other nine things on the plan, but because it was the one built to survive the calendar rather than announced into it.
What’s The Earliest Signal The Plan is Slipping?
Watch the calendar, specifically watch what refills first. Picture the six weeks after a strategy day: three or four priorities, each meant to get dedicated time, but nobody blocked that time while it still felt spacious in February.
As the year rolls on, the ordinary rhythm of the business quietly claims the gaps first. An extra client call here, a recurring status meeting there, a “quick” catch-up that becomes weekly. None of it looks like resistance, each addition is reasonable on its own, but by May the calendar meant to hold the new plan has been fully re-occupied.
That’s the earliest tell, well before the numbers move: when the meetings meant to carry the plan start getting shortened or merged “just this once.” Once that happens twice, the calendar is telling you exactly where the real priorities sit, and that’s the signal worth acting on before the mid-year review makes it obvious.
Signs Your FY Plan Has a Planning to Action Gap
- The plan has no calendar slot of its own, it only gets discussed “when there’s time.”
- No priority has one named owner, just “the leadership team” collectively.
- The reporting cadence for the new plan is the same as, or slower than, the annual review.
- Meetings meant to carry the plan get merged or shortened “just this once,” more than once.
- The first mid-year review is the first time anyone asks what’s actually changed.
If two or more of these are already true of your FY plan, the gap isn’t a risk on the horizon, it’s already open.
What Actually Closes the Gap
None of this is solved by wanting it more, or a stronger speech at the next kickoff. It’s solved with the same infrastructure business-as-usual already has: a calendar slot that existed before the year got busy, a named owner whose job depends on the outcome, and a reporting rhythm that surfaces slippage in weeks, not at the annual review. This is execution discipline, not a communications fix, get that scaffolding right in the first 48 hours after the plan is agreed, and the odds change substantially.
I build this exact structure with leadership teams in the new financial year kickoff engagement, the part that lets a plan survive its own launch. If your team just finished a strategy day and you want the plan still recognisable in October, that’s worth talking through now, while there’s still room in the calendar to build it in.
You have more leverage over the calendar in the first few weeks of the year than at any other point, while priorities are still fresh and last year’s muscle memory hasn’t fully reasserted itself.
Go make tomorrow better than today!
Keep The Plan Alive Past Kickoff
For the fuller mechanism, see New Financial Year Kickoff: Turning the Plan Into Focus and Momentum.
If you want a second set of eyes on where your FY plan is most likely to erode, book a conversation with me.
About the author: AJ Kulatunga is a Melbourne-based keynote speaker and business strategist, and a former technologist, who works with senior leadership teams on Execution Intelligence™, the discipline of turning strategy into action. He helps executive teams close the gap between what they plan and what actually happens across the year.
FAQs
What is the planning to action gap?
It’s the distance between the priorities a leadership team agrees to and the resourcing, time, budget and attention that actually moves to match them once the year gets busy. Bain’s research puts the average shift at around 2% of budget, which is why so many good plans quietly stall.
Why do good strategies fail to execute?
Usually not because the strategy was wrong. It’s because the plan was never given a calendar slot, a named owner and a reporting rhythm of its own, so it loses the competition for time against business-as-usual, which already has all three.
How do you know if your FY plan is losing momentum?
Watch the calendar before you watch the numbers. The earliest tell is meetings meant to carry the plan getting shortened or merged “just this once.” Once that happens twice, the plan is already slipping.
What’s the difference between a discipline problem and a design problem?
A discipline problem assumes people didn’t try hard enough. A design problem, the more common one, means the plan was never built a place to live, no calendar slot, no named owner, no reporting cadence, so it was competing against business-as-usual with none of its infrastructure.
How much of a strategic plan usually gets implemented?
McKinsey has found only about 52% of executives say their time actually matches their stated strategic priorities. Most plans get partial, not full, implementation, and the shortfall is rarely visible until the mid-year review.
What should change in the calendar once a plan is agreed?
Each surviving priority needs a specific slot in a meeting that already exists, a single named owner, and a reporting cadence measured in weeks, not quarters. That’s the Calendar Test, and it should be run before kickoff, not after.
How can a new financial year kickoff prevent the planning to action gap?
By building the calendar slot, the owner and the reporting rhythm into the kickoff itself, rather than leaving them for a follow-up email. A kickoff that only announces the plan produces applause. One that also answers the Calendar Test produces a plan that’s still alive in October.
