Start by clarifying and restating the question
Before doing anything else, make sure you understand exactly what's being asked. Ask one or two clarifying questions if anything is ambiguous, such as the specific goal (is this about growing revenue or diagnosing a decline), the timeframe, or any constraints already known. Then restate the question back in your own words: 'So we're trying to figure out why this company's profits dropped over the last year, is that right?' This confirms alignment before you invest time building a structure around the wrong problem entirely.
Take time to build your structure before diving in
Ask for a short moment (30 seconds to a couple of minutes) to organize your thoughts before speaking. Build a structure, whether that's a profitability tree, a market entry framework, or something custom to the case, and make sure it's MECE, covering the problem without gaps or overlap. Present this structure to the interviewer clearly before moving into analysis, so they can follow your plan and redirect you early if needed, rather than discovering thirty minutes in that you've been solving a slightly different problem than the one they asked.
Work through the case methodically
- Move through your structure branch by branch rather than jumping around, this keeps your analysis organized and easy for the interviewer to track.
- Ask for data as you need it rather than all at once, tied to the specific branch you're currently investigating.
- State your interim conclusions as you go, for example 'this tells me the issue is likely on the cost side, so I'll focus there next,' rather than staying silent until the very end.
- Do math out loud, narrating your logic rather than presenting only the final number.
- Stay flexible, if the data points you toward something outside your original structure, follow it rather than forcing the analysis back into your original plan.
Close with a clear synthesis
When you're ready to wrap up, or the interviewer asks for your recommendation, lead with your answer first, then support it. 'I'd recommend the company invest in the new market, for three reasons.' Don't walk the interviewer back through your entire analysis chronologically, that's what you already did during the case, the synthesis should be the compressed, top-line version aimed at someone who needs the answer quickly, similar to how you'd brief a client executive who has two minutes before their next meeting.
Why this order matters
Each step exists to prevent a specific failure mode: skipping clarification risks solving the wrong problem, skipping structure risks a disorganized, hard to follow analysis, skipping narration during the case risks looking like you're guessing, and skipping a clear synthesis at the end risks leaving the interviewer unsure what you actually concluded. Following this order consistently is what makes an answer feel controlled and confident rather than improvised, and it holds up regardless of what specific case content you're given.
Adjusting your pace as the case unfolds
A well-structured answer still needs to flex with how much time is left and how the interviewer is engaging. If you notice time running short partway through, it's reasonable to say so directly: 'given the time we have left, I want to focus on what seems like the strongest lead so far,' and then move more quickly toward a synthesis rather than trying to complete every branch of your original structure at the same depth. Interviewers generally respect a candidate who manages time well over one who runs out of time mid-analysis with no recommendation at all.
Practicing the full sequence, start to finish
It's common to practice pieces of a case in isolation, structuring, or math, or the final synthesis, without ever running through the complete sequence in one sitting. Make a point of practicing full cases end to end regularly, timing yourself against a realistic total length, so the transitions between each stage, from clarifying to structuring to analysis to synthesis, become smooth rather than something you have to consciously remember to do in the moment during a real interview.
What to do when the case topic is completely unfamiliar
Every candidate eventually gets a case set in an industry or situation they know almost nothing about. In that moment, resist the urge to apologize for the unfamiliarity or to guess wildly, instead lean harder on the general structuring process itself, since it doesn't depend on industry knowledge to work. Ask more clarifying questions than usual to establish the basic mechanics of how the business makes money, then build your structure from those fundamentals. Interviewers know unfamiliar cases will come up in real client work too, and they're specifically watching whether your process holds up without deep prior knowledge to lean on.
Keeping the case feeling like a conversation, not a recitation
A risk of following a structured process closely is that it can start to sound rehearsed or robotic if applied too rigidly. The best candidates make the structure invisible to the listener, it's there, guiding the analysis underneath, but the delivery still sounds like a natural, engaged conversation rather than a memorized script being read aloud. This comes with practice and with genuinely caring about the problem in front of you rather than just trying to hit every step of a checklist in the correct order.
Remembering that structure serves the analysis, not the other way around
It's worth periodically reminding yourself that the entire point of structuring a case answer is to help you reach a sound, well-supported conclusion faster and more reliably, not to perform a ritual for its own sake. If at any point following your structure exactly would mean ignoring something clearly important the interviewer just told you, the right move is to follow the important information, adapting your structure on the fly, rather than sticking rigidly to a plan that no longer serves the actual goal of solving the client's problem.