An Annual business plan rarely fails because leaders forget what they agreed.
The strategic priorities remain in the presentation. The financial targets stay in the budget. Every initiative has an owner, a proposed timetable and a reassuring place in the board pack. Yet by the end of the first quarter, progress is already uneven.
One initiative is waiting for a technology decision. Another needs people who have been committed elsewhere. A product launch depends on operational work that was never included in the original business plan. Customer assumptions are proving less reliable than expected. Several apparently separate priorities require decisions from the same two or three senior people.
The organisation describes this as an execution problem.
Often, however, the conditions for weak execution were designed into the business plan before the year began.
Agreement is not the same as commitment
A leadership team can approve a business plan without making the choices needed to deliver it.
Agreement may simply mean that nobody has raised a final objection. Each function has retained enough of its preferred activity. The financial model balances. The board deadline has been met. The difficult questions have been moved out of the planning meeting and into implementation.
The business plan feels acceptable because every leader can see something they support within it, but that is not the same as collective commitment to a small number of enterprise priorities.
A stronger test is whether leaders have agreed what will receive less attention, what will stop and which functional ambitions must give way when the wider business priority requires it.
- If sales growth is the priority, what will operations, product, technology and finance do differently to support it?
- If service quality is the priority, which commercial promises or internal initiatives will be constrained while the organisation stabilises delivery?
- If margin improvement matters most, which customer exceptions, products or established ways of working will no longer be protected?
Those are harder conversations than agreeing a set of objectives. They expose the trade-offs that a polished annual business plan can conceal.
If nothing meaningful has been deprioritised, the organisation probably has a list of ambitions rather than a plan.
Too many priorities survive the planning process
An annual business plan can very easily be weakened by addition.
Every commercial concern becomes an initiative. Every operational problem generates a workstream. Existing commitments remain in place while new strategic priorities are layered on top.
Nobody wants to remove something another leader considers important. Projects that have already consumed time or money feel difficult to stop. Business-as-usual activity is treated as fixed, while new work is presented as strategically necessary.
The result is a business plan in which:
- Ten priorities are described as the top five.
- Existing projects continue without being retested.
- New initiatives are approved without releasing people from old ones.
- Business-as-usual workload is treated as free capacity.
- Teams receive multiple critical requests from different leaders.
- Every function believes its work has leadership backing.
The business plan may be financially funded while remaining organisationally impossible.
Budgets can be divided between initiatives. The same specialist, senior leader or delivery team cannot be divided quite so easily.
A priority that does not displace anything is usually an additional demand, not a priority.
Functional plans fit individually and conflict collectively
Sales, marketing, product, operations, technology and finance may each produce a credible plan.
The conflict becomes visible only when those plans are viewed together.
Sales may plan for growth through a broader, more flexible proposition while operations intends to increase standardisation. Product may require specialist input that delivery has already committed to customer work. Marketing may schedule a launch before onboarding, service reporting or customer support is ready.
Finance may remove cost or capacity that the growth plan quietly depends upon. Technology may sequence work according to system risk while commercial teams promise customer dates based on revenue opportunity.
Each function may be planning responsibly from its own perspective.
The annual business plan loses momentum because nobody has reconciled those legitimate but competing realities into a workable enterprise sequence.
This is the same leadership problem explored in The Reality Cheque. Each functional view can be accurate and still provide an incomplete picture of what the organisation can achieve as a whole.
The useful question is not which function has produced the correct plan, but what happens when their plans meet inside the same business.
The annual business plan understates dependencies
An annual business plan usually shows initiatives, owners, dates and intended outcomes, but they are often less clear about the connections that will determine whether the work can move.
A commercial launch may depend on a technology release. The technology release may depend on product decisions. Those decisions may require customer evidence that has not yet been gathered. Delivery may need new people, contractual and process changes or training before the organisation can support what sales intends to sell.
An apparently self-contained initiative may depend on:
- A technical change being completed first.
- Reliable data becoming available.
- Recruitment in a difficult market.
- Customer or partner participation.
- Contractual or regulatory approval.
- Another department changing an established process.
- A senior decision that has not yet been made.
- The same specialist contributing to several programmes.
These dependencies are rarely dramatic enough to prevent plan approval. They emerge later as delays, exceptions, additional meetings and requests for escalation. By then, the organisation believes execution has fallen behind.
The more accurate diagnosis may be that the plan treated dependent work as though it could proceed independently.
A date beside an initiative does not remove the sequence of events required to reach it.
Capacity is expressed in money rather than attention
A budget can demonstrate that an initiative is affordable. It cannot prove that the organisation has the attention, authority or specialist knowledge required to deliver it.
Many plans repeatedly depend on:
- The founder connecting functions and resolving ambiguity.
- The managing director making every difficult trade-off.
- A small number of technical specialists.
- The same programme, project and change people.
- Senior customer relationships held by one person.
- Leaders already responsible for day-to-day performance.
- Employees expected to absorb change alongside their normal roles.
Those people may appear against only one line in the plan while carrying hidden responsibility across several initiatives.
A technology project may have a project manager and an approved budget but still require repeated product, operational and commercial decisions from the leadership team. A market launch may have funded marketing activity but depend on senior people providing source material, approving claims and resolving disagreements about the offer.
The budget exists. The less visible capacity does not.
The organisation therefore enters the year with enough money assigned but insufficient leadership attention and specialist availability to keep decisions moving.
The first visible symptom is delay. The underlying constraint is concentrated dependency on people the plan has treated as infinitely available.
Ownership is assigned without decision rights
Placing a name beside an initiative creates the appearance of accountability. Real ownership requires more. The named person must understand the outcome they are responsible for, the decisions they can make, the resources they control and the constraints within which they can act.
They also need to know:
- Which dependencies they can challenge.
- What must be escalated.
- Who resolves conflict between functions.
- What they are authorised to stop or change.
- How progress will be judged.
- What happens when the original plan no longer reflects reality.
Without those conditions, the owner becomes a coordinator. They arrange meetings, collect updates and report delays while the substantive decisions remain elsewhere. When a dependency fails or a trade-off becomes uncomfortable, the issue returns to the leadership team.
The initiative appears owned but still depends on senior intervention whenever something difficult happens.
That can create unfair judgements about execution. The named owner is criticised for a lack of momentum while lacking the authority to resolve the issues preventing it.
A useful planning question is therefore not simply: “Who owns this?”
It is: “What can this person decide without returning to this room?”
If the honest answer is very little, the plan has assigned responsibility without sufficient control.
Not everyone is able or willing to deliver the annual business plan
Planning processes often assume that agreement in the room will translate into consistent behaviour afterwards.
However, that is not always the case. Some people support the business plan but lack the capability, confidence or resources to deliver their part. Others understand what is required but remain committed to an established functional priority, customer promise or way of working. A small number may agree publicly while privately delaying decisions, withholding support or waiting for the initiative to lose momentum.
These conditions should not be treated as interchangeable.
A capability gap may require support, development or different ownership. Conflicting incentives require leadership alignment. Genuine disagreement should be surfaced and tested. Persistent obstruction may eventually require a direct performance or personnel decision.
Leaders should be cautious about labelling someone resistant or incapable before examining the system around them. A person who repeatedly escalates decisions may lack authority rather than courage. A team that protects existing work may be responding rationally to measures and incentives that have not changed. Someone who appears uncommitted may never have understood what the plan requires them to do differently.
But the opposite mistake is also costly.
When the expectations, authority and support are clear, leaders must be willing to confront the possibility that a critical person cannot or will not deliver what the plan requires.
A plan cannot maintain momentum when influential people are permitted to agree with it formally and operate against it in practice.
The assumptions beneath the annual business plan are not tested
Every annual business plan contains assumptions.
Customers will accept the new proposition. Existing accounts will renew. Sales cycles will shorten. Recruitment will succeed. Partners will participate. Technology will reduce effort. Teams will absorb change while maintaining existing service.
Planning would be impossible without making judgements about an uncertain future.
The problem arises when assumptions disappear into targets and are subsequently treated as commitments.
A revenue number may depend on several beliefs about customer demand, conversion, pricing and delivery capacity. Once those beliefs have been converted into a spreadsheet, they can acquire a level of authority the underlying evidence does not justify.
The organisation then monitors performance against the target without continuing to test the conditions on which the target depends.
Before approving the plan, leaders should distinguish between:
- What is known.
- What is reasonably evidenced.
- What is an informed judgement.
- What remains a material assumption.
- What evidence would cause the plan to change.
This does not weaken the plan. It makes the reasoning visible.
It also allows the leadership team to monitor the assumptions most capable of changing the outcome rather than waiting for a lagging financial result to reveal that something was wrong.
A credible plan should not require leaders to defend every original assumption. It should help them recognise when the evidence has moved.
The annual business plan has milestones but no operating rhythm
A completed annual business plan often contains quarterly targets, monthly reporting and initiative milestones.
That is not necessarily an operating rhythm.
Reporting tells leaders what has happened. An operating rhythm helps the organisation decide what to do next.
A useful rhythm establishes:
- When dependencies will be reviewed across functions.
- Where competing priorities will be resolved.
- How customer and market evidence enters the conversation.
- Which decisions belong at which level.
- When important assumptions will be retested.
- How leaders identify activity that should stop.
- What happens when delivery reality no longer supports the original plan.
Without this, the organisation periodically reports the plan rather than actively managing it.
Project updates may remain green because each team is completing its immediate activities. The enterprise outcome can still be drifting because the dependencies between those activities are not being examined.
The first quarterly review may become the first serious moment at which leaders reconnect the plan with operational reality.
By then, a quarter has passed.
Seven questions to ask before the year begins
Leaders do not need another elaborate planning process to test whether a plan can move.
They do need to ask questions that expose the conditions hidden beneath it.
1. What has this plan caused us to stop?
A genuine priority consumes time, money and attention that cannot be used elsewhere. If the answer is nothing, the organisation may be assuming capacity rather than creating it. The question should apply to established work as well as new proposals. An existing project should not continue merely because it started first.
2. Which priorities conflict when the functional plans are viewed together?
Do not ask each function whether its own plan works. Ask what happens when all the plans compete for the same customers, people, systems, investment and leadership decisions. This is where apparently sensible functional assumptions become enterprise constraints.
3. Which people or capabilities appear as dependencies most often?
The answer identifies likely bottlenecks before delivery begins. If the same technical expert, commercial leader, project team or senior decision-maker appears repeatedly, the plan needs to reflect that constraint. Naming more owners will not create more of the scarce capability.
4. What can each named owner actually decide?
Establish the boundary between ownership and coordination. If every material choice returns to the leadership team, the initiative has not been delegated in practice. The plan must either provide greater authority or acknowledge the decision capacity it will require from senior leaders.
5. Which customer or market assumptions could make the plan wrong?
Identify the beliefs about demand, behaviour, pricing, retention or adoption that have the greatest influence on the intended result. Then decide how and when they will be tested. Customer reality should shape the plan before missed targets provide the answer.
6. Where will cross-functional trade-offs be made during delivery?
“Through normal governance” is not a sufficient answer. The organisation needs a clear route for resolving conflicts that sit between functions, particularly when each team can reasonably defend its own position. Without that route, difficult choices remain unresolved while activity continues around them.
7. What evidence would cause us to change the plan?
A plan that cannot adapt is not disciplined. It is brittle. Leaders should agree what would justify changing the sequence, reducing the scope, redirecting investment or stopping an initiative. That makes adaptation an expected part of judgement rather than an admission that the original plan failed.
Building the bridge from intent to traction
A plan becomes useful when it creates a bridge between agreed intent and delivery traction.
Oak has historically used PACE as a practical way of thinking about that bridge. The value is not in adding another planning framework to the board pack. It is in testing whether the organisation has created the necessary conditions around the plan.
- Is the purpose sufficiently clear to guide real choices?
- Are functions, resources and incentives aligned around the same enterprise outcome?
- Is there a dependable cadence for communication, evidence and decisions?
- Can the organisation execute with the authority, capacity and dependencies it actually has?
These questions move the conversation beyond whether the annual business plan has been completed and test whether the organisation can use it.
A plan can be strategically sound and financially credible while still lacking the connections needed to turn intent into movement. PACE helps expose where that bridge is weakest, but the diagnosis must remain grounded in the particular business rather than forcing every situation through a standard process.
The objective is not to create more planning activity. It is to give the organisation a realistic route from what leadership has agreed to what people can actually deliver.
Momentum is designed before execution begins
An annual business plan does not lose momentum only after teams begin working on it.
Momentum is often weakened earlier—when priorities are added without displacement, functional plans remain unreconciled, dependencies are understated, capacity is assumed and owners lack the authority to decide.
The answer is not necessarily a more detailed planning document. Additional pages, milestones and reporting requirements can create greater apparent control without resolving the underlying constraints.
The stronger response is a more honest connection between ambition and the organisation expected to deliver it. Before approving the plan, leaders should ask whether its priorities, dependencies, capacity, assumptions, ownership and decision routes work together in reality. If they do not, the start of the year will not create momentum. It will begin the gradual process of explaining why the plan is already slipping.
Oak CORE helps leadership teams test important plans against commercial, customer and operational reality before weak assumptions become delivery problems.
If the plan looks credible on paper but the leadership team is not confident it will move in practice, arrange a CORE Fit Conversation.