How to use this section

# Case Type Playbooks: How To Use This Section

In the Core Toolkit, you built the skills: clarifying, structuring, math, exhibits, hypotheses, synthesis, communication, sizing, brainstorming, and business intuition. This section is where those skills meet real cases.

Here is the idea that makes it work: most case interviews are variations on a small number of recurring question patterns. Once you recognize the pattern, you already know roughly where to look. These playbooks train that recognition.

A case type is a question, not an industry

This is the first thing to get right. "Profitability," "market entry," and "pricing" are not industries. They are patterns of question.

The same coffee chain can be the setting for a profitability case (profits fell, why?), a pricing case (how should we price the new cold brew?), a market entry case (should we open in a new city?), or a growth case (how do we bring more customers in?). The business never changed. The question did, and the question is what determines your approach.

So do not file cases by industry, as "retail cases" or "airline cases." File them by the question being asked. That is the unit that actually transfers from one case to the next.

Real cases blend types

Here is the part beginners most often miss: real cases rarely stay in one box.

A profitability case often turns into a cost-reduction case the moment you find the leak, and then into an operations case when you ask why costs rose. A market entry case often contains a quick sizing check. An M&A case contains a profitability analysis of the target. A pricing question shows up in the middle of a growth case.

So these playbooks are not separate islands. They are overlapping patterns you will frequently combine inside a single case. The skill is not picking the one correct box. It is recognizing which patterns are in play and moving fluidly between them.

Use this as a recognition library, not a script

The goal of this section is not to walk into an interview with a stack of frameworks ready to recite. Memorized frameworks make you rigid, and interviewers can hear them coming.

The goal is to hear a prompt, recognize the pattern underneath it, reach for the right starting structure, and then adapt it to the specifics in front of you. Recognized patterns make you fast and flexible. Memorized templates make you brittle. Read these playbooks to build the recognition, then let the actual case shape your answer.

One coffee chain, many cases

To make the patterns easy to see, we will keep returning to one familiar business across the playbooks: a coffee chain. Watch what it does. The same coffee chain will generate a profitability case, a pricing case, an acquisition, a growth problem, and more.

That repetition is deliberate. It is the clearest possible demonstration of the core lesson: case type lives in the question, not the company. The drills, by contrast, deliberately roam across other industries, from gyms to airlines to hospitals, so you also practice carrying the pattern onto unfamiliar ground.

How each playbook is built

Every playbook follows the same shape, so you always know where to look:

The seven patterns

You already have the skills. This section trains the pattern recognition that sits on top of them, so that when a prompt lands, you are not staring at a blank page. You are thinking: I have seen this shape before, and I know where to start.