Consider this scenario: A CFO spent two weeks on slides for the monthly budget review. He created thirty-four charts, each one polished in Excel, every number verified three times. He presents to the board, but at the end of his presentation, the CEO looks at him and says: "I understand the numbers are accurate. I just don't know what I'm supposed to do with them."
This is the most common problem in finance team presentations. The data is correct, there's a lot of it, but little of it leads anywhere – for the audience, it's simply a jumble of meaningless figures. Financial presentations in many companies still look like Excel tables spread across slides, while the board doesn't need spreadsheets of data. The board needs conclusions that lead to decisions.
This article offers five recommendations that will help you build real presentation skills in your finance team in 90 days.
A Presentation Is Not a Report
Most finance teams treat a presentation like an extended report. A financial statement has its own structure: assets, liabilities, P&L, cash flow. Slides follow the same track, because that's how financial data is organized and how the analyst who prepared them thinks.
This is how you build a document meant to be read. It's not how you build a meeting meant to end in a decision.
A presentation exists to improve how the company operates. Information is only the raw material. Meaning comes from the conclusions drawn from the data, the recommendations that follow from those conclusions, and the decisions those recommendations trigger in the board. If a presentation ends with just the numbers, the board has to walk the path from data to decision on its own – which means it will either do it badly or postpone the decision to the next meeting.
The finance team holds a unique position in this conversation. It sees numbers no one else in the company sees. It also sees relationships between those numbers that operations, sales, and product can't see. This is the moment when the finance team can become either the board's most valuable advisor or the most poorly understood department in the company. Five recommendations make the difference.
Why Classic Presentation Training Doesn't Help Finance Teams
Most trainers typically assume the problem lies in how the message is delivered. Speak clearly, use confident gestures, command the room. All of that makes sense, but that's not where finance teams lose the board's attention.
They lose it because their slides are designed to be read, not to be viewed. A chart with twelve data series, a table with thirty rows, a three-paragraph description below it – that's a detailed document, not a slide. The board looks at it for fifteen seconds and already knows that they'll either start reading or stop listening. Most choose the latter.
There's also a deeper problem. Financial analysts are trained in precision. Every number must be true, every one must have a source, every one must be accurate to four decimal places. The same precision that is the foundation of their profession gets in the way of a presentation, because of it, finance people want to show everything. They feel it's more honest to show everything – so the audience has the full picture. Then the slide count grows to forty, and preparation takes two weeks instead of two days.
In finance teams, a completely different way of working on a presentation is effective. Instead of training delivery technique, we should change the role of the presentation in the analyst's mind. From a document that describes the state of affairs, to a tool that leads the board to a decision.
Five Recommendations That Actually Work
Here are five recommendations that change the way a financial presentation is structured. Each one addresses one of the most common situations in which finance teams present outside their department: monthly budget review, quarterly earnings prep, capital investment pitch, and a profitability audit from the board's perspective.
None of them requires new analytical skills. Each grows out of what the finance team already does well, and shows how to translate it into a situation where the audience more easily makes decisions instead of analyzing spreadsheets.
Recommendation 1: Conclusion First, Analysis Second
In a financial statement, the conclusion appears at the end, because it follows from the numbers. In a presentation, it's the opposite – the conclusion opens the presentation, and the numbers serve to justify it.
The reason is practical. The board doesn't walk into a meeting with an empty head. Every board member carries three or four big questions in their head and needs to know within the first or second minute whether this presentation answers any of them. If the conclusion appears on slide twenty, the board has already decided twenty minutes earlier that it probably won't hear anything important, and starts checking their phone.
In practice, a monthly budget review opens like this: "This month we are 4 percent above budget on operating costs. We recommend two adjustments that will bring us back to the growth trend. In a moment I'll show you the data on which we base this." Everything that follows serves this opening. First the general, then the specific.
Analysts sometimes resist this approach because it looks like they're skipping over all the work they did. Meanwhile, the work is still there, on slides three through ten. The only thing that changes is that from the first sentence, the board knows where the meeting is headed. Decisions are made faster, and the questions that come up are smarter, because they come based on the context the presenter has laid out.
Recommendation 2: A Number Must Have Meaning, Not Just a Value
Numbers alone don't make decisions. Decisions are made because of the meaning behind the number. "EBITDA fell by 8 percent" is data. "EBITDA fell by 8 percent because the two largest contracts shifted by a quarter, and in Q1 it returns to the trend" is an insight on which a recommendation can be built. The first sentence forces the board to look for the conclusion on its own. The second sentence delivers the conclusion together with the number.
This is the hardest change for finance teams, because the habit of presenting data neutrally is strong. The analyst feels that adding interpretation goes beyond their role – that it's already the CFO's or the board's job. This is a misunderstanding. The finance team's job doesn't end with showing the number. It ends with showing what that number means for the business, where it came from, and where it's heading.
In practice, every key number in a presentation should have three elements: value, cause, and direction. The value says what happened. The cause says why. The direction says what to expect next. Without these three elements, the board gets a fragment on which no reasonable decision can be based.
Teams that start presenting this way notice the change after a few weeks. The board stops asking "what does this mean?" and starts asking "what do you recommend?" The conversation moves one level up.
Recommendation 3: Three Charts Instead of Thirty
Finance teams fall into the trap of "since I have the data, I'll show the data." Every chart is polished, every one has a point, every one says something true about the business. Together they say so much that they say nothing.
The board has limited working memory capacity for a single meeting. Over the course of sixty minutes, it will carefully process three, maybe four key threads. Anything beyond that flows through the head without leaving a trace. Thirty charts don't make the board understand the company better. They make it understand the company worse, because it loses the essence in the noise.
So before every presentation, it's worth asking yourself one question: which three charts must the board remember in order to make the decision I expect from them? Those three go into the main presentation. The rest goes into the appendix – well-prepared, available to anyone who wants to go deeper, but not shown during the presentation. Only when someone asks for detail.
Hans Rosling, the statistician who changed the way the world looks at demographic data, said it plainly: don't use more data to explain something, use less data, better arranged. In financial presentations, the same applies. Three well-chosen charts, each answering a specific business question, do more than thirty charts showing everything that could be counted.
Recommendation 4: Variants
One of the most powerful presentation techniques is showing variants. The board doesn't make "yes or no" decisions. It makes "which of these options" decisions. If a presentation shows only one recommendation, the board has to imagine the alternatives on its own to assess whether the recommendation is good. Most boards then postpone the decision to find time for their own analysis.
Variants mean showing three scenarios side by side, on a single slide. Base scenario A: what happens if we do nothing. Scenario B: the recommended option. Scenario C: the alternative we considered.
Each scenario with three numbers: cost, time, risk. Each with one line of commentary explaining why it leads to one outcome and not another.
The base scenario is the most important, though most often omitted. Finance teams rarely show what happens if the board does nothing, because it seems obvious. It is not obvious. "Do nothing: -12 million EBITDA by Q4. Variant B: -3 million. Variant C: +5 million" – on a slide like this, the decision becomes simple. Without the base scenario, you compare B with C, but you don't know what doing nothing costs.
Showing variants has one more effect that finance teams only appreciate after a few uses. It builds credibility. The board sees that you didn't come with a ready answer you're trying to push through. You came with an analysis of three paths, you recommend one, but you show the others and explain why you set them aside. The homework was done – and the audience notices. This builds a reputation as a person who is thorough, insightful, and analytical.
Recommendation 5: Two Levels of Language – for a Twelve-Year-Old and for an Expert
Every key thought in a financial presentation should resonate on two levels at once. At the general level, even a twelve-year-old should understand. At the detailed level, an expert should understand. Both layers are needed, because each does something different.
The general level helps everyone understand. The board is made up of people who don't spend their days in Excel. The CEO has their head full of strategy, the COO of operations, the head of sales of the pipeline. When the finance team starts talking about working capital efficiency or EBITDA margin contribution by segment, half the room loses the thread in the first minute. The sentence "customers are paying more slowly, so we're financing them with credit" is short, and everyone in the room knows what it means.
The detailed level helps build credibility. If the whole presentation were at the twelve-year-old level, the board would start wondering whether the team understands the topic deeply or only superficially. Individual technical terms, used at the right moment, demonstrate competence. "Working capital grew by 18 million compared to the previous quarter, mainly because DSO extended from 45 to 58 days" is a sentence for an expert. The next sentence returns to the general level: "This means customers are paying us more slowly, so we're holding more cash in invoices than in the bank."
What Changes When a Finance Team Implements This
The first change appears in the board's decisions. Meetings end with a decision instead of a request for additional analysis. The question "can you send this in an extended version?" comes up less and less. The board stops feeling that it needs more data, because it immediately gets the data it actually needs.
The second change concerns the role of the finance team in the company. From a department that reports, it becomes a department that advises. The difference is not cosmetic. A team perceived as a strategic advisor gets earlier access to business decisions, larger budgets, and better talent.
The third change is internal and usually surprises finance managers. Analysts start to understand the business better, because working on a conclusion and a recommendation forces thinking in a broader business context, not just in analytical, domain terms. A team that works in this model for a year starts thinking in terms of the company, not in terms of its own area. For a finance manager, this is a long-term improvement in the quality of the team that reaches far beyond presentations.
Where to Start
The transformation of a finance department is worth starting with Data Storytelling training, which takes these five recommendations and embeds them in your company's specific context. Our trainings grow precisely from this model. We work on real cases from your team, in a typically business-oriented format, not in the style of a TED Talk. No acting, no theatrical tricks, no artificial energy. Simply, clearly, in a way tailored to the conference room and the decision-making situations in which the finance team actually operates.
After one day of training, the effects are visible immediately. Presentations become shorter. Narratives more accessible. Slides easier to read at a glance. The board stops asking for additional analyses, because it receives conclusions together with the numbers.
Schedule a 30-minute consultation with us – we'll talk about the situations in which your team most often presents, and we'll show you what Data Storytelling training looks like in a version tailored to your company.
Piotr Garlej
