Chapter 25: Risk and Mitigation

Chapter 25: Risk and Mitigation - Making the Recommendation Resilient

Video: Risks & Mitigations That Actually Strengthen Your Recommendation: Don't Hide Them - Integrate Them

Learning Objectives

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

• identify strategic risks
• distinguish risk from impact
• prioritise risks
• develop practical mitigations
• integrate mitigation into implementation
• communicate risk honestly without undermining the recommendation

Why This Matters

Many teams treat risk as a final slide: "Here are some risks." Then they move on. That isn't risk management. A key Masterclass principle about risk is: Risk should never be an afterthought. Risks should appear in the analysis, and mitigations become part of the implementation steps.

Discover Your Mad Skills Principle

Don’t pretend your strategy has no risks. Show that you know how to manage them.

A recommendation becomes more credible when the team acknowledges what could go wrong.

What Is a Strategic Risk?

A strategic risk is something that could materially prevent your strategy from achieving its objectives. Examples might include:

• customer adoption;
• regulatory change;
• technology failure;
• implementation delays;
• cost overruns;
• talent shortages;
• competitor response;
• supply disruption.

Risk ≠ Impact

One important distinction in your existing material is that teams often confuse probability and impact. Think about two dimensions:

• Probability: How likely is the risk?
• Impact: How damaging would it be if it happened?

A low-probability, catastrophic risk may deserve more attention than a high-probability, minor risk.

Prioritise 

Focus on the risks that matter most. A simple approach:

Risk	Probability	Impact	Priority
Customer adoption	High	High	1
Cost overrun	Medium	High	2
Competitor response	Medium	Medium	3

Don't create a list of 15 risks. Identify the few that could actually derail the strategy.

Mitigation

A mitigation should be an action.

• Not: "Monitor customer adoption."
• Better: "Launch a six-week pilot with a 15% adoption threshold before full rollout."

Now the mitigation becomes part of the implementation. Each major risk should have a concrete mitigation that appears as an actual step in the timeline, with owners and, where appropriate, budgets.

Coach's Lens

The strongest risk mitigation often comes from the implementation plan itself.

For example:

• Risk: Customers reject the new product.
• Mitigation: Pilot with a defined customer segment before national launch.
• Risk: Technology isn't ready.
• Mitigation: Complete technical validation before committing to full deployment.
• Risk: Costs exceed budget.
• Mitigation: Stage investment based on milestone achievement.

Risk becomes part of strategy.

Common Mistakes

• Listing Every Possible Risk
• Focus on strategic risks.
• Confusing Probability and Impact
• They are different.
• Generic Mitigation
• "Monitor the situation" isn't enough.
• Separate Risk Slide
• Risk should be integrated into the solution.
• Hiding Risk
• Acknowledging risk can increase credibility.

Mad Skills Drill

Identify the top three risks to your recommendation. For each:

1. What could happen?
2. How likely is it?
3. What would the impact be?
4. What can we do to reduce the probability?
5. Where does that mitigation appear in the implementation plan?

If the answer to #5 is nowhere, fix the implementation plan.

Chapter Summary

Strong teams don't eliminate uncertainty. They demonstrate that they have thought through it.

Risk analysis makes the recommendation more honest. Mitigation makes it more resilient.

Key Takeaways

✓ Focus on strategic risks.

✓ Separate probability from impact.

✓ Prioritise.

✓ Create concrete mitigations.

✓ Build mitigations into implementation.

✓ Use risk to strengthen credibility.

Looking Ahead

A plan is not complete simply because it has actions. We also need to know: How will we know whether it is working?