Skip to main content

Part IV

PART IV: Deck Architecture

Once the story is clear, you can begin designing the deck. But not by opening PowerPoint. The first step is to translate the case story into a sequence of messages the audience can follow. Only then should you decide how those messages will appear visually. This part focuses on two disciplines:

  1. Build the deck before you build the slides.

  2. Give each slide one primary message.

The goal is to create a deck that feelsreads likeas onea single, connected argument rather than a collection of individual analyses. Story first. Slides second.

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:

  1. The company is losing profitable customers.

  2. The decline is being driven by aA deteriorating customer experience.experience is driving the decline.

  3. High-value customers are disproportionately affected.

  4. Three credible strategic responses exist.

  5. Retention is the strongest option based on our decision criteria.

  6. The strategy can generate $X in incremental profit.

  7. We will implement the recommendation in three phases.

  8. Customer adoption is the largest implementation risk.

  9. A phased pilot reduces that risk before full rollout.

  10. 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:

  1. Situation Analysis

  2. Customer Analysis

  3. Competitor Analysis

  4. Alternatives

  5. Recommendation

  6. Financials

  7. 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:audience, "What am I supposed to learn from this slide?" This allows the judges to follow the presentation even if they miss some of the detail.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:

  1. Customer retention is the primary driver of declining profitability.

  2. High-value customers account for most of the lost economic value.

  3. The current experience no longer meets their expectations.

  4. A targeted retention strategy creates greater value than additional acquisition.

  5. A loyalty program provides the best combination of impact and feasibility.

  6. The strategy generates $X in incremental profit.

  7. A six-month pilot allows us to validate the economics before scaling.

  8. 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:

  • What do we recommend?
  • Then ask: What must the judges believe for that recommendation to make sense?
  • Then: What evidence proves those beliefs?

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.
  • And Explain
    • Why customers are leaving.
  • Then Demonstrate
    • Why retention creates more value than acquisition.

Now the analytical slides are being chosen because they support the recommendation. Not because the team completed them.

Identify the Role of Every Slide

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

  • establish context;

  • create urgency;

  • identify the problem;

  • reveal an insight;

  • compare alternatives;

  • justify the decision;

  • quantify financial impact;

  • explain implementation;Implementation;

  • address risk;

  • reinforce the conclusion.

Ask: What job is this 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;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 implementationImplementation 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.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 changeadjust the argument while changes are still easy.easy to make. PowerPoint should translate the story—not discover it.

The Bottom Line

Before opening PowerPoint:

  1. Write the message of every slide.

  2. Put those messages in sequence.

  3. Read them as a story.

  4. Remove anything that does not advance the argument.

  5. 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.

Chapter 8: One Slide. One Message.

Once you know what each slide needs to communicate, the next challenge is making that message obvious. A common mistake is trying to make one slide communicate five things. The team adds:

  • a chart;

  • a table;

  • three callout boxes;

  • a competitor comparison;

  • six bullets;

  • two icons;

  • a financial number;

  • and a conclusion.

Technically, everything fits. Communicatively, nothing does. The audience does not know where to look. The solution is simple: One slide. One primary message.

One Message Does Not Mean One Fact

This distinction matters. A slide can contain several pieces of information. It simply needs one central idea. For example:

Primary Message

Customer churn is concentrated among our highest-value customers. That slide might contain:

  • churn rates by segment;

  • customer lifetime value;

  • a comparison with the prior year;

  • a highlighted high-value segment.

Several facts. One message. Every element supports the same conclusion.

The Slide Hierarchy

A useful structure is:

  • MESSAGE: What should the audience understand?
  • EVIDENCE: What proves it?
  • IMPLICATION: Why does it matter?

This creates a simple communication hierarchy.

Example

Message

Customer churn is concentrated among our most valuable customers.

Evidence

A chart showing:

  • churn by segment;

  • revenue contribution by segment;

  • year-over-year change.

Implication

Retaining high-value customers offers greater economic value than broad-based acquisition.

Now the slide is doing analytical work. It tells the audience:

WHAT WE FOUND → WHY WE BELIEVE IT → WHY IT MATTERS

The Message Comes First

When designing the slide, start with the headline. Then ask: What is the simplest evidence that proves this? Do not begin with: "We have this chart. How do we fit it onto the slide?" That reverses the process again. Start with the message. Then select the evidence.

Evidence Should Earn Its Place

Every chart, number, label, icon, or annotation should contribute to the message. For example, suppose the message is: The recommended market is significantly more attractive than the alternatives. Useful evidence might include:

  • market growth;

  • margin potential;

  • customer fit;

  • competitive intensity.

But if a demographic statistic does not help explain why the market is attractive, it may not belong. The slide is not a storage space. It is an argument.

The Implication Is Often Missing

Teams are often good at showingpresenting evidence and weaker at explaining what the evidenceit means.

For example: Evidence

Market X is growing at 12% annually. Then the slide stops. But the audience may still ask:ask, "So what?" A stronger slide adds: This growth, combined with ACME's existing distribution capability, makes Market X the most attractive near-term expansion opportunity. Now the evidence has become decision-relevant.

Visual Hierarchy Should Match Thinking Hierarchy

If the message is the most important thing, it should visually appear important. The audience should naturally notice information in approximately this order:

MESSAGE → KEY EVIDENCE → SUPPORTING EVIDENCE → DETAIL

If the least important number is the largest thingelement on the slide, the visual hierarchy isconflicts fightingwith the analytical hierarchy. Design should guide attention toward the logic.

Don't Make Everything Important

Teams often try to create emphasis by:

  • bolding;

  • highlighting;

  • circling;

  • colouring;

  • adding arrows;

  • enlarging text.

All of those can work. But if you highlight everything, you haveend highlightedup highlighting nothing. Ask: What do I want the judge to notice first? Then make that obvious. Let everything else support it.

The Three-Second Question

Show the slide to someone for three seconds. Then hide it. Ask: What was the slide telling you?

  • If they say: "There was a graph and some numbers," the slide may not have a clear message.
  • If they say: "Your highest-value customers are leaving.leaving," the slide is working.

This is a powerful test because judges often process slides quickly while also listening to the speaker.Speaker.

Use More Than One Slide When Necessary

"One slide, one message" does not mean forcing complicated analysis onto one slide. If the idea requires:

  1. establishing the problem;

  2. explaining the cause;

  3. demonstrating the financial implication;

you may need three slides. That is often better than cramming everything onto one. For example:

  • Slide 1
    • High-value customer churn has doubled.
  • Slide 2
    • The declinecustomer experience is being driven bydriving the customer experience.decline.
  • Slide 3
    • Fixing retention creates greater value than increasing acquisition.

Each message builds naturally on the previous one.

Split the Slide Test

When a slide feels overcrowded, ask: Are there actually two different messages here? If yes, split it. For example:

  • A slide titled: Customer Growth and Financial Impact
  • may actually contain:
    • Message 1: Customer growth is concentrated in Segment A.
    • Message 2: Segment A has the lowest margins.

Those may deserve separate slides because the second insight changes the meaning of the first.

The Slide + Speaker Relationship

Remember the principle from Part I: Slides support the story. They are not the story.

  • The slide does not need to explain everything.
  • The speakerSpeaker provides interpretation.

Think:

  • SLIDE
    • Shows the message and evidence.
  • SPEAKER
    • Explains the meaning and implication.

If the slide contains every sentence the speakerSpeaker plans to say, it probably contains too much information.

The One-Slide Test

For every slide, answer:

  • MESSAGE What is the one primary idea?
  • EVIDENCE What proves it?
  • IMPLICATION Why does it matter?
  • VISUAL What is the clearest way to communicate the evidence?
  • SPEAKER What will the speakerSpeaker add that is not already visible?

If the team cannot answer all five, the slide is not ready.

Discover Your Mad Skills Principle

One slide. One primary message. Everything else earns its place by supporting that message.

Clarity comes from hierarchy. The audience should know immediately:

  • what matters,
  • why they should believe it,

and

  • why it affects the decision.

The Bottom Line

A strong slide follows a simple logic:

MESSAGE → EVIDENCE → IMPLICATION

The slide title communicates the insight. The visual provides the proof. The speakerSpeaker explains why it matters. If the judge has to search the slide to discover the point, the slide is doing too much—or the hierarchy is not clear enough.

Part IV: Practice Before Moving On

Before moving into visual communication, complete two quick tests.

Exercise 1: The Headline Deck

Remove everything from the presentation except the slide titles. Read them in order. Ask:

  • Do they tell a coherent story?

  • Does one naturally lead to the next?

  • Is the recommendation obvious?

  • Does the implementationImplementation logically follow?

  • Does the final title reconnect to the value?

If not, fix the architecture before fixing the visuals.

Exercise 2: The Slide Message Audit

For every proposed slide, complete:

  • The judge should understand:
  • The evidence proving it is:
  • The implication is:
  • The speakerSpeaker will add:

If a slide cannot pass this test, it is not ready for design. Once the message architecture is clear, you are ready for Part V: Visual Communication—choosing the visual that makes each message easiest to understand.

Back to top