How to Structure a Case Interview (No Memorizing)

To structure a case interview well, build a custom issue tree from first principles instead of forcing a memorized framework onto the problem. Start from something you know (usually an equation like Profit = Revenue − Costs), break it into clean, non-overlapping branches that cover the whole problem, tailor it to the specific prompt, then present it out loud top-down. Structure is the most important moment of the case. Here is how to do it without memorizing a single framework.

I conducted 100+ McKinsey interviews, and structuring is where I could separate candidates within about 90 seconds. The ones who reached for a memorized framework and jammed the problem into it looked rehearsed and brittle. The ones who built a clean breakdown tailored to the actual question looked like consultants. This guide is about becoming the second kind. It complements the case interview frameworks guide, which covers the classic templates. Here we go one level deeper into how to build and present structure that is genuinely yours.

What "structure" really means

Structure is not a framework you memorized. Structure is starting from something you know and building toward something you don't.

Picture the situation. You're in a new environment, an industry you've never touched, with a weird problem you've never solved. You know nothing about spacecraft insulation or carpet manufacturing. What do you do naturally? You think from first principles. You ask: what do I actually know about how any business works? How do I start from there? How do I build on that to reach the answer?

That is all a framework is. A way to decompose an unfamiliar problem into known, manageable pieces. When you understand that, you stop needing to memorize, because you can generate structure for any problem on the spot.

The two properties every good structure has

A strong structure does two jobs. First, it captures everything, so you don't miss a driver of the problem. Second, it avoids double-counting, so your branches don't overlap and confuse the analysis. Consultants call this MECE.

MECE, in plain English

MECE means Mutually Exclusive, Collectively Exhaustive. Mutually exclusive: your buckets don't overlap. Collectively exhaustive: together they cover the whole problem. That's it.

If you're diagnosing falling profit, "Revenue" and "Costs" are MECE, they don't overlap, and together they explain profit completely. But "Revenue," "Marketing," and "Costs" are not MECE, because marketing is already inside costs. You'd be double-counting and your tree would be muddled.

You don't need to chant "MECE" at the interviewer. You just need branches that pass both tests. When your structure is genuinely MECE, the interviewer can see your logic is airtight without you naming the acronym.

Issue trees, the workhorse tool

An issue tree breaks a big question into branches, then sub-branches, until each piece is small enough to analyze. For a profit problem:

• Profit splits into Revenue and Costs.
• Revenue splits into Price and Volume.
• Volume splits into number of customers and purchases per customer.
• Costs split into Fixed and Variable.

Each level is MECE. Each branch is something you can actually investigate with data. That's a working structure, and I built it without naming a single named framework.

Why equations beat memorized frameworks

Here's my single favorite move for building structure fast: start from an equation.

Simpler frameworks win. The cleanest starting point for most cases is a formula you already know:

An equation is automatically MECE, the variables don't overlap and they fully explain the outcome, and it gives you an instant, defensible first layer. From there you just decompose each variable. This is far more reliable than trying to recall whether a memorized framework had four boxes or five.

Tailoring structure to the prompt

This is where most candidates lose points. They walk in with a generic profitability framework and bolt it onto every case. The interviewer sees it instantly, and it reads as memorized.

Your structure has to fit the specific prompt. If the client's problem is that market share is shrinking despite industry growth, a plain Revenue/Cost tree misses the point. You'd want branches around the company's offering, competitors' moves, and changing customer demand, because the question is about losing ground to rivals, not raw cost control.

A quick way to tailor: before you build the tree, restate the objective and let it dictate the top branches. The objective is your North Star. Every branch should help answer it. If a branch doesn't move you toward the objective, cut it. Interesting is not the same as relevant.

Worked example: tailoring in action

Prompt: "Our client makes specialty industrial coatings. Revenue is flat while the market grows 8% a year. Why, and what should they do?"

A lazy structure: "Revenue and costs." Wrong. Costs aren't the issue, the question is why revenue is flat in a growing market.

A tailored structure: "I'll look at three areas. First, the market, is growth concentrated in segments our client doesn't serve? Second, the competition, are rivals winning share with better products, pricing, or distribution? Third, our client's own offering, has anything changed in their product, price, or sales channel that's costing them deals?" That tree is built for this prompt. It's still MECE, and it goes straight at the actual question.

For deeper, case-type-specific structures, see the profitability case interview and market entry case interview walkthroughs, which show tailored trees end to end.

The opening response: set up your structure right

Before you present structure, you open the case. A clean opening earns you the room to think and frames the whole problem. Use this four-part template right after the interviewer finishes the prompt:

• Client introduction. "Our client is [name], and they [what they do / context]." Example: "Our client is Space Art, a manufacturer of sophisticated insulating technology for spacecraft."
• Restate the facts. Play the key numbers back accurately. "They have $400 million in revenue, and profits have declined 19% year over year." This is your natural checkpoint to confirm you heard the numbers right.
• State the challenge and objective. "They're losing market share despite industry growth, and they want us to find the root causes and reverse it."
• Confirm the goal, then ask a couple of clarifying questions tied to it.

This template means you never freeze or fumble at the start. You synthesize from the first sentence, which is exactly the consulting skill being tested. Synthesize, don't summarize: merge the facts into a new statement that shows the relationship between them, rather than reciting them back to back.

Taking the pause (the one acceptable silence)

After your opening and clarifying questions, you take a pause to build your structure. This is the only place in the entire case where silence is expected and welcome. Take 60 seconds to two minutes, maximum. Tell the interviewer: "Give me a moment to structure my thinking." Then build your tree on paper.

Two risks live inside that silence, so manage them. If you stay quiet too long, the interviewer wonders if you're lost. If you rush out half-formed, your structure is sloppy. Aim for the middle: enough time to build something clean, not so much that the room goes cold.

How to present structure out loud

A great structure in your head is worthless if you can't deliver it. Present it top-down, the way you'd brief a partner.

• Signpost first. "I'd like to break this into three areas." Now the interviewer knows the shape before the detail.
• Name each branch, then its sub-points. "First, revenue, which I'll split into price and volume. Second, costs, fixed and variable. Third, the external market and competition."
• Explain why, briefly. One line on what each branch will tell you keeps it from sounding like a list you memorized.
• Then propose where to start. "I'd like to begin with revenue, since the prompt suggests a top-line problem." This shows you can prioritize, not just decompose.

Write the tree cleanly on your page as you talk, with section headers down the left and your work on the right, so you can reference it later and it looks professional. Clean notes during structure pay off through the whole rest of the case.

Structure do's and don'ts

The bottom line

Strong case interview structure is built, not recalled. Start from an equation you know, decompose it into MECE branches, tailor those branches to the exact prompt, and present them top-down with clear signposting. Do that and you'll look like a consultant on day one, while the framework-memorizers look rehearsed. The skill is generative, which means once you learn it, it works on any case you'll ever see.

Go deeper

The full Cut to the Case course teaches the complete Interview Dance method, including the opening template, the structuring approach above, and the CaseMap business-concept system that lets you generate tailored structures for any case. It's how 130+ candidates have landed MBB offers. If you're still new to the format, start with what is a case interview.

Get the free resume module →

Get the complete Cut to the Case course →

One payment, lifetime access, 30-day guarantee.