Chapter 17: Four Speakers Should Sound Like One Team

Chapter 17: Four Speakers Should Sound Like One Team

A team presentation can easily become four individual mini-presentations. Speaker one delivers the analysis. Then:

• "I'll pass it over to Sarah."
• Sarah presents the alternatives. Then:
• "Now I'll hand things over to Alex."
• Alex discusses financials.
• Eventually the final speaker closes.

Everyone may present well individually, but the audience experiences four disconnected sections, which is not the goal. The judges should experience: One team. One story. One Recommendation.

The Team Owns the Entire Presentation

One of the most important mindset shifts is: You don't own your slides. You own the solution.

• A finance specialist may have built the financial model.
• Another teammate may have conducted the customer analysis.
• Someone else may have designed the implementation plan.

Once the presentation begins, the entire team owns all of it. Every team member should understand:

• the problem;

• the key insights;

• the alternatives;

• the decision criteria;

• the Recommendation;

• the financial logic;

• the implementation;

• the major risks;

• the expected impact.

That becomes especially important during Q&A. If only one person understands the financials or can explain the implementation, the judges may begin to question whether the Recommendation truly belongs to the team.

Speaker Transitions Should Advance the Story

Transitions are small moments that can significantly affect how connected the presentation feels. Avoid:

• "Okay, now I'll pass it over to Sarah." or:
• "That's my section. Alex will talk about the financials."

These transitions announce a speaker change. They do notdon't advance the argument; instead, they connect the ideas. For example:

• "Now that we've established why retention is the central issue, Sarah will show how the economics support our recommendation." Or:
• "The financial case is compelling. The next question is whether the organisation can execute it. Alex will take you through our implementation plan."

The transition now does three things: Closes the Previous Idea → Creates the Next Question → Introduces the Next Speaker. That keeps the story moving.

The Transition Formula

A useful structure is: What We Just Learned → Why it Matters → What Comes Next. For example:

• "Our analysis shows that high-value customers are driving the profitability decline. That makes retention our strategic priority. Sarah will now explain how we evaluated the available retention strategies." Or:
• "Option B provides the strongest strategic fit, but strategy alone isn't enough; the investment also needs to create value. Alex will walk you through the financial impact."

The audience should understand why the next section exists.

The Receiving Speaker Should Continue the Thought

The transition should not stop when the first speaker finishes. Suppose one presenter says: "The economics support the investment. The next question is how we make it happen. Sarah will take you through our implementation." Sarah should not begin: "Thanks, Cam. So now I'm going to talk about implementation." The momentum disappears. Instead: "We will execute the recommendation in three phases, beginning with a six-month pilot." The second speaker immediately continues the argument. Think of the handoff like passing a baton. The story should keep moving.

Consistency Between Speakers

The audience should never hear different versions of the strategy. Before presenting, agree on:

• terminology;

• pronunciation;

• recommendation wording;

• key numbers;

• customer or stakeholder names;

• alternative names;

• implementation phases;

• financial assumptions;

• major risks;

• expected outcomes.

For example, if one speaker calls the recommendation "Project Elevate," another should not call it "The Customer Loyalty Strategy" and another "Our Retention Initiative" unless those terms have different meanings. Consistency reduces cognitive load and signals an aligned team.

Know the Anchor Numbers

Every team member should know the most important numbers in the case. For example:

• Investment: $2.5M

• Expected NPV: $1.7M

• Payback: 2.3 years

• Target retention improvement: 8%

• Pilot: six months

• Full rollout: 18 months

The judges should not hear one speaker say $2.5 million and another say "about $3 million." Even small inconsistencies can create doubt. Agree on the anchor numbers and use them consistently.

Agree on the Recommendation Sentence

One useful team exercise is to ask every member individually: "What exactly are we recommending?" Then compare the answers. If four teammates provide four substantially different answers, the Recommendation is not yet sufficiently clear. Develop one core recommendation sentence. For example: "We recommend launching a targeted loyalty strategy for high-value customers through a six-month pilot before scaling nationally." Everyone does notdoesn't need to repeat that sentence word-for-word, but everyone must communicate the same strategy.

Don't Divide the Presentation Into Equal Pieces

A common team instinct is: "There are four of us and twelve minutes, so everyone gets three minutes." That may be fair. It may not produce the strongest presentation. Speaking time should reflect:

• the story;

• individual strengths;

• complexity of the material;

• credibility;

• natural transitions;

• strategic importance.

A complex financial argument may need more time. A short situation-setting section may need less. A particularly strong closer may be the best person to deliver the final recommendation and impact. The goal is not equal airtime, but each member needs time to get their points across to the judges. The goal is the strongest team presentation.

Match Speakers to the Communication Challenge

Think strategically about who should present each section. Consider:

• Analytical Strength: Who can explain complex reasoning?
• Financial Confidence: Who can communicate the financial model without becoming overly technical?
• Storytelling: Who establishes connection particularly well?
• Executive Presence: Who can deliver the Recommendation with conviction?
• Implementation Understanding: Who can explain how the Recommendation becomes operational?
• Closing Ability: Who can bring the argument together and land the final message?

Use people's strengths. That does notdoesn't mean hiding weaker presenters. Everyone should develop their presentation skills. Competition strategy and practice strategy are not always identical.

Avoid the Relay-Race Presentation

Another problem occurs when each person presents once: Speaker 1 → Speaker 2 → Speaker 3 → Speaker 4. This can reinforce the feeling of four separate sections. Typically, thereopportunities are opportunitiesexist for speakers to return later. For example:

• Speaker 1: Opening + Situation
• Speaker 2: Analysis
• Speaker 3: Alternatives + Recommendation
• Speaker 4: Financials
• Speaker 2: Implementation
• Speaker 1: Close

This is not automatically better, and excessive switching can become distracting. The point is don't let equal division determine the presentation architecture. Let the story determine it.

Team Presence When You Are Not Speaking

You are still presenting when you are silent. Judges can see the entire team. Avoid:

• staring at the floor;

• checking notes constantly;

• looking disengaged;

• whispering with teammates;

• reacting negatively to a mistake;

• appearing surprised by something a teammate says;

• visibly preparing your own section instead of listening.

Instead:

• remain engaged;

• listen;

• face the active speaker or audience naturally;

• know where the presentation is;

• be ready for the transition.

Your body language should communicate "This is our recommendation," not "I'm waiting for my turn."

Recover as a Team

Mistakes happen. Someone may:

• forget a point;

• stumble over a number;

• skip a slide;

• miss a transition;

• phrase something differently than rehearsed.

Do notDon't make the mistake bigger through your reaction. Avoid:

• grimacing;

• shaking your head;

• interrupting unnecessarily;

• correcting a teammate publicly over something insignificant.

Keep going. If clarification is necessary, integrate it naturally later. The judges may not even notice the original mistake unless the team signals through its reaction that something went wrong.

Don't Rescue Too Quickly

Strong teammates want to help; sometimes they help too much. If a speaker pauses briefly, another teammate jumps in. That can undermine the speaker and make the team look less coordinated. Give teammates space to recover. Support should be available; it should not become an interruption. This principle becomes even more important during Q&A.

Rehearse the Handoffs

Teams often rehearse the content extensively but pay little attention to transitions; that is a mistake. Transitions are precisely where the audience can feel the seams between speakers. Practice:

• the final sentence of Speaker A;

• the handoff;

• the first sentence of Speaker B.

Do those three sentences create one continuous thought? If yes, the transition is working.

Rehearse as a Team, Not Just Individually

Individual rehearsal is useful, but it cannot reveal:

• awkward handoffs;

• inconsistent terminology;

• repeated information;

• contradictions;

• timing problems;

• differences in energy;

• unclear speaker positioning.

At some point, the entire presentation must be rehearsed as a single performance and, ideally, repeatedly.

The Team Consistency Test

Before the competition, ask every team member separately:

• What is the central problem?
• What is our Recommendation?
• Why does it win?
• What are the three most important supporting insights?
• What does it cost?
• What value does it create?
• What is the biggest risk?
• How are we mitigating it?
• What does success look like?

Compare the answers. They don't need identical wording. They need consistent meaning. If the answers differ substantially, the team is not yet ready.

From Four Voices to One Argument

Individual presentation styles do notdon't need to disappear. One speaker may naturally be:

• more energetic;

• more analytical;

• more conversational;

• more deliberate.

That is fine.fine; Youyou are not trying to manufacture four identical presenters. The consistency should come from the argument, not identical personalities. Think: Different Voices + Shared Logic + Shared Language + Shared Recommendation = One Team.

Discover Your MAD Skills Principle

You don't own your section. You own the team's recommendation.

The strongest teams do notdon't simply divide the presentation.presentation; Theythey collectively understand and communicate it.

The Bottom Line

A strong team presentation should feel like: One Team → One Story → One Recommendation. Build that through:

• connected transitions;

• consistent terminology;

• shared anchor numbers;

• deliberate speaking roles;

• engaged team presence;

• rehearsed handoffs;

• collective ownership.

The judges should never wonder whether the team agrees with itself.

MAD Skills Drill

This part is about integration. Finish with a Team Alignment Drill. Before a full rehearsal, give each teammate five minutes independently to write:

• Our problem is:
• Our recommendation is:
• The three strongest reasons are: 
  • 1
  • 2
  • 3
• The investment is:
• The expected impact is:
• Our biggest risk is:
• We mitigate it by:

Compare where answers differ, then resolve the inconsistency before rehearsing again. Finally, run one complete presentation and evaluate only three things:

• The Story: Does the argument remain connected when speakers change?
• The Handoffs: Does each speaker create the reason for the next speaker?
• The Team: Do four individual presenters feel like one advisory team?

If the answer to all three is yes, you have moved beyond dividing up a presentation; you are presenting as a team.