PART X: Q&A

PART X: Q&A

The presentation does not end when the final slide appears. Q&A is where judges test the depth behind the presentation. They may challenge your assumptions, calculations, alternatives, recommendation, implementation plan, risk analysis, or understanding of the case. That does not automatically mean they disagree with you. Often, they are trying to determine: Does this team really understand the decision it is asking us to support?

Part X focuses on three disciplines:

1. Treat Q&A as part of the presentation.

2. Answer clearly and directly before explaining.

3. Demonstrate judgment when the answer is uncertain.

The objective is not to survive the questions. The objective is to use Q&A to strengthen confidence in your recommendation.

Chapter 20: Q&A Is Part of the Presentation

The prepared presentation may be finished. Your work is not. Q&A is where the judges move beyond the story you chose to present and begin exploring the thinking underneath it. They may challenge:

• your assumptions;

• your numbers;

• your recommendation;

• your alternatives;

• your implementation;

• your risks;

• your stakeholder analysis;

• your timing;

• your measures of success;

• your understanding of the case.

This is where the team demonstrates that it owns the solution, rather than simply memorising the presentation.

The Q&A Mindset

Teams sometimes approach Q&A as an interrogation. They think: "How do I defend myself?" That mindset can immediately change:

• tone;

• body language;

• listening;

• response style.

The presenter becomes defensive. A more useful mindset is: "How do I help the judge understand our thinking?" That creates a very different conversation. You are still advising the same decision-maker. It seems you are still explaining the same recommendation. The format has changed.

Q&A Is a Conversation

During the formal presentation, your team controls:

• the order;

• the timing;

• the evidence;

• the transitions.

During Q&A, the judges control the sequence. That requires flexibility. The questions may jump from: Financials → Implementation → Customer → Risk → Financials again. Your job is to maintain the recommendation's logic even when the conversation is no longer linear. This is one reason deep understanding matters more than memorised answers.

Listen Before You Answer

A surprisingly common Q&A mistake is answering the question the team expected rather than the question the judge actually asked. Listen fully. Do not begin constructing your answer halfway through the question. A useful mental sequence is:

LISTEN → UNDERSTAND → ANSWER → SUPPORT → STOP

The final step matters. Once you have answered the question, stop.

The Answer Structure

A useful approach is:

• ANSWER: Respond directly.
• EVIDENCE: Explain why.
• IMPLICATION: Connect the answer back to the recommendation.

Think: ANSWER → EVIDENCE → IMPLICATION. For example:

• Question: "Do you really believe this investment is justified?"
• Answer: "Yes."
• Evidence: "The initiative generates an estimated $4.2 million in incremental annual contribution and has a projected payback of less than two years."
• Implication: "More importantly, it addresses the root cause of the retention problem rather than simply spending more to acquire new customers."

This is strong because the judge does not have to wait for the conclusion.

Answer First

Compare these two responses.

• Response A
  • "Well, when we were looking at the financials, there were several assumptions that we had to make, and one of the things we considered was…"

The judge is still waiting for the answer.

• Response B
  • "Yes. We believe the investment is financially justified."

Then explain. The principle is simple: Don't bury the answer. This is executive communication.

The Shortest Complete Answer

A good Q&A answer is usually not the longest possible answer. It is the shortest complete answer. Your response should provide enough information to:

• answer the question;

• demonstrate your reasoning;

• connect to the case.

Then stop. If the judge wants more detail, they can ask for it. A 30-second answer that directly addresses the concern is often stronger than a two-minute response that wanders through everything the team knows.

Don't Answer Three Questions When One Was Asked

Judges sometimes ask narrow questions. For example: "How did you calculate the customer acquisition cost?" Answer that. Do not use the question as an opportunity to explain:

• your entire financial model;

• your market-sizing analysis;

• the recommendation;

• and implementation.

Stay focused. The audience should feel: They listened to me.

Clarify When Necessary

Sometimes a question is ambiguous. It is better to clarify than to answer the wrong question. For example: "Just to clarify, are you asking about the cost of the initial pilot or the cost of the full rollout?" That is not a weakness. It is good communication. Do not use clarification to delay every difficult question. Use it when genuinely necessary.

When You Don't Know

You will not know every answer. Cases contain incomplete information. Research time is limited. Judges may ask about something the case never addressed. Do not bluff. A useful structure is: "We don't have enough information in the case to answer that definitively. Our assumption was X. If that assumption changed, we would revisit Y." This demonstrates:

• honesty;

• judgment;

• awareness of assumptions;

• adaptability.

That is much stronger than inventing a number.

Separate Facts From Assumptions

When answering, be clear about what comes from the case and what comes from your team's reasoning. For example: "The case tells us the company currently serves 400,000 customers. We assumed a 10% initial adoption rate based on the comparable we used, which gives us roughly 40,000 pilot users." Now the judge can follow the logic. This also makes it easier to challenge the assumption intelligently.

When the Judge Challenges Your Assumption

Suppose the judge says: "I think your 10% adoption assumption is too optimistic." Do not respond: "No, it's realistic." Instead: "That's a fair concern. At 10% adoption, our base case produces the projected return. We also tested a 6% downside case, where the recommendation remains profitable, although the payback extends by approximately eight months." You have answered the concern with evidence. The assumption is no longer a matter of debate; it's a fact.

Don't Become Defensive

A judge may disagree with you. That is okay.

Avoid:

• arguing;

• interrupting;

• changing tone;

• dismissing the concern.

You can disagree professionally. For example: "We considered that alternative. We ultimately rejected it because it requires significantly more capital and capabilities than ACME currently possesses. However, if management's priority shifted toward long-term control rather than near-term return, we would reassess that choice." That demonstrates both conviction and flexibility.

Don't Abandon the Recommendation Too Quickly

There is another danger: agreeing with every judge immediately. A judge challenges the strategy, and the team says: "Yes, actually, you're right. We would probably do that instead." Now the judges may wonder how strongly the original recommendation was developed. Listen to the objection. Consider it. But distinguish between:

• adjusting an assumption;

• acknowledging a risk;

• adding nuance;

• completely abandoning your recommendation.

Your solution should be robust enough to withstand reasonable questioning.

Know Why You Rejected the Alternatives

One of the most common questions is: "Why not Option B?" Do not answer: "Because Option A scored higher." Explain the underlying trade-off. For example: "Option B provides greater long-term control, but it requires almost twice the upfront investment and adds an 18-month capability-building period. Given ACME's current financial position and need for faster impact, we believe the partnership provides the stronger balance of return, speed, and risk." Now the decision matrix has become a strategic argument.

Financial Questions

Teams should be prepared to explain:

• where numbers came from;

• major assumptions;

• cost estimates;

• revenue estimates;

• market size;

• ROI;

• NPV;

• payback;

• sensitivity.

The finance person should not be the only person who understands these numbers. Every teammate should know the financial story. You may not all know every Excel formula. Everyone should understand what the calculations mean.

Implementation Questions

Judges may ask: "Can the organisation actually do this?" Be prepared to explain:

• who owns implementation;

• capabilities required;

• timing;

• resources;

• dependencies;

• decision gates;

• KPIs.

A good answer often connects implementation back to risk: "That's why we recommend a pilot rather than a full launch. It allows ACME to validate adoption, build the operating capability, and limit financial exposure before scaling."

Risk Questions

The strongest teams are comfortable discussing what could go wrong. If asked: "What is the biggest risk?" do not say: "There really aren't any major risks." There are always risks. Instead: "The largest risk is customer adoption. That's why our first phase is designed as a six-month pilot with a 15% adoption threshold before additional capital is committed." That makes the risk analysis strengthen the recommendation.

Stakeholder Questions

Judges may ask:

• Who might resist?

• How will employees respond?

• What will customers think?

• What about regulators?

• Who loses from this recommendation?

Prepare to discuss competing interests. A recommendation is more credible when the team demonstrates an understanding of the people affected by the decision.

Timing Questions

A simple: "Why now?" can be a powerful challenge. Your team should know what creates urgency. Possible answers include:

• declining performance;

• competitor moves;

• regulatory change;

• customer shifts;

• expiring contracts;

• available financing;

• technological change.

Timing should connect back to the case.

Measurement Questions

Be prepared for: "How will you know whether this worked?" A strong answer includes both:

• Leading Indicators
  • Early signals.
    
• Lagging Indicators
  • Outcomes.

For example: "In the pilot, we would track adoption, engagement, and training completion as leading indicators. Ultimately, success is defined by improved retention, incremental contribution, and positive ROI."

Future Questions

Judges may ask: "What comes next?" This is where the future considerations work from Manual 1 become useful. Keep the current recommendation clear. Then explain how success creates later opportunities. For example: "Our recommendation today is the domestic pilot. If it reaches our adoption and profitability thresholds, the next opportunity would be national expansion. We would not recommend committing to that expansion until the pilot validates the economics." This demonstrates strategic sequencing.

The Q&A Preparation Grid

Before presenting, prepare likely questions across ten areas.

Area	Question to Prepare
Strategy	Why this strategy?
Alternatives	Why not Option B?
Financial	How did you calculate this?
Assumptions	What if your assumption is wrong?
Implementation	Can the organisation actually do this?
Risk	What is the biggest threat?
Stakeholders	Who might oppose this?
Timing	Why now?
Measurement	How will you know it worked?
Future	What happens next?

Do not necessarily memorise responses. Prepare the thinking.

Build a Red-Team Session

Before competition, have someone deliberately attack the recommendation. Their job is to challenge:

• your weakest assumption;

• your most optimistic financial number;

• your preferred alternative;

• implementation feasibility;

• stakeholder impact;

• risk.

The team's job is not to "win." The goal is to discover where the recommendation is vulnerable before the judges do.

Q&A Is a Team Activity

When a question is asked, everyone should listen. Do not:

• stare at the person you expect to answer;

• look panicked;

• whisper;

• disengage.

The team is still presenting. One person may answer, but everyone owns the solution.

Who Should Answer?

Generally, the person with the greatest knowledge of the question should respond. Avoid making the process mechanical. You do not need: "Finance question. Sarah." The person who is ready and appropriate can answer. The team should know its strengths well enough that this happens naturally.

Don't Pile On

Suppose a teammate gives a strong answer. Another teammate says: "Just to add to that…" Then another says: "And one more thing…" A concise answer becomes a team speech. Unless something important was omitted, let the answer stand. A complete answer does not need a sequel.

Use Backup Slides When Helpful

Supporting slides may help with questions about:

• detailed financials;

• sensitivity analysis;

• market research;

• competitor comparisons;

• decision matrices;

• implementation;

• risks.

But do not frantically search for a backup slide when a direct verbal answer would be clearer. The slide supports the answer. It should not replace it.

Stay in Role

Most importantly, do not suddenly stop being advisors when Q&A begins. If you presented to Ms Chen, CEO, continue speaking to her as the CEO. Maintain:

• professional language;

• confidence;

• eye contact;

• composure.

Q&A is not the moment when the role-play ends. It is often where the professional credibility becomes most visible.

Discover Your MAD Skills Principle

Q&A is not about proving that the judge is wrong. It is about demonstrating that your thinking is strong.

• Listen.
• Answer clearly.
• Support the answer.
• Connect it to the recommendation.
• Then stop.

The Bottom Line

Approach Q&A as: LISTEN → UNDERSTAND → ANSWER → EVIDENCE → IMPLICATION → STOP. Prepare for questions about:

STRATEGY → ALTERNATIVES → FINANCIALS → ASSUMPTIONS → IMPLEMENTATION → RISK → STAKEHOLDERS → TIMING → MEASUREMENT → FUTURE

And when you do not know: Don't bluff. State what you know, explain your assumption, and show how the decision would change if the assumption changed. That is not weakness. That is judgment.

MAD Skills Drill

I would finish this part with a 10 × 30 Q&A Drill. Prepare ten questions—one from each area in the Q&A grid. Give the team approximately 30 seconds per answer. The objective is not to force every answer into exactly 30 seconds. It is to train three habits:

1. ANSWER FIRST: Did the first sentence actually answer the question?
2. SUPPORT: Did the team provide enough evidence to demonstrate its reasoning?
3. STOP: Did the speaker finish once the question was answered?

Then repeat the exercise with a second round where the questioner deliberately challenges the first response. Finally, ask:

• Did we become defensive?

• Did we contradict ourselves?

• Did we invent information?

• Did we abandon our recommendation too easily?

• Did different teammates give consistent answers?

• Could we explain our assumptions?

• Did we remain in role?

The final test is simple: Can the judges question any part of our solution and still encounter the same logic, the same evidence, and the same recommendation they heard in the presentation? If yes, your team does not simply present the solution. It owns it.