The Budget Was Approved Long Before the Meeting

One of the more curious things I’ve noticed over the years is that budgets are often approved long before anyone walks into the conference room.

That sounds ridiculous, of course. The meeting is on everyone’s calendar. The deck is polished. The assumptions have been circulated. People ask questions. Slides get skipped. Someone inevitably says, “Let’s come back to that.” It all looks like a decision is being made.

But I’ve sat through enough planning cycles to suspect something else is happening.

Most budget meetings aren’t really about deciding.

They’re about confirming.

The real decisions have usually happened in dozens of smaller conversations that nobody remembers individually. A hallway discussion after a leadership meeting. A quick call between the CFO and the head of Sales. An offhand comment that begins with, “We’re probably going to have to assume…” None of those moments feel important at the time. Collectively, they’re the budget.

By the time the numbers appear in a spreadsheet, they’ve already accumulated a surprising amount of momentum.

That’s what makes them difficult to challenge.

People like to imagine budgets are built cell by cell. In my experience, they’re built conversation by conversation. The spreadsheet simply records where those conversations eventually landed.

Looking back, some of the healthiest planning processes I’ve been part of had very little drama in the budget meeting itself. The difficult conversations happened early, while assumptions were still flexible and before anyone had become emotionally invested in a particular outcome.

The unhealthy ones followed the opposite pattern. Nobody wanted to make anyone uncomfortable during planning, so uncomfortable questions were postponed until variance reviews six months later. By then, the assumptions weren’t assumptions anymore. They had become commitments.

That’s an expensive time to discover the conversation never really happened.

Over time I’ve found myself paying less attention to how polished the budget presentation is and more attention to how the assumptions arrived there in the first place.

Whenever I review a planning model, there are a handful of questions that matter far more to me than the formatting:

• Which assumption generated the longest discussion?
• Which assumption generated almost no discussion at all?
• Who was willing to challenge the prevailing view?
• What changed because of that challenge?

Those answers usually tell me more about the quality of the budget than another round of formatting, reconciliations, or sensitivity tables ever will.

I’ve come to believe that good FP&A isn’t simply about producing a better budget. It’s about creating an environment where people feel comfortable changing their minds before the numbers become official. That sounds like a small distinction, but I don’t think it is. Once a number appears on a slide, it begins collecting a kind of authority that has very little to do with whether it’s right.

Maybe that’s why the best finance leaders I’ve worked with never seemed particularly attached to the budget they were presenting. They were attached to the process that produced it. They understood that a budget isn’t a prediction. It’s the best story an organization can tell itself with the information it has today.

Stories should improve as new evidence arrives.

Budgets should too.

The first draft is already carrying politics

People sometimes talk about the first budget draft as though it is a neutral starting point.

I have rarely found it neutral.

The first draft contains targets, expectations, prior conversations and somebody’s view of what is reasonable.

If Sales receives a revenue target before discussing capacity, that number has already framed the conversation. If every department receives a cost ceiling, the debate starts inside that box.

This is not necessarily wrong.

Leadership is allowed to have a point of view.

I just prefer making the point of view visible instead of pretending the spreadsheet emerged naturally from the mist.

Anchors become powerful very quickly

Put 12% growth on the first slide and watch what happens.

Now 10% feels conservative. Fourteen feels ambitious. Everyone begins discussing the world relative to 12.

Maybe 12 was supported by a thoughtful strategy.

Maybe it was the number required to hit an investor expectation.

Maybe someone typed it into a planning deck six weeks ago and nobody remembers why.

The source matters.

I like asking what the business would believe if the first number had never been shown.

That question can expose how much of the budget is analysis and how much is anchoring.

Pre-meetings are not automatically a bad thing

I am not against conversations before the budget meeting.

Quite the opposite.

The best planning work usually happens in smaller groups where people can test assumptions without performing for a room of fifteen executives.

Sales and Finance can challenge conversion. Operations can explain capacity. HR can talk about hiring reality. The CFO can pressure-test the investment plan.

The problem is when those conversations quietly turn into decisions that the formal process pretends are still open.

Then the meeting becomes theater.

Everyone is invited to discuss a number that already has bodyguards.

I want disagreement while the numbers are still cheap to change

There is a moment in planning when changing an assumption is easy.

Then there is a moment when changing it requires rebuilding three models, rewriting a deck and explaining to leadership why the number moved.

Human beings become considerably less curious in the second phase.

That is why I want difficult questions early.

What has to be true for this revenue plan to work? Can we actually hire this quickly? Does Operations have capacity? Is the margin improvement supported by something real?

Those questions are cheaper before the workbook becomes a monument.

Silence in the meeting can mean several things

A quiet budget meeting may mean everyone agrees.

It may also mean the disagreement happened earlier.

Or people believe challenging the number is pointless.

Those are very different situations.

I pay attention to who speaks, which assumptions get challenged, and whether new information can still change the answer.

A planning process where nothing ever changes in the final review may be exceptionally disciplined.

It may also be exceptionally predetermined.

The behavior around the numbers usually tells me which one.

The CFO has more influence than the spreadsheet admits

Finance likes to present itself as the neutral facilitator of planning.

We are not completely neutral.

The questions we ask, the ranges we show, the historical periods we choose and the assumptions we challenge all shape the conversation.

A CFO saying, “I am uncomfortable with this hiring pace” can move a budget before anyone changes a cell.

That influence is part of leadership.

I just think Finance should be aware of it.

If we want honest operating input, people need to know when we are asking for a forecast and when leadership has already made a strategic choice.

Targets and forecasts should not impersonate each other

This is one of the easiest ways to create a predetermined budget.

Leadership sets a target. Then Finance asks the business for a forecast. The forecast comes back below the target.

Instead of preserving the difference, the forecast gets “challenged” until it reaches the target.

Sometimes the challenge identifies real opportunities.

Sometimes we have simply renamed the target.

I prefer showing both.

Here is what we believe under current assumptions. Here is what leadership wants to achieve. Here is the gap and the set of actions required to close it.

That is a management conversation.

Forcing the forecast to equal the aspiration removes the most useful information.

Budget ownership should include the assumptions, not just the dollars

Department leaders are often told they own their budgets.

Then Finance gives them numbers built from assumptions they did not choose.

I want ownership to be more specific.

Who owns the hiring plan? Who owns conversion? Who owns price? Who owns utilization? Which assumptions are corporate decisions and which belong to the business unit?

Once that is clear, accountability gets healthier.

We can discuss whether the assumption changed instead of accusing a manager of “missing budget” when the original number depended on something outside their control.

Scenario planning can loosen the grip of one official number

One reason budgets become politically sticky is that everyone is forced to argue about one answer.

Scenarios can make the disagreement more productive.

If Sales believes the upside is achievable and Finance sees risk, show the conditions for both. If hiring capacity is uncertain, model the consequences of slower hiring. If pricing is the key assumption, show the sensitivity.

Now the meeting does not have to decide which person is “right” about an unknowable future.

It can decide what management will do under different outcomes.

That is usually a better use of executive time.

The budget meeting should still have a job

If the real decisions happened earlier, what is the formal meeting for?

I think it should confirm strategic alignment, surface unresolved tradeoffs, test the largest assumptions and make explicit decisions where disagreement remains.

It should not be the first time the CFO sees the revenue plan.

It also should not be a ceremonial reading of numbers everyone is afraid to change.

A good final review is less dramatic because the organization did the hard thinking earlier.

But it is still capable of changing something when new evidence deserves it.

After approval, preserve the story

Once the budget is approved, I like documenting the handful of assumptions that actually explain it.

Not every cell.

The important beliefs.

Revenue growth depends on these drivers. Margin improvement depends on these actions. Hiring assumes this pace. Cash assumes these collection terms.

Six months later, variance analysis becomes much more useful because we can compare actual reality with the story management approved.

Did execution fail? Did the environment change? Was the original assumption weak?

Without that history, people have a tendency to remember the budget as more obvious than it was.

The meeting is the end of a process, not the beginning of a decision

I still think budgets are often approved before the formal approval meeting.

I no longer think that is automatically a criticism.

Good planning should involve many conversations before the final review.

The question is whether those conversations improved the assumptions or merely hardened them.

Did people have permission to challenge the number? Did new evidence change anything? Were targets kept separate from expectations? Does management understand the tradeoffs it approved?

If yes, the quiet final meeting may be evidence that the work happened where it should have.

If no, the polished deck is just documenting momentum.

I care much more about the first version.

I also watch for the assumption nobody wants to own

Every planning cycle seems to have one.

The number is important. Everyone has an opinion. Nobody quite owns it.

Maybe it is a corporate efficiency target spread across departments. Maybe it is a revenue synergy. Maybe it is a hiring reduction leadership expects but no function has translated into roles.

Those orphan assumptions make budgets look complete while leaving execution unresolved.

I like assigning an owner before approval.

Not someone to blame later.

Someone responsible for explaining what actions make the assumption real and what evidence will tell us whether it is working.

Planning quality shows up months later

The real test of a budget process is not whether the meeting went smoothly.

It is what happens when actual results begin arriving.

Can management explain the variances in terms of the assumptions it debated? Does the forecast update naturally as those assumptions change? Do business leaders remember what they committed to and why?

When the answer is yes, the budget becomes useful context rather than an annual artifact.

When the answer is no, Finance spends the year reverse-engineering a number everyone once approved.

That is a long way to discover the meeting was mostly theater.

That is why I would rather have a slightly uncomfortable planning conversation in October than a beautifully explained variance in June. One can still change the outcome. The other is history with better formatting.