Structuring fundamentals
How to build a custom structure for any case - instead of forcing the problem into a framework you half-remember.
Most candidates lose the case in the first ninety seconds — not because they can't do the maths, but because they reach for a framework they half-remember and bend the problem to fit it. The strongest candidates do the opposite: they build a structure on the spot, custom to the question in front of them. That is the whole skill. Every framework you have been taught — profitability, market entry, growth — is just a structure someone already built for one kind of problem. Learn how the building works and no case can catch you empty-handed, because you will make your own framework in real time.
TL;DR · Key Takeaways
What you will be able to do
- Restate the real question in one line before you split anything — solving the wrong problem cleanly still loses the case.
- Make every level MECE: no overlaps, no gaps, and no buckets that are clean but not worth analysing.
- Carry five lenses instead of a stack of frameworks — equation, process, segmentation, conceptual buckets, and stakeholder.
- Choose your structure deliberately and defend the choice in a sentence; there is no single correct tree.
- Drill only the branch that swings the answer, and lead with a hypothesis so the structure has direction.
- When a case has no obvious framework, build one from the decision being made — that is where the marks are.
Structure is the whole game
A case interview is not a quiz with the answer hiding at the back. It is a test of how you think when you do not know the answer yet. The interviewer hands you a messy, open question and watches how you carve it into something you can attack. Carve it well and the analysis almost does itself; carve it badly and no amount of clever arithmetic saves you. This is why structuring is weighted more heavily than any single calculation — it is the part that shows whether you can be trusted in front of a client.
Every good structure has the same four layers. At the top sits the real question, restated in one clean line so you are sure you are solving the right problem. Below it, you split that question into three or four buckets that do not overlap and leave nothing out. Inside the bucket that matters most, you go one level deeper into the drivers you can actually move. At the bottom, everything rolls back up into a so-what — the recommendation the tree was built to produce. If your buckets do not add back up to answer the question on top, you have made a list, not a structure.
MECE: the one rule that matters
MECE — mutually exclusive, collectively exhaustive — sounds like jargon until you see what it buys you. Mutually exclusive means no item can sit in two buckets, so you never count the same thing twice or argue with yourself about where it belongs. Collectively exhaustive means the buckets cover the whole problem, so you cannot be ambushed by a factor you forgot. Together they are a quiet promise to the interviewer: I will not double-count, and I will not miss anything.
The three ways a split goes wrong
Overlap — splitting customers into new and lapsed breaks the moment a lapsed customer returns: now they are both. Gap — splitting cost into fixed and labour quietly forgets variable inputs like raw material. And a third, sneakier one: a split can be perfectly MECE and still useless if the buckets are not worth analysing. Clean is necessary, not sufficient.
The toolkit: five ways to break anything down
Here is the secret the frameworks do not advertise: there are only a handful of ways to split a problem, and every named framework is just one of them applied to one situation. Master the five lenses below and you stop memorising frameworks altogether — you reach for the lens that fits and build the structure yourself.
Every framework is a pre-built structure
Look closely and you will recognise old friends. Profitability is the equation lens — profit = revenue − cost. Market entry is the conceptual-buckets lens — is the market attractive, and can we win? Growth is the segmentation lens — which customers, products, geographies? Due diligence walks the process lens end to end. None of them are magic; they are structures someone built once and gave a name. You can build the same thing live.
There is no single right structure
Beginners freeze because they are hunting for the correct tree, as if one exists. It does not. The same problem can be structured several valid ways, and a strong candidate picks the lens that isolates the answer fastest — then says out loud why they chose it. Watch one problem split three different ways.
All three are MECE. All three are defensible. The equation lens is best when the maths is the bottleneck; the segment lens when one slice is quietly dragging the rest down; the journey lens when you are losing people somewhere in a funnel. The skill is not finding the one true tree — it is choosing deliberately and being able to defend the choice in a single sentence.
How to build one live
Knowing the lenses is not enough; you have to perform the structuring out loud, under pressure, without freezing. Here is the sequence that works — six moves, the first three done silently in your opening minute, the rest narrated as you draw.
Buy yourself a structure with silence
Resist the urge to start talking immediately. Take a visible pause — twenty to thirty seconds of silence while you run moves one to three in your head. Interviewers read that pause as composure, not as being stuck. Then turn your paper around, walk them through the structure, and ask permission before you dive into a branch. The silence is what buys you a structure worth presenting.
Worked example: a case with no obvious framework
Most of what you will face will not map to a textbook framework — and that is exactly where structuring earns its marks. Take this one. Anandam Dairy, a ₹1,200 crore cooperative in Gujarat, is losing suppliers: roughly twelve per cent of its eighty thousand farmer-members have started selling to private milk buyers in the last year. There is no farmer-retention framework to recall. You have to build one — and the move that scores is refusing to treat it as a profitability case.
Notice what the structure does not do: it does not start from Anandam's P&L. It starts from the only decision that matters — the farmer's. Why would a farmer stay or leave? Because of what we give them, what a rival offers instead, and how hard it is to switch. Three buckets, mutually exclusive and exhaustive from the farmer's point of view. Then you drill the one that is actually pulling them away, and you commit to a hypothesis before you drown in data.
Anandam Dairy, live
Anandam Dairy is a ₹1,200 crore cooperative in Gujarat. Over the last year, about 12% of its 80,000 farmer-suppliers have started selling to private buyers instead. The board wants to know why, and what to do about it. How would you approach this?
Before I structure, let me make sure I have the goal right. We are trying to stop — ideally reverse — farmers leaving for private buyers, and protect Anandam's milk volumes. Is that the objective, or are we also worried about the price we pay them eating into margin?
Clarifies the objective before structuring — move 1.
Stopping the defection is the priority. Treat margin as a constraint, not the goal.
Then I will not treat this as a profitability problem, because the decision being made is not ours — it is the farmer's. So I will structure it from the farmer's choice. A farmer stays or leaves based on three things: what we give them, what a rival offers instead, and the friction of switching. Those three are mutually exclusive and, from the farmer's point of view, cover the whole decision. May I take a moment to lay it out?
Picks the lens — and explicitly rejects the profitability tree.
Go ahead.
Bucket one, what we give: our procurement price per litre, how fast we pay, and the services bundled in — subsidised feed, veterinary visits, cattle insurance. Bucket two, what rivals offer: I would expect a higher spot price, faster cash, perhaps doorstep pickup. Bucket three, switching friction: the farmer's equity in the co-op, social and loyalty ties in the village, distance to our collection centre. The buckets do not overlap and nothing is missing. The branch most likely driving the defection is bucket two, so I would open that one first.
Draws level 1, pressure-tests, then drills the branch that matters — moves 3 to 5.
My hypothesis: rivals are winning on visible cash — paying maybe eight per cent more, in hand the same day — while our real edge, the feed and vet care and insurance, is worth more to the farmer over a year but is invisible at the moment of sale. If that is true, we are losing on perception, not on value. I would test it by comparing total annual farmer economics, ours versus a private buyer, and by asking defected farmers what actually tipped them.
Leads with a hypothesis — move 6.
Suppose your hypothesis holds. What do you recommend?
Two moves, piloted on the routes losing the most farmers before any blanket change. First, make the invisible visible: put the annual rupee value of feed, vet care and insurance on every payment slip, so the farmer sees the full deal and not just the per-litre price. Second, close the cash-velocity gap with same-day or next-day payment, since that is the lever rivals are actually pulling. I would avoid simply matching their price across the board — it hits the margin constraint and rewards the wrong behaviour.
The candidate scored the moment they refused the profitability tree and built the structure from the farmer's decision instead. The arithmetic came later and barely mattered — the marks were won in the choice of lens.
The rest of this section is just worked structures
Once you can build structures, the other pages read differently. Profitability, Market entry, Growth, Pricing and the M&A cluster are not separate things to memorise — they are worked structures you can now take apart, see the lens inside, and rebuild for any variant an interviewer throws at you.