Let me paint a picture that will be familiar to anyone who has worked in or alongside a finance function.
It is the end of the month. The finance team is heads down, working late, pulling data from multiple systems, reconciling numbers, chasing approvals, formatting slides. The close process consumes days. By the time the management report lands in the inbox of the leadership team, it is already several days old. The business has moved on. Decisions have already been made, or delayed waiting for the numbers to arrive.
The leadership team flicks through the deck, notes a few variances, asks a handful of questions that the finance team will spend the next week answering, and the cycle begins again.
This is not a broken finance team. This is how most finance functions operate. And it represents a fundamental misunderstanding of what Financial Planning and Analysis is actually for.
The confusion between reporting and analysis.
The most common mistake I see in finance functions is treating reporting and analysis as the same thing. They are not.
Reporting is the production of information. Analysis is the interpretation of that information in a way that leads to better decisions. Reporting tells you what happened. Analysis tells you why it happened, what it means, and what should happen next.
Most finance teams spend the majority of their time on reporting. They are consumed by the mechanics of closing the books, producing the pack, distributing the slides. By the time the report is out the door, there is little time or energy left for the analysis that would actually change how the business operates.
This is not a people problem. Finance teams are typically hardworking, capable, and well-intentioned. It is a design problem. The function has been structured around production rather than insight, and the incentives, timelines, and tools all reinforce that structure.
The seat at the table problem.
There is a lot of talk in finance circles about earning a seat at the table, about finance being a true business partner rather than a back-office function. I believe in this aspiration deeply. I have spent my career trying to embody it.
But here is the uncomfortable truth: many finance functions have not earned that seat because they have not demonstrated that they can do anything more than report what already happened.
A leadership team will include finance in strategic conversations when finance consistently adds something that the business could not figure out on its own. When finance identifies a risk before it becomes a problem. When finance surfaces an opportunity that was hidden in the data. When finance helps the business understand not just where it is, but where it is going and what choices it faces.
A finance function that shows up with last month’s actuals and a variance commentary is providing a service. A finance function that shows up with a clear point of view on the next ninety days and a set of recommendations is providing leadership.
The difference between those two things is not talent. It is priorities, tools, and the courage to move beyond the comfort of the numbers into the discomfort of judgment and recommendation.
The forecast trap.
Another thing most companies get wrong is how they use forecasts.
In many organizations, the forecast has become a performance management tool rather than a planning tool. Teams are held accountable to their forecast numbers in a way that creates the wrong incentives. If you know you will be judged against your forecast, you will forecast conservatively. You will build in buffers. You will shade your numbers toward achievability rather than accuracy.
The result is a forecast that does not actually reflect the team’s best view of what will happen. It reflects what they are comfortable being held to. Which means the leadership team is making decisions based on a number that has been deliberately softened.
A good forecast is an honest forecast. It reflects the best available information and the team’s genuine assessment of where the business is headed. It should make leadership slightly uncomfortable because it should surface real risks and real uncertainties rather than smoothing them away.
Building a culture of forecast honesty is harder than it sounds. It requires leadership to respond to bad news with curiosity rather than blame. It requires finance to have the confidence to deliver an uncomfortable number and defend it. And it requires both sides to agree that the purpose of a forecast is to help the business prepare, not to set a target for finance to hide behind.
The planning cycle problem.
Most companies plan annually. They spend weeks or months building a detailed budget for the year ahead, present it to the board, and then spend the rest of the year explaining why actuals differ from a plan that was built on assumptions that were already outdated by the time it was approved.
The world moves faster than an annual planning cycle can accommodate. Markets shift. Competitors move. Costs change. Customer behavior evolves. A finance function that is still anchored to a budget built six months ago is not helping the business navigate reality. It is helping the business explain the past.
The most effective finance functions I have seen operate on a rolling planning model. They maintain a continuously updated view of the next twelve months, refreshed regularly as new information becomes available. They distinguish between the budget as a financial commitment and the forecast as the team’s best current view of where they are headed. And they build scenario thinking into the routine rather than treating it as an emergency exercise when something goes wrong.
This requires more discipline and more investment in planning processes and tools. But it fundamentally changes the value that finance delivers to the business.
What great Financial Planning and Analysis actually looks like.
I want to be clear that I am not describing a utopian vision that exists nowhere. I have seen finance functions that genuinely operate as strategic partners. That close fast, report efficiently, and spend the majority of their energy on forward-looking analysis and decision support. That have earned genuine respect and influence within their organizations because they consistently help the business make better calls.
What they have in common is not a particular technology or a particular organization structure. What they have in common is clarity about their purpose.
They exist to help the business make better decisions. Everything else, the close process, the reporting, the forecasting, the planning cycles, is in service of that purpose. When a process or a report or a meeting does not serve that purpose, they question it, simplify it, or eliminate it.
That clarity sounds simple. But in practice, in the middle of a monthly close with deadlines everywhere and stakeholders asking for more and more information, holding onto that clarity takes discipline and leadership.
It is, I would argue, the most important thing a head of Financial Planning and Analysis can do. Not build the best model. Not produce the cleanest report. But relentlessly focus the team on the question that actually matters.
What does the business need to know, right now, to make a better decision?
Everything else is a means to that end.
