Chapter 1: You Are Not Building Slides. You Are Building an Argument

One of the biggest mistakes case teams make is starting their presentation by opening PowerPoint. The case analysis finishes, someone creates a blank deck, and the team begins asking:

What should go on Slide 1?
Who is building the financial slide?
Who has the SWOT?
Where should we put the implementation?
How many slides do we need?

The team has started building slides before deciding what those slides need to accomplish. That reverses the process. A strong presentation starts with the message, not the slides. Before deciding what to include in PowerPoint, your team should know the argument it wants to make. At its simplest, that argument needs to answer four questions:

What is happening? What is the situation facing the organisation? This establishes context and demonstrates that your team understands the case.
Why does it matter? What is the real problem, opportunity, tension, or strategic implication? This moves beyond describing what is happening toward explaining its significance.
What should the organisation do? What decision are you recommending? The audience should never have to guess what you want the organisation to do.
Why should the judges believe you? What analysis, evidence, financial reasoning, implementation logic, and risk assessment demonstrate that your recommendation is credible?

This is where analysis becomes persuasion. Together, these questions create the backbone of the presentation: What → So What → Now What → Why Believe Us? Everything in the presentation should contribute to answering one of those questions.

The Presentation Equation

A strong case presentation combines five elements: Strategy + Story + Evidence + Visual Communication + Delivery = Persuasion. Each performs a different role.

Element	The Question It Answers
Strategy	Are we recommending the right thing?
Story	Can the judges follow our thinking?
Evidence	Why should they believe us?
Visual Communication	Can they understand the important information quickly?
Delivery	Can we communicate the message with clarity, confidence, and credibility?

None of these elements works particularly well in isolation. A great strategy poorly communicated may lose. A beautiful deck containing weak analysis may lose. Excellent analysis buried beneath twenty crowded slides may lose. A confident speaker without evidence may sound impressive but remain unconvincing. A team with all the right pieces can still struggle if those pieces ~~do not~~don't form one coherent argument. Winning presentations bring them together.

The Presentation Is a Decision-Making Tool

This changes how you should think about the deck. The objective is not to prove how much work your team completed. The objective is not to demonstrate that you used every framework you know. The objective is certainly not to fit every interesting fact from the case onto a slide. Your presentation should help the audience make a decision. That means information earns its place because it contributes to the decision, not simply because your team spent time analysing it. Consider two teams.

Team A conducts twelve analyses and presents all twelve.
Team B conducts twelve analyses but determines that only four materially influence the recommendation. Those four become central to the presentation. Several others are available for Q&A, while the rest are removed.

Team B has not done less work. It has exercised more judgment. That distinction is fundamental to great case presentations.

Think Like the Audience

Teams naturally see the presentation from their own perspective. They remember:

the hours spent solving the case;
the debate over alternatives;
the spreadsheet that took forty minutes to fix;
the research they discovered;
the framework that generated an interesting insight.

The judges experienced none of that. They encounter your solution for the first time when you present it. That creates an important communication principle: The presentation should be designed around what the audience needs, not around the process the team used to get there.

Your analysis may have been messy.
Your presentation should not be.
Your team may have explored five possibilities before reaching the recommendation.

The judges ~~do not~~don't necessarily need to experience all five. Your job is to transform a complicated problem-solving process into a clear decision-making journey.

Discover Your MAD Skills Principle

Slides support the story. The slides are not the story.

This principle should influence almost every decision you make about the deck. The judges should be able to follow your argument by listening to your team. The slides should make that argument easier to understand by providing:

evidence;
numbers;
comparisons;
diagrams;
timelines;
visual relationships;
key messages.

The speaker and the slide therefore perform different jobs.

The slide shows.
The speaker explains.

If the slide contains a chart showing customer churn increasing from 8% to 17%, the speaker ~~does not~~doesn't need to read those numbers aloud. The speaker should explain what they mean: Customer churn has more than doubled, but the more important insight is where that churn is occurring: our highest-value customers are leaving fastest.

The visual provides evidence.
The speaker provides meaning.

Together, they create understanding.

The Competing Attention Problem

There is another reason not to overload slides. It is hard to read a complicated slide and listen to you at the same time. When you display a paragraph-heavy slide and begin speaking, you effectively ask the judges to choose: Should I listen to you or read this? That is not the competition you want. Instead, your slides and speaking should complement one another. The audience should be able to glance at the slide, understand its major message, and return its attention to you. This idea becomes especially important when we examine visual communication and slide design later in this manual.

The Argument Test

Before building the deck, try this exercise. Without PowerPoint, explain your team's entire recommendation in approximately 60 seconds. Answer:

What is happening?
Why does it matter?
What should the organisation do?
Why should we believe you?

If the team cannot explain the argument clearly without slides, adding slides probably will not solve the problem. The presentation needs clarity before it needs design.

The Bottom Line

~~Do not~~Don't begin by asking, "What slides should we build?" Begin by asking: "What argument do we need to make?" Once the argument is clear, the slides become much easier to build.