Chapter 32: Mastering Q&A - Turning Questions into Opportunities
Chapter 32: Mastering Q&A—Turning Questions into Opportunities
Video:ideo: Master the Q&A: Never Lose Points in the Scariest Part of Your Case Presentation
The question-and-answer session is not an interrogation. It is your final opportunity to strengthen the judges’ confidence in your recommendation.
Learning Objectives
By the end of this chapter, you should be able to:
-
understand what judges are evaluating during Q&A;
-
recognise why a judge is asking a particular question;
-
distinguish among clarification, validation, assumption, scenario, trade-off, implementation, and challenge questions;
-
listen for both the stated question and the underlying concern;
-
organise direct, concise, and evidence-based responses;
-
think clearly under pressure;
-
communicate assumptions and uncertainty honestly;
-
respond professionally when you do not know the answer;
-
manage multi-part, ambiguous, or repeated questions;
-
disagree with a judge respectfully;
-
route questions among teammates without confusion;
-
avoid unnecessary additions and contradictions;
-
use appendix slides selectively;
-
recover from incomplete or incorrect responses;
-
use Q&A to reinforce the recommendation rather than merely defend it.
Why This Matters
For many teams, the presentation feels like the finish line.
It is not.
The question-and-answer session is the final stage of the decision conversation. It is where judges determine whether the recommendation is:
-
genuinely well supported;
-
financially understood;
-
operationally realistic;
-
resilient under uncertainty;
-
owned by the entire team;
-
adaptable when conditions change.
A prepared presentation shows what the team planned to say.
Q&A reveals:
-
how deeply the team understands the solution;
-
how members think without a script;
-
whether assumptions can withstand challenge;
-
whether the team can remain aligned;
-
whether judges should trust the presenters with an important decision.
Some teams fear questions because they assume every question exposes a weakness.
Experienced competitors recognise something different: questions often indicate interest. Judges may be giving the team an opportunity to explain something the presentation did not have time to cover.
The objective is not to survive Q&A.
It is to use the conversation to deepen confidence in the recommendation.
Discover Your Mad Skills Principle
Questions are not obstacles. They are invitations to demonstrate your thinking.
A difficult question does not automatically mean the judge dislikes the recommendation. It may mean the judge wants to understand:
-
how you reached the conclusion;
-
what assumptions support it;
-
where its limits are;
-
whether another option was considered;
-
how the strategy adapts;
-
whether your team remains credible under pressure.
Q&A Is a Continuation of the Presentation
Do not treat Q&A as a separate event in which the judges suddenly become opponents.
The presentation established:
-
the problem;
-
the recommendation;
-
the evidence;
-
the implementation;
-
the expected impact.
Q&A allows the judges to explore those elements more deeply.
Your role remains the same: help the audience make a better decision.
What Judges Are Really Evaluating
Judges may be evaluating more than the technical accuracy of an answer.
They observe:
Strategic Thinking
Can the team connect the question to the organisation’s objectives and strategic choices?
Analytical Depth
Does the team understand the evidence, assumptions, and calculations behind the slides?
Judgment
Can the team make a reasonable decision when information is incomplete?
Listening
Does the presenter answer the question actually asked?
Adaptability
Can the recommendation respond when conditions change?
Teamwork
Does the team appear aligned, coordinated, and mutually supportive?
Composure
Can presenters remain calm when challenged?
Honesty
Will the team acknowledge uncertainty rather than invent an answer?
Professionalism
Can the team disagree respectfully and communicate under pressure?
The answer matters. How the team reaches and communicates it also matters.
Why Judges Ask Questions
Understanding the purpose behind a question helps you respond effectively.
1. Clarification
The judge wants to understand something that was unclear or presented quickly.
Examples:
-
“Which customer segment are you targeting first?”
-
“Is this a pilot or a national launch?”
-
“What does the $280,000 include?”
Respond directly. Do not repeat the entire presentation.
2. Validation
The judge wants evidence supporting a claim or choice.
Examples:
-
“Why did you select Calgary?”
-
“Why is partnership preferable to acquisition?”
-
“How did you calculate the payback period?”
Reinforce the relevant analysis and assumptions.
3. Stress Testing
The judge wants to understand the limits of the recommendation.
Examples:
-
“What happens if adoption is half your forecast?”
-
“What if the partner withdraws?”
-
“What if implementation costs are 30% higher?”
Show how the strategy adapts, where the threshold lies, and what action follows.
4. Alternative Perspective
The judge sees the case through another professional lens.
Examples:
-
an operations executive asks about fulfilment;
-
a financial executive asks about cash flow;
-
a marketer challenges customer adoption;
-
a regulator questions compliance;
-
a community leader raises stakeholder impact.
Recognise the legitimacy of the perspective and respond through that lens.
5. Trade-Off Exploration
The judge wants to understand what the recommendation sacrifices.
Examples:
-
“Does the partnership reduce control?”
-
“Would a premium strategy exclude price-sensitive customers?”
-
“What are you choosing not to do?”
Acknowledge the trade-off and explain why it is acceptable.
6. Assumption Testing
The judge wants to understand what must be true.
Examples:
-
“Why did you assume an 8% conversion rate?”
-
“What supports your retention forecast?”
-
“How confident are you in the market size?”
Identify:
-
the source;
-
the level of confidence;
-
the sensitivity;
-
the plan for validation.
7. Curiosity
The judge may simply find the recommendation interesting.
Examples:
-
“How might this scale nationally?”
-
“Could the model work for institutional customers?”
-
“What would Phase Two look like?”
Not every question is a challenge. Some invite the team to extend its thinking.
Diagnose Before You Respond
The words in the question may not reveal the full concern.
For example:
“Did you consider outsourcing?”
The underlying concern may be:
-
Did you evaluate implementation alternatives?
-
Does the organisation have the required capability?
-
Could the solution be delivered more cheaply?
-
Have you considered speed and flexibility?
A strong response answers the stated question and addresses the underlying concern.
The LPTAC Framework
Use the LPTAC framework to manage the response process.
Listen
Listen to the complete question.
-
Do not interrupt.
-
Do not assume where the judge is going.
-
Maintain eye contact.
-
Listen for multiple parts.
-
Notice whether the judge is asking for a fact, judgment, assumption, or response to a scenario.
The second half of the question may change the meaning of the first.
Pause
Take a moment.
Silence feels longer to the presenter than it does to the audience.
A brief pause communicates thoughtfulness. It also gives the team time to determine:
-
who should answer;
-
what the judge is really asking;
-
which evidence matters.
Do not begin speaking simply because silence feels uncomfortable.
Think
Identify:
-
the direct question;
-
the underlying concern;
-
the answer;
-
the strongest evidence;
-
the implication for the recommendation.
If the question has several parts, organise them before responding.
Answer
Begin with the conclusion.
Then provide the most relevant reasoning or evidence.
For example:
“Yes, we evaluated outsourcing. We rejected it as the primary model because the expected cost savings were modest while dependency and service risk increased. We instead use the regional partner for distribution while retaining control of the customer experience.”
The direct answer comes first.
Confirm
Where useful, confirm that the response addressed the concern.
Examples:
-
“Does that address the distinction you were asking about?”
-
“Would you like us to expand on the financial assumption?”
-
“Was your concern primarily adoption or the timing of expansion?”
Do not end every answer with “Does that answer your question?” Repetition can sound uncertain. Use confirmation when:
-
the question was ambiguous;
-
the judge asked several parts;
-
the concern appears unresolved;
-
clarification would improve the discussion.
The Direct-Answer Structure
LPTAC manages the thinking process. The spoken response can use three parts:
Answer → Evidence → Implication
Answer
Give the conclusion.
Evidence
Explain the key reason, fact, or assumption.
Implication
Connect the response to the recommendation or action.
Example:
Answer: “The recommendation remains viable if adoption is 20% below our base case.”
Evidence: “At that level, the pilot remains above operating break-even, although payback extends beyond 22 months.”
Implication: “We would delay expansion and refine customer acquisition before committing additional capital.”
This structure keeps answers focused.
Answer the Question Asked
One of the most important Q&A rules is:
Answer the question the judge asked—not the question you hoped they would ask.
If the judge asks:
“What is your greatest implementation risk?”
Do not begin with:
“Before answering that, let me explain why our recommendation is strategically attractive.”
Answer:
“The greatest implementation risk is customer adoption.”
Then explain it.
Long detours can make the judge feel unheard.
Begin With Yes, No, a Number, or a Position
When appropriate, start with the direct response.
Examples:
-
“Yes, we considered acquisition.”
-
“No, we would not expand nationally at this stage.”
-
“The pilot requires an initial investment of $280,000.”
-
“Customer adoption is the most important risk.”
-
“We would continue the pilot but delay expansion.”
The explanation can follow.
Avoid beginning with:
-
extensive background;
-
repeated appreciation for the question;
-
a framework definition;
-
several qualifications;
-
“It depends” without explaining what it depends on.
When the Answer Is “It Depends”
Sometimes “it depends” is the correct response. Complete it.
Weak:
“It depends on the market.”
Stronger:
“It depends primarily on customer acquisition cost. If acquisition remains below $120 per customer, the expansion meets our return requirement. Above that threshold, we would revise the channel strategy before expanding.”
Explain:
-
what it depends on;
-
why that factor matters;
-
what decision follows.
Types of Questions and How to Answer Them
Clarification Questions
Be concise.
“The initial pilot is limited to Calgary. Edmonton becomes the next market only after the pilot achieves the customer, margin, retention, and service thresholds.”
Do not repeat the entire market-entry strategy.
Financial Questions
Use numbers accurately and explain assumptions.
A strong financial response may contain:
-
the number;
-
the calculation or assumption;
-
the sensitivity or threshold;
-
the decision implication.
“The pilot requires $280,000 in initial investment. Under our base case, it produces $156,000 in annual operating profit and approximately 22-month payback. Adoption is the most sensitive input, which is why further investment is contingent on achieving at least 1,200 active customers.”
Never invent a precise financial result.
Strategic Questions
Reconnect to:
-
the objective;
-
where to play;
-
how to win;
-
the trade-off;
-
organisational capability.
“We selected partnership because the objective is not simply market access. It is to validate profitable demand while preserving financial flexibility. Owned entry provides more control but commits significant capital before that demand is proven.”
Implementation Questions
Show:
-
sequence;
-
owner;
-
resources;
-
dependencies;
-
timing;
-
decision gates.
“The COO owns operational readiness. Systems integration and fulfilment testing occur before employee training and pilot launch. The launch will be delayed if the service-readiness threshold is not achieved.”
Risk Questions
Identify:
-
the risk;
-
probability or seriousness;
-
mitigation;
-
trigger;
-
contingency.
“The greatest risk is adoption below the level required for profitable expansion. We reduce that risk through a six-month pilot. If active customers remain below 1,200, we delay expansion and revise the offering and channel mix.”
Ethical or Stakeholder Questions
Acknowledge competing interests.
Avoid treating ethical concerns as public-relations problems.
A useful structure is:
-
identify the affected stakeholders;
-
acknowledge the tension;
-
explain the principle guiding the decision;
-
describe the mitigation or protection.
“Automation improves productivity but may displace employees. We would therefore stage implementation, prioritise retraining and redeployment, and measure both financial benefits and employee outcomes.”
“What If?” Questions
Do not reject the scenario simply because it differs from your assumptions.
Use:
Change → Effect → Response
“If implementation costs increase by 30%, payback extends beyond our preferred period. We would preserve the pilot but postpone the next market, reduce discretionary launch spending, and reassess the partnership economics before committing further capital.”
This demonstrates adaptability.
Alternative Recommendation Questions
A judge may ask:
“Why not acquire a regional competitor?”
Respond by comparing the alternatives using the decision criteria.
“Acquisition provides immediate scale and control, but it requires significantly more capital and creates integration risk. Because the company’s priority is validating demand while protecting liquidity, partnership provides the stronger balance under current conditions.”
Do not dismiss the alternative as unreasonable if it was genuinely credible.
Future Opportunity Questions
Separate current recommendation from future consideration.
“We would not build owned distribution now because regional volume remains unproven. If multiple regional markets become profitable and delivery scale supports the fixed investment, owned infrastructure becomes a legitimate future consideration.”
This preserves strategic focus.
Multi-Part Questions
When a judge asks several questions:
-
identify the parts;
-
repeat them briefly if necessary;
-
answer in order;
-
signal the transitions.
“There are two parts to that question: affordability and operational capacity. On affordability… On capacity…”
If you cannot remember every part:
“I heard the questions on financing and implementation timing. Could you repeat the third part?”
That is better than ignoring part of the question.
Ambiguous Questions
Clarify before answering.
“When you refer to scale, are you asking about customer volume within Calgary or expansion into additional markets?”
A concise clarification prevents a long answer to the wrong question.
Questions With a False Premise
Correct the premise respectfully.
“I agree that customer acquisition cost is a concern. One clarification is that our model does include acquisition spending within the $280,000 pilot budget. The remaining uncertainty is whether the cost per acquired customer stays below the expansion threshold.”
Avoid:
“That’s not correct.”
Focus on clarifying the evidence rather than defeating the judge.
Leading Questions
A judge may ask:
“Wouldn’t acquisition obviously be faster?”
Do not feel forced to agree with the premise.
“Acquisition would provide faster access to operating assets. However, it would not necessarily provide the best risk-adjusted path because integration and capital requirements are substantially higher. Under the company’s current liquidity constraints, partnership remains the stronger choice.”
Repeated Questions
A repeated question may mean:
-
the first response was unclear;
-
the judge disagrees;
-
the judge is testing consistency;
-
the judge wants a more direct answer;
-
the judge is testing composure.
Do not say:
“As I already explained…”
Instead:
“Let me answer that more directly.”
Then simplify or approach the concern from another angle.
When You Do Not Know
Strong teams do not know every answer.
Do not guess or invent evidence.
Use this structure:
What We Know
“The case does not provide regional retention data.”
What We Can Reasonably Infer
“The company’s current retention provides a useful starting benchmark, but regional behaviour may differ.”
What We Would Learn
“The pilot will measure repeat purchasing during the first six months.”
How the Decision Is Protected
“Expansion remains contingent on meeting the retention threshold.”
A concise response might be:
“We cannot determine that definitively from the case information. We used the company’s current retention as a base assumption, tested a downside range, and designed the pilot to validate the regional result before expansion.”
Honesty combined with a learning plan builds credibility.
Do Not Use “More Research” as the Answer to Everything
Saying “we would conduct more research” can become a way to avoid judgment.
Explain:
-
what information is missing;
-
why it matters;
-
how it would be collected;
-
what decision it would change.
For example:
“We would test willingness to pay through a targeted pilot because a price below $75 would weaken the required contribution margin and change the offering design.”
Use the Appendix Selectively
The appendix can support answers with:
-
detailed calculations;
-
scenario analysis;
-
alternative evaluation;
-
market sizing;
-
implementation detail;
-
risk registers;
-
customer research.
Do not jump to an appendix slide for every question.
First answer verbally.
Then, if the visual materially strengthens the explanation:
“We have the sensitivity range in the appendix if it would be useful.”
The appendix supports the answer. It does not replace it.
Know the Appendix
Every team member should know:
-
which appendix slides exist;
-
where important calculations are located;
-
who controls the deck;
-
how to return to the main Q&A anchor slide.
Avoid searching visibly through numerous slides while the judges wait.
Managing Team Responses
Q&A is a team activity.
Before presenting, identify likely ownership for:
-
strategy;
-
customers and marketing;
-
finance;
-
operations;
-
implementation;
-
risk;
-
stakeholders.
Ownership provides a starting point, but it should not become rigid. The person with the strongest answer should respond.
The Primary-Responder Principle
For each question:
-
allow a brief pause;
-
identify the teammate best positioned to answer;
-
let that person provide the complete response;
-
avoid simultaneous speaking.
Do not point visibly, whisper, or hold an extended team conference.
No Contradictions
Another essential Q&A rule is:
Never contradict the presentation or a teammate without clearly correcting a material error.
If a teammate states something differently from your understanding:
-
do not compete publicly;
-
do not provide a second, conflicting answer;
-
clarify only if the difference materially affects the decision.
Use:
“To build on that point, the threshold specifically applies to expansion rather than the initial pilot.”
This clarifies without undermining the teammate.
Use Add-Ons Sparingly
A teammate should add to an answer only when the additional information creates substantial value.
An add-on may be useful if it:
-
corrects a material error;
-
answers an omitted part;
-
provides a critical number;
-
addresses an important risk;
-
resolves visible judge confusion.
Do not add on merely because:
-
you want to speak;
-
you know another detail;
-
the answer could be phrased differently;
-
you want to demonstrate expertise.
Multiple add-ons can make a strong answer appear incomplete and the team appear uncoordinated.
Do Not Answer Every Question as a Group
One clear response is usually stronger than four partial responses.
A disciplined team communicates:
-
confidence in the responder;
-
shared understanding;
-
respect for the judges’ time.
When Judges Disagree
A judge may challenge your conclusion directly.
Remain calm.
Use:
-
acknowledge the concern;
-
identify the point of agreement;
-
explain the reasoning;
-
state what evidence would change the decision.
For example:
“That is a reasonable concern, and we agree that owned entry provides greater control. We prioritised partnership because the company’s limited liquidity makes early capital exposure the more important criterion. If the company had substantially greater available capital and confirmed regional demand, owned entry would become more attractive.”
This demonstrates judgment rather than defensiveness.
Do Not Try to Defeat the Judge
The objective is not to win an argument.
Avoid:
-
dismissing the judge’s experience;
-
becoming sarcastic;
-
speaking aggressively;
-
repeating the same answer more loudly;
-
treating the question as an attack.
Your role is to explain why the recommendation deserves confidence.
Buying Thinking Time
Useful techniques include:
-
pausing;
-
briefly restating the question;
-
identifying two parts;
-
requesting clarification;
-
taking a breath before answering.
Examples:
-
“There are two considerations: financial exposure and operational control.”
-
“Let me answer that in the context of the pilot gate.”
-
“Are you asking about the initial launch or the later expansion decision?”
Avoid repeatedly saying:
-
“That’s a great question.”
-
“Thank you for that excellent question.”
-
“We appreciate the opportunity to answer that.”
Occasional acknowledgement is natural. Repetition sounds rehearsed and consumes time.
Answer Length
A strong answer is usually:
-
direct;
-
complete;
-
concise.
Stop when the question has been answered.
Avoid turning every response into another presentation.
A useful discipline is:
-
conclusion first;
-
one or two supporting points;
-
implication;
-
stop.
Allow the judge to ask a follow-up if they want greater detail.
Recovering From a Weak Answer
Everyone gives imperfect answers.
If you realise your response was incomplete:
“Let me add one important clarification…”
If a number was wrong:
“I need to correct that figure. The initial investment is $280,000, not $250,000.”
If you misunderstood the question:
“I answered that from the perspective of the pilot. I now understand that you are asking about national scale…”
Correct the issue and continue.
Do not spend the next several answers apologising for it.
Recovering as a Team
If a teammate struggles:
-
remain composed;
-
allow them time;
-
avoid visible panic;
-
provide support only when needed;
-
preserve their credibility.
A useful support line is:
“The financial threshold reinforces that point. May I add the specific figure?”
This is better than interrupting with a competing answer.
Preparing for Q&A
Q&A preparation should begin before the presentation is finished.
Build a Question Bank
For every main slide, ask:
-
What would a sceptical judge challenge?
-
Which assumption is vulnerable?
-
What evidence is missing?
-
What trade-off did we make?
-
What would a financial, operational, customer, or ethical judge ask?
-
What happens if the result is worse than forecast?
Prepare the Ten Questions You Hope They Do Not Ask
These are often the questions requiring the most preparation.
They might involve:
-
an optimistic assumption;
-
a missing capability;
-
a weak alternative;
-
an implementation dependency;
-
an ethical concern;
-
a financial inconsistency;
-
the limits of the recommendation.
Do not avoid these questions during practice.
Red-Team the Recommendation
Assign teammates, coaches, or other students to challenge:
-
the root cause;
-
the market choice;
-
the customer assumptions;
-
the financial model;
-
the strategic alternative;
-
the implementation;
-
the risk mitigation;
-
the KPI thresholds.
The purpose is not to destroy confidence. It is to expose weaknesses while the team still has time to improve them.
Practise Different Question Styles
Include judges who are:
-
supportive;
-
sceptical;
-
highly technical;
-
indirect;
-
impatient;
-
conversational;
-
repetitive;
-
focused on one functional area.
Teams that practise only friendly questions may struggle when the tone changes.
Practise Answering Without Slides
This reveals whether the team understands the logic or depends on the deck.
Every teammate should be able to explain:
-
the recommendation;
-
why it wins;
-
the major assumptions;
-
the financial result;
-
the implementation sequence;
-
the greatest risk;
-
the expansion threshold.
Practise Follow-Up Questions
The first answer may produce another question.
For example:
-
“Why partnership?”
-
“What if the partner underperforms?”
-
“How would you protect service quality?”
-
“What if the partner rejects the service-level terms?”
Follow-ups test whether the reasoning remains coherent beyond the prepared first response.
Worked Q&A Examples
Question: Why Not Build the Regional Operation Internally?
“Owned entry provides greater long-term control, but it requires substantial capital before demand is proven. Because the company’s immediate objective is to validate profitable regional growth while protecting liquidity, partnership provides the stronger balance. If the pilot establishes sufficient volume and attractive unit economics, owned infrastructure becomes a future consideration.”
Question: What Happens if You Reach Only Half the Expected Customers?
“At half the base forecast, the pilot would fall below our 1,200-customer expansion threshold. We would not proceed to Edmonton. We would extend the pilot, examine conversion and retention, revise the value proposition and channel mix, and reconsider the entry model before committing additional capital.”
Question: What Is Your Greatest Assumption?
“Customer adoption is the most important assumption. The case does not provide a regional conversion rate, so we used an 8% base estimate informed by current performance and tested a downside range. The pilot is specifically designed to validate that assumption before expansion.”
Question: Doesn’t the Partnership Create Too Much Dependency?
“It does create dependency, which is the principal trade-off. We manage it through shared governance, service-level agreements, data-access requirements, and backup distribution planning. That remaining dependency is acceptable because the model avoids the substantially greater capital exposure of owned entry.”
Question: What Would Cause You to Abandon the Strategy?
“We would reconsider the strategy if customer adoption remained below 900 active customers after corrective action, contribution margin fell below the minimum threshold, or the partner repeatedly failed the service standard. Those results would suggest that the market or delivery model cannot support the required economics.”
Winning the Room
The best Q&A sessions feel less like examinations and more like executive discussions.
The team should demonstrate:
-
direct answers;
-
clear reasoning;
-
evidence;
-
adaptability;
-
alignment;
-
intellectual honesty;
-
composure.
Every thoughtful response builds trust.
Every defensive or evasive response weakens it.
Coach’s Lens
During an international competition, a judge repeatedly challenged one presenter with variations of the same question.
The student remained composed, listened carefully, and refined the response without becoming defensive.
After the competition, the judge explained that the repeated questions were not intended to embarrass the presenter. The judge wanted to see how the student handled sustained pressure.
That experience reinforced an important lesson:
Sometimes judges are evaluating your composure as much as your answer.
A repeated question is not permission to become frustrated. It is an opportunity to demonstrate that you can continue thinking professionally when the first response does not end the discussion.
Common Mistakes
Interrupting the Judge
Listen to the complete question.
Answering Too Quickly
Pause and organise the response.
Answering the Wrong Question
Address what was actually asked.
Beginning With Background
Lead with the conclusion.
Giving Long Answers
Stop when the concern has been addressed.
Repeating the Presentation
Add clarity or depth rather than replaying a section.
Becoming Defensive
Treat challenge as part of the decision conversation.
Guessing
Distinguish facts, assumptions, and uncertainty.
Saying “It Depends” Without Explaining
Identify the variable, threshold, and implication.
Using “More Research” as an Escape
Explain what must be learned and how it changes the decision.
Ignoring Part of a Multi-Part Question
Organise and answer each part.
Treating a False Premise Aggressively
Correct it respectfully.
Overusing the Appendix
Answer first; use the slide only if it adds value.
Allowing One Teammate to Dominate
Use the best-positioned responder while demonstrating team depth.
Rigid Question Ownership
Allow flexibility when another teammate has the stronger answer.
Multiple Add-Ons
Add only when there is substantial value.
Contradicting a Teammate
Clarify material differences without undermining the team.
Introducing a New Strategy
Keep responses consistent with the recommendation.
Failing to Connect to the Decision
Explain what the answer means for the recommendation.
Mad Skills Drill
Watch a recording of a previous case competition.
Pause after each judge’s question before hearing the response.
Part One: Diagnose
Identify:
-
the stated question;
-
the likely underlying concern;
-
the question type.
Part Two: Build the Direct Answer
Write:
-
the conclusion;
-
the supporting evidence;
-
the implication.
Part Three: Compare
Listen to the original response.
Ask:
-
Did it answer the question?
-
Was the conclusion first?
-
Was it concise?
-
Did it use evidence?
-
Did it connect to the recommendation?
-
Did it create unnecessary risk?
Part Four: Build a Question Bank
Develop at least two questions for each category:
-
strategy;
-
customer;
-
finance;
-
implementation;
-
risk;
-
ethics and stakeholders;
-
uncertainty.
Part Five: Practise LPTAC
For each question:
-
Listen;
-
Pause;
-
Think;
-
Answer;
-
Confirm where appropriate.
Part Six: Practise “I Don’t Know”
Answer one question for which the case lacks sufficient information.
Include:
-
what is known;
-
what is assumed;
-
what must be learned;
-
how the decision is protected.
Part Seven: Practise Team Routing
Run ten questions rapidly.
Focus on:
-
selecting one primary responder;
-
avoiding overlapping answers;
-
using add-ons only when essential;
-
maintaining team engagement.
Part Eight: Practise Repeated Questions
Have a teammate ask the same concern three different ways.
Respond without:
-
irritation;
-
repeating the same words;
-
weakening the recommendation.
Part Nine: Practise Correction
Intentionally give an incomplete answer, then correct it professionally.
Part Ten: Red-Team the Strategy
Ask:
What is the one question we most hope the judges do not ask?
Then practise answering it until the response is honest, clear, and defensible.
Reflection Questions
-
Why are judges likely to ask questions about this recommendation?
-
Which assumptions are most vulnerable?
-
Can every team member explain why the recommendation wins?
-
Does the team listen completely before answering?
-
Do answers begin with the conclusion?
-
Can the team distinguish the stated question from the underlying concern?
-
How does the team handle multi-part questions?
-
Can members acknowledge uncertainty without sounding unprepared?
-
Who is best positioned to answer each major category?
-
Does the team avoid unnecessary add-ons?
-
Can teammates clarify without contradicting one another?
-
Which appendix slides are most useful?
-
How will the team respond to a repeated question?
-
What evidence would genuinely change the recommendation?
-
Would the judges experience Q&A as a constructive executive conversation?
Chapter Summary
The question-and-answer session is not separate from the presentation. It is the continuation of the decision conversation.
A disciplined response moves through:
Listen → Pause → Think → Answer → Confirm
The spoken answer then follows:
Conclusion → Evidence → Implication
Outstanding teams:
-
listen carefully;
-
diagnose the concern;
-
answer directly;
-
support responses with evidence;
-
acknowledge uncertainty;
-
adapt the recommendation when conditions change;
-
coordinate as a team;
-
remain composed under pressure.
Judges are not evaluating only what the team knows. They are evaluating whether they would trust the team to make and implement difficult decisions.
Key Takeaways
✓ Questions are opportunities to strengthen—not merely defend—the recommendation.
✓ Understand why the judge is asking before deciding how to answer.
✓ Listen to the complete question and never interrupt.
✓ Use LPTAC: Listen, Pause, Think, Answer, and Confirm.
✓ Begin with the conclusion.
✓ Answer the question asked rather than the question you hoped to receive.
✓ Support the response with the most relevant evidence.
✓ Address the underlying concern without avoiding the direct question.
✓ For scenarios, explain the change, effect, and response.
✓ Explain assumptions, ranges, and decision thresholds honestly.
✓ When information is missing, distinguish what is known, inferred, and still to be learned.
✓ Use the appendix selectively and answer verbally first.
✓ Select one primary responder for each question.
✓ Add to a teammate’s response only when it creates substantial value.
✓ Never contradict the presentation or a teammate unnecessarily.
✓ Disagree with judges respectfully.
✓ Correct weak or inaccurate responses briefly and professionally.
✓ Practise difficult, repeated, ambiguous, and follow-up questions.
✓ Composure builds credibility.
Looking Ahead
Even the best-prepared teams encounter moments they did not expect:
-
technology failures;
-
missing slides;
-
forgotten points;
-
interruptions;
-
time warnings;
-
weak answers;
-
sudden changes in direction.
The final chapter focuses on what happens when the plan breaks.
It asks:
How can a team recover quickly, remain credible, and continue leading the room when the presentation no longer unfolds as expected?