September 21, 2026 • 5 Min Read

But by the time the conversation has narrowed to numbers, some of the most important planning work should already have happened. 

Leadership teams need to have a shared view of what they believe is changing in the business, where the company needs to place its bets and what it is willing to stop doing to fund them. Without that groundwork, annual planning can quickly become an exercise in reconciling competing functional wish lists rather than deciding how the enterprise should deploy its resources. 

That distinction matters even more now. Growth expectations, technology costs, AI investments, workforce requirements and economic assumptions are all moving at different speeds. Gartner reports that scenario planning and agile budgeting have become top priorities for CFOs as they try to manage that volatility. 

The question for leadership heading into planning season, then, isn’t simply What should next year’s budget be? It is What do we need to resolve before we can build a budget we actually believe in? 

Start With Assumptions, Not Numbers

Every annual plan rests on assumptions. The trouble is that many of them never get discussed explicitly.

What are we assuming about customer demand? Pricing? Hiring? Interest rates? Technology spending? Productivity? The pace of AI adoption? Which transformation programs will begin delivering benefits next year, and which will continue consuming resources before they produce a return?

Leadership should put those assumptions on the table before individual functions start building budgets around their own versions of the future.

That conversation can expose disagreements early. Sales may be planning for aggressive growth while Operations is budgeting conservatively. Finance may be counting on productivity gains from automation that business leaders don’t believe will materialize yet. Technology may be expecting significant new AI investment while other functions have already incorporated that same money into their own priorities.

Those aren’t budgeting problems. They’re leadership problems that budgeting happens to uncover.

Make Choices Before Allocating the Money

One of the easiest ways for an annual plan to become overloaded is to allow every existing initiative to roll forward while adding a new layer of priorities on top.

Leadership teams should challenge that instinct.

Before asking what needs funding, ask what has changed enough that the organization should reconsider where resources are going. Which programs are still strategically important? Which investments are producing results? Which initiatives made sense two years ago but no longer deserve the same priority? And where is the company underinvesting because resources remain tied up elsewhere?

This is where strategy and budgeting need to meet. Harvard Business Review has pointed to the persistent disconnect between strategic plans and budgets: companies may articulate one set of priorities while allocating resources according to another.

A strong annual planning process forces those two views together.

If leadership says AI, customer growth or a major transformation is strategically important, the budget should show what the company is willing to move, reduce or stop in order to support it. A priority that receives no meaningful resources isn’t really a priority.

Look Across the Enterprise, Not Just Down the Functions

Annual planning also gives leaders an opportunity to see something that functional budgets can obscure: where one team’s plan depends on another team’s ability to deliver.

A new growth initiative may require technology capacity that hasn’t been budgeted. An AI program may depend on data remediation happening somewhere else in the organization. A transformation may assume employees can absorb significant process change at the same time another function is reducing headcount.

Individually, each plan may look reasonable. Together, they may be impossible.

Before the budget is finalized, leadership should look across the major initiatives planned for the year and ask where they intersect. Where are the same people, data, technology or capital being counted on more than once? Where does one program need another to succeed first? And where is the organization trying to absorb more change than it realistically can?

This is becoming particularly important as AI investments expand. Gartner’s 2026 budget research found that CFOs continued to prioritize technology and AI spending even as growth in headcount and compensation slowed. That creates a different planning challenge: leaders have to think not only about what technology costs, but about where it will change work, create new capability requirements or alter the economics of existing processes.

Those connections need to be visible in the plan.

Build a Plan That Can Change

Perhaps the most important shift is to stop treating the approved annual budget as a prediction of exactly what the next twelve months will look like. It won’t be.

Leadership teams should determine in advance what they will watch and what would cause them to change course. If revenue comes in below plan, what gets reconsidered first? If a new investment begins producing results faster than expected, is there room to accelerate it? If an important assumption proves wrong, who has the authority to reallocate resources?

This is where scenario planning becomes useful as a way of preparing leadership to act before conditions change. Gartner’s work on budget planning increasingly emphasizes multiple economic scenarios, leading indicators and predefined actions rather than a single forecast treated as certain.

The best annual plans create that kind of flexibility.

A budget should provide discipline. It should not lock an organization into decisions made months earlier when the facts have changed.

Planning Before Planning

There will always be spreadsheets, forecasts and difficult conversations about money. But those are the mechanics of annual planning, not the heart of it.

The more valuable work happens earlier, when leadership agrees on what it believes, what it wants to accomplish, where it is willing to make tradeoffs and what could cause those decisions to change. Get those conversations right, and the budget becomes an expression of the strategy.

Skip them, and annual planning can become something very different: twelve months of organizational ambition squeezed into a spreadsheet, without ever resolving whether the pieces actually fit together.