Chapter 28: Building a Persuasive Story

Learning Objectives

By the end of this chapter, you should be able to:

organise a case presentation around a coherent decision narrative;
distinguish strategic storytelling from entertainment or unsupported anecdotes;
create context, tension, and direction;
give the audience the destination without turning the presentation into a mystery;
connect claims, evidence, insights, recommendations, and actions;
use the 5 P’s to create greater audience connection;
use customer stories, personas, journeys, and mock-ups appropriately;
create logical transitions between presentation sections;
maintain a consistent central message;
remove slides and analysis that do not advance the argument;
build a presentation story that judges can understand and remember.

Why This Matters

One of the biggest misconceptions about case presentations is that judges evaluate every slide independently. They evaluate the story created by the slides, presenters, evidence, and recommendation. Weak presentations feel like a sequence of unrelated sections:

“Here is our customer analysis.”
“Here is our SWOT.”
“Here is our financial analysis.”
“Here are our alternatives.”
“Here is our recommendation.”
“Here is our implementation.”

Every section may be technically correct, but the audience must reconstruct the relationships among them. A stronger presentation sounds like:

“The company’s profitability problem is being driven primarily by declining retention among its highest-value customers. Our customer analysis reveals that service failures—not weak awareness—are causing those customers to leave. Increasing acquisition spending would therefore treat the symptom rather than the cause. We evaluated three retention-focused alternatives and recommend redesigning the premium customer experience.”

The analysis is now connected. Each idea creates the need for the next one. The recommendation resolves a problem the audience already understands. Great presentations feel inevitable. Every section advances the same argument, and every major question receives an answer.

Discover Your Mad Skills Principle

People rarely remember every analysis. They remember the story that the analysis created.

The purpose of storytelling is not to turn the case into entertainment. It is to make the logic of the decision easier to:

follow;
believe;
remember;
act upon.

Storytelling Is Not Fiction

A business presentation story is not:

a dramatic tale invented for effect;
an emotional anecdote without evidence;
a mystery that hides the recommendation until the end;
a collection of metaphors;
a performance designed to distract from weak analysis.

A business story explains:

where the organisation is now;
what has changed;
why that change matters;
what decision must be made;
what the team recommends;
why the recommendation is credible;
how it will be implemented;
what value it will create.

The story is the connected logic of the case.

The Case Story

A useful communication structure is: Situation → Complication → Question → Answer → Proof → Execution → Impact

Situation

What is happening? Establish the context the audience needs to understand the case.

Complication

What has changed or created urgency? Introduce the tension that makes the current situation unsustainable or the opportunity worth pursuing.

Question

What decision must management make? Focus the presentation on the central issue.

Answer

What do you recommend? Give the audience the direction.

Proof

Why should the judges believe you? Provide the critical analysis, customer evidence, decision logic, and financial support.

Execution

How will the organisation make it happen? Show the roadmap, owners, resources, risks, and KPIs.

Impact

What will the recommendation accomplish? Reconnect the solution to the organisation’s objectives and the people affected.

This creates a decision journey: Context → Tension → Decision → Direction → Evidence → Action → Value

SCQA: Building the Opening Logic

The first four elements form the SCQA structure: Situation → Complication → Question → Answer

Situation

Begin with something the audience can accept. “The company has built a trusted meal-kit brand and a profitable position in its current market.”

Complication

Show what has changed. “However, growth in its existing market is slowing, while capital constraints make a fully owned national expansion too risky.”

Question

Define the decision. “How can the company establish its next source of profitable growth without committing substantial capital before regional demand is proven?”

Answer

State the recommendation. “We recommend entering Western Canada through a partnership-led pilot beginning in Calgary.” The judges now understand:

the current position;
the tension;
the decision;
the direction of the presentation.

Do Not Make It a Mystery

Teams sometimes hide the recommendation because they want to create suspense. That may work in a novel. It is usually less effective with business decision-makers. Executives often want the answer first. Then they want the reasoning.

Think: Answer → Why → How → Impact rather than: Analysis → Analysis → Analysis → Surprise

The Controlling Idea

A strong presentation has one central message that connects every section. For the meal-kit case, the controlling idea might be: Validate regional demand before investing in owned infrastructure. That idea connects:

the market analysis;
customer research;
alternative evaluation;
financial model;
partnership strategy;
pilot implementation;
risk mitigation;
expansion gate.

If judges remember only one message, this should be it. Ask: What is the one idea we want the judges to believe when the presentation ends? If the team produces several different answers, the story may lack focus.

Build the Story Before the Slides

Many teams begin by opening PowerPoint and assigning slides. One person creates the customer analysis. Another creates financials. Another builds implementation. The slides are assembled later, and the team hopes they form a story. That reverses the process. Begin by writing the argument in plain language.

The Story Spine

Complete these statements:

Situation: The organisation is currently…
Complication: However…
Question: Management must therefore decide…
Answer: We recommend…
Proof: This is the strongest choice because…
Execution: The organisation will implement it through…
Impact: This will enable the organisation to…

Read the seven statements aloud. Do they sound like one connected argument? If not, fix the logic before building the slides.

Storytelling at Three Levels

A persuasive story should exist at three levels.

Presentation Level

Does the complete deck tell one coherent strategic story?

Section Level

Does each section answer a specific audience question? For example:

Situation: What is happening?
Analysis: Why is it happening?
Alternatives: What could we do?
Recommendation: What should we do?
Financials: Is it worth it?
Implementation: Can it be done?
Risk: What could prevent success?
KPIs: How will we know it worked?

Slide Level

Does each slide communicate one clear message that advances the section? Alignment across all three levels creates flow.

Build Around Audience Questions

Every section should answer a question the previous section created. For example:

Growth has slowed.
Why?
The current market is reaching maturity.
Where could future growth come from?
Western Canada contains an attractive customer segment.
How should the company enter?
A partnership-led pilot provides the strongest balance.
Can the company afford it?
The pilot requires limited initial capital and reaches payback within the acceptable period.
How will it be implemented safely?
Through staged investment and customer, financial, and service gates.

The audience is continually given a reason to care about the next piece of information.

The “Why Are You Telling Me This?” Test

For every slide or section, imagine a judge asking: “Why are you telling me this?” Your answer should be immediate.

Customer Analysis
- “Because it identifies the priority segment and reveals the need our strategy must solve.”
Competitive Analysis
- “Because it demonstrates that convenience alone will not create a defensible position.”
Financial Analysis
- “Because it shows that a partnership-led pilot creates value without exceeding the company’s available capital.”
Implementation
- “Because it demonstrates that the strategy can be executed within the organisation’s current capabilities.”
If the answer is unclear:
- remove the slide;
- revise its message;
- reconnect it to the decision;
- move the detail to the appendix.

Claim, Evidence, Meaning, and Implication

A persuasive analytical slide should move through four elements.

Claim

What are you saying? “The greatest growth opportunity is concentrated among time-constrained urban professionals.”

Evidence

What supports the claim? Customer research, demographic concentration, market growth, and spending data.

Meaning

Why does the evidence matter? This segment values convenience, health, and flexibility more than the lowest price.

Implication

How does it affect the decision? The company should focus the pilot on a convenient, flexible offering rather than competing through discounts.

This progression turns data into a strategic argument.

Use Transitions to Connect the Story

Transitions should explain why the presentation is moving to the next section.

Weak: “Now I’ll pass it over to Alex for the financial analysis.”
Stronger: “The partnership-led pilot is strategically attractive, but the company must still determine whether it creates sufficient value within its capital constraints. Alex will now take you through the financial case.”

The stronger transition:

closes the previous section;
creates the next question;
explains why the next presenter matters;
maintains narrative flow.

The 5 Ps as a Storytelling Lens

The 5 P’s provide prompts for making the story more concrete and relatable. They are not a checklist that must be forced into every presentation.

1. People

Who matters in the story? Consider:

customers;
employees;
decision makers;
partners;
communities;
other stakeholders.

A strategy affects people. Identifying who matters helps prevent the story from becoming an abstract discussion of frameworks and numbers.

Ask:

Who experiences the problem?
Who benefits from the recommendation?
Who must change their behaviour?
Who could resist?
Who determines whether implementation succeeds?

2. Place

Where is the story happening? Place may include:

geography;
market;
organisation;
industry;
customer environment;
physical or digital setting.

Place provides context. For example:

“In Calgary, the priority customer is not simply looking for another meal subscription. They are managing long workdays, commuting, and limited time for planning and preparation.”

The market becomes more concrete.

3. Pictures

What can the audience see? Pictures may include:

charts;
diagrams;
customer journeys;
process maps;
photographs;
prototypes;
mock-ups;
visual comparisons;
before-and-after experiences.

Pictures make ideas easier to understand and remember. The objective is not decoration. The visual should help the audience see:

the problem;
the solution;
the change;
the value.

4. Personal

What makes the issue relatable?

A personal connection might involve:

a customer frustration;
an employee experience;
a stakeholder consequence;
a recognisable decision;
an organisation’s mission.

For example:

“For a customer arriving home after a ten-hour workday, the problem is not simply food preparation. It is the mental burden of deciding what to cook, shopping for ingredients, and avoiding waste.”

This makes the need tangible. Personal does not mean inventing unsupported details. The human element should represent the broader evidence.

5. Platform

How will the story be delivered? Consider how these elements work together:

slides;
speaking;
visuals;
transitions;
demonstrations;
mock-ups;
handoffs;
Q&A.

The platform should support the story. A detailed visual may be effective on a slide but difficult to explain in ten seconds. A mock-up may communicate the customer experience better than several bullet points. A powerful statistic may be more memorable when spoken and left alone on the screen.

Human Connection Must Be Evidence-Based

A customer story can make the problem memorable. It does not prove the entire market behaves the same way. Ask:

Is this person representative of the priority segment?
Does the evidence support the experience?
Does the story clarify something strategically important?
Does it influence the recommendation?

If the answer is no, the story may be emotionally interesting but analytically weak. Use a human example to illustrate evidence, not replace it.

Personas as Story Anchors

The persona developed in Chapter 17 can become a thread through the presentation. For example:

At the Beginning
- Introduce the priority customer and their problem.
- “Meet Maya, a time-constrained professional who values healthy meals but abandons subscription services when they become inflexible.”
During Analysis
- Show what the evidence reveals about customers like Maya.
During the Recommendation
- Explain how the proposed value proposition resolves the problem.
During Implementation
- Show how the pilot reaches, serves, and learns from this customer.
During Impact
- Demonstrate how the experience changes.

The persona creates continuity, but it should not appear on every slide or become a fictional performance.

Mock-Ups Make the Future Visible

A recommendation can remain abstract until judges can see how it works. Mock-ups might show:

a mobile application;
website experience;
retail display;
service package;
customer dashboard;
product prototype;
marketing message;
redesigned process;
future customer journey.

A useful mock-up answers: “What will the customer, employee, or stakeholder actually experience?”

Mock-Ups Are Evidence of Thoughtfulness. Not Proof of Feasibility

A polished mock-up can make a solution appear complete even when:

technology requirements remain uncertain;
costs are unknown;
customer demand is untested;
implementation is complicated.

Clearly label conceptual visuals where appropriate. Use the mock-up to explain:

the intended experience;
the value proposition;
the important features;
where it fits in the journey.

Do not use it to imply that the solution has already been built or validated.

Use the Appropriate Level of Fidelity

Not every idea requires a fully designed prototype.

Low-Fidelity

A sketch, wireframe, or simple process visual. Useful for explaining:

structure;
flow;
key features;
early concepts.

Medium-Fidelity

A more realistic screen or service mock-up. Useful for demonstrating:

customer experience;
brand alignment;
functionality;
interaction.

High-Fidelity

A near-finished visual or interactive prototype. Useful when the appearance and experience are central to the recommendation. Choose the simplest mock-up that helps judges understand the solution.

Create Tension Before Resolution

A story needs a reason for action. The tension might come from:

declining performance;
an unmet customer need;
a changing market;
a capability gap;
competitive pressure;
an implementation barrier;
an opportunity the organisation may miss.

Tension does not require exaggeration. The purpose is to establish: Why can’t the organisation simply continue as it is? The recommendation then resolves that tension.

Keep the Recommendation Visible

The central recommendation should not disappear after the executive summary. Reinforce it through:

consistent terminology;
decision-led slide titles;
recurring strategic themes;
aligned initiative names;
financial logic;
roadmap milestones;
KPIs;
closing summary.

Do not use several different labels for the same strategy. If the recommendation is “Partner, Prove, Scale,” use that language consistently.

Story Through Slide Titles

Read only the slide titles in order. Do they tell the argument?

Weak titles:

Market Analysis
Customer Analysis
Alternatives
Recommendation
Financials
Implementation

Stronger titles:

Growth in the current market is approaching its practical limit
Western Canada offers the strongest concentration of the priority customer
Owned entry creates unnecessary capital risk before demand is proven
A partnership-led pilot provides the strongest route to profitable expansion
The pilot recovers its investment within 22 months
Customer and financial gates control the move from pilot to scale

The second set tells the story even without the slide content.

Open With Direction

The opening should quickly establish:

the situation;
the complication;
the decision;
the recommendation or strategic direction.

Avoid spending the first minute on:

team introductions;
a long agenda;
a quotation unrelated to the case;
a dramatic story with no clear relevance;
background the judges already know.

Give the audience a reason to listen.

End With Resolution

The conclusion should resolve the question introduced at the beginning. Return to:

the central problem;
the recommendation;
why it wins;
what it will accomplish.

For example:

“The company’s challenge is not a lack of growth opportunity. It is finding a path that does not commit substantial capital before regional demand is proven. A partnership-led Calgary pilot resolves that tension by providing immediate market access, protecting financial flexibility, and creating the evidence required for responsible expansion. Partner, prove, and then scale.”

The story now feels complete.

Worked Example: The Meal-Kit Story Spine

Situation

The company has built a trusted meal-kit brand and profitable operations in its current market.

Complication

Growth is slowing, but building owned infrastructure for national expansion would require substantial capital before demand is validated.

Question

How can the company establish its next source of profitable growth while limiting financial and execution risk?

Answer

Enter Western Canada through a partnership-led pilot beginning in Calgary.

Proof

Calgary contains a strong concentration of the priority customer.
The partner closes the company’s distribution and local-access gaps.
The pilot requires substantially less capital than owned entry.
Base-case economics support payback in approximately 22 months.
Staged investment preserves flexibility.

Execution

Implement through four coordinated workstreams:

partnership and governance;
product and customer experience;
operations and technology;
customer acquisition and measurement.

Impact

Establish a profitable regional model and create a lower-risk path towards broader Canadian growth.

Controlling Idea

Validate demand before investing in owned infrastructure. Every slide should strengthen this story.

The Story Audit

Before finalising the presentation, test it.

The Logic Test
- Does each section lead naturally to the next?
The Relevance Test
- Does every slide support the decision?
The Consistency Test
- Do the problem, recommendation, financial model, implementation, risks, and KPIs tell the same story?
The Evidence Test
- Does every major claim have support?
The Human Test
- Can the audience understand who is affected and why the decision matters?
The Memory Test
- What are the three things judges are most likely to remember?
The Removal Test
- If a slide disappears, does the story change? If not, remove it or move it to the appendix.
The Title Test
- Do the slide titles alone communicate the argument?
The No-Slides Test
- Can the team explain the entire story clearly without opening the deck? If not, the slides may be hiding weaknesses in the logic.

Winning the Room

A persuasive story reduces the effort required from the judges. They should always understand:

where they are in the argument;
why the current information matters;
what question is being answered;
how the evidence supports the recommendation;
where the presentation is going next.

Winning the room does not mean adding drama to every slide. It means creating clarity, momentum, connection, and resolution.

Coach’s Lens

One of the easiest ways to improve a presentation is to remove any slide that does not answer a question the audience already has or create a question the next section will answer. Teams often resist removing slides because the analysis took time to complete, but the amount of work required to create a slide does not determine whether the judges need to see it. The presentation is not a record of everything the team did. It is the argument the judges need to hear.

Common Mistakes

Building Slides Before the Story: Create the argument first.
Treating Every Slide Independently: Slides should operate as connected parts of one decision narrative.
Storytelling as Entertainment: The story should make the strategy easier to understand—not distract from it.
Hiding the Recommendation: Do not turn the presentation into a mystery.
Analysis Without Implication: Explain what every important finding means for the decision.
Repeating Instead of Advancing: Each section should add something new.
Framework-Led Storytelling: Do not structure the presentation around the order in which frameworks were completed.
Unsupported Anecdotes: A compelling story does not replace representative evidence.
Too Much Context: Give judges only the background required to understand the decision.
No Tension: Explain why action is required.
Too Many Strategic Threads: Focus on one controlling idea.
Weak Transitions: Explain why the next section matters.
Decorative Mock-Ups: Use mock-ups to clarify the customer experience or operating model.
Overpromising Through Mock-Ups: A polished design does not prove customer adoption, technical feasibility, or financial value.
Inconsistent Terminology: Use the same language for the problem, strategy, initiatives, and outcomes.
Ending Without Resolution: Return to the decision and show how the recommendation resolves the original tension.

Mad Skills Drill

Take the complete case solution developed in the previous chapters.

Part One: Write the Story Spine

Complete:

Situation:
Complication:
Question:
Answer:
Proof:
Execution:
Impact:

Read the seven statements aloud. Do they sound like one connected argument?

Part Two: Identify the Controlling Idea

Complete: If the judges remember only one idea, it should be…

Part Three: Map the Audience Questions

For every section, identify:

the question it answers;
the question it creates next.

Part Four: Apply the 5 P’s

Identify:

People: Who matters?
Place: Where is the decision happening?
Pictures: What should the judges see?
Personal: What makes the issue relatable?
Platform: How will the story be delivered?

Do not force all five if they do not improve the presentation.

Part Five: Build the Human Thread

Select one customer, employee, or stakeholder perspective grounded in the evidence. Show how their experience changes:

Part Six: Create One Mock-Up

Build one visual that helps the judges imagine the solution. Explain:

what it shows;
where it fits in the journey;
what assumption still requires testing.

Part Seven: Write Decision-Led Titles

Read only the slide titles. Do they communicate the argument?

Part Eight: Perform the Removal Test

Remove one slide. If the story remains complete, consider moving the slide to the appendix.

Part Nine: Present Without Slides

Tell the entire case story in 90 seconds. Your teammates should be able to identify:

the problem;
the recommendation;
the proof;
the implementation;
the impact.

Reflection Questions

What is the central story of your case?
What has changed to create urgency?
What decision must management make?
Does the audience receive the answer early enough?
What is the controlling idea?
Does each analysis create an implication?
Does each section create a reason for the next?
Who is the human centre of the story?
Is the human example supported by broader evidence?
What should the judges see rather than merely hear?
Does the mock-up clarify the solution?
Do the slide titles tell the story?
Which slide could be removed?
Does the ending resolve the opening tension?
Can every team member tell the same story without slides?

Chapter Summary

A persuasive case story is a connected decision argument. It moves through: Situation → Complication → Question → Answer → Proof → Execution → Impact. The strongest presentations:

establish context without wasting time;
create a clear reason for action;
define the decision;
provide the answer;
support it with evidence;
demonstrate execution;
conclude with measurable value.

Storytelling does not replace analysis. It connects the analysis so that judges can understand why the recommendation makes sense.

Key Takeaways

✓ Build the story before building the slides.

✓ Treat storytelling as connected decision logic—not entertainment.

✓ Use Situation, Complication, Question, and Answer to establish direction.

✓ Give the audience the destination before asking them to follow the journey.

✓ Build the full story through Proof, Execution, and Impact.

✓ Identify one controlling idea that connects the entire presentation.

✓ Ensure every section answers a question and creates a reason for the next.

✓ Turn evidence into implication.

✓ Use the 5 P’s—People, Place, Pictures, Personal, and Platform—to strengthen audience connection.

✓ Use human examples to illustrate representative evidence.

✓ Use mock-ups to help judges imagine the solution without overstating feasibility.

✓ Write decision-led slide titles that communicate the argument.

✓ Use transitions to maintain narrative momentum.

✓ Remove slides that do not advance the decision.

✓ End by resolving the tension introduced at the beginning.

Looking Ahead

A persuasive story gives the presentation structure and meaning. But winning the room also requires the team to communicate with the clarity, confidence, and discipline expected of senior decision-makers. The next chapter focuses on: How do we stop sounding like students presenting a project and start communicating like executives recommending a decision? That begins with executive communication.