Published 8 min read
The 30-Day Case Interview Prep Plan
A case interview prep plan for 30 days should move through four phases in order: understand the format and learn to structure without memorized frameworks in week one, build your math and framework toolkit in week two, drill communication skills like brainstorming and charts in week three, then run full mock cases and fix specific weaknesses in week four. Most candidates skip straight to memorizing frameworks and mock cases, then wonder why they freeze on a case they've never seen before. The order matters as much as the hours.
I conducted more than 100 McKinsey interviews, and I could usually tell within the first two minutes whether a candidate had prepped in the right order or just crammed frameworks the night before. The crammers sound rehearsed the moment the case deviates from a textbook example, which it always does. The candidates who prepped in the right sequence sound like they're thinking, because they actually are. Here's the 30-day version of that sequence.
Why the order matters more than the hours
Most prep plans you'll find online are just a list of resources: read this guide, watch these videos, do 20 practice cases. That's not a plan, that's a shopping list. A real plan sequences skills so each one builds on the last.
You cannot brainstorm well until you can structure a problem. You cannot structure well until you understand what a case interview is actually testing. You cannot perform well in a mock until you've drilled the individual pieces, math, structure, communication, separately first. Skip a layer and the whole thing wobbles under pressure, because a live case interview stacks all four skills at once and gives you no time to think about which one is failing.
Thirty days is enough time to build all four layers if you don't skip ahead. It is not enough time if you spend three weeks reading frameworks and one week panicking through mocks, which is what most candidates do by accident.
Week 1 (days 1-7): understand the format, then learn to structure
Before you touch a single framework, get clear on what's actually being evaluated. If you're newer to this, start with what a case interview actually is, because a lot of wasted prep time comes from candidates optimizing for the wrong thing, like memorizing facts about industries instead of practicing structured thinking.
Once you understand the format, spend the rest of week one on one skill only: building a custom issue tree from first principles instead of forcing a memorized framework onto a problem you've never seen. This is the single highest-impact skill in the entire case, and it's the one most candidates never practice deliberately because it's less concrete than "read the market entry framework." I wrote a full walkthrough on how to build structure without memorizing frameworks, and it's worth doing before you open a single case book.
By day 7 you should be able to take a plain business prompt, any prompt, even one you make up yourself, and build a MECE tree from an equation in under two minutes without looking anything up.
Week 2 (days 8-14): frameworks, math, and drivers
Now that you can build structure from scratch, frameworks become useful shortcuts instead of crutches. Spend the first half of the week learning the handful of classic starting points, profitability, market entry, market sizing, pricing, not to memorize and recite, but to recognize which equation applies fastest. The full frameworks guide covers all of them with the tailoring logic attached, which matters more than the framework itself.
The second half of week two is math. Case math is not hard math, it's fast, clean, sanity-checked arithmetic under mild pressure. Drill percentages, weighted averages, and break-even calculations daily, out loud, narrating your steps the way you would in an actual interview. Ten minutes a day of drilling beats one long session on a Sunday, because the skill you're building is speed and composure, not the arithmetic itself.
By day 14 you should be comfortable converting a business prompt into an equation, building a tree from it, and doing back-of-envelope math on the numbers the interviewer gives you, all without a calculator.
Week 3 (days 15-21): the skills between structure and the answer
This is the week candidates skip most often, and it's the one that separates a good case from a forgettable one. Structure and math get you an answer. Brainstorming, chart reading, and a clean recommendation are what make the interviewer believe you'd be good in front of a client.
Spend a few days specifically on brainstorming the MECE way, because unstructured idea generation under time pressure is a different skill than structuring an opening tree, and most candidates never separate the two in practice. Then spend a few days on reading charts and exhibits quickly and correctly, since a surprising number of candidates build the right structure, do the math right, then misread a bar chart and confidently deliver a wrong answer. Finally, drill the close: a case interview lives or dies on whether you can deliver a clear, structured recommendation in under 60 seconds, with a because, a risk, and a next step. An interviewer forgives a shaky middle far more than a mushy ending.
Week 4 (days 22-30): full mock cases and targeted fixes
Now, and only now, do full-length mock cases earn their keep. Running mocks before weeks one through three means you're practicing your mistakes at full speed instead of fixing them in isolation.
Run one full case a day if you can find partners, alternating who interviews. After each one, write down the single biggest issue, not five issues, one, and drill that specific piece the next day before your next mock. If your structure was fine but your math was sloppy, do ten more minutes of mental math drills before the next case. If your recommendation trailed off, write out three closing lines and say them out loud until they're automatic.
Save the last two or three days for rest, not cramming. Case interviews reward composure more than raw knowledge, and showing up tired from three weeks of cramming undoes weeks of good prep.
The 30-day plan at a glance
| Days | Focus | You're ready to move on when |
|---|---|---|
| 1-3 | Understand what's being tested | You can explain the five things an interviewer scores, in your own words |
| 4-7 | Build structure from first principles | You can tree out a random business prompt in under 2 minutes, unaided |
| 8-11 | Learn framework starting points | You recognize which equation fits a prompt within seconds |
| 12-14 | Drill mental math | You can do weighted averages and percentages out loud, under time pressure |
| 15-17 | Brainstorming under time pressure | You can generate MECE ideas on a prompt with no prep time |
| 18-19 | Chart and exhibit reading | You can extract the right number from a chart in under 30 seconds |
| 20-21 | The recommendation and close | You can deliver a structured close in under a minute, unscripted |
| 22-27 | Full mock cases, one fix at a time | Each mock shows fewer repeated mistakes than the last |
| 28-30 | Rest, light review, logistics | You feel calm, not cram-tired, walking into the real thing |
What if you have less than 30 days
Not everyone gets a full month. If your timeline is tighter, the sequence stays the same, structure before frameworks, frameworks before drilling, drilling before mocks, you just compress each phase and cut the rest days. I broke down realistic timelines for shorter windows in how long it actually takes to prepare for case interviews, including what to cut first when you're short on time and what you should never skip no matter how compressed the schedule gets.
Signs you're actually ready, not just busy
Busy and ready are different things. You've done a lot of prep, that's not the same as being ready. A few honest checks: you can build structure on a prompt you've never seen without an awkward pause longer than two minutes, you can do mental math without your voice trailing off mid-calculation, and you can deliver a recommendation without the interviewer having to ask "so what's your answer" because you never quite landed it.
If any of those three still feel shaky with a week left, that's where your remaining days go. Don't add a new case book. Fix the specific gap.
The bottom line
Thirty days is enough time to go from unfamiliar with case interviews to genuinely ready, but only if you build the skills in order: structure first, then frameworks and math, then the communication skills between the analysis and the answer, then full mocks. Cramming frameworks and skipping straight to mock cases is the single most common mistake I saw candidates make, and it shows up as a candidate who sounds rehearsed the second the case gets unusual.
Go deeper
If you want the whole sequence built for you already, structured practice, the framework logic, and the drilling order laid out day by day, that's exactly what the CaseMap method inside the course does.
Get the complete Cut to the Case course →
One payment, lifetime access, 30-day guarantee.
Frequently Asked Questions
How many hours a day should I study for case interviews?
One to two focused hours a day beats four unfocused hours on weekends. Case skills are built through repetition and correction, not volume, so daily consistency for 30 days will outperform a handful of long cramming sessions.
Can I prepare for case interviews in less than 30 days?
Yes, but the sequence stays the same and you compress each phase instead of skipping any. Structure still comes before frameworks, and frameworks still come before full mock cases, you just have fewer days in each bucket.
What should I do in the first week of case prep?
Understand what a case interview actually evaluates, then spend the rest of the week practicing how to build a structure from first principles instead of a memorized framework. Frameworks and math can wait until week two.
How many practice cases do I need before I'm ready?
There's no fixed number that works for everyone, what matters is whether each mock shows fewer repeated mistakes than the last one. Someone doing five focused mocks with real feedback will outperform someone who ran twenty mocks without fixing anything between them.
Should I read case books before I start practicing?
Read enough to understand the format and a handful of starting frameworks, then start practicing structure immediately. Reading more case books instead of practicing is one of the most common ways candidates waste their first two weeks.
Is 30 days really enough time for MBB-level case interviews?
For most candidates, yes, if the days are spent in the right order and the last few days are reserved for rest instead of cramming. The candidates who struggle at 30 days usually spent three weeks reading and one week panicking, not the reverse.