41.1 Why “I Need More Practice” Is Not a Useful Diagnosis
More practice helps only if the practice addresses the right problem.
If your structures are consistently generic, doing ten additional full cases without changing your approach may simply reinforce the same habit. If your math errors come from losing track of units, generic mental-math drills may not solve the real issue.
Better diagnosis: Replace vague statements with specific ones such as, “I fail to prioritize within my initial structure,” or, “I calculate correctly but rarely explain the implication.”
The more precise the diagnosis, the more targeted your improvement plan can be.
41.2 Evaluating Structure
After a case, ask whether your structure actually helped solve the problem.
Evaluate:
- Relevance: Did every major branch connect to the client’s objective?
- Completeness: Did you miss an important driver?
- Specificity: Was the structure tailored to the case?
- Prioritization: Did you identify where to start and why?
- Flexibility: Did you revise the structure as evidence changed?
Warning sign: If the same structure could have been used almost unchanged for many different cases, it was probably too generic.
41.3 Evaluating Math
Do not evaluate math only by whether the final number was correct.
Ask:
- Did I define what I was calculating?
- Did I write the equation first?
- Did I keep track of units?
- Was my arithmetic accurate?
- Did I sanity-check the result?
- Did I interpret the answer?
Diagnose the error type: A setup error requires different practice from an arithmetic error, a unit error, or a failure to interpret the result.
41.4 Evaluating Analysis
Strong analysis moves from information to insight.
Review whether you identified patterns, tested hypotheses, and connected findings to the business problem.
Weak analysis: “Region A declined by 15%.”
Stronger analysis: “Region A accounts for most of the company-wide decline, so I would focus further analysis there rather than treating this as a broad national problem.”
Ask whether your analysis consistently produced implications and useful next steps.
41.5 Evaluating Business Judgment
Business judgment is about whether your conclusions make practical sense.
Ask whether you considered customers, competitors, economics, capabilities, incentives, and implementation when relevant.
Common weakness: Recommending an option because the numbers look attractive without asking whether customers will accept it or whether the client can execute it.
When reviewing a case, identify where your answer was technically correct but commercially incomplete.
41.6 Evaluating Communication
Communication problems are often easier to notice after the case than during it.
Evaluate whether you:
- Answered first: Did you state your conclusion before explaining it?
- Structured your points: Did you number or signpost them?
- Stayed concise: Did you avoid unnecessary detail?
- Used complete thoughts: Were your answers easy to follow?
- Reduced filler language: Did you sound controlled rather than rushed?
Recording practice sessions can reveal communication habits that are difficult to detect in real time.
41.7 Evaluating Synthesis
Ask whether you connected separate findings throughout the case or treated each analysis as an isolated task.
A strong candidate periodically states:
- Finding: What did we learn?
- Implication: What does it mean?
- Updated view: How does it change the hypothesis?
- Next step: What should we investigate now?
Warning sign: If your final recommendation requires you to reconstruct the entire case from scratch, you probably did not synthesize enough along the way.
41.8 Evaluating Pacing
Pacing is about using limited interview time effectively.
Ask whether you spent too long on low-value areas, rushed important calculations, or failed to move on after reaching a clear conclusion.
Good pacing: Spend more time on high-impact questions and less time on issues unlikely to change the answer.
Also notice whether you pause appropriately before difficult questions rather than rushing simply to avoid silence.
41.9 Evaluating Confidence and Presence
Confidence does not mean never hesitating or making mistakes. It means remaining composed and deliberate while solving the problem.
Evaluate whether you:
- Spoke clearly and at a controlled pace.
- Used pauses productively.
- Recovered calmly from mistakes.
- Responding constructively to challenges.
- Avoided unnecessary apologies or defensive behavior.
Practical standard: Ask whether you appeared like someone the interviewer could comfortably put in front of a client.
41.10 Separating Recurring Weaknesses from One-Off Mistakes
Not every mistake deserves a new training plan. Everyone occasionally miscalculates, misses an idea, or misunderstands a question.
What matters most is the pattern across several cases.
Track weaknesses over time and ask:
- Frequency: Does this happen repeatedly?
- Impact: Does it materially hurt my performance?
- Cause: Is the problem knowledge, technique, pressure, or communication?
- Trend: Is it improving with practice?
Final principle: Diagnose case performance at the skill level. Identify exactly what went wrong, understand why it happened, and look for recurring patterns across multiple interviews. The goal is not simply to do more cases. It is to use every case to generate a more precise understanding of what you need to improve next.
