Chapter 22: Making the Recommendation Inevitable

Chapter 22: Making the Recommendation Inevitable -From Evidence to Decision

Video: Recommendation & Implementation That Seals the Win: Make It Realistic, Visual & Unforgettable

Learning Objectives

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

• state a recommendation clearly, confidently, and concisely;

• connect the recommendation directly to the central problem and analysis;

• explain why the selected alternative wins;

• support the recommendation with the strongest strategic, customer, operational, and financial evidence;

• distinguish the recommendation from the strategy, initiatives, and tactics supporting it;

• acknowledge trade-offs without weakening the choice;

• anticipate the most likely objections to the recommendation;

• design a recommendation slide that communicates the decision quickly;

• make the recommendation specific, defensible, and memorable.

Why This Matters

Many teams spend hours analysing the case, generating alternatives, building financial models, and developing implementation plans. Then, at the most important moment in the presentation, they say: "Therefore, we recommend Option B." They immediately advance to the next slide and begin discussing implementation. That misses the decision moment. The recommendation is where your team answers the central question:

What should the organisation do? This is the moment when the judges should understand:

• what you chose;

• why you chose it;

• how it solves the problem;

• why it is stronger than the alternatives;

• what value it will create;

• why the organisation can realistically deliver it.

The recommendation should not be mumbled, rushed, or buried beneath tactics. It deserves emphasis because everything before it builds towards the choice, and everything after it depends upon that choice.

Discover Your MAD Skills Principle

The recommendation should not feel like a surprise. It should feel like the only logical conclusion to the argument you have built.

By the time judges reach the recommendation, they should already understand:

• what the organisation is trying to accomplish;

• what problem prevents it from succeeding;

• what evidence reveals the root cause;

• who is affected;

• what alternatives were available;

• how those alternatives were evaluated;

• what financial and operational conditions matter.

The recommendation completes the logic. It should make the judges think: "Given everything they have shown us, this choice makes sense."

Inevitable Doesn't Mean Certain

Making a recommendation feel inevitable doesn't mean pretending there is no uncertainty or that no other option has merit. Business decisions involve:

• incomplete information;

• assumptions;

• competing objectives;

• opportunity costs;

• risks;

• trade-offs.

A credible recommendation acknowledges these realities. "Inevitable" means that the selected choice is the most defensible conclusion based on:

• the problem;

• the available evidence;

• the organisation's objectives;

• the decision criteria;

• the organisation's capabilities;

• the financial and operational realities;

• the risks and assumptions.

Your recommendation is not the only imaginable choice. It is the strongest choice under the case conditions.

Deciphering Case Characteristics

The emphasis of the recommendation should reflect the nature of the case.

Growth Case

Emphasise:

• where growth will come from;

• why the selected market or customer matters;

• how growth will create long-term value;

• why the organisation can grow profitably.

Turnaround Case

Emphasise:

• the root cause of declining performance;

• which actions must occur first;

• how the recommendation protects cash or stabilises operations;

• when growth can responsibly resume.

Market-Entry Case

Emphasise:

• the selected market;

• the entry method;

• why the market is attractive;

• why the organisation has a right to win;

• how risk will be limited.

Innovation Case

Emphasise:

• the customer problem;

• the distinctive solution;

• how uncertainty will be tested;

• why a pilot or staged commitment is appropriate.

Operational Case

Emphasise:

• the source of inefficiency;

• the operational change;

• its effect on cost, quality, speed, or capacity;

• how service levels will be protected.

Public-Sector or Nonprofit Case

Emphasise:

• the priority outcome;

• the beneficiaries or stakeholders;

• mission alignment;

• resource feasibility;

• public value and accountability.

The recommendation should answer the question the decision maker actually cares about.

The Evidence Chain

A strong recommendation is the final link in a clear chain of reasoning: Case Objective → Core Problem → Root Cause → Critical Insight → Strategic Alternatives → Decision Criteria → Selected Strategy → Expected Impact. For example:

• Objective: Establish profitable regional growth.

• Problem: The company lacks cost-effective access to the new market.

• Root Cause: Building owned infrastructure would require substantial capital before demand is validated.

• Insight: A regional partner can provide distribution, local credibility, and customer access.

• Alternatives: Build, acquire, partner, or delay entry.

• Decision Criteria: Growth potential, financial return, feasibility, speed, and flexibility.

• Selected Strategy: Enter through a partnership-led pilot.

• Impact: Validate demand quickly while limiting capital exposure.

If the recommendation cannot be traced through this chain, the argument may contain a gap.

Build the Recommendation Before Building the Slide

Before designing the recommendation slide, write the recommendation in plain Language. A useful recommendation should answer six questions:

1. What should the organisation do?

2. Where or for whom should it do it?

3. How will the strategic choice work?

4. Why does this alternative win?

5. What impact should it create?

6. What important condition or guardrail applies?

Not every answer must appear in one long sentence. However, the team should be able to articulate all six clearly.

The Recommendation Formula

A practical structure is: We recommend that [ORGANISATION] pursue [STRATEGIC CHOICE] for [priority customer, market, or area] through [KEY MECHANISM], because it [REASON ONE], [REASON TWO], and [REASON THREE]. This will [MAJOR IMPACT], subject to [CRITICAL CONDITION OR GUARDRAIL].

For example: We recommend that the company enter Western Canada through a partnership-led pilot focused initially on time-constrained urban professionals in Calgary. This approach leverages the company's existing meal-kit capabilities, uses the partner's regional distribution network, and limits capital exposure while demand is validated. It is expected to establish a profitable regional position within 24 months, with expansion contingent on customer adoption, contribution margin, and retention thresholds. This recommendation is:

• specific;

• strategic;

• evidence-based;

• measurable;

• conditional where uncertainty exists;

• connected to implementation.

The Core Recommendation and the Supporting Message

If the full recommendation is too long for the opening statement, divide it into two parts.

• Core Recommendation
  • State the choice in one concise sentence.
  • We recommend entering Western Canada through a partnership-led pilot beginning in Calgary.
• Supporting Message
  • Immediately explain why it wins and what it achieves.
  • This approach provides the strongest balance of growth, speed, financial feasibility, and flexibility by combining the company's meal-kit capabilities with the partner's regional reach.

The first sentence answers what. The second answers why.

Recommendation, Strategy, Initiative, and Tactic

The recommendation should remain distinct from the activities used to execute it.

Level	Purpose	Example
Recommendation	States what the organisation should do	Enter Western Canada through a partnership-led pilot
Strategy	Explains where to play and how to win	Focus on urban professionals and win through convenience, local relevance, and partner-enabled distribution.
Strategic initiative	Defines a major programme of work	Activate the regional partner channel
Tactic	Identifies a specific action	Launch in-store demonstrations in 20 partner locations
Metric	Measures performance	Active customers, retention, and contribution margin

A recommendation overloaded with tactics becomes difficult to remember.

• Weak: "We recommend hiring regional staff, redesigning the website, launching social media advertisements, creating promotional discounts, partnering with influencers, and developing new packaging."
• Stronger: "We recommend a partnership-led regional entry strategy designed to validate demand before committing to owned infrastructure."

The tactics belong in implementation.

Support the Recommendation With the Strongest Evidence

Immediately after stating the recommendation, reinforce it with the evidence that matters most. Useful categories include:

• Problem Fit: Why does the recommendation address the root cause rather than a symptom?
• Customer Value: How does it solve the priority customer's problem or improve their experience?
• Strategic Fit: How does it support the organisation's objectives, mission, and long-term direction?
• Competitive Advantage: Why can the organisation win? What makes the approach distinctive or difficult to imitate?
• Capability Fit: Which existing resources, relationships, or competencies support the recommendation?
• Financial Value: What revenue, savings, profit, cash flow, return, or social value is expected?
• Feasibility: Why can the organisation realistically execute the recommendation?
• Risk and Flexibility: How does the recommendation limit downside exposure or preserve the ability to adapt?

You don't need to use every category. Select the three pieces of evidence that most strongly explain why the recommendation wins.

The Three-Proof Test

Ask what are the three pieces of evidence that make this recommendation difficult to argue against? For the partnership-led market entry, they might be:

1. Customer and market proof: The selected region contains a sufficiently large concentration of the priority customer.

2. Capability and feasibility proof: The partnership closes the company's regional distribution gap.

3. Financial proof: The pilot reaches operating break-even at a realistic customer threshold and requires substantially less capital than owned entry.

These proofs should come from different dimensions of the decision. Using three variations of the same financial argument may leave customer or implementation questions unanswered.

One Controlling Insight

Although the recommendation may have several supporting reasons, one insight usually matters most. For example: The company should not invest in owned infrastructure before validating regional demand. That insight explains why the partnership-led pilot wins. The recommendation, financial case, guardrails, and implementation sequence can all connect back to it. Identify the one sentence you want judges to remember. This becomes the controlling message of the recommendation.

Demonstrate Why the Alternative Wins

Don't merely say that the preferred option received the highest score. Explain the decisive trade-off. A useful structure is: Option A provides [ADVANTAGE], but requires [MAJORSCARIFICE]. Option B provides [SELECTED BALANCE OR ADVANTAGE], making it the strongest choice given [CASE PRIORITY]. Option C offers [ADVANTAGE], but doesn't sufficiently address [CENTRAL PROBLEM].

For example: "Owned entry provides greater long-term control but requires substantial capital before customer demand has been proven. Delaying entry protects cash but misses the immediate growth opportunity. A partnership-led pilot provides the strongest balance by enabling rapid market access, limiting upfront investment, and preserving the option to scale after demand is validated." This demonstrates that the alternatives were credible and that the decision involved judgment.

Acknowledge the Trade-Off

Every credible recommendation sacrifices something. The selected strategy may provide:

• speed but less control;

• lower cost but less customisation;

• flexibility but lower immediate scale;

• high return but greater risk;

• stronger impact but slower payback;

• broader reach but a less personalised experience.

Acknowledging the main trade-off increases trust. Use this structure: The recommendation sacrifices [DISADVANTAGE], but this is acceptable because [REASON]. We will manage it through [MITIGATION]. For example: "The partnership model provides less direct control over distribution and customer data. This trade-off is acceptable because it significantly reduces entry cost and execution risk. We will manage it through service-level agreements, shared performance standards, and clearly defined data-access requirements." The weakness has not disappeared, but it has been understood and managed.

Include Guardrails When Uncertainty Matters

If the recommendation depends heavily on uncertain assumptions, make the conditions visible. Examples include:

• expand only if adoption exceeds the minimum threshold;

• proceed only if regulatory approval is obtained;

• maintain a minimum contribution margin;

• stop the pilot if acquisition costs exceed the established limit;

• delay the next phase if implementation milestones are missed.

A conditional recommendation is not weak. It demonstrates disciplined decision-making. 

• Weak: "We are confident this will work."
• Stronger: "The base case supports proceeding with the pilot. Full expansion will occur only if customer adoption, retention, and contribution margin meet the predefined thresholds."

Name the Recommendation

A memorable strategy name can help judges follow the presentation. A useful name should:

• reflect the strategic logic;

• be concise;

• be professional;

• be easy to repeat;

• avoid replacing substance with cleverness.

Examples:

• Partner, Prove, Scale

• Premium Through Partnership

• Stabilise, Strengthen, Grow

• Digital First, Human Always

• Local Access, Scalable Growth

Avoid names that are:

• vague;

• overly dramatic;

• difficult to pronounce;

• disconnected from the strategy;

• based on forced acronyms.

The name should reinforce the recommendation, not conceal it.

When to Reveal the Recommendation

"The recommendation should not feel like a surprise" doesn't mean it must appear only at the end of the analysis. Many strong presentations communicate the recommendation early, then build the argument supporting it. This is an answer-first approach. For example: "We recommend a partnership-led entry into Western Canada. To explain why, we will show that the opportunity is attractive, owned entry creates unnecessary capital risk, and a pilot provides the strongest path to profitable growth." The judges know where the presentation is going. The analysis then earns the conclusion.

Alternatively, some presentations develop the reasoning before formally confirming the recommendation. This can work when the story requires discovery. Whichever structure you choose:

• signal the strategic direction;

• maintain consistency;

• avoid concealing the answer;

• ensure every major section advances the recommendation.

The judges should never wonder what your team believes the organisation should do.

The Recommendation Slide

A recommendation slide should communicate the decision within seconds. A useful structure includes:

Headline

State the recommendation as a conclusion.

• Weak: "Our Recommendation"
• Stronger: "Enter Western Canada through a partnership-led pilot before investing in owned infrastructure"

Strategic Choice

Show:

• where to play;

• how to win;

• the entry or operating model.

Three Reasons It Wins

Use the strongest evidence, such as:

• lower capital exposure;

• faster customer validation;

• strong capability fit.

Expected Impact

Show the most decision-relevant outcomes:

• customer growth;

• financial return;

• implementation period;

• mission or stakeholder outcome.

Guardrail or Trade-Off

Include the most important condition, risk, or threshold. The slide should not contain the entire analysis. It should crystallise it.

Recommendation Slide Example

Partner, Prove, Scale

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

Why it wins

• Uses the partner's established distribution and regional customer access.

• Requires substantially less capital than building owned infrastructure.

• Validates adoption and unit economics before full expansion.

Expected impact

• 2,000 active customers;

• $960,000 in annual incremental revenue;

• approximately 22-month payback;

• scalable regional entry model.

Expansion guardrail

Proceed to the next market only after achieving the required customer adoption, retention, contribution margin, and acquisition-cost thresholds.

Delivering the Recommendation

How the recommendation is spoken matters.

Pause Before the Recommendation

Create a deliberate transition: "Based on this analysis and the alternatives evaluated, our recommendation is…" Pause briefly. Then state the recommendation clearly.

Use Direct Language

Say: "We recommend…" Avoid:

• "We were kind of thinking…"

• "One possibility might be…"

• "We feel that perhaps…"

• "Option B seems pretty good…"

Slow Down

Don't rush through the most important sentence in the presentation.

Emphasise the Choice

Use your voice to highlight:

• the strategic direction;

• the priority customer or market;

• the key reason it wins.

Transition Deliberately

After establishing the recommendation, move into implementation: "We have shown why this is the strongest strategic choice. We will now explain how the organisation can execute it." That keeps strategy and implementation distinct.

Test the Recommendation for Clarity

Ask someone unfamiliar with the case to read or hear the recommendation once. Then ask:

• What are we recommending?

• Who or where is the focus?

• Why does it win?

• What result should it create?

• What important condition applies?

If they cannot answer, the recommendation may be too vague, complicated, or overloaded.

Test the Recommendation for Specificity

Replace vague Language with clear choices.

Vague	Specific
Improve customer experience	Redesign onboarding for first-time institutional customers
Expand internationally	Enter Western Canada through a regional partnership
Invest in digital	Build a mobile ordering channel for time-constrained urban customers
Improve sustainability	Reduce packaging waste through a reusable container pilot
Increase marketing	Focus acquisition spending on the two highest-value customer segments
Strengthen operations	Centralise fulfilment and automate the highest-volume process stages

Specificity makes the recommendation easier to evaluate and implement.

Test the Recommendation Against the Analysis

For every phrase in the recommendation, ask:

• What evidence supports this?

• Which analysis produced that evidence?

• Which customer problem does it solve?

• Which organisational capability enables it?

• Which financial result justifies it?

• Which risk could undermine it?

If the recommendation introduces a major idea that did not appear in the analysis, it may feel disconnected or surprising.

Anticipate the Judge's Objections

Before finalising the recommendation, identify the strongest argument against it.

Likely objections include:

• The organisation cannot afford it.

• Customers may not adopt it.

• Competitors can copy it.

• The organisation lacks the required capabilities.

• The implementation period is unrealistic.

• Stakeholders will resist.

• The financial return depends on optimistic assumptions.

• The partnership creates too much dependency.

• The recommendation doesn't address the root cause.

Then prepare a concise, evidence-based response. A strong team doesn't ask: "How can we make the recommendation look perfect?" It asks: "Where is the recommendation most vulnerable, and how will we manage that vulnerability?"

The Red-Team Test

Assign one team member to challenge the recommendation as if they were a sceptical judge. Ask them to argue:

• why another alternative should win;

• why the financial assumptions are too optimistic;

• why implementation will fail;

• why stakeholders will resist;

• why the competitive advantage will not last.

The rest of the team must respond using evidence. If the recommendation cannot survive internal challenge, it is not ready for the presentation.

Keep the Story Consistent

The recommendation should match:

• the problem statement;

• the analytical insights;

• the personas and customer journey;

• the alternatives;

• the decision criteria;

• the financial model;

• the strategic choice;

• the implementation plan;

• the risks and metrics.

Common inconsistencies include:

• identifying one customer as the priority but recommending tactics for another;

• selecting an option because it limits risk, then proposing a high-risk implementation;

• promising premium differentiation while relying on price discounts;

• forecasting one level of adoption in the financial model and another in the implementation plan;

• describing a pilot but budgeting for national expansion.

Judges notice these contradictions.

Coach's Lens

You don't need to repeat the entire analysis when presenting the recommendation. The recommendation slide is not another ten-minute summary. It is the moment to emphasise the few pieces of evidence that decide the case. Ask what the three reasons are that this recommendation is difficult to argue against. Then ask what the single strongest argument against it is. The first question sharpens your recommendation. The second prepares you for Q&A. Strong teams communicate confidence without pretending the decision is risk-free. They understand why the recommendation wins, what it sacrifices, and what evidence would cause the organisation to change direction.

Common Mistakes

• The Surprise Recommendation: The judges should not encounter a new strategic direction at the end of the analysis.
• Rushing the Decision: Don't mumble the recommendation and immediately advance to implementation.
• Recommending "Option B": Use the strategic choice rather than the label assigned in the decision matrix.
• Generic Language: "Improve customer experience" is an aspiration, not a sufficiently specific recommendation.
• Too Much Detail: Don't overload the recommendation with every action, timeline, and metric.
• Too Little Detail: "Enter the market" doesn't explain where, how, or why.
• No Evidence: The recommendation must connect to the analysis.
• Repeating All the Evidence: Select the evidence that determines the decision rather than summarising every framework.
• Confusing Strategy With Tactics: Keep the strategic choice distinct from the actions used to execute it.
• Ignoring the Alternatives: Explain why the recommendation is stronger than the other credible paths.
• Hiding Trade-Offs: Pretending the recommendation has no weaknesses reduces credibility.
• Unsupported Impact Claims: Don't promise dramatic results without explaining the assumptions behind them.
• Excessive Conditions: Guardrails strengthen a recommendation, but too many conditions can make it sound indecisive.
• A Clever Name Without Substance: Branding cannot compensate for weak strategic logic.
• Inconsistent Numbers: The recommendation, financial model, implementation plan, and final summary must use the same figures.

MAD Skills Drill

Take the strategic choice developed in Chapter 21.

Part One: Write the Core Recommendation

Complete: We recommend… Use no more than one sentence.

Part Two: Add the Strategic Focus

Clarify:

• where the organisation will play;

• who it will serve;

• how it will win.

Part Three: Identify the Three Proofs

Write three bullets explaining why the recommendation wins. Use evidence from different dimensions, such as:

• customer;

• strategy;

• capability;

• finance;

• feasibility;

• risk.

Part Four: Identify the Controlling Insight

Complete: The most important reason this recommendation wins is…

Part Five: State the Impact

Identify:

• one customer or stakeholder result;

• one financial or quantitative result;

• one strategic or operational result.

Part Six: Acknowledge the Trade-Off

Complete: This recommendation sacrifices… Then explain why the trade-off is acceptable and how to manage it.

Part Seven: Establish the Guardrail

Complete: We will proceed or expand only if…

Part Eight: Challenge the Recommendation

Ask a teammate to argue for the second-place alternative. Defend the recommendation without referring to the total decision-matrix score.

Part Nine: Deliver It

Present the recommendation aloud in no more than 45 seconds. Ask your teammates:

• Was the choice clear?

• Did the reasons support the choice?

• Was the impact memorable?

• Did I sound confident?

• What question would you ask next?

Reflection Questions

1. Can every team member state the recommendation in the same way?

2. Does the recommendation directly answer the case question?

3. Is the strategic choice specific?

4. Which three pieces of evidence support it most strongly?

5. What is the single most important reason it wins?

6. What does the recommendation sacrifice?

7. What is the strongest argument against it?

8. Which assumption could change the decision?

9. Does the financial model support the expected impact?

10. Can a judge understand the recommendation within ten seconds?

11. Does every implementation initiative clearly support the recommendation?

12. What do you want the judges to remember after the presentation ends?

Chapter Summary

The recommendation is the decision moment of the case. A strong recommendation connects: Problem → Insight → Alternatives → Evaluation → Strategic Choice → Evidence → Impact. It should clearly communicate:

• what the organisation should do;

• where and for whom it should do it;

• how the strategic choice will work;

• why it is stronger than the alternatives;

• what value it will create;

• what trade-off it requires;

• what condition or guardrail must be monitored.

The goal is not merely to announce the answer. It is to help the judges understand why this is the best answer based on the available evidence.

Key Takeaways

✓ The recommendation should feel like the logical conclusion of the argument.

✓ State the strategic choice directly and confidently.

✓ Don't refer to the recommendation only as "Option B."

✓ Explain where the organisation will focus and how it will win.

✓ Support the recommendation with the three pieces of evidence that matter most.

✓ Connect the choice to the root cause, customer need, organisational capabilities, and financial results.

✓ Demonstrate why the recommendation is stronger than the other credible alternatives.

✓ Acknowledge the main trade-off and explain how it will be managed.

✓ Use guardrails when the decision depends on uncertain assumptions.

✓ Keep the recommendation separate from the initiatives and tactics used to implement it.

✓ Make the recommendation slide easy to understand within seconds.

✓ Deliver the recommendation slowly, clearly, and with confidence.

✓ Prepare for the strongest argument against your choice.

✓ Ensure the recommendation remains consistent with every part of the presentation.

Looking Ahead

The recommendation establishes:

• what the organisation should do;

• why the choice wins;

• what value it should create;

• what conditions must hold.

The next step is to prove that the organisation can make it happen. The following chapter turns the recommendation into an implementation plan by determining what must happen, in what sequence, by whom, with which resources, and how progress will be measured.