Chapter 7: Build the Deck Before You Build the Slides

Video: Slide Deck Tips That Make Your Case Presentation Professional and Persuasive

A common case-team workflow looks like this:

Someone opens PowerPoint.
Another person asks for the template.
Someone else starts building the financial slide.
A teammate creates a SWOT.
Another begins formatting the implementation timeline.
Twenty minutes later, the team has several slides but no clear presentation.

The problem is not PowerPoint. The problem is that the team started designing before deciding what it needed to say. Before opening PowerPoint, build a storyboard.

What Is a Storyboard?

A storyboard is the presentation stripped down to its essential messages. Write the main takeaway from every proposed slide in one sentence. For example:

The company is losing profitable customers.
A deteriorating customer experience is driving the decline.
High-value customers are disproportionately affected.
Three credible strategic responses exist.
Retention is the strongest option based on our decision criteria.
The strategy can generate $X in incremental profit.
We will implement the recommendation in three phases.
Customer adoption is the largest implementation risk.
A phased pilot reduces that risk before full rollout.
The strategy restores profitable growth.

Read those sentences in order. They should tell the story of the presentation without any charts, icons, colours, or formatting. If they do, you have the beginnings of a deck. If they do not, PowerPoint will not fix the problem.

Storyboard Before Slides

The storyboard forces the team to answer several important questions early:

What is the argument?
What does the audience need to learn first?
What insight creates the need for the next slide?
Which evidence matters?
Where does the recommendation appear?
How much time should each part receive?
What can we remove?

It also allows the team to change the story quickly. Moving a sentence on a page takes seconds. Rebuilding six finished PowerPoint slides can take much longer. The cheapest time to change the deck is before the deck exists.

Build in Messages, Not Topics

Teams often storyboard using topic labels:

Situation Analysis
Customer Analysis
Competitor Analysis
Alternatives
Recommendation
Financials
Implementation

That is better than nothing, but it still does not reveal the argument. These are topics. Instead, write what the audience should learn.

Topic: Customer Analysis
Message: High-value customers are leaving because the current experience no longer meets their expectations.

The topic tells the team what the slide contains. The message tells the audience what the slide means. That distinction is critical.

The Slide Message Test

Every slide should have a message. Ask if the judges remember only one sentence from this slide, what should it be? That sentence should often become the slide title.

Instead of Customer Analysis, use: High-Value Customers Are Leaving Faster Than Any Other Segment
Instead of Financial Analysis, use: The Strategy Generates Positive Value Even Under Our Downside Scenario
Instead of Implementation, use: A Three-Phase Rollout Limits Risk Before National Expansion

These titles do more than label the slide. They advance the argument.

Action Titles and Message Titles

You may hear these referred to as:

action titles;
message titles;
takeaway titles;
insight headlines.

The terminology matters less than the principle. A strong title should tell the audience, "What am I supposed to learn from this slide?" This allows judges to follow the presentation even if they miss some details. It also creates another useful test. Remove everything from your slides except the titles. Read them in sequence. Do they tell the story? If not, the deck may need restructuring.

The Headline Story Test

Imagine the titles of your presentation are:

Customer retention is the primary driver of declining profitability.
High-value customers account for most of the lost economic value.
The current experience no longer meets their expectations.
A targeted retention strategy creates greater value than additional acquisition.
A loyalty program provides the best combination of impact and feasibility.
The strategy generates $X in incremental profit.
A six-month pilot allows us to validate the economics before scaling.
This approach restores profitable growth with manageable risk.

That is almost a presentation by itself. The body of each slide now has a clear job: Prove the Headline.

Build Backwards From the Recommendation

Another useful technique is to storyboard backwards. Start with:

For example:

Recommendation: Launch a targeted retention strategy.
The Judge Must Believe: Retention is the real problem.
Therefore, We Need to Show: Retention decline is concentrated among valuable customers.
Explain: Why customers are leaving.
Then Demonstrate: Why retention creates more value than acquisition.

The analytical slides are now being chosen because they support the recommendation, not because the team completed them.

Identify the Role of Every Slide

Before building the deck, assign a role to each proposed slide. Possible roles include:

establish context;
create urgency;
identify the problem;
reveal an insight;
compare alternatives;
justify the decision;
quantify financial impact;
explain Implementation;
address risk;
reinforce the conclusion.

Ask what job is the slide doing? If two slides perform the same job, you may not need both. If a slide has no clear job, reconsider whether it belongs.

Storyboard With Time in Mind

The storyboard is also where you begin allocating presentation time. Suppose you have ten minutes. If your storyboard contains:

five minutes of situation analysis;
thirty seconds for the recommendation;
thirty seconds for financials;
thirty seconds for Implementation;

the problem is visible before you build a single slide. Your time should reflect strategic importance. The central decision, supporting evidence, financial impact, and Implementation generally deserve more attention than background the judges already know.

Don't Build the Deck in Team Silos

Another common problem occurs when teams divide slide-building too early. For example:

Person 1 builds analysis.
Person 2 builds alternatives.
Person 3 builds financials.
Person 4 builds Implementation.

Each person creates good individual slides. But the finished deck feels like four separate presentations. Build the storyboard as a team first. Agree on:

the central message;
the sequence;
terminology;
recommendation wording;
major numbers;
slide purposes.

Then divide the production work. This dramatically improves consistency.

Discover Your MAD Skills Principle

Build the logic before you build the slides.

A storyboard gives you the freedom to adjust the argument while changes are still easy to make. PowerPoint should translate the story, not discover it.

The Bottom Line

Before opening PowerPoint:

Write the message of every slide.
Put those messages in sequence.
Read them as a story.
Remove anything that does not advance the argument.
Make sure the recommendation is supported by everything that comes before it.

Then build the deck. If the storyboard works, the slides have a chance to work.