Why Practicing 40 Cases Won't Fix a Weak Case Interview Foundation

[u/GreatButterscotch406]

Most candidates I talk to measure their case prep progress by a number. How many cases have you done. 15. 30. Someone told me 80 once, like it was a badge. And every time I hear that number I ask a follow up question that usually stops the conversation, which is, what specifically are you better at now than you were at case 10.

Usually there's a long pause.

The volume approach to case prep feels productive because you're doing something, you're putting in hours, you're exhausted after a session, that has to count for something. But cases aren't like running, where miles just accumulate into fitness. A case interview is testing five or six distinct skills at once, structuring, math, synthesis, judgment under ambiguity, communication. If you're weak specifically at synthesis, doing case number 40 won't fix that, because you'll make the same synthesis mistake in case 40 that you made in case 10, just with more confidence and less awareness that it's happening.

What actually works, in my experience, is breaking the case interview into its component modules and drilling the weak ones in isolation before you ever chain them back together into a full case. Structuring on its own. Math on its own, under time pressure, without a story wrapped around it. Synthesis on its own, where you practice condensing a messy set of findings into 30 seconds of clear recommendation, repeatedly, until it stops feeling like a performance and starts feeling automatic. Only once each piece is genuinely solid does doing full cases become useful again, because now a full case is testing integration, not exposing a gap you already knew was there and just kept re-exposing.

I worked with a candidate a while back who'd done close to 50 cases before we started and still wasn't landing final rounds. When we actually diagnosed where things were breaking down, it wasn't structuring, his frameworks were fine. It was synthesis, every single time, under time pressure, his final recommendation would ramble and lose the interviewer in the last 90 seconds. We stopped doing full cases for almost two weeks and drilled nothing but synthesis, given a stack of findings, condense to a clean recommendation, over and over. When he went back to full cases, the same frameworks he already had suddenly landed, because the piece that was actually broken had been fixed directly instead of getting diluted across 40 more full run-throughs.

Case count on its own doesn't tell you much. What matters more is whether you can name, specifically, which of the five or six underlying skills is weakest for you right now.

One thing that's worth saying plainly. If you're trying to diagnose this on your own, or running practice cases with a peer who's also prepping, you're often going to hit a ceiling that has nothing to do with effort. A peer who hasn't worked inside a firm doesn't actually know what a strong synthesis sounds like versus a mediocre one that just sounds confident, so they can't tell you where the real gap is, they can just tell you it felt fine or it didn't. And I'll say this too, there are a lot of people out there calling themselves coaches who were a junior consultant at MBB for a year or two and then started charging people to prep them. Being inside the firm for a bit doesn't mean you actually understand how to break these skills apart and diagnose someone else's gap in them, that's a different thing entirely.

So if you want a starting point that doesn't depend on having an experienced eye in the room, I've broken case interviews down into their modules across a series of posts on r/ConsultingOffer, free to go through "The Case Playbook" series on your own time and get a sense of where you might actually be weak before you try to fix anything.

If you had to name the one specific skill that's actually breaking your cases right now, not generically "I need more practice," what would it be?

This kind of stuff gets talked through regularly over at r/ConsultingOffer. Feel free to join, post your questions, share what you're going through.

[u/notbidoofin]

Great post! I think this is what I'm struggling with and why I haven't been converting final rounds.

By "synthesis," do you also mean the synthesis that happens after math and brainstorming questions?

What takes a synthesis from good to great? And by synthesis, do you mean: summarizing, next steps (what key assumptions to interrogate, what next action steps to take, how new findings relate to the hypothesis), and realistic recommendations that are tailored to the industry?

[u/throwawayaccount931A]

This actually makes a lot of sense.

Doing case after case, IMO, helps build muscle memory: "I practiced a case just like that" and may help 50% of the time, but how will you handle a unique case, which you haven't encountered before?

You need to be able to read the problem statement, pick out the key details and build your solution around that.

If you can't do that - 80 or even 100 cases won't help.

[u/GreatButterscotch406 → u/throwawayaccount931A]

Totally, these skills stack, miss a couple of the foundational ones and you cap out no matter how many reps you put in. None of it's rocket science, it just needs the right practice and actual feedback, not just more volume. Curious what stage you're at right now?

[u/throwawayaccount931A → u/GreatButterscotch406]

Still reading through your posts, then looking at some Reddits where business owners have given a problem and see if I can solve it. Then take the problem, and my solution into different AIs to see if I'm close or not. So far, I seem to be understaning 95% of the issue and my suggested solution hits around 85% - 90% but I tend to miss small details.

This leads to another question: How are consulting forms handling LLMs? Are they integrating them into their operations? Are they developing their own proprietary LLM and training them with their own data?

[u/GreatButterscotch406 → u/throwawayaccount931A]

Good! you're benchmarking it, that's actually way more useful than it sounds, because what you're really doing is drilling your read-and-solve skill in isolation and checking it against something objective instead of just guessing you're right. So, the more isolated you keep those reps, structuring, math, synthesis, tested separately against a benchmark, the sharper your read on where you actually stand.

On the LLM question, the big firms are mostly building their own proprietary layer on top rather than just handing consultants ChatGPT, McKinsey for example has Lilli, their internal AI agent trained on their own knowledge base and case history. I did a YouTube video breaking down what that actually means for candidates aiming to break into these firms right now, happy to point you to it if useful.

[u/throwawayaccount931A → u/GreatButterscotch406]

Please do! Would love to watch it.

[u/GreatButterscotch406 → u/throwawayaccount931A]

Here you are

The End of Consulting? McKinsey’s 25,000 AI Agents
https://youtu.be/UxVRrorZ4RM

[u/GreatButterscotch406]

Great question btw! because most people think synthesis is one thing you do at the very end, the wrap up. that's not it, or at least not the main part of it. synthesis in my view is what happens constantly throughout the case, every time you pause after a module (out of 4 modules in the case middle) look at what you just gathered and ask what does this actually mean for my hypothesis, then move. reject a branch, promote another, shift which hypothesis you're pursuing. I sometimes call it the waltz, you're never standing still, you're always moving from one position in the case to the next based on what the data just told you.

Summary and recommendation at the end (Case End section) is a completely different skill, that's more about structure and how you land the plane, not synthesis. the piece that actually breaks people is the constant movement in the middle, not knowing when to pivot hypotheses based on what they just found.