Chapter 28

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 don't 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 don't. 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

o What is happening?

o Establish the context the audience needs to understand the case.

· Complication

o What has changed or created urgency?

o Introduce the tension that makes the current situation unsustainable or the opportunity worth pursuing.

· Question

o What decision must management make?

o Focus the presentation on the central issue.

· Answer

o What do you recommend?

o Give the audience the direction.

· Proof

o Why should the judges believe you?

o Provide the critical analysis, customer evidence, decision logic, and financial support.

· Execution

o How will the organisation make it happen?

o Show the roadmap, owners, resources, risks, and KPIs.

· Impact

o What will the recommendation accomplish?

o 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

o Begin with something the audience can accept.

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

· Complication

o Show what has changed.

o "However, growth in its existing market is slowing, while capital constraints make a fully owned national expansion too risky."

· Question

o Define the decision.

o "How can the company establish its next source of profitable growth without committing substantial capital before regional demand is proven?"

· Answer

o State the recommendation.

· The judges now understand:

o the current position;

o the tension;

o the decision;

o the direction of the presentation.

Don't Make It a Mystery

Teams sometimes hide the recommendation 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 a single central message that connects all sections. 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 one idea do we want the judges to believe by the end of the presentation. 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:

1. Situation: The organisation is currently…

2. Complication: However…

3. Question: Management must therefore decide…

4. Answer: We recommend…

5. Proof: This is the strongest choice because…

6. Execution: The organisation will implement it through…

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

o Does the complete deck tell one coherent strategic story?