Consulting Case Study: How to Structure Your Answer Under Pressure
Updated: Oct 6
The best lesson I know for a consulting case study comes from a cockpit. On January 15, 2009, US Airways Flight 1549 hit a flock of geese at about 2,800 feet and lost thrust in both engines. First Officer Jeffrey Skiles started working the Engine Dual Failure checklist, which was written for a failure at a much higher altitude, where a crew has more time. The plane was on the Hudson River about three and a half minutes later, so the crew never finished the list. Captain Chesley Sullenberger didn't wait for it. About ten seconds after the strike he started the auxiliary power unit, a backup power source, and the NTSB report found that choice improved the outcome. All 155 people on board survived. They had a structure to hold onto and the judgment to do the most important thing first. That's what a case interview tests.
I'm Stephen Turban. I went through McKinsey's on-cycle recruiting, worked at the firm, and now run WallStreetGuide, where I coach undergrads through case interviews every cycle. This guide gives you the routine I'd want you to run on autopilot when the prompt lands: how to build the structure, walk it, do the math, recover when you blank, and close with a recommendation a partner would act on.
Staying structured under pressure mostly comes from repetition, so build it into a wider consulting interview prep plan. If you want to run timed cases on your own, these management consulting interview prep tools and resources are the ones worth your time
How do you structure a consulting case study answer?
You structure a consulting case study by breaking the client's question into a short list of pieces that don't overlap and together cover the whole problem, then choosing which piece to test first.In practice, that means replaying the core prompt, asking two or three targeted clarifying questions, taking 60 to 90 seconds to draw a customized issue tree, walking the interviewer through your primary buckets, prioritizing where to begin, and stating an initial working hypothesis.The structure should come from this client's specific question, not from a memorized template. Everything after that (the math, the charts, the recommendation) hangs off the tree you built in the first five minutes.
How long should you take to structure a case?
Most candidates ask for about a minute, and 60 to 90 seconds of silence is normal and expected. Taking a short, announced pause to structure is a strength, not a stall, because the interviewer is grading the structure you produce, not how fast you start talking. Past about two minutes the silence starts to feel long, so practice until a clean tree takes you 90 seconds or less.
1. Structure in a consulting case study means an issue tree, not a framework
An issue tree is a drawing that breaks one big question into smaller questions, level by level, until each piece is small enough to answer with data. The top of the tree is the client's question. The first level splits it into three or four big areas. The second level splits each of those into the things you'd actually go measure.
Here's a simple example. The question is "Why did the client's profits fall?" Profit is revenue minus costs, so the first level has two branches: revenue and costs. Revenue is price times the number of units sold, so the revenue branch splits into price and volume. Costs split into fixed costs, which stay the same no matter how much you sell (rent, salaried staff), and variable costs, which rise with every unit sold (materials, shipping). Now you have four questions you can go test with data instead of one vague one.
A framework is different. A framework is a prebuilt list someone else made for a generic situation, like the 4Cs (customer, competitor, company, context) or Porter's Five Forces. Frameworks aren't useless. The 4Cs are a fine checklist to make sure you haven't forgotten a whole area in a market entry case. But interviewers at McKinsey, BCG and Bain hear the recited version over and over. A tree built from this client's words tells the interviewer you're thinking about the problem, while a recited framework tells them you memorized a book.
When I was at McKinsey, the thing that stood out about good candidates wasn't which framework they knew. It was that their first two minutes sounded like they were talking about this client, with this client's numbers, instead of any company in any industry.
2. MECE is two simple tests you can run on any list
MECE stands for mutually exclusive, collectively exhaustive. It sounds like jargon, but it's two plain tests you run on every level of your tree.
Mutually exclusive means no overlap. Every possible cause should belong to exactly one branch. If one fact could sit in two branches, you'll count it twice or argue about where it goes.
Collectively exhaustive means nothing is missing. Add up all the branches and you should cover every possible cause. If the real answer could fall outside every branch, your tree has a hole in it.
Here's what passing and failing look like for a few real case prompts.
Prompt | Branches | MECE? | Why |
Why did revenue fall? | Price, volume | Yes | Revenue is price times volume, so every revenue change is one or both. |
Who buys our product? | Customers under 30, customers 30 to 55, customers over 55 | Yes | Every customer has exactly one age, and the three ranges cover all ages. |
Where do our sales come from? | Domestic, international, online | No, overlaps | An online order from a customer in Canada is both international and online. |
Why are costs up? | Labor, materials | No, gaps | Slices only direct production; omits indirect operating overhead (rent, SG&A, logistics, and capital depreciation). |
Who buys our product? | Students, young professionals, families | No, both overlaps and gaps | Categories conflate life stage with household structure (a student can belong to a family), while leaving demographic gaps (retirees, single older adults). |
The fix for an overlap is to split on one idea at a time. "Domestic versus international" is one split. "Online versus in store" is a different split. Pick one for the first level and put the other one underneath it.
The fix for a gap is often an "other" branch, or a split built on math. Math splits are MECE by construction. Revenue equals price times volume. Customers at the end of the year equal customers at the start, plus new customers, minus customers who left. Nothing can hide outside an equation. When you can split a branch with an equation, do it, because an equation is MECE by definition and the interviewer can't poke a hole in it.
3. The first five minutes follow the same routine every time
Pressure makes people skip steps. The cure is a routine you've run so many times that you don't have to think about the order. Here it is, step by step.
Step 1: Repeat the question back in one or two sentences. Say the client, the problem, and the goal. "So our client is a 50-location gym chain in the Midwest, profits have fallen from $20 million to $12 million over two years, and they want to know why and what to do about it. Is that right?" This does two jobs. It proves you listened, and it gives the interviewer a chance to correct you before you build on a wrong fact.
Step 2: Ask two or three clarifying questions, no more. Good clarifying questions fall into three buckets:
The objective. "Is the goal to get profits back to $20 million, or is there a specific target and deadline?" Many candidates skip this, and it's the one that shapes the recommendation.
The business model. "How does the client make money: monthly memberships only, or also personal training and other sales?" You can't build a revenue branch if you don't know where revenue comes from.
Anything unusual in the prompt. If the interviewer mentioned "the Midwest" or "over two years," ask why that detail is there. Details in a case prompt are rarely random.
Skip questions you could answer yourself or questions that are really the whole case ("So why did profits fall?").
Step 3: Ask for time. "Would you mind if I took a minute to structure my thinking?" Then actually write. I've never seen a candidate lose points for asking for a minute.
Step 4: Build the tree on paper. Two levels, three or four branches at the first level, and each branch in words specific to this client. Section 4 walks through three full examples.
Step 5: Walk the interviewer through it, top down. Say how many branches there are before you go into any of them. "I'd look at this in three areas: membership revenue, other revenue, and costs." Then go through each one in a sentence or two. Announcing the count first gives the listener a map, the same way a table of contents does.
Step 6: Prioritize a branch and say why. Don't just finish the walk and wait. "I'd like to start with membership revenue, because it's usually most of a gym's revenue, and a two-year slide sounds more like members leaving than like a one-time cost spike."
Step 7: State a hypothesis. A hypothesis is your best guess at the answer, stated so it can be proven wrong. "My hypothesis is that a lower-priced competitor has pulled members away. To test that, I'd want to see how member counts changed at locations near competitors versus locations without them." A hypothesis gives your analysis a direction. It also lets the interviewer steer you quickly: if you're wrong, they'll hand you data that says so, and you've lost nothing.
One firm difference matters here. McKinsey's first-round cases have usually been interviewer-led, which means the interviewer asks a series of set questions and may tell you which branch to go to next. BCG cases are candidate-led, meaning you must synthesize each finding and drive the agenda: 'Based on this margin compression, I'd like to look at distribution costs next.' Bain blends formats, often using semi-interviewer-led questions in round one before transitioning to candidate-led partner rounds. McKinsey remains strictly interviewer-led across all rounds.. Run all seven steps either way. In an interviewer-led case, steps 6 and 7 are shorter, because the interviewer may point you somewhere else, and that's fine. The WSG McKinsey case interview guide walks through the interviewer-led format question by question.
4. Build a custom structure for each consulting case study (three worked examples)
The only way to learn custom structure is to watch it happen on real prompts. Here are three, each worked from the top of the tree to the bottom, with the reasoning for every branch.
Example A: profitability case, a regional gym chain
Prompt: "Our client runs 50 gyms in the Midwest. Profits fell from $20 million to $12 million over the last two years. Why, and what should they do?"
Clarifying answers from the interviewer: revenue comes from monthly memberships (about $50 a month), personal training, and small add-ons like drinks and merchandise. The goal is to get back to $20 million within two years.
The tree:
Membership revenue = Active base × Monthly dues ($50) × 12 months. Decompose the active base into: Starting cohort + New gross additions – Churn (cancellations). This immediately isolates whether the issue is top-of-funnel marketing or member retention.
Personal training and add-on revenue = number of members who buy training × sessions per member × price per session. Split the same way for add-ons.
Fixed costs: rent, equipment leases, salaried managers. These don't change with member count, so if one rose sharply (a lease renewal, say), that's a clean, separate cause.
Variable costs: class instructors paid per class, cleaning, card processing fees. These should move with members, so check whether cost per member rose.
Notice what's custom here. A generic profit framework says "revenue and costs." This tree says "sign-ups versus cancellations" because gyms live and die on members leaving, and it separates training from memberships because they have different buyers and different prices. The best branches in a case are the ones that only make sense for this client's business.
Hypothesis: "Membership revenue fell because cancellations rose after a lower-priced competitor opened nearby. I'd start by comparing member counts at gyms near a competitor with gyms that aren't."
Example B: market entry case, a grocery chain launching meal kits
Prompt: "A mid-size US grocery chain with 300 stores is considering launching a meal-kit delivery business. Should it?"
Clarifying answers: the goal is a new profit stream that breaks even within three years. The client has no delivery operation today.
The tree:
Is the market worth entering? How big is meal-kit spending in the client's regions, is it growing or shrinking, and do the existing players make money? A market where the biggest competitors lose money is a warning sign by itself.
Can this client win? List what the client already has that helps: 300 stores that could double as pickup points, supplier relationships that could make ingredients cheaper, and a brand shoppers already trust. Then list what it lacks: delivery vans and drivers, a subscription app, and experience with direct-to-home marketing.
Will it make money, and when? The upfront investment (kitchens, app, vans), the profit on each kit (price minus ingredients, packing and delivery), and how many kits a year it takes to cover the fixed costs. Section 6 works this math.
What does it do to the core business? Evaluate portfolio cannibalization and margin substitution: if existing in-store shoppers migrate to meal kits, does the incremental kit margin ($12 contribution) exceed the grocery basket margin they forfeit in the aisles
In a market entry case, the question of what entry does to the client's existing business is often where the real answer hides.
Hypothesis: "I suspect the market is attractive but crowded, so the answer depends on whether the store network gives the client a real cost advantage. I'd start with the unit economics of one kit."
Example C: operations case, a hospital emergency room
Prompt: "A hospital's average emergency room wait time doubled from two hours to four hours over the past year. What's going on?"
No revenue or cost framework fits this at all, which is exactly why it's a good test. The structure comes from how a patient moves through the ER.
The tree:
More patients coming in (demand). Did total arrivals rise? Did the mix change toward sicker patients who take longer? Did arrivals bunch up at certain hours, so the average hides a nightly jam?
Less capacity to see them (supply). Fewer beds open, fewer doctors or nurses per shift, or more staff out sick.
Each patient taking longer (process). Follow a patient's path: check-in, triage (the quick first assessment that decides who is seen first), seeing a doctor, waiting for tests like X-rays or bloodwork, then either going home or being admitted. Time can pile up at any stop.
Patients who can't leave. Patients admitted to the hospital sometimes wait in an ER bed because no bed is free upstairs. Hospitals call this boarding. Each boarded patient blocks a bed that a new ER patient needs, so a problem upstairs shows up as a wait downstairs.
The first three branches map directly to queueing dynamics: arrival rate (λ), service capacity (c), and cycle time (W). In any throughput diagnostic—whether an ER, airport security, or an underwriting queue—wait times spike from arrival volume surges, service station bottlenecks, or processing delays. That's a structure you can reuse for airport security, a restaurant kitchen or a call center, without ever memorizing it. When no standard framework fits a prompt, follow the thing that moves through the business, whether that's a patient, a package or a dollar, and your structure will be MECE almost automatically.
Hypothesis: "Wait times doubling in one year without a matching jump in arrivals points to boarding. I'd first check whether arrivals rose, and if they didn't, look at how long admitted patients sit in the ER."
5. When you blank, get new data, or get a chart, go back to the tree
The tree isn't only for the opening. It's the thing you return to every time the case knocks you off balance.
When you blank
Everyone blanks at some point. The recovery is mechanical, which is why it works:
Say out loud that you're stepping back. "Let me go back to my structure for a second."
Reread the objective you wrote at the top of your page.
Look at the tree and say which branches you've already covered and what they showed.
Move to the next untested branch.
That's it. Stepping back to your tree out loud turns a scary silence into visible, organized thinking, which is exactly what the interviewer is grading. It's what Skiles did in the cockpit: when the situation got confusing, he went to the page in front of him.
When the interviewer hands you new data
New data arrives constantly in a case, usually as a number or a short fact. Handle every piece in three moves. First, say what it means in plain words. Second, say where it sits on your tree. Third, say what it does to your hypothesis.
In the gym case, say the interviewer tells you new sign-ups held steady at about 20,000 a year, but cancellations rose from 20,000 to 25,000 a year. "So joining isn't the problem. Leaving is. That sits under the membership branch, and it supports my competitor hypothesis, since a cheaper option nearby gives members a reason to cancel. Do we know where the cancellations happened?"
When new data kills your hypothesis, drop it cleanly. "That rules out the competitor. If cancellations are flat everywhere, I'd move to the cost side and look at the lease renewals." Interviewers aren't testing whether your first guess was right; they're testing whether you update fast when the facts change.
When you get a chart or a table
Charts cause more mid-case freezes than anything else, because people try to read everything at once. Use the same four steps every time:
Read the title out loud, so you and the interviewer agree on what the chart shows.
Read the axes and the units. Is it members or revenue? Thousands or millions? One year or three?
Read the legend, if there is one, so you know what each line or bar stands for.
Find one big takeaway, then say the "so what" for the client.
Here's a worked example. The interviewer hands you this table for the gym chain:
Group | Members, 2024 | Members, 2026 | Change |
20 gyms with a new budget competitor nearby | 40,000 | 31,000 | down 9,000 |
30 gyms with no new competitor | 60,000 | 59,000 | down 1,000 |
All 50 gyms | 100,000 | 90,000 | down 10,000 |
Weak reading: "Members went down in both groups."
Strong reading: "This shows members by gym, split by whether a budget competitor opened nearby. Gyms near a competitor lost 9,000 of their 40,000 members, which is about 23 percent. Gyms without one lost 1,000 of 60,000, under 2 percent. So 90 percent of the member loss sits at the 20 gyms near a competitor. That strongly supports the hypothesis, and it tells the client where to focus: those 20 locations, not all 50."
The interviewer is waiting for the one sentence that turns the chart into a decision, not a description of every bar.
6. Case math under pressure: talk it out, round on purpose, and track your zeros
Case math is rarely hard math. It's easy math done while nervous, out loud, with someone watching. Four habits make it reliable.
Habit 1: Say your plan before you calculate. "To get the revenue loss, I'll multiply the lost members by the monthly fee, then by 12 months." If your setup is right and your arithmetic slips, the interviewer will usually catch the slip and let you fix it. If your setup is silent and wrong, nobody can help you.
Habit 2: Write units next to every number. "10,000 members," "$50 per member per month," "12 months." Units catch mistakes. If your answer comes out in "members times dollars" when you wanted dollars, you know you multiplied the wrong things.
Worked example, the gym revenue loss: 10,000 lost members × $50/month × 12 months = $6,000,000 in lost top-line revenue. At high gross gym margins (~80–90%), roughly $5M+ drops straight to the bottom line, explaining over 60–75% of the total $8 million profit decline. The remaining $2–3 million gap points directly to cost creep elsewhere in the chain.
Habit 3: Round on purpose, and say which way. Rounding makes mental math fast. The trick is to round one number up and the other down so the errors partly cancel.
38 × 52: round to 40 × 50 = 2,000. The exact answer is 1,976, so you're off by about 1 percent. Good enough for a case.
3.2 million × 45: split it. 3 × 45 = 135, and 0.2 × 45 = 9. So 3.2 × 45 = 144, and the answer is 144 million.
When you round, say so. "I'll call 38 about 40 to keep this clean, so this will run a little high."
Habit 4: Handle zeros separately from the digits. Big numbers are where people drop a zero and end up a factor of ten off. Strip the zeros off, do the small math, then add the zeros back.
Worked example: $2.4 billion divided by 60,000 customers. Write it as 2,400,000,000 ÷ 60,000. Cancel four zeros from both: 240,000 ÷ 6. That's 40,000. So the answer is $40,000 per customer.
Another way to track zeros is to count them. 2.4 billion is 2.4 × 1,000,000,000 (nine zeros), and 60,000 is 6 × 10,000 (four zeros). So the answer is (2.4 ÷ 6) followed by 9 minus 4 = 5 zeros. 2.4 ÷ 6 = 0.4, and 0.4 with five zeros added is 40,000. Same answer, checked two ways.
Percentages without a calculator
Break any percentage into easy pieces: 10 percent, 5 percent and 1 percent.
Worked example: 18 percent of 2,400. Ten percent is 240. Five percent is half of that, 120. One percent is 24, so 3 percent is 72. Add them: 240 + 120 + 72 = 432.
Percent change always divides by the starting number. Worked example: sales went from 80 to 92. The change is 12. Divide by the start, 80: 12 ÷ 80 = 0.15, or 15 percent growth.
Watch the difference between percent and percentage points. If profit margin (profit as a share of revenue) drops from 20 percent to 15 percent, it fell 5 percentage points. But as a percent of where it started, it fell 25 percent, because 5 ÷ 20 = 0.25. Say "points" when you mean points. Interviewers notice.
A few fractions are worth memorizing because they come up constantly: 1/3 is about 33 percent, 1/6 about 17 percent, 1/7 about 14 percent, 1/8 is 12.5 percent, and 1/9 about 11 percent. High-frequency case fractions: 1/6 ≈ 16.7%, 1/7 ≈ 14.3%, 1/8 = 12.5%, 1/9 ≈ 11.1%, and 1/12 ≈ 8.3%
Breakeven, the most common case calculation
Breakeven is the number of units a business has to sell for profit to hit zero. Each unit sold earns a contribution: the price minus the variable cost of that unit. Breakeven is the fixed costs divided by that contribution per unit.
Worked example, the meal kits from Example B. Say each kit sells for $60, and ingredients, packing and delivery cost $48 per kit. Each kit contributes $60 − $48 = $12 toward fixed costs. Say the kitchens, app and vans cost $30 million a year to run no matter how many kits ship. Breakeven is $30,000,000 ÷ $12 = 2,500,000 kits a year. Divide by 52 weeks and that's roughly 48,000 kits a week.
Then do the step most candidates skip: sanity check. Is 48,000 kits a week realistic for a 300-store grocer? That's about 160 kits per store per week, or 23 a day. That's plausible if the client can sell kits to its existing shoppers, which brings you right back to the cannibalization branch. A number only matters once you've said what it means for the client's decision.
7. Synthesize with a recommendation a partner could repeat in 30 seconds
At the end of the case the interviewer usually says something like "The CEO just walked in. What do you tell her?" This is the synthesis. Many candidates answer by retelling the case in order. Don't. Lead with the answer.
Use this template:
The recommendation, in one sentence.
Two or three reasons, each with a number from the case.
One or two risks.
Next steps.
Worked example, the gym case:
"I recommend the client focus its turnaround on the 20 gyms near the new budget competitor, with a lower-priced membership tier and a push on personal training there. Three reasons. First, lost members cost about $6 million a year, which is three quarters of the $8 million profit drop. Second, 90 percent of that loss is at those 20 gyms, so a targeted fix beats a chain-wide price cut. Third, the other $2 million came from lease renewals, which we can't reverse this year. The main risk is that a cheaper tier pulls existing members down from $50, so we'd want to limit it to those 20 locations and test it first. Next steps: price test at five of those gyms, and a review of the lease terms coming up for renewal."
That's about 45 seconds spoken. A good synthesis works because every sentence carries a number from the case, and a partner could repeat the first sentence to a client without the rest.
A synthesis that starts with "So, in summary, we looked at revenue and costs" has already lost the room, and one that starts with the recommendation has already won it.
8. The physical side of pressure is trainable
Pressure is partly in your body, and the fixes are practical.
Breathing. Before the interview, and during any pause you've asked for, breathe in through your nose for about four counts and out slowly for about six. A longer exhale than inhale slows you down. Do two or three of these while you look at your paper. Nobody can tell. Slow breathing during the pause you asked for is the cheapest way to get your thinking back, and the interviewer sees only a candidate looking at their notes.
Pacing. Nervous candidates talk fast, and fast talkers skip steps. Wait a full second after the interviewer finishes before you respond. Speak a little slower than feels natural. During math, it's fine to go quiet for five seconds and then say the number. Filling the air with "um, so, like" costs more than a short silence.
Paper layout. A messy page creates panic, because you can't find the number you wrote five minutes ago. Set your page up the same way every time:
Top of page one: the objective in one line, plus the key facts from the prompt (50 gyms, $20M to $12M, two years).
Middle of page one: the issue tree, big and clean, so you can turn the page toward the interviewer and point at it.
A separate page for math, with each calculation labeled ("revenue loss," "breakeven") and the final number circled. Use a dedicated landscape page for calculations. Align math horizontally from left to right, box key interim figures, write units ($ / units / months) after every number, and double-underline the final business answer.
A running list of findings in one corner, one line per piece of data. When synthesis time comes, your three reasons are already sitting there.
Write in landscape if it helps the tree fit. In a video interview, keep paper and a pen anyway, and ask if the interviewer would like you to hold your structure up to the camera.
Candidates who set up their page the same way every time find their numbers faster and panic less, because the layout does the remembering for them.
9. A four-week practice plan for the consulting case study
Structure under pressure comes from practice that feels like the real thing, not from reading more frameworks. Here's the plan I'd give a student four weeks out from first rounds. The WSG guides on how to prepare for a consulting interview and breaking into MBB cover the wider recruiting picture this sits inside.
Week 1: structure drills and math. Collect about 20 case prompts from free case libraries (the WSG list of free case prep resources has good sources). For each one, set a 90-second timer and build only the tree. Then check it against the two MECE tests. Separately, do 15 minutes of mental math a day: multiplication, percentages and zeros from section 6.
Week 2: full cases with a partner. Do full cases with a partner, several a week, and switch roles. Giving cases teaches you as much as taking them, because you see what a messy structure looks like from the other side of the table. Start with McKinsey's official interactive case walkthroughs (such as Conservation International, Parks Inc., or Electro-Light on their candidate portal). Supplement with BCG's interactive case library and curated business school casebooks (e.g., Wharton, Kellogg, or Columbia club books) for realistic partner prompts.
Week 3: pressure on purpose. Now make practice uncomfortable. Practice with someone you don't know well. Turn the camera on. Ask your partner to interrupt with a chart or throw in data that kills your hypothesis. Practice both interviewer-led and candidate-led formats. After each case, write down the one moment you froze and what you'd do differently.
Week 4: full mock interviews and rest. Do two or three full mocks that include the behavioral half, since the pressure doesn't stop when the case does. For McKinsey, that's the Personal Experience Interview. Take the last day or two off from cases. Tired candidates structure worse.
For a shorter list of habits to layer on top of this plan, the WSG 10 tips to beat the case interview is a good quick read.
A junior I worked with through WSG, call her R, froze on her first two practice charts and assumed she was bad at charts. She wasn't. She was reading every bar before deciding what the chart was about. Once she forced herself through the title, axes, legend and one-takeaway routine on every chart for two weeks, the freezing stopped, and she went into her final round with McKinsey calm enough to catch a units trick the interviewer had built into the data.
Say this, don't say that
Opening the case
Don't say: "I'll use a profitability framework."
Say: "Profits can only fall because revenue fell, costs rose, or both. For a gym, I'd split revenue into members joining and members leaving, because those need different fixes."
Asking for time
Don't say: "Um, okay, so, I think the first thing is maybe revenue..."
Say: "Would you mind if I took a minute to structure my thinking?"
When you blank
Don't say: "Sorry, I'm totally lost."
Say: "Let me step back to my structure. We've ruled out new sign-ups, so the next branch is cancellations."
When the data kills your hypothesis
Don't say: "Well, it could still be the competitor, because..."
Say: "That rules out the competitor. If cancellations are flat everywhere, I'd move to the cost side."
Doing the math
Don't say: nothing, while you compute silently for 40 seconds.
Say: "I'll multiply 10,000 lost members by $50 a month, then by 12. I'll round where it helps and tell you which way."
Reading a chart
Don't say: "This chart shows members over time."
Say: “Ninety percent of our membership decline is isolated to the 20 locations facing new budget competitors, where churn reached 23% versus 2% elsewhere. We should focus our intervention exclusively on these 20 facilities rather than deploying a dilutive chain-wide price discount.”
Closing the case
Don't say: "So, in summary, we looked at revenue, then costs, then..."
Say: "I recommend focusing the turnaround on the 20 gyms near the competitor, for three reasons."
Build the routine before you need it
The Flight 1549 crew didn't build their habits at 2,800 feet. Sullenberger and Skiles had tens of thousands of flight hours between them before that afternoon, which is why they could follow a checklist and break from it at the right moment. Your case prep works the same way. Pick one practice prompt tonight, set a 90-second timer, and build the tree on paper. Then do it again tomorrow with a different case type. By first rounds, the routine should run before the nerves do.
Comments