r/ConsultingOffer

You've done the cases. Dozens of them. You've watched the YouTube videos, read the prep books, practiced with partners until the questions felt familiar. And then you walked into the interview and something broke down anyway.

The firm's rejection letter tells you almost nothing. "We've decided to move forward with other candidates" is not feedback. It's a form email.

But this could have been avoided and the culprit is the vague feedback candidates get throughout their preparation phase, from peers, from generic case prep platforms, from AI tools, from coaches who may have worked at these firms but can't always articulate what the interviewers are actually evaluating or how to systematically improve a specific skill needed for acing case interviews.

"Your structure could be stronger."

"You need to be more confident."

"Your recommendation lacked clarity."

None of that tells you which specific part of your case broke down or what to actually do about it. And so candidates keep practicing, keep getting vague feedback, and keep making the same mistakes without knowing it.

That's the real problem most candidates face, non-traditional or not. Not that they haven't practiced enough. It's that they've been practicing without knowing which specific part of the case is costing them points.

Volume without diagnosis is just expensive repetition.

In my view, after coaching tens of candidates from non-traditional backgrounds into McKinsey, BCG, Bain, and Tier 2 firms, the candidates who improve fastest are the ones who stop thinking about "the case" as one skill and start treating it as seven (7) distinct skills, each one trainable on its own. And the ones who perform best in the room are the ones who approach every case with an owner attitude: this is my problem to solve, not a test to perform for someone watching.

That mindset, combined with first principles thinking rather than memorized frameworks, is the thread running through every post in this series. That's what this series is built around.

This post is the map. It's not a drill and it's not a module walk-through. If you're new to The Case Playbook, this is where to start. If you've been following along and you're not sure what to focus on next, this is where to locate yourself. And if you've been grinding cases without seeing improvement, this post will show you exactly why that happens and what to do instead.

The problem most candidates don't know they have

A candidate who does thirty cases with the same weakness in their clarifying question phase will have that weakness for all thirty cases. The fix isn't more cases. It's knowing which specific module in a case interview architecture is costing you points.

And, again "Volume without diagnosis is just expensive repetition"

If you want honest module-level feedback on where you're leaving points on the table, I run one-on-one mock case interview sessions built around exactly that. But first, here's the architecture.

Why the module-level view changes everything

A case interview is not one skill. It's seven skills, sequenced across thirty minutes, each one distinct enough to be trained, measured, and improved independently.

When a partner gives you feedback that your "framework felt generic," they're commenting on one specific module: the Issue Tree. When they say you "didn't feel confident in the opening," they're commenting on the Case Opening module. When they say your "recommendation was unclear," they're commenting on the Case Wrap-Up module.

If you know which module the feedback belongs to, you can isolate it, drill it, and improve it without touching the others. That's how real improvement happens. Not by doing more cases in general. By doing targeted work on the specific module where you're leaving points on the table.

This is how I work with candidates one-on-one, After a mock case interview, I give feedback at the module level: where in the seven modules did you lose points, where did you gain them, and what specifically to work on next. I also assess whether the candidate is approaching each module with an owner attitude, genuinely curious about the problem and reasoning from first principles, or whether they're performing a rehearsed script. Partners within elite consulting firms feel that difference within the first two minutes. That level of specificity is what makes feedback actionable. Without it, "do more cases" is the best advice anyone can give you. Even my grandmom would say that, and she's never heard of MBB, L.E.K, Roland Berger and others. With it, you can improve in days rather than weeks.

The mock case walk-through: NordPlay Studios

The best way to see how all 7 modules connect is to step inside a real case interview. Throughout this series we've used NordPlay Studios as the anchor case. Let me walk you through what 30 minutes actually feels like when all seven modules are running together.

You're sitting across from a partner. Pen in hand. One sheet of paper in front of you. Nothing else.

The partner reads: "Our client is NordPlay Studios, a mobile gaming company headquartered in Stockholm. They employ over 3,000 developers and designers. Net profits have declined over the past 2 years. They'd like to understand why and how you can help."

Module 1: Case Opening

The moment the prompt lands you start writing. Bullet points. Fast. You're not organizing yet, you're capturing. Game developer and publisher. B2C. App stores. Profits declining. Two years.

You reiterate: "Let me make sure I have this right. NordPlay develops and publishes mobile games for end users globally through app stores. Net profits have declined over two years. They want to understand the root cause and how to address it. Is that correct?"

While confirming, your pen is moving. You circle "profits" because that's not a number yet, and "globally" because markets matter. You ask circle by circle. Net profits specifically. Down from $2.4 billion to $2 billion, a $400 million decline. Objective: restore to $2.4 billion. Constraint: one year.

You look at your page. You build the problem statement: find the root cause of why NordPlay's net profits fell by $400 million over two years and identify how to restore them within one year.

The partner nods. Case Opening done. Posts 1, 2, 3, 4, and 6 cover this module in depth.

Module 2: Issue Tree

"Could I take a moment to develop my hypothesis and issue tree?"

Forty-five seconds. You're not staring at the ceiling. You're thinking like an owner. NordPlay is your company. Your CFO just walked in. Profits dropped $400 million. You don't reach for a framework! You ask the simplest possible question: did we make less money or spend more?

That question becomes your issue tree.

Branch one: revenues and costs.

Branch two: fixing the root causes and executing the recovery within one year.

Under revenues you go one level deeper: volume, pricing, product mix, because those are the three levers any B2C mobile gaming company has.

Under costs: fixed and variable, then specific to NordPlay, headcount and R&D on the fixed side, app store fees and contractors on the variable side.

You state four sub-hypotheses and ask for NordPlay's P&L. The partner slides a dataset across the table.

Posts 5, 7, 8, 9, 10, 11, and 13 cover this module.

Module 3: Structured Brainstorming

Partway through Case Middle, the partner pivots. "Before we go deeper into the data, can you brainstorm why the premium subscription revenue might have declined?"

The owner attitude kicks in. This is your subscription business. You don't list ideas at random. You apply a contrast pair derived from first principles: did fewer people subscribe, or did the same people pay less? Under fewer subscribers: acquisition or retention. Under lower revenue per subscriber: price level or pricing architecture misalignment.

You prioritize two areas: pricing architecture and premium tier churn. You explain why. The partner writes something down.

Posts 14, 15, 16, 17, 18, 19 cover this module across four different case types.

Module 4: Data Conversion

The partner hands you a chart. NordPlay Net Revenue by Segment, Year 1 through Year 2. Two lines. Subscription revenue dropping from $1.8 billion to $1.4 billion. Advertising flat at $600 million.

You don't dive into the numbers immediately. You read the title. You identify the axes. You name the two lines. Then you talk: "Subscription revenue fell $400 million while advertising held flat. The entire net profit gap is on the subscription side, not a broad demand problem. This confirms sub-hypothesis one and tells me the next data request should be subscriber volume by tier."

The partner is nodding before you've finished the sentence. Post 22 covers this module.

Module 5: Consulting Math

"If NordPlay raises premium prices by 10% and loses 5% of subscribers, what happens to monthly revenue?"

You state the equation before touching a number. New revenue equals new subscribers times new price. Current: 8 million at $25, $200 million per month. After: 7.6 million at $27.50. You work through the arithmetic out loud on paper. $209 million per month. Net gain: $9 million monthly, roughly $108 million annually.

You interpret: meaningful contribution to the $400 million gap, but the 5% churn assumption is the key variable. If actual churn is 10%, the picture reverses. The partner asks you to hold that thought.

Post 20 covers this module.

Module 6: Problem Solving

"App store fees are currently 15% of revenue. If NordPlay renegotiates to 10%, what happens to net profit margin?"

You set up the equation. Current net profit: $2 billion on $8 billion revenue, 25% margin. A 5 percentage point fee reduction saves 5% of $8 billion, or $400 million. New net profit: $2.4 billion. New margin: 30%.

You look up from the paper. "This single lever closes the entire gap and restores net profits to $2.4 billion within one year. In my view this should be the first recommendation."

Post 21 covers this module.

Module 7: Case Wrap-Up

"Let's wrap up. What's your recommendation?", the Partner says:

"Could I take sixty seconds to pull this together?" You look at your notes. Issue tree. Sub-hypotheses tested. Data findings. You deliver top-down.

What: NordPlay should pursue a two-track recovery plan through a premium subscription pricing restructure and an app store fee renegotiation, targeting full $400 million restoration within one year.

Why: three reasons:

First, the revenue decline is entirely concentrated in the premium subscription tier, attributable to pricing architecture not platform demand.

Second, a managed price increase adds over $100 million annually with acceptable churn risk.

Third, app store fee renegotiation is the single highest-impact controllable lever available within the one-year window.

How: as next steps, I'd recommend three workstreams:

First, a thirty-day pricing architecture study, because the churn assumption is the key variable and we need to size it before committing to a price change.

Second, a sixty-day fee benchmarking and negotiation strategy, because this is the fastest path to closing the remaining gap with zero product risk.

Third, a risk monitoring workstream from day one tracking churn response in real time, so we can course-correct within ninety days if the numbers move against us.

The partner closes their notebook. That's the case.

Post 23 covers this module.

The architecture: three sections, seven modules

What you just read wasn't a list of techniques. It was a thirty-minute consulting case interview. You went from a vague eighty-word prompt to a fully structured recommendation backed by data, math, and a clear implementation plan. You did it without a calculator, without knowing the gaming industry in advance, and without a script.

That's what the owner attitude and first principles thinking make possible across all seven modules.

Here's the architecture you just lived through, laid out in one place so you can use it as a reference map going forward.

Every consulting case interview, regardless of firm, round, or case type, moves through three sections containing seven modules in total.

Case Start (3 to 10 minutes)

This is where you set the stage. Two modules.

Module 1: Case Opening. The five mental moves that take you from a vague prompt to a sharp, quantified problem statement. Clarifying questions, reiteration, surgical data asks, objective and constraints, problem statement.

Module 2: Issue Tree. From the problem statement, you state a hypothesis, build a bespoke issue tree from first principles rather than memorized templates, state four sub-hypotheses, and make your first data request.

Case Middle (15 to 24 minutes)

This is where you do the work. Four modules that cycle in different combinations depending on the interviewer, the firm, and the case type.

Module 3: Structured Brainstorming. Generating structured, insightful ideas using the four-step approach and contrast pairs rather than memorized category lists or any framework.

Module 4: Data Conversion. Reading charts and data exhibits, orienting to what you're looking at, generating second and third-degree insights, and connecting those insights back to the main hypothesis.

Module 5: Consulting Math. Setting up the right equation before touching a number, narrating your arithmetic out loud, and interpreting the result in terms of the case.

Module 6: Problem Solving. Translating a multi-sentence business scenario into the right equation, working through it verbally, and connecting the answer to the hypothesis.

Case End (3 to 5 minutes)

This is where you close. One module.

Module 7: Case Wrap-Up. A top-down recommendation answering What, Why, and How, with three supporting reasons anchored in case findings and next steps that include a risk monitoring workstream.

How to use this series

If you're just starting case prep, read the posts in order. The series is designed to build on itself. Each post assumes you've read the ones before it.

If you're already in case prep and have specific gaps, use this post as a diagnostic map. Find the module where your feedback has been concentrated and go straight to those posts. You don't need to reread everything.

But, if you want to practice the full arc with someone who knows what top performers actually sound like in a case interview, 1-on-1 mock case sessions are available. Again, r/ConsultingOffer community for details and any Q&A.

Or even, if you want the full structured journey from non-traditional background to consulting offer, check out the quarterly Consulting Offer Program, the Q4 cohort starts September 1, 2026. Seats are limited. This is where I work with a small group of candidates through the complete methodology over a sustained period, with a money-back guarantee on the outcome. If that's what you're looking for, don't wait.

Everything else in this series is free and will stay free. The r/ConsultingOffer community is where the conversation lives. Drop your questions, share your practice cases, and engage with others who are on the same path. That's what the community is here for.

What module are you currently working on, and where in the series are you getting stuck?

I want to show you something practical in this post. Not more theory. An actual walk-through of how the first few minutes of a profitability case should go, and more importantly, why each move happens in the order it does.

This is post 2 in The Case Playbook, a series built for non-traditional candidates breaking into MBB, Tier 2, and Big 4 consulting firms. If you haven't read post 1 on the five mental moves yet, start there. This post picks up directly from it.

But before I get into the case itself, I need to give you the mental frame that makes everything else click. Because without it, you'll read this walk-through and try to memorize it, and that's exactly the trap I want to pull you out of.

The reframe that changes everything

Most candidates walk into a consulting case interview thinking: "I am a student being tested on whether I know the right things to say."

That frame is what creates the robotic, scripted clarifying questions that interviewers at McKinsey, BCG, and Bain can spot within the first exchange.

Here's the frame I coach instead. You are the owner of a business. You don't know every technical detail of every department you run, but this business is yours. One of your senior employees walks into your office and says: "We have a problem. Profits are down."

What do you do? You don't sit there staring at the wall. You don't pull out an issue tree you memorized in business school. You get curious. Naturally, instinctively curious. You start asking questions because you genuinely need to understand what's going on before you can do anything useful about it. The five moves I'm about to walk you through aren't a script. They're just what naturally happens when a curious owner starts thinking out loud.

Hold that frame as you read the rest of this.

The case: NordPlay Studios

Here's the prompt as the interviewer delivers it:

"Our client is a mobile game developer called NordPlay Studios. They employ over three thousand developers and designers and are headquartered in Stockholm, Sweden. They develop and publish mobile games for end users globally. End users download the games and play them on their devices. NordPlay Studios has seen profits decline over the past two years. They would like to understand why that is the case and how you can help them."

That's it. About eighty words. No numbers, no specifics, no clear problem. Just a blob of English.

And here's the first thing an owner thinker recognizes: this isn't solvable yet. That's not a failure. That's the point. No serious consultant, no matter how experienced, can take that prompt and go straight to building an issue tree. The prompt is a starting point, not a brief. Your job in the next three to four minutes is to turn it into something you can actually work with.

Move 1: Absorb before you react

When the prompt is being read, the owner's instinct is to write everything down. Not to organize, not to categorize, just to capture. You listen and you write in bullet points at the pace the interviewer is speaking.

The memorizer starts building their structure in their head while the interviewer is still talking. The owner stays open because they know they don't have enough yet to decide what matters.

There's something else happening in Move 1 that most candidates miss. You're managing the initial shock of a new industry, a new situation, a new set of unknowns. Writing anchors you. It gives your nervous system something to do other than panic. And it signals to the interviewer, who is watching you from the moment the prompt starts, that you are present and tracking.

In this case, the owner hears "mobile game developer," "profits declining," "two years," and immediately starts getting a rough shape of what this is likely to be. Probably a find-the-root-cause, fix-it, get-back-to-a-number type of problem. That's not a conclusion, it's a working hypothesis. The specifics come later.

Move 2: Play it back, then mark what you don't understand

After the prompt, the owner confirms what they heard. Not word for word, that's annoying. They reiterate the key details to verify accuracy and show they were listening.

"Thank you. Let me make sure I have this right. Our client is NordPlay Studios, a mobile game developer and publisher with over three thousand developers and designers, headquartered in Stockholm. They make games for end users globally who download and play on their devices. Profits have declined over the past two years and they want to understand why and how we can help. Is that correct?"

While confirming, the pen is moving. You're circling phrases you're genuinely curious about. In this prompt, in my view there are four natural circles: "game developer and publisher" (what does that mean operationally?), "end users" and "devices" (what's the actual value chain here?), "globally" (which markets and through which channels?), and "profits" (which profits exactly?).

Those circles become your clarifying questions. You're not inventing questions to seem thorough. You're asking about the things you actually don't know, because as the owner, you need to know them before you can do anything useful.

The memorizer asks three generic questions because that's what they were taught. The owner looks at their four circles and asks about those specific things, in this specific case, because those are the real ambiguities.

Move 3: Ask surgically, then find the math

Now you go circle by circle. Direct, curious, unhurried. Not firing questions in rapid succession like a checklist. One at a time, with genuine interest in the answer.

"When you say game developer and publisher, what does that mean exactly? Do they design, code, and distribute their games themselves end to end?"

The interviewer confirms: yes, they design, code, and publish globally.

"You mentioned end users downloading games on devices. Is this a B2C business, and do they distribute through the App Store and Google Play?"

Yes, B2C, through App Store and Google Play.

"When you say devices, are we talking primarily mobile, or also PC and console? And to help me get oriented, is this similar to something like Candy Crush, casual mobile gaming?"

Primarily mobile, some PC. Yes, casual mobile gaming is the right reference point.

Now comes the move that separates good clarifying questions from great ones. You need to find the math. The prompt is in English. Your issue tree has to be grounded in math. So the last circle, profits, is where you convert.

"You mentioned profits are declining. Which profits specifically are we looking at, and what were the figures two years ago compared to now?"

Net profits. $2.4 billion two years ago, now $2 billion.

That's a $400 million decline. Now you have something real to work with.

Move 4: Lock down the objective and the constraints

The owner doesn't start working until they know what success looks like and what the rules of the game are. These are two separate questions that most candidates collapse into one, or skip entirely.

"From an objective standpoint, would you like me to recover net profits back to the level from two years ago, so back to $2.4 billion?"

Yes.

"Are there any constraints I should be aware of, timeline or otherwise?"

One year. Nothing else for now.

This move takes about fifteen seconds. It's not glamorous. But without it you're solving in the dark. A one-year constraint versus a five-year constraint changes everything about what solutions are even viable. If the constraint were "revenues must not decrease," that eliminates entire categories of cost-cutting approaches immediately. You need the walls of the room before you start moving around inside it.

From what I've seen coaching candidates, this is the most commonly skipped move. They ask about objectives, get a vague answer, and move on. They never ask about constraints. Or they ask about both but in such a rushed way that they don't actually absorb what they're told. Either way, they end up building an issue tree around a problem they haven't fully defined.

Move 5: Build the problem statement, not a summary

Now you take a moment. You look at your notes. And you build one crisp sentence that defines the problem you're about to solve.

"I'd like to take a moment to put together a problem statement. I believe the core question is: why did NordPlay Studios' net profits fall from $2.4 billion to $2 billion over the past two years, and how do we identify and fix the root causes to recover back to $2.4 billion within one year. Does that capture it?"

The interviewer agrees.

Compare that to the original prompt. Eighty words of vague English versus one precise, quantified, time-bound question. That's the transformation the owner thinker creates in three to four minutes. A $400 million decline, a specific recovery target, a one-year window. That's a case you can actually structure and solve.

Here's why this matters more than it looks. In real consulting work, one of the most valuable things a team does for a client is help them define their own problem correctly. Clients come in with a vague sense that something is wrong. The consultant's job is to turn that vague discomfort into a precise, answerable question. When you nail the problem statement in a case interview, you're demonstrating exactly that ability at a micro level.

What the interviewer is actually watching

The five moves above aren't just about getting to the right problem statement. They're signals. Every move of the Case Opening is the interviewer reading your working style.

Are you composing yourself under pressure? Are you genuinely curious or just performing curiosity? Are you listening to the answers you get and adjusting, or are you just firing the next question on your list? Are you organized without being robotic?

The memorizer performs all of this. The owner actually does it, because they genuinely need to understand the situation before they can help.

That's the difference. And interviewers who have seen hundreds of cases feel it within the first few minutes.

One thing I'd encourage you to try: take this walk-through and replicate it out loud, with a friend reading the NordPlay prompt to you. Not reading along, speaking it live. Because the real skill here is doing all five moves verbally, in real time, with no script in front of you. That's where the practice has to live.

If you're currently prepping for a case interview and want to share where you're getting stuck in this phase specifically, drop it in the comments. Happy to give you a more specific steer based on what you're running into. And if you found this through another community, the full Case Playbook series is in r/ConsultingOffer.

The next post in The Case Playbook applies the same five moves to a public sector case, a government ministry facing a completely different kind of problem in a completely different industry. It's designed to show you that the owner thinker approach works on any prompt you'll ever receive, not just private company profitability cases. That's where most candidates discover whether they've actually internalized the moves or just memorized them for one case type.

I've been posting here for a while now and I realize I actually don't know where most of you are in the process. Like, are you still figuring out if consulting is even the right path, or are you deep in interview prep right now? Makes a big difference in terms of what's actually useful to cover.

So let's do this the simple way. Drop a letter in the comments:

A) Still exploring, not sure consulting is the right move for me yet

B) Convinced I want in, but haven't started networking seriously

C) Actively building relationships and trying to land a referral

D) In interviews right now (or just wrapped up a round)

E) Already in consulting, here to learn or give something back

No right answer. Wherever you are is wherever you are. I'm just curious - and honestly, the responses will shape what I focus on here over the next few weeks.

Drop your letter below.

Posts 15, 16, and 18 covered Structured Brainstorming across a profitability case, a public sector finance case, and an M&A case. Each of those involved organizations, financial variables, and business dynamics that candidates have some familiarity with.

This is post 19 in The Case Playbook, a series built for non-traditional candidates breaking into McKinsey, BCG, Bain, Tier 2, and Big 4 consulting firms. This post is different. It covers brainstorming on a physical asset, a water treatment plant, and that requires a different kind of reasoning than anything we've covered so far.

If you've been following the Solvik case through this series, posts 6 and 13 covered Case Start and the issue tree. The problem statement is established: find the root cause of why the Voss plant's output fell from 90 million liters per day to 54 million liters per day and restore it within four weeks. The issue tree mapped the system into upstream, plant, and downstream. Now the partner pivots to brainstorming.

The brainstorming question: "We've mapped the system. Can you brainstorm the specific reasons why the Voss plant might be experiencing reliability problems that reduced its output by 36 million liters per day?"

Why physical asset brainstorming is different

Before running the four steps, it's worth naming what makes this case type categorically harder than the others.

When you brainstorm on a profitability case, you're reasoning about financial variables you encounter daily: revenue, cost, margin, pricing. When you brainstorm on an M&A case, you're reasoning about organizational dynamics you can extrapolate from general business knowledge.

When you brainstorm on a physical asset, you're reasoning about a system you've almost certainly never operated. Most candidates have never been inside a water treatment plant. Most don't know the difference between particle filtration and biological treatment. And when they hear "brainstorm why a water plant is unreliable," they freeze. Not because they can't think, but because they don't have a mental image of the system to reason from.

The owner thinker handles this the same way they handle any unfamiliar territory: they go back to first principles. Forget that it's a water treatment plant. Ask the most basic question possible: how does anything flow through a physical system? It comes in, it gets processed, it goes out. That's upstream, the plant, and downstream. Everything else is a sub-level of those three.

That instinct, applying a simple physical logic to an unfamiliar asset, is what separates candidates who can brainstorm on any case type from those who can only brainstorm on familiar ones.

Step 1: Absorb and anchor

Write it down: "Brainstorm why the Voss plant is experiencing reliability problems causing a 36 million liter per day decline."

Reiterate: "So you'd like me to brainstorm the specific reasons why the Voss plant's operational reliability has degraded to the point where output fell from 90 million liters per day to 54 million liters per day. Is that the right scope?"

The partner confirms.

The reiteration does something important here. It converts a vague "reliability problem" into a specific quantitative gap. You're not brainstorming why water plants in general have problems. You're brainstorming why this specific plant lost 36 million liters per day of output. That precision raises the quality ceiling of everything that follows.

Writing it down also gives your brain a moment to build a mental image of the system before the brainstorm begins. That's the activation phase working exactly as designed.

Step 2: Clarify and orient

Two circles: "reliability" and "clean water."

"When you say the plant is unreliable, I'm reading that as a supply capacity issue, the plant is producing less clean water than it should rather than producing water of degraded quality. Is that the right interpretation?"

The partner confirms: yes, it's a supply volume problem, not a quality problem.

"And to confirm scope: we're looking at the Voss plant's own operational system, so upstream infrastructure feeding the plant, the plant's internal processing, and downstream distribution from the plant to residents?"

The partner confirms.

That second clarification defines the three zones of your brainstorm before you begin. You've just sketched the structure in the partner's mind through a question rather than announcing it as a presentation. That's the owner thinker approach: derive the structure from the conversation rather than declaring it from memory.

Step 3: Brainstorm with contrast pairs across the physical system

The mental image you need is simple: water moves through this system in one direction. It enters the Voss plant from a source, gets treated inside the plant, and exits toward residents. Something in that journey is causing 36 million liters per day to not complete the trip. Your job is to brainstorm where in the journey the problem could be.

What Flows In (upstream)

Before water reaches the Voss plant, it travels through an intake infrastructure. Apply the first contrast pair: the physical components versus the support systems that keep them running.

The Pipes: the intake pipes themselves could be the problem. A blockage reduces inflow volume. A rupture or leak means water that should reach the plant is lost before it arrives. Corrosion over time reduces pipe capacity below design specifications.

The Equipment: pumps and valves control the rate of water flow into the plant. A failed pump reduces inflow pressure and volume. A malfunctioning valve creates flow restrictions or uncontrolled flow rates that the plant's processing system can't handle at full capacity.

The Support System: physical components don't fail in isolation. Something enables or prevents their proper function. Split into three: software and hardware (the monitoring systems, sensors, and control systems that manage intake operations), people and processes (the operators and maintenance routines that catch problems before they become failures), and external factors (power outages, upstream environmental events, seasonal changes in water source availability that affect inflow quality or volume).

The Plant Itself

This is the most complex zone and the most likely source of the problem, which is why you test it first even though you announce upstream first. Apply the same physical logic: water moves through three stages inside the plant.

Raw Water Intake: at the point where water enters the plant's processing system, the same categories apply: pipes, equipment, and support systems. But now you're inside a controlled environment where problems have immediate downstream effects on everything that follows.

The Processing Core: this is the heart of the plant and where the highest complexity and highest failure probability lives. Three stages, each essential and each a potential failure point.

Particle Removal: dirty water carries physical matter, large debris and fine sediment. The filtration systems that remove these particles can clog, degrade, or fail. When particle removal capacity is compromised, the downstream stages are overwhelmed with material they weren't designed to handle at that volume, reducing overall throughput.

Germ Removal: biological contaminants require a separate treatment process, typically UV treatment or chlorination. If the germ removal system is operating below capacity, the plant faces a choice: continue at full output and compromise water quality, or throttle output to ensure treated water meets safety standards. A plant that chooses safety over volume will show exactly the kind of output reduction we see at the Voss plant.

Chemical Treatment: the final treatment stage adjusts pH and adds disinfectants to make water safe for consumption. Problems here can cascade back upstream: if chemical treatment can't handle the current inflow volume, the entire processing rate gets throttled to match treatment capacity.

Clean Water Discharge: at the output end of the plant, the same physical categories apply again: pipes, equipment, and support systems. A failure here means treated water that's ready to distribute can't actually leave the plant at the designed rate.

What Flows Out (downstream)

Once water leaves the Voss plant, it travels through a distribution network to reach the approximately 500,000 affected residents. The same contrast pair applies: physical components versus support systems.

The Pipes: distribution pipes can fail the same ways intake pipes can. Blockages, ruptures, and capacity degradation all reduce the volume of clean water that actually reaches homes even if the plant is producing normally. A significant leak somewhere in the distribution network could explain why plant output appears to have declined when the actual failure is in delivery.

The Equipment: pumping stations maintain pressure throughout the distribution network. If a key pumping station fails, the pressure drop affects delivery to entire segments of the city.

The Support System: monitoring, maintenance routines, and emergency response protocols govern how quickly problems are identified and addressed. A gap in any of these means problems that could be caught early become failures that persist.

Step 4: Prioritize and drive forward

"Based on what I've laid out, two areas feel most likely to contain the root cause. First, The Processing Core, specifically germ removal and chemical treatment: a 36 million liter per day drop is a 40 percent reduction in output, and that's the kind of magnitude you'd expect from a safety-driven throttling decision rather than a catastrophic failure. I'd want to see the plant's operational logs and shutdown records first. Second, the downstream distribution network: it's possible the plant is producing at normal capacity and the problem is in delivery, not production. Cross-referencing plant output data with distribution pressure readings would clarify this quickly. I'd want to test the plant-side hypothesis first since that's where we've focused the issue tree, but I wouldn't rule out the distribution network until I've seen the data."

Why physical system brainstorming transfers

Here's the insight that has the most long-term value.

The structure you just used to brainstorm the Voss water plant works on any physical asset. An oil refinery has a feedstock intake, a processing core, and a product output. A gas plant has an intake, compression and treatment, and distribution. A manufacturing facility has raw material input, production, and finished goods output. The specific equipment and terminology changes. The logic of input, process, output is universal.

This means that learning to brainstorm one physical asset gives you a transferable template for any other. You don't need to study every asset type. You need to internalize the physical logic that underlies all of them: something flows in, something happens to it, something flows out. Where in that journey is the problem?

That's the contrast pair applied to a physical system. And it's available to any candidate willing to stop trying to recall technical knowledge and start reasoning from first principles.

If you're prepping infrastructure or asset-level brainstorms and want to share a question you've been working on, drop it in the comments. I'll show you where the contrast pairs apply. And if you found this through another community, the full Case Playbook series is at r/ConsultingOffer.

The next post in The Case Playbook moves into a new Case Middle module: Consulting Math. If Structured Brainstorming across four different case types is now feeling solid, Consulting Math is what comes next. It covers how to handle quantitative questions in a case interview, from quick market sizing estimates to back-of-the-envelope calculatio

About six years ago I was on the other side of this. Going through strategy consulting recruiting myself, targeting multiple firms, trying to figure out what each process actually looked like from the inside. I ended up getting offers from several of the firms I'll name in this post and accepted two of them. That experience is where everything started.

Since then I've been coaching candidates, non-traditional backgrounds, career switchers, people without MBAs or target school pedigrees, to break into these same firms. Tens of people over the past few years, across MBB, Tier 2, and Big Four. And the single most consistent mistake I see is candidates treating every firm as if it runs the same process.

I built this series to reduce the friction I see again and again. Sixteen firms, each broken down stage by stage, with my honest read on what each firm is actually testing, where the process varies by office, and where candidates most commonly get it wrong. What I'm sharing is my perspective, built from going through these processes myself, coaching candidates through them, and having direct conversations with consultants and partners inside these firms. This is not a neutral research document. It's a coach's view. And it's a living document. I'll keep updating it as I work with more candidates and as these processes evolve.

Here's the map before you go into the individual breakdowns.

MBB: The Benchmark Everything Else Is Measured Against

McKinsey, BCG, and Bain are the reference point. Most candidates know this. What fewer understand is how meaningfully different the three processes are from each other.

McKinsey runs the most structured process of the three. The interviewer leads the case. The PEI is a heavily weighted standalone component that candidates consistently underestimate relative to the case itself. I went through McKinsey myself after my PhD in 2017 and made it to the final partner round. Four years later, having worked inside strategy consulting, I came to the conclusion it wasn't the right fit for my personality. But going through that process is part of why I understand it well enough to coach others through it. [Full McKinsey breakdown]

BCG is candidate-led, which requires more self-direction than most candidates expect. You drive the structure and the direction. BCG also has more pre-interview filters than almost any other firm in this series: Pymetrics, a one-way video interview in many offices, the CCA, a quantitative test, and the Casey chatbot. Five distinct filters before you ever sit across from a live interviewer. [Full BCG breakdown]

Bain sits between the two in feel, candidate-led but warmer and more conversational in tone. The written case in final round is something a lot of Bain candidates don't prepare for specifically enough. [Full Bain breakdown]

Across all three: MBB cases are deliberately unpredictable. They want to see how you think under genuine ambiguity, not how well you've memorized a framework. That's a meaningful distinction from what you'll encounter further down this list.

Tier 2: More Variation Than People Expect

This is where I see the most under-preparation. Candidates assume Tier 2 means slightly easier MBB prep. It doesn't. Each firm has a distinct identity, and that identity shapes the entire interview process.

Roland Berger is the only major European-headquartered strategy firm in this group. German-rooted, operationally rigorous, direct in tone. The process reflects the culture. Having worked inside Monitor Deloitte myself, I've seen this process from both sides. [Full Roland Berger breakdown]

Kearney has deep roots in operations and supply chain. If your prep has been built entirely around market entry and growth strategy, Kearney's operational framing can catch you off guard in R1. [Full Kearney breakdown]

L.E.K. is the private equity and life sciences specialist. The written case in final round is a dense document pack with independent analysis under time pressure. The super day format means first and second round can happen on the same day, which requires a different kind of stamina than a process spread across multiple weeks. [Full L.E.K. breakdown]

Oliver Wyman is the most quantitatively demanding firm in this tier. Banking, insurance, asset management, risk: that's the core of the work, and the cases reflect it. Mental math, data exhibits, financial metrics throughout. I went through this process myself and got an offer from the Stockholm office, so I know firsthand how quickly the quantitative intensity shows up. Candidates from non-financial backgrounds consistently feel the gap in R1. [Full Oliver Wyman breakdown]

Strategy& is PwC's strategy arm, but don't let the Big Four parent mislead you. The process is firmly Tier 2 in rigor. I got an offer from Strategy& myself, and one thing that comes up consistently both from my own experience and from candidates I've worked with: Strategy& interviewers actively screen for people treating the firm as an MBB backup. Your "why Strategy&" answer needs to be specific and credible. [Full Strategy& breakdown]

EY-Parthenon needs its own note because I keep seeing candidates confuse it with EY. They are not the same process in any meaningful sense. EY-Parthenon is the strategy arm of EY, built out of the acquisition of The Parthenon Group, and it sits firmly in Tier 2 in terms of case rigor and process intensity. MBB-level case difficulty, a distinctive group case in final round, genuine PE and transaction advisory focus. EY, which I cover separately in the Big Four section below, is an entirely different experience. [Full EY-Parthenon breakdown]

Arthur D. Little is the oldest consulting firm in existence, founded in 1886, and it has the most distinct culture of any firm in this tier. Smaller, more entrepreneurial, strong in technology and innovation sectors. I got an offer from ADL myself, and the thing I remember most, and what I consistently hear from candidates I've coached through it, is that the interviewers are harder to read than at any other firm in this series. Straight to the point. Transactional in tone. Don't mistake the silence for a negative signal. [Full Arthur D. Little breakdown]

Simon-Kucher built its entire identity around one thing: pricing, monetization, and topline revenue growth. I got an offer from Simon-Kucher myself, and the case content is genuinely unlike anything you'd encounter at a generalist strategy firm. Pricing-specific scenarios, not generic strategy problems. If you show up having practiced fifteen profitability cases and zero pricing cases, you'll feel it immediately in R1.[Full Simon-Kucher breakdown]

Big Four + One: Scale, Variance, and a Different Kind of Rigor

Deloitte, KPMG, PwC, and EY share one characteristic that distinguishes them from MBB and Tier 2: internal variation. These are enormous organizations with dozens of practice areas, and the recruitment experience differs meaningfully depending on which door you walk through. Accenture isn't technically Big Four, but I'm grouping it here because the dynamic is similar.

Deloitte is the one I'd push candidates to take most seriously in terms of rigor. The consulting practice specifically runs a process with acceptance rates comparable to MBB, a values-driven behavioral evaluation that sits at the center of the hiring decision, and a group case format in final round that almost nobody prepares for. Having worked inside Monitor Deloitte myself, I've seen this process from both sides. [Full Deloitte breakdown]

KPMG is the most process-variable firm in this entire series. Less case-heavy than MBB or Tier 2, more weight on competency-based evaluation and cultural fit. The format varies more across offices than at any other firm I've covered. Confirm your specific format with your recruiter early. [Full KPMG breakdown]

PwC has one wrinkle worth knowing upfront: when you apply you choose a service area, Consulting, Deals, Audit, Tax, and moving between service areas after you're hired is genuinely difficult in most offices. Choose your door carefully. The cases in the consulting and deals tracks are drawn from real PwC project work, which means there's usually no single right answer. What's being evaluated is whether your recommendation is credible and well-argued. [Full PwC breakdown]

EY, as I said above, is not EY-Parthenon. The broader EY consulting business is closer to execution, transformation, and implementation than to pure strategy. The process scores candidates against a defined competency framework covering Teaming, Communication, Analytical thinking, and Leadership, at every stage from the video interview through to the final partner conversation. Build your stories to cover all four deliberately, not just the ones that feel most natural to talk about. [Full EY breakdown]

Accenture has more internal variation than any other firm in this series. Strategy, Consulting, Operations, Technology, and Song each run meaningfully different processes under the same brand. I got an offer from Accenture Strategy myself, and the case rigor there is real. It competes directly with MBB for top-tier strategy work and the process reflects that. The other tracks lean toward implementation and technology delivery, which is a genuinely different experience. Know which track you're targeting before you start prepping, because generic Accenture interview advice blurs these distinctions in ways that won't serve you. [Full Accenture breakdown]

This is a living document. I'll keep updating the individual firm breakdowns as processes shift, as I work with more candidates across these firms, and as I learn things that change my view. If your experience with any of these firms differed from what I've described, say so in the comments. That's how this gets better over time.

The full series lives in r/ConsultingOffer, a community I run for non-traditional candidates breaking into MBB, Tier 2, and Big Four consulting. If that's you, join us there.

What firm are you targeting right now, and where in the process are you?

Hi everyone,

I'm a PhD candidate in Biomedical Engineering planning to recruit for MBB (McKinsey, BCG, and Bain) and could really use some guidance on where to start with case interview prep.

Coming from a STEM research background, I have no formal business training, so consulting interviews are completely new to me. I've been researching resources, but there are so many recommendations—Case in Point, Victor Cheng, CaseCoach, RocketBlocks, Crafting Cases, Management Consulted, PrepLounge, AI tools, etc.—that I'm feeling overwhelmed.

If you were starting from scratch today, how would you approach preparation?

Some questions I have:

• What's the best first step? Learn case fundamentals first or jump straight into practicing live cases?
• Which resources are genuinely worth the time for beginners?
• Are paid platforms like CaseCoach or RocketBlocks worth it, or can you prepare just as well using free resources?
• How many live cases did it take before you felt interview-ready?
• For those who successfully transitioned from a PhD into MBB, what do you wish you had known when you started?

I'm aiming to recruit for 2027 and want to build a solid, structured preparation plan instead of randomly jumping between resources.

Any advice or recommendations would be greatly appreciated. Thanks!

Looking for any help/coaching to prepare for Excel tests for A&M PEPI!