How partners run cases, and handling pushback
What changes in final rounds, the shape of a partner answer, and when to hold or update your view.
Key takeaways
- In a partner case the numbers are only the support. What is being tested is whether you reach a clear view quickly, say it simply, and hold it or change it for the right reasons.
- The pushback contained no new fact, so there was nothing to update on.
- This pushback contained a real fact. Ignoring it looks rigid.
- Common mistakes in partner cases: Waiting for more data before giving any view.
This is part of the expert track. It assumes you have worked through the foundation lessons (structuring, case math, exhibits, synthesis) and several case types, and that you have run a few cases out loud. If not, start there and come back.
Key idea
In a partner case the numbers are only the support. What is being tested is whether you reach a clear view quickly, say it simply, and hold it or change it for the right reasons.
The lesson "Partner interviews and final rounds" in the Final rounds and offers module covers what partners look for and what to ask them. This lesson goes one level further: how a partner actually runs the case in the room, and how to answer when they push back.
How partners often run a case
Patterns candidates often report from final rounds (they vary by firm, office, and person)
- Open questions with no neat structure: "Our client is thinking about closing a factory. What would you tell the CEO?" There may be no exhibit and only two or three numbers.
- Judgment over calculation: a partner may accept a rough number if it is clearly labeled and asks "so what does that mean?" straight after.
- Early requests for a view: "Forget the analysis. If you had to decide now, what would you do?" can come in the first five minutes.
- Challenge and pushback: "I do not buy that" or "The CEO will hate this" to see whether you give in at once, refuse to move, or think it through.
- Real-world detail: the case may be loosely based on the partner's own work, so they may add facts you could not have known.
- A blend of fit and case: in many offices a partner moves between a story about you and the case, or asks "have you ever had to make a call like this?" in the middle.
What changes compared with a first round
- Less time on the structure, more on the answer. A clean three-bucket structure said in under a minute is usually enough; the partner wants to get to the view.
- Fewer numbers, more so-what. Each number you compute should end with one sentence on what it means for the decision.
- Stakeholders matter. Partners often ask about the CEO, the board, the staff, or a regulator. A recommendation that ignores them sounds junior.
- Conversation, not a script. Treat the partner as a client you are advising, not an examiner you are answering.
"I would tell the CEO to do X. Three reasons: first..., second..., third.... The main risk is..., and I would manage it by.... The next step is.... What would change my mind is...." The last sentence is the one most candidates leave out, and it is often what a partner remembers.
Holding a position under pushback, and when to update
Four moves when a partner pushes back
- 1Restate the challenge in one sentence, so you are sure what it is: "So the concern is that investors will read the closures as failure."
- 2Ask yourself whether the pushback contains a new fact or only tests your conviction. "Commuters are coming back" is a new fact. "I do not buy it" is not.
- 3If there is no new fact, hold your view calmly and give the reason again with its number. Offer what would change your mind.
- 4If there is a new fact, test it out loud, then say clearly whether it changes your answer, your plan, or nothing: "That changes how we do it, not whether."
Partner: "I do not buy it. I think we should keep all the stores open."
Weaker answer
"You may be right. Maybe we should keep them open and see what happens."
Stronger answer
"I understand the instinct. My view is still to close them, because they lose about GBP 3.6 million a year and closing pays back in about two years. What would change my mind is evidence that sales in those stores can rise by about half. Do you have a reason to expect that?"
Why the stronger answer wins: The pushback contained no new fact, so there was nothing to update on. The strong answer holds the view with its reason, stays polite, and invites the partner to share a fact. The weak answer gives up the view, which suggests it was never based on anything.
Partner: "Our data team says our own payment data predicts risk better than a bank's credit score."
Weaker answer
"I still think the answer is no. My analysis showed the risk is too high."
Stronger answer
"That is new and it matters. It makes a low loss rate more believable, although it is not yet proven. So I would keep my answer but change the plan: run a test with the users the model rates safest, and scale if losses stay below break-even."
Why the stronger answer wins: This pushback contained a real fact. Ignoring it looks rigid. The strong answer says exactly what the fact changes (the plan) and what it does not (the need to prove the loss rate).
Waiting for more data before giving any view. Answering "it depends" without saying on what. Treating every challenge as a test to resist, or every challenge as a signal to give in. Talking about the analysis instead of the decision. Forgetting the people: the CEO, the staff, the customers, the regulator.
Practice
You have recommended closing 30 loss-making stores. The partner says: "Closing 30 stores will look like failure to our investors." Answer out loud in under 30 seconds, then reveal a model answer.
You recommended against a new product because demand looked weak. The partner says: "Our biggest customer told us last week they would buy it if we launched." Answer out loud in under 30 seconds: does this change your answer, your plan, or nothing?
A partner asks: "A client is thinking about moving its head office out of the capital city to save rent. What would you tell the CEO?" You have no data. Give a view in under 60 seconds: answer, three reasons, main risk, next step, and what would change your mind.
A partner says "I do not agree" but gives no new information. What is the best response?
Which change from first rounds do candidates most often report in partner cases?
The partner adds a fact that weakens one of your three reasons. What should you do?
Sources for this lesson (1)
- Recognized public explanations of case-interview concepts and frameworks
My notes on this lesson
0 of 5,000 characters. Saves automatically.
Try the 6 remaining checks and drills above to complete this lesson (0 of 6 done).
Spotted something wrong or out of date? Report a mistake. We check every report and correct the page.