Chapter 33: Recovering Under Pressure

Chapter 33: Recovering Under Pressure - Turning Mistakes into Moments of Leadership

"The judges rarely remember the mistake. They remember how you responded to it."

Video: Effective Speaking Strategies: 10 Practical Techniques to Deliver a Memorable Case Presentation

Learning Objectives

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

• remain composed when a presentation doesn't unfold as planned;

• distinguish minor setbacks from material errors and critical disruptions;

• decide whether to continue, clarify, correct, or change course;

• recover confidently after losing your train of thought;

• adapt to slide, technology, timing, and interruption problems;

• protect the recommendation and conclusion when time becomes limited;

• support teammates without highlighting or compounding their mistakes;

• communicate material corrections honestly;

• return the audience to the central story after disruption;

• prepare contingency plans for predictable presentation failures;

• practise uncertainty through controlled disruption;

• use reflection to turn difficult experiences into future confidence;

• demonstrate resilience and leadership under pressure.

Why This Matters

No presentation is perfect.

• Slides fail.

• Technology crashes.

• Someone forgets a transition.

• The wrong slide appears.

• A financial number is stated incorrectly.

• A judge interrupts.

• A presenter loses their place.

• The clock suddenly shows only two minutes remaining.

The question is not whether something unexpected might happen. The question is: How will your team respond when it does? Many competitors believe judges reward perfection. Experienced judges understand that business rarely unfolds exactly as planned. Organisations face:

• changing markets;

• competitor reactions;

• customer surprises;

• operational failures;

• budget constraints;

• incomplete information.

Leaders are not judged only by their ability to create a plan. They are judged by how they respond when the plan encounters reality. Case competitions reveal the same qualities.

Can your team:

• remain calm;

• assess what matters;

• adapt;

• protect the central decision;

• continue communicating clearly?

Effective recovery can create greater confidence than flawless but inflexible delivery.

Discover Your MAD Skills Principle

Confidence is not built by avoiding mistakes. Confidence is built by recovering from them.

Every disruption creates an opportunity to demonstrate:

• judgment;

• composure;

• flexibility;

• teamwork;

• leadership.

The objective is not to pretend the mistake did not happen. It is to ensure that the mistake doesn't control what happens next.

Pressure Is Part of the Competition

Students often think pressure is something they must eliminate before competing. Experienced competitors understand that pressure is part of the experience.

• Every team feels nervous.

• Every presenter experiences uncertainty.

• Every competition contains variables the team cannot control.

The goal is not to feel no pressure. It is to function effectively under pressure.

Pressure Reveals Preparation

Pressure doesn't automatically create strong performance. It reveals what the team has prepared to do. When the unexpected occurs, teams rely on:

• their understanding of the recommendation;

• their knowledge of the story;

• their decision priorities;

• their time-compression plan;

• their team recovery protocols;

• their previous experience recovering.

This is why preparation creates flexibility, and memorisation creates fragility. If the team understands the ideas, it can adapt the words, slides, and timing. If the team knows only the script, even a small interruption can become destabilising.

The Recovery Mindset

When something goes wrong, presenters often focus immediately on themselves:

• Do I look unprepared?

• Did everyone notice?

• Have I ruined the presentation?

• What will my teammates think?

Professional presenters shift the question to what the audience needs from us right now. The audience may need:

• the correct number;

• the missing conclusion;

• a clear explanation;

• a brief pause;

• reassurance that the team remains in control;

• a return to the central recommendation.

An audience-focused mindset reduces panic and improves judgment.

The Recovery Loop

A practical recovery process is: Pause → Assess → Prioritise → Act → Reconnect.

Pause

Stop the automatic reaction.

• Finish the current sentence where possible.

• Breathe.

• Ground your stance.

• Look towards the judges.

• Avoid immediate apologies or nervous explanations.

A two-second pause feels longer to the presenter than to the audience.

Assess

Determine what happened. Ask:

• Did I miss a word, a point, or an entire section?

• Is the error visible to the judges?

• Does it affect their understanding?

• Does it change the recommendation or financial result?

• Is this an individual problem or a team problem?

• How much time remains?

Prioritise

Decide what matters now. Protect:

1. the central problem;

2. the recommendation;

3. the decisive supporting logic;

4. implementation credibility;

5. the close.

Don't attempt to recover every minor detail at the expense of the strategic message.

Act

Choose the appropriate response:

• continue;

• restate;

• correct;

• compress;

• ask for clarification;

• shift to another presenter;

• proceed without the technology.

Reconnect

Return the judges to the story. Use a line such as:

• "The key point is…"

• "What this means for our recommendation is…"

• "Returning to the strategic decision…"

• "This leads directly to our implementation approach…"

Recovery is complete when the audience is focused on the decision again.

Distinguish Minor, Material, and Critical Problems

Not every mistake deserves the same response.

Level 1: Minor and Non-Material

Examples include:

• stumbling over a word;

• missing an unimportant sentence;

• a brief pause;

• using a slightly different transition;

• advancing an animation too early.

Response: Continue and don't advertise a mistake that doesn't affect understanding.

Level 2: Noticeable but Manageable

Examples include:

• skipping a useful supporting point;

• briefly losing your place;

• advancing to the wrong slide;

• missing a planned handoff;

• stating something unclearly.

Response: Clarify or restate briefly, then continue. For example: "Let me restate the central point: the pilot is designed to validate demand before the company commits to owned infrastructure."

Level 3: Material Error

Examples include:

• stating the wrong investment;

• confusing the recommended alternative;

• giving an incorrect target;

• contradicting a critical assumption;

• misrepresenting a stakeholder consequence.

Response: Stop and correct the error clearly. For example: "I need to correct that figure. The initial pilot investment is $280,000, not $250,000. The 22-month payback is based on the $280,000 investment." A brief correction protects credibility.

Level 4: Critical Disruption

Examples include:

• complete technology failure;

• loss of substantial presentation time;

• inability of a presenter to continue;

• missing or corrupted presentation file;

• a major error that changes the recommendation;

• an interruption that fundamentally changes the session.

Response: Shift to the contingency plan. The team may need to:

• continue verbally;

• move to a backup file;

• reassign a section;

• compress the deck;

• clarify the recommendation;

• follow the competition organiser's instructions.

The Correction Test

Before correcting an error publicly, ask:

1. Does it affect the recommendation?

2. Does it affect the financial result?

3. Could it mislead the judges?

4. Does it create a contradiction they are likely to notice?

5. Would leaving it uncorrected damage credibility?

If yes, correct it. If no, continuing may be the more professional choice.

Never Allow One Mistake to Become Two

The first mistake may be unavoidable. The second often occurs because the presenter:

• panics;

• apologises repeatedly;

• speeds up;

• loses eye contact;

• abandons the structure;

• skips the close.

The objective is to contain the disruption. A useful internal message is: that moment is finished, what is the next idea?

Recovering From a Lost Train of Thought

When your mind goes blank:

1. stop speaking;

2. breathe;

3. look at the slide title;

4. identify the slide's central message;

5. state that message directly;

6. transition to the next point.

Use: "The central point is that customer adoption determines whether we expand. That is why the pilot includes a 1,200-customer decision gate." You don't need to recover the exact forgotten sentence. The judges don't know the script.

Use Message Anchors

Prepare several reliable anchors:

• the core problem;

• the recommendation;

• the three reasons it wins;

• the key financial result;

• the implementation phases;

• the largest risk;

• the closing statement.

If you lose your place, return to one of these anchors.

Don't Search Publicly for the Missing Sentence

Avoid:

• staring silently at notes for an extended period;

• repeating the previous sentence several times;

• saying, "I completely forgot what comes next";

• asking teammates, "What was I supposed to say?"

Summarise the point and move forward.

Recovering From Technology Failure

Slides support the presentation. They are not the presentation. If the screen fails:

1. pause briefly;

2. allow the organiser or designated teammate to address the equipment;

3. continue verbally if permitted;

4. describe only the essential visual information;

5. remain focused on the judges.

For example: "While the slide is being restored, the key result is that the partnership pilot requires $280,000, substantially less than the owned entry and reaches base-case payback in approximately 22 months."

Build Technology Redundancy

Where competition rules allow, prepare:

• a local copy;

• a cloud or external backup;

• a PDF version;

• fonts and media embedded;

• videos available separately;

• key figures in presenter notes;

• a team member who knows the slide sequence;

• the ability to present without animations.

Test the final file on a different device where possible.

If a Video or Animation Fails

Don't wait indefinitely. Explain the intended point: "The demonstration illustrates how a customer moves from selecting a meal to adjusting delivery in three steps. The important change is the added flexibility, which directly addresses the abandonment problem identified in the customer journey." The failed feature should not become more memorable than the strategy.

If the Wrong Slide Appears

Don't panic. Options include:

• explain the current slide if it is the next logical point;

• return to the correct slide;

• continue verbally while the deck is corrected.

Use: "Before moving to implementation, let me complete the financial conclusion." Then do so.

Recovering Under Time Pressure

When warned that time is short, don't attempt to preserve every word by speaking faster. Use the compression plan. Prioritise:

1. recommendation;

2. why it wins;

3. financial or strategic value;

4. implementation credibility;

5. closing.

Reduce:

• framework descriptions;

• secondary evidence;

• examples;

• detailed assumptions;

• lower-priority implementation steps;

• additional future considerations.

The Two-Minute Recovery

If only two minutes remain, a team might allocate:

• 30 seconds: recommendation and reasons;

• 45 seconds: implementation, risk, and decision gate;

• 30 seconds: impact and financial support;

• 15 seconds: close and invitation to questions.

The exact allocation depends on what has already been presented. The principle is to protect the decision.

Never Sacrifice the Recommendation

A team that finishes every analytical slide but fails to state the recommendation has not completed the presentation. If necessary, say: "Given the remaining time, we will move directly to our recommendation and implementation." That is better than rushing through several slides and losing the close.

Recovering After a Teammate's Mistake

Strong teams protect one another. Don't:

• show visible frustration;

• roll your eyes;

• whisper criticism;

• correct every minor error;

• blame the presenter;

• make a joke at their expense.

Instead:

• remain engaged;

• provide calm eye contact;

• allow the speaker to recover;

• incorporate a missing point later if it is important;

• clarify material errors professionally.

The Team Rescue Test

Before intervening, ask:

• Is the teammate still able to continue?

• Is the missing information essential?

• Will intervention help or increase confusion?

• Can the correction occur naturally later?

• Am I helping the audience or relieving my own discomfort?

Rescue only when it creates meaningful value.

Useful Team Rescue Lines

• If a teammate loses their place: "The key implication for implementation is the customer adoption gate. Would you like to take us through that next?"
• If a critical number is missing: "To reinforce that point, the break-even threshold is approximately 1,072 active customers."
• If the transition was skipped: "That establishes why the market is attractive. The next question is how the company should enter it."

These responses support rather than embarrass.

If a Teammate States a Materially Incorrect Number

Correct it without drama: "One clarification on the investment: the total is $280,000, including the $80,000 acquisition budget." Don't say: "That's wrong." Protect both accuracy and team credibility.

If a Presenter Cannot Continue

Teams should know who can cover each section. The supporting presenter should:

1. continue from the central message;

2. avoid explaining the internal problem;

3. preserve the narrative;

4. return control where appropriate.

"The important conclusion from this analysis is that partnership provides the strongest risk-adjusted entry path. I'll continue with how we implement it."

Recovering From an Unexpected Interruption

If a judge interrupts during the presentation:

1. stop and listen;

2. answer concisely;

3. determine whether the concern requires deeper discussion;

4. return to the presentation.

For example: "Yes. The $280,000 includes the technology integration and initial acquisition spending. Returning to the roadmap, that investment is staged across the first five months." Don't restart the entire section.

If the Interruption Becomes a Discussion

Follow the competition format and the judge's direction. If appropriate: "We would be happy to explore that further during Q&A. For now, the direct answer is that the pilot remains viable above the 1,200-customer expansion threshold." Maintain respect. Never imply that the judge should not have interrupted.

Recovering From a Challenged Assumption

A challenged assumption is not automatically a mistake. Respond by distinguishing:

• what is known;

• what was assumed;

• how sensitive the result is;

• how the organisation will test it.

"The case doesn't provide a regional conversion rate, so we used an 8% base assumption informed by current performance. The recommendation remains viable at a lower rate, and the pilot validates conversion before expansion." Don't defend an assumption as if it were a proven fact.

Recovering From a Weak Q&A Answer

• If you realise an answer was incomplete: "Let me add one important point to complete that response…"
• If you misunderstood: "I answered from the perspective of the initial pilot. I understand that you are asking about the later expansion decision…"
• If the answer was wrong: "I need to correct my previous response…"

Correct it once and move forward.

Managing Physical Signs of Pressure

Pressure may produce:

• shallow breathing;

• fast speech;

• shaking hands;

• dry mouth;

• narrowed attention;

• difficulty recalling words.

Use a physical reset:

1. exhale slowly;

2. place both feet firmly;

3. relax the shoulders;

4. focus on one judge;

5. state one complete sentence;

6. pause again.

You don't need to feel calm before acting calmly. Behaviour can lead the emotional recovery.

Composure Is Contagious

The audience takes cues from the team. If the presenters:

• panic;

• rush;

• blame;

• over-apologise;

the judges may assume the disruption is serious. If the team remains calm and purposeful, the judges are more likely to view it as manageable. Teammates also take cues from one another. One grounded presenter can stabilise the entire group.

Use Apologies Carefully

An apology is appropriate when:

• the audience is materially inconvenienced;

• the team made a meaningful factual error;

• professionalism requires acknowledgement.

Keep it brief. "Apologies for the incorrect figure. The correct investment is $280,000." Avoid apologising for:

• pausing;

• checking a number;

• taking a breath;

• asking for clarification;

• correcting yourself promptly.

Repeated apologies shift attention from the decision to the presenter's discomfort.

Reconnect to the Story

After any disruption, return to the central narrative. Useful lines include:

• "The key decision remains…"

• "What this means for the recommendation is…"

• "Returning to the central customer problem…"

• "This is why the pilot approach matters…"

• "The next step is therefore…"

The story gives the team a route back.

Build a Recovery Plan

Before presenting, agree on:

• Time Signals: How will the team know it must compress?
• Essential Content: Which messages can never be removed?
• Backup Presenter: Who can cover each section?
• Technology Ownership: Who manages the deck or backup file?
• Rescue Protocol: When should a teammate intervene?
• Correction Protocol: How will material errors be clarified?
• Closing Protection: Who ensures sufficient time remains for the close?

A recovery plan reduces the need to invent one under pressure.

Practise Recovery, Not Only Perfection

Teams frequently rehearse the ideal presentation repeatedly. This improves familiarity but may not improve adaptability. Introduce controlled disruptions after the core presentation is stable.

Chaos Practice

During a mock presentation, ask a coach or teammate to:

• skip a slide;

• turn off the projector;

• change the remaining time;

• interrupt with a question;

• request clarification;

• provide the wrong slide;

• ask one presenter to cover another section;

• remove presenter notes;

• repeat a challenging question;

• introduce a minor calculation inconsistency.

The objective is not to embarrass presenters. It is to normalise uncertainty and practise response.

Progressive Pressure

Build difficulty gradually.

• Level 1: Familiar Conditions
  • Present with slides, notes, and expected timing.
• Level 2: Reduced Support
  • Present without notes or selected visuals.
• Level 3: Time Compression
  • Remove one or two minutes without warning.
• Level 4: Interruption
  • Add questions, slide errors, or missed transitions.
• Level 5: Full Disruption
  • Combine multiple realistic challenges.

Pressure should remain at a level safe enough to support learning. The objective is confidence through experience, not humiliation.

The Recovery Cycle

Confidence grows through: Experience Pressure → Act Anyway → Recover → Reflect → Practise Again. Each successful recovery teaches the brain:

• the disruption was manageable;

• the presentation could continue;

• perfection was not required;

• the team could adapt.

Confidence becomes evidence-based.

Conduct an After-Action Review

After practice or competition, don't ask only: "Did we make mistakes?" Ask:

1. What happened?

2. What did we notice first?

3. How did we respond?

4. What worked?

5. What made the disruption worse?

6. What should we do next time?

7. What recovery protocol needs to change?

8. What did this experience teach us?

Keep the review focused on behaviour and systems, not blame.

Learn Without Overcorrecting

One mistake doesn't always require a complete redesign. For example:

• one forgotten line may not require full scripting;

• one clicker problem may not require removing every animation;

• one difficult question may not invalidate the recommendation.

Identify the underlying cause before changing the process. Ask: Was this a one-time error, a preparation gap, or a system weakness?

Worked Recovery Scenarios

Scenario 1: The Financial Slide Fails

Problem

The screen goes blank during the financial case.

Recovery

"While the slide is restored, the key financial conclusion is that the $280,000 pilot generates approximately $156,000 in annual operating profit and reaches payback in about 22 months. Customer adoption is the critical assumption, so expansion remains contingent on achieving at least 1,200 active customers."

Reconnection

"That financial gate leads directly to our phased implementation."

Scenario 2: The Team Receives a Two-Minute Warning Early

Problem

Several planned slides remain.

Recovery

"Given the remaining time, we will move directly to the recommendation and the actions required to implement it." The team then protects:

• recommendation;

• value;

• roadmap;

• decision gate;

• close.

Scenario 3: A Presenter Forgets the Transition

Problem

The speaker pauses and loses their place.

Recovery

The speaker looks at the title and says: "The central insight is that owned entry creates unnecessary capital exposure before demand is proven. We therefore recommend a partnership-led pilot." Then moves to the recommendation.

Scenario 4: A Teammate Gives the Wrong Investment

Problem

The teammate says $250,000 instead of $280,000.

Recovery

The next speaker states: "One clarification before we continue: the total pilot investment is $280,000, including $80,000 in customer-acquisition spending." Then proceeds without blame.

Scenario 5: A Judge Challenges the Conversion Assumption

Problem

The judge suggests the 8% base rate is too optimistic.

Recovery

"That is the most important uncertainty in our model. Because the case doesn't provide a regional conversion rate, we used 8% as the base case and tested a lower range. The pilot prevents us from committing to full expansion until conversion and retention have been validated." The assumption challenge strengthens the logic of the staged recommendation.

Winning the Room

Recovery is one of the clearest demonstrations of leadership. When disruption occurs, judges observe whether the team:

• protects the decision;

• communicates honestly;

• remains aligned;

• adapts without panic;

• continues serving the audience.

The team doesn't need to convince judges that nothing went wrong. It needs to demonstrate that the problem is under control.

Coach's Lens

I have seen podium-winning teams:

• forget slides;

• lose their place;

• encounter technology failures;

• receive difficult interruptions;

• make visible mistakes.

What distinguished them was not flawless execution. It was their ability to prevent one difficult moment from defining the rest of the presentation. They acknowledged what mattered, adapted, and continued. Some of the strongest presentations I have judged contained obvious imperfections. The judges did not remember the mistake for long. They remembered the professionalism of the recovery.

Common Mistakes

• Panicking After a Minor Error: Assess its importance before reacting.
• Repeated Apologies: Correct what matters and continue.
• Advertising Invisible Mistakes: The judges don't know what you planned to say.
• Ignoring a Material Error: Correct information that affects the decision.
• Allowing One Mistake to Become Two: Don't add rushing, confusion, or a missed close to the original problem.
• Searching for the Exact Script: Return to the message.
• Speaking Faster After an Interruption: Use the compression plan.
• Sacrificing the Recommendation: Protect the strategic choice and close.
• Waiting Indefinitely for Technology: Continue verbally where possible.
• Blaming Teammates: Recover as one team.
• Correcting Every Minor Difference: Intervene only when accuracy or clarity requires it.
• Over-Rescuing: Give teammates space to recover on their own.
• Contradicting the Presentation: Clarify material issues carefully.
• Becoming Defensive When Assumptions Are Challenged: Explain the evidence, uncertainty, and validation plan.
• Treating an Interruption as Disrespect: Respond professionally and return to the story.
• Practising Only Ideal Conditions: Build adaptability through controlled disruption.
• Focusing Only on What Went Wrong: Use after-action review to identify what worked and what should change.

MAD Skills Drill

Run a controlled Chaos Practice.

Part One: Establish the Recovery Anchors

Every team member should be able to state:

• the problem;

• the recommendation;

• the three reasons it wins;

• the key financial result;

• the implementation sequence;

• the major risk;

• the final close.

Part Two: Introduce Disruptions

Ask a coach or teammate to:

• skip a slide;

• turn off the projector;

• announce that two minutes remain;

• interrupt with a difficult question;

• provide the wrong slide;

• remove notes;

• ask a presenter to cover another section;

• challenge a critical assumption.

Part Three: Apply the Recovery Loop

For each disruption: Pause → Assess → Prioritise → Act → Reconnect.

Part Four: Classify the Problem

Was it:

• minor;

• noticeable but manageable;

• material;

• critical?

Did the response match its severity?

Part Five: Review Team Support

Ask:

• Did teammates remain composed?

• Did anyone over-rescue?

• Was a material error corrected?

• Did the team avoid blame?

• Was the story restored?

Part Six: Review Strategic Protection

Did the team preserve:

• the recommendation;

• the value;

• the implementation;

• the close?

Part Seven: Conduct an After-Action Review

Discuss:

• what happened;

• what worked;

• what made recovery difficult;

• what the team will do differently.

Part Eight: Repeat the Scenario

Run the same disruption again. The goal is not merely to discuss the better response. It is to experience delivering it.

Reflection Questions

1. What disruption is your team least prepared to handle?

2. Can every presenter continue without slides?

3. Does everyone know the central story?

4. Which errors require correction?

5. Which errors should be left behind?

6. What content will be removed under time pressure?

7. How will the team protect the recommendation and close?

8. Who can cover each section?

9. When should a teammate intervene?

10. How will the team correct a material number?

11. What physical reset helps each presenter regain composure?

12. Does the team have a technology backup?

13. Has the team practised realistic disruptions?

14. Does the team review recovery without blame?

15. What evidence from past recovery should increase your confidence?

Chapter Summary

Recovery is one of the defining capabilities of outstanding case competitors. A disciplined recovery follows: Pause → Assess → Prioritise → Act → Reconnect. Strong teams:

• distinguish minor disruptions from material errors;

• protect the central recommendation;

• correct important information honestly;

• compress rather than rush;

• continue without unnecessary dependence on slides;

• support teammates without highlighting mistakes;

• reconnect the audience to the story;

• practise uncertainty before the competition.

The objective is not perfect execution. It is maintaining leadership when execution becomes imperfect.

Key Takeaways

✓ Mistakes and disruptions are inevitable.

✓ Confidence grows through successful recovery, not the absence of difficulty.

✓ Preparation creates flexibility; memorisation creates fragility.

✓ Shift attention from how you look to what the audience needs.

✓ Use the recovery loop: Pause, Assess, Prioritise, Act, and Reconnect.

✓ Match the response to the seriousness of the problem.

✓ Continue through minor errors without advertising them.

✓ Correct material errors briefly and clearly.

✓ Never allow one mistake to create several more.

✓ Return to message anchors when you lose your place.

✓ Prepare to communicate the recommendation without slides.

✓ Compress content rather than speaking faster.

✓ Protect the recommendation and the close.

✓ Support teammates without blaming, contradicting, or over-rescuing.

✓ Treat assumption challenges as opportunities to demonstrate judgment.

✓ Build technology and presenter redundancy where possible.

✓ Practise disruptions through safe, progressive pressure.

✓ Use after-action reviews to turn experience into improvement.

✓ Recovery under pressure is not only a presentation skill. It is leadership practice.

Looking Ahead

Recovering well allows the team to maintain control of its message. The next chapter explores another real-time leadership skill: how to read the judges, interpret their reactions, and adapt your communication without abandoning the strategy. Understanding the people across the table helps a strong team turn a prepared presentation into a responsive executive conversation.