u/GreatButterscotch406

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?

Most candidates treat a chart in a case interview the way they'd treat an exam question. Find the relevant number, report it, wait for the next question. That's not Data Conversion. That's just reading.

This is post 22 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 covers the Data Conversion module, the fourth of the four Case Middle modules. If Structured Brainstorming is about generating ideas and Consulting Math is about setting up equations, Data Conversion is about reading what a chart or dataset is actually telling you and converting that into an insight that moves the case forward.

The name matters. Data Conversion is not data reading. It's not data reporting. It's the act of taking raw information and converting it into something the client can act on.

What you might receive

Before getting into how to approach a chart, it's worth naming what Data Conversion actually covers in practice because it varies more than most candidates expect.

In a formal final round at McKinsey, BCG, or Bain, you'll typically receive a printed exhibit, a professionally formatted chart or table labeled "Exhibit 1" or "Chart A," handed to you mid-case. In some interviewer-led formats, the partner describes the data verbally and you have to work with what you hear rather than what you see. In case competitions or Big 4 settings, you might receive an Excel file or a multi-tab data pack. In some final rounds, the partner will describe a trend in passing and ask you to interpret it without a visual at all.

The form varies. The cognitive skill being tested doesn't. In every version, the question is the same: can you orient yourself quickly to unfamiliar data, extract what's relevant, generate a real insight, and connect it back to the problem you're supposed to be solving?

The three degrees of insight

This is the spine of the whole module. Everything else in this post supports this structure.

When a partner hands you a chart, there are three levels of response available to you.

The first degree is reading. You describe what the chart shows. "NordPlay's subscription revenue declined by 18% between Q2 of the first year and Q4 of the second year." That's accurate. It's also the minimum. Any literate person can do that. If you stop here, you've done nothing a senior partner couldn't do by looking at the exhibit themselves.

The second degree is generating an insight from the data. You take what the chart shows and calculate, compare, or combine it with something else you know to produce something that wasn't directly visible in the exhibit. "NordPlay's subscription revenue declined 18% while advertising revenue held flat. That means the entire $400 million net profit gap is attributable to the subscription side, not a broad-based revenue problem." That required combining two data points from the chart and connecting them to the gap we're trying to explain. Now the partner has something they didn't have before.

The third degree is connecting the insight back to the case. You take what you just generated and tell the partner what it means for the hypothesis. "This confirms sub-hypothesis one: the revenue decline is concentrated in subscriptions, likely a pricing or retention issue rather than a product mix problem. It tells us we can narrow the issue tree significantly and focus the next data request on the subscription segment specifically." Now you've moved the case forward.

Most candidates reliably produce first-degree responses. Some reach the second degree. Very few consistently reach the third. That gap is what Data Conversion training is designed to close.

How to orient yourself to an unfamiliar chart

Before generating any insight, you need to actually understand what you're looking at. This sounds obvious. Under pressure, with a partner watching and a clock running, it's where candidates most often go wrong.

The sequence I recommend:

Read the title first. Not the data. The title. The title tells you what the chart is claiming or showing. Gene Zelazny, who spent over forty years as Director of Visual Communications at McKinsey and wrote what is widely considered the standard reference on consulting data visualization, "Say It With Charts," put it simply: the purpose of a chart is not to show data, it is to convey a message. The title is that message. If the exhibit is titled "NordPlay Subscription Revenue by Tier, Q1 Year 1 through Q4 Year 2," you immediately know you're looking at revenue broken down by subscription type over eight quarters. That context shapes everything you look at next.

Identify the axes and units. What is being measured on each axis? What are the units? A chart showing revenue in millions versus billions changes the scale of every conclusion you draw. A chart showing month-over-month change versus absolute values requires a completely different interpretation. Checking units before calculating is the single most common error prevention step and the most commonly skipped.

Identify the categories. What are the segments, lines, bars, or data series? In a stacked bar chart, what does each color represent? In a line chart, what does each line track? Naming the categories out loud as you orient yourself serves two purposes: it demonstrates to the partner that you're reading the chart systematically, and it catches any misreading before it propagates into your analysis.

Find the trend. Now that you understand what the chart is showing, ask: what is the dominant pattern? Is something increasing, decreasing, fluctuating, or flat? Is there a point where the trend changes? Are there outliers that break the pattern? The trend is usually the raw material for your second-degree insight.

Recap before calculating. Before you do any math, describe what you see to the partner in one or two sentences. "I can see that NordPlay's premium subscription revenue dropped significantly from Q3 of year one onward, while the standard tier held relatively stable. The total gap I'm seeing is roughly $150 million across the two-year period." This serves the same function as restating the equation before calculating: it gives the partner a chance to correct your reading if you've misunderstood something, before you spend three minutes calculating from the wrong starting point.

When the data is incomplete

One of the things that happens in real case interviews that no one tells candidates to prepare for: sometimes the chart doesn't have everything you need to answer the question you're working on.

The wrong response is to go silent or guess. The right response is to name what's missing, explain why you need it, and propose what you'd do next.

"I can see the revenue breakdown by tier, but I don't have the subscriber count or average revenue per user for each tier. To calculate whether the decline came from pricing or churn, I'd need one of those. Is there another exhibit that covers subscriber volumes? Alternatively, I can estimate the subscriber count using the revenue figure and the listed price point, if that's helpful."

That response demonstrates three things simultaneously: you understand what the calculation requires, you noticed that data was missing rather than proceeding incorrectly, and you offered a path forward without waiting to be told what to do. That's Drive and Acumen in the ABCDEF framework running together.

The resource worth your time

If you're new to reading charts at a consulting level and want to build that pattern recognition before your interviews, "Say It With Charts" by Gene Zelazny is the book I'd point you to. Zelazny was McKinsey's Director of Visual Communications for over forty years and the book remains the standard reference for how consulting firms think about data visualization. His core framework is practical: virtually every business message can be conveyed with five chart types. Bar charts for comparing items. Line charts for showing change over time. Column charts for showing distribution. Scatter plots for showing correlation. Pie charts sparingly, and only when one segment owns more than half the total.

Understanding why specific chart types are used for specific purposes makes you faster at orienting yourself to new exhibits. When you know that a line chart is always showing change over time, you don't waste precious seconds figuring out what the axes mean. You already know. Your attention goes straight to what's interesting in the trend.

What Data Conversion looks like in the NordPlay case

To make this concrete: imagine you're in the NordPlay case and the partner hands you a chart. The title reads "NordPlay Net Revenue by Segment, Year 1 through Year 2." You see a line chart with two lines: subscription revenue and advertising revenue. The subscription line declines steadily from around $1.8 billion in Q1 of year one to roughly $1.4 billion by Q4 of year two. The advertising line stays flat at approximately $600 million throughout.

First degree: "Subscription revenue declined by approximately $400 million over the two-year period while advertising revenue remained stable."

Second degree: "The entire $400 million revenue decline is concentrated in subscriptions. Advertising held flat, which means this isn't a demand or platform problem. Something specific happened on the subscription side."

Third degree: "This confirms the revenue branch of our issue tree and points directly toward the premium subscription tier as the source. Our sub-hypothesis one is looking increasingly supported. The next question is whether this decline is driven by pricing, churn, or product mix within subscriptions. I'd want subscriber volume data to determine that."

That's the full arc. Three sentences. One chart. The case moves forward.

If you're currently building your Data Conversion skills and want to share a chart type that's giving you trouble, drop it in the comments. I'll explain how to orient to it and what kind of second and third-degree insights it typically produces. And if you found this through another community, the full Case Playbook series is at r/ConsultingOffer.

The next posts in The Case Playbook move into the Case Wrap-Up module, the final section of the case interview, where everything you've built across Case Start and Case Middle gets synthesized into a recommendation and next steps.

Post 20 covered what Consulting Math is, how the interviewer is testing for equation setup and narrated reasoning rather than raw arithmetic speed, and how to build the skill over time. This post is the applied version of that.

This is post 21 in The Case Playbook, a series built for non-traditional candidates breaking into McKinsey, BCG, Bain, Tier 2, and Big 4 consulting firms. We're staying in the NordPlay Studios case that we've been building throughout the series. The problem statement is established, the issue tree is on the page, and you're deep in Case Middle. The partner starts handing you word-based quantitative questions. This post shows you what to do with them.

Three problem types. Full narration on each. The goal is not the number. The goal is the process you demonstrate to get there.

What a Problem Solving question looks like in a case

Unlike a pure arithmetic drill where you're given two numbers and asked to calculate, a Problem Solving question gives you a scenario in English and expects you to identify what equation is needed before any numbers are touched.

The difference matters. A pure arithmetic question: "What is 15% of $2.4 billion?" A Problem Solving question: "NordPlay's premium subscription tier currently has 8 million subscribers at $25 per month. If a 10% price increase causes 5% of subscribers to cancel, what happens to monthly subscription revenue?"

The second question requires you to identify which variables interact, build the equation, and then do the arithmetic. The equation step is where most candidates stumble, and it's also where the most points are won.

The three-step approach is identical to what we covered in post 20: state the equation out loud, plug in the numbers and work through the arithmetic on paper while narrating, then interpret what the result means for the case. Never skip the interpretation. The number without context is just a number.

Problem one: Pricing impact on subscription revenue

The partner says: "NordPlay's premium subscription tier currently has 8 million subscribers paying $25 per month. The team is considering a 10% price increase. Market research suggests this would cause 5% of subscribers to cancel. Would this price increase help or hurt monthly subscription revenue?"

Before touching a number, state the equation.

"To answer this I need to compare current revenue to projected revenue after the price change. Revenue is subscribers multiplied by price per subscriber. Let me work through both."

Current revenue: 8 million subscribers multiplied by $25 gives $200 million per month.

Projected revenue: the price increases 10% from $25 to $27.50. Subscribers fall 5% from 8 million to 7.6 million. New revenue is 7.6 million multiplied by $27.50.

Narrate the arithmetic: "7.6 million times $27.50. I'll break that down. 7.6 times 27 is 205.2, and 7.6 times 0.50 is 3.8. Total is $209 million."

Interpretation: "The price increase generates $209 million versus the current $200 million, so it's a net positive of $9 million per month, roughly $108 million annually. That's meaningful given our $400 million gap. However, this assumes the 5% churn estimate is accurate, and in my view that assumption deserves scrutiny before we recommend the change. If actual churn is closer to 10%, the picture reverses."

Notice what the interpretation does. It answers the question, names the annual impact so the partner can connect it to the main hypothesis, and immediately flags the key assumption that could change the conclusion. That's what a consultant does. Not just math. Judgment about what the math means.

Problem two: Breakeven analysis on a new product line

The partner says: "NordPlay is considering launching a cloud gaming subscription service. The fixed cost to build and launch the service is $120 million. Each subscriber generates $40 in annual contribution margin. At what subscriber count does the service break even, and how long would it take to break even if NordPlay acquires 500,000 new subscribers in year one and grows that by 20% each year?"

Two parts. State both equations before starting either calculation.

"For the breakeven subscriber count, I need to divide total fixed cost by contribution margin per subscriber. For the payback timeline, I need to track cumulative subscribers year by year until they cover the fixed cost."

Part one: breakeven subscribers = $120 million divided by $40 = 3 million subscribers.

Part two: narrate the accumulation.

"Year one: 500,000 subscribers. Cumulative contribution: 500,000 times $40 = $20 million. Remaining gap: $100 million.

Year two: 20% growth on 500,000 is 100,000 additional subscribers, so 600,000 new subscribers. Cumulative contribution adds 600,000 times $40 = $24 million. Total so far: $44 million. Remaining gap: $76 million.

Year three: 20% growth on 600,000 is 120,000 additional, so 720,000 new subscribers. Contribution adds $28.8 million. Total: $72.8 million. Remaining gap: $47.2 million.

Year four: 864,000 new subscribers. Contribution adds $34.6 million. Total: $107.4 million. Remaining gap: $12.6 million.

Year five: the service breaks even partway through the year."

Interpretation: "At these growth rates, the cloud gaming service breaks even sometime in year five. Given NordPlay's one-year recovery target, this doesn't contribute meaningfully to the immediate $400 million gap. It's a longer-term bet. Whether it belongs in the recommendation depends on whether the client wants a short-term fix or is willing to invest in a growth lever that pays out over five years. That's a conversation worth having before we close the case."

Problem three: Cost reduction impact on net profit margin

The partner says: "NordPlay's current net profit is $2 billion on revenues of $8 billion, giving a net margin of 25%. App store fees are currently 15% of revenue. If NordPlay renegotiates those fees down to 10% of revenue, what happens to the net profit margin?"

State the equation: "App store fee reduction is 5% of revenue. I need to calculate the dollar saving and add it to current net profit, then recalculate the margin."

Revenue is $8 billion. A 5 percentage point reduction in app store fees saves 5% of $8 billion = $400 million.

New net profit = $2 billion plus $400 million = $2.4 billion.

New net margin = $2.4 billion divided by $8 billion = 30%.

Interpretation: "This is significant. A successful renegotiation of app store fees would close the entire $400 million gap we identified in the issue tree and restore net profits to $2.4 billion within one year, assuming revenue holds. It's also the single lever in our analysis that's fully within NordPlay's control to pursue without requiring product development or subscriber growth. In my view this should be the first recommendation in the Case Wrap-Up, subject to understanding how realistic the renegotiation actually is given the platform dynamics."

Notice how the interpretation connects directly back to the main hypothesis. The $400 million gap is the north star of the entire case. Every calculation should be interpreted in terms of how much it contributes to closing that gap.

The pattern across all three problems

Looking at the three problems together, the same structure runs through every one.

State the equation before the arithmetic. This signals to the partner that you understand what relationship you're solving for. It also gives them a moment to catch you if you've set up the wrong equation, which is far better than discovering the error after several minutes of calculation.

Narrate the arithmetic on paper. Don't go silent. The partner is not just waiting for your answer. They're watching how you handle numbers under pressure and whether your process is transparent enough to be corrected if needed.

Interpret the result in terms of the case. Every number in a case interview is a data point that should either confirm, update, or challenge the main hypothesis. A calculation that produces a number and then goes nowhere is a missed opportunity.

That three-step sequence is the difference between a candidate who gets a number right and a candidate who demonstrates consulting judgment. The first passes a test. The second earns an offer.

If you're working through NordPlay or any other case from the series and want to share a quantitative question you've been stuck on, drop it in the comments. I'll walk through the equation setup and the narration. 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 the Data Conversion module, where the question shifts from setting up equations to reading what a chart or dataset is actually telling you and translating that into an insight that drives the case forward.

Most candidates who struggle with the Consulting Math module think they have a math problem. In my view, they usually have a communication problem.

This is post 20 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 opens the Consulting Math module of the series. We're not solving a specific math problem here. We're defining what consulting math actually is, how it differs from academic math, what the interviewer is testing for, and how to build the skill if numbers under pressure are not your natural habitat.

What consulting math is, and what it isn't

Consulting math is not advanced mathematics. You will not be asked to solve differential equations or run statistical regressions. The concepts involved are ones you learned before university: addition, subtraction, multiplication, division, percentages, ratios, and basic algebra. The math concepts in consulting interviews are essentially addition, subtraction, multiplication, division, and percentages. That's roughly 90% of what appears in a case.

What makes consulting math hard is not the math itself. It's the conditions under which you have to do it. No calculator. A partner or interviewer watching you. A thirty-minute case running in the background with multiple other things demanding your attention. Large numbers with several zeros that create opportunities for errors in magnitude. And the expectation that you'll not only get the answer but explain your reasoning out loud as you work through it.

That last point is what most case prep resources underemphasize, and it's the one I want to spend the most time on.

The skill the interviewer is actually testing

When a partner gives you a Consulting Math question in a case interview, they're not checking whether you can multiply. They're checking whether you can reason quantitatively in real time while under pressure and communicate that reasoning to another person clearly enough that they can follow it and catch errors before they compound.

Think about what this mirrors in real consulting work. You're in a client meeting. A CFO raises a question about unit economics. You can't say "give me a moment, I'll get back to you." You need to work through the calculation out loud, in front of the client, in a way that makes the client feel included in your thinking rather than waiting for a verdict.

That's exactly what the case interview is testing. Not the answer. The process.

Here's what that looks like in practice. If the interviewer asks you to calculate the breakeven volume for NordPlay Studios given a specific subscription price and cost structure, a top performer doesn't go quiet for thirty seconds and then announce a number. They say something like: "To find breakeven volume I need to cover fixed costs with contribution margin. Contribution margin is price minus variable cost per unit. If price is $12 and variable cost is $8, contribution margin is $4 per subscriber. Fixed costs are $200 million. So breakeven volume is $200 million divided by $4, which gives me 50 million subscribers." That narration, spoken while writing the equation on paper, is what earns points. Not the number alone.

The interviewer can help you if you're going off course. They can't help you if they can't see your reasoning.

How consulting math appears in a case

Consulting Math doesn't arrive as a standalone test. It's woven into the case at various points and takes several different forms.

Profitability calculations: revenue minus cost, margin analysis, breakeven. These are the most common and typically involve applying percentage changes to base numbers or solving for an unknown variable when two others are given.

Market sizing: estimating a number through logical decomposition when you don't have the data directly. How many liters of clean water does Solvik consume per day? You'd estimate from population, household size, and average daily consumption per person. These require chaining multiple estimates together without losing track of your assumptions.

Growth and change calculations: percentage increases, compound annual growth rates, payback periods. These often appear in investment or expansion questions and require knowing which formula applies before you touch the numbers.

Rate and ratio problems: two variables changing at different rates, combined production rates, efficiency calculations. These require setting up the right relationship between variables before calculating.

Sanity checks: quick back-of-envelope calculations to verify whether a number makes intuitive sense. Is $6 billion in cost savings for a company with $50 billion in revenue plausible? That's a 12% cost reduction. Directionally reasonable or aggressive? The partner wants to see you engage with that question, not just report the number.

The approach: equation first, arithmetic second

The owner thinker's approach to Consulting Math follows the same first principles logic we've applied throughout this series. Before touching a number, identify what relationship you're solving for.

That means asking yourself: what is the equation that connects the variables I've been given to the variable I need to find? Once you've identified the equation and written it down, the arithmetic is just execution.

This sequencing matters more than most candidates realize. The most common Consulting Math errors don't come from arithmetic mistakes. They come from setting up the wrong equation, often because the candidate started calculating before they understood what they were solving for. Interviewers care more about your logic and structure than the last digit, so round boldly and state your assumptions.

The practical sequence is: state the equation out loud, plug in the numbers, do the arithmetic on paper while narrating, state the answer with units, and then interpret what the number means for the case. That last step, interpretation, is what most candidates skip. A number without context is just a number. "50 million subscribers to break even, compared to NordPlay's current 30 million active subscribers, tells us the company needs to nearly double its user base to cover fixed costs at the current price point. That's a significant gap and suggests pricing may need to change before the subscriber target is achievable." That interpretation is the insight the partner is waiting for.

How to build the skill

There are two distinct things to train, and most candidates conflate them.

The first is arithmetic speed and accuracy with large numbers under pressure. This is a muscle that atrophies if you've been using a calculator for everything since school. Mental math is just a skill that you can learn once you know the method and spend time practicing. Accuracy around the 95% mark is generally acceptable, but speed is paramount. The most effective way to rebuild this muscle is isolated drilling: percentages of large numbers, multiplying and dividing by non-round figures, percentage changes, and CAGR estimates. These don't need to be done in a case context. Ten to fifteen minutes of focused arithmetic drills daily, done under a timer, builds the automatic response you need.

A few techniques worth building into your practice. Breaking percentages into components: instead of calculating 15% directly, calculate 10% first and add half of that. 17.5% becomes 10% plus 5% plus 2.5%. This keeps you from reaching for a calculation you can't do cleanly in your head. Rounding before multiplying: if you need to multiply 48 by 25, round to 50 by 25 which is 1,250, then subtract 2 by 25 which is 50, giving you 1,200. Working with clean numbers first and adjusting the difference is faster and more accurate under pressure than trying to multiply the original figures directly. The Rule of 72 for doubling time: divide 72 by an annual growth rate to estimate how many years it takes for a number to double. At 8% growth, a fund doubles in roughly 9 years. Useful for CAGR questions and quick sanity checks on growth projections.

The second is equation setup within a business context. This requires practicing math within cases, not in isolation. The reason is that knowing how to multiply quickly doesn't tell you which variables to multiply. That judgment comes from pattern recognition built through case practice. After doing enough profitability cases, breakeven questions, and market sizing exercises, you start to recognize the equation type before the problem is fully stated. That recognition is what creates the appearance of effortlessness in a case interview.

For the arithmetic drilling side, I'm planning to release a set of the math drills I use with candidates in the Consulting Offer Program. These are built specifically around the types of calculations that come up in MBB and Tier 2 case interviews, not generic arithmetic practice. I'll share those in an upcoming post in this series. In the meantime, the most important thing is to start drilling with a timer, whatever resource you use, because the pressure of the clock is the thing most candidates never practice until the interview itself.

The one thing that doesn't work is treating Consulting Math as something to cram in the week before your interview. The arithmetic muscle takes weeks of consistent practice to rebuild. And the equation setup judgment takes dozens of cases to develop. Both need time.

One thing most guides don't say

Consulting Math is not a test you pass or fail independently. It lives inside a case. The number you produce has to connect back to the issue tree, update the hypothesis, and move the case forward. A correct calculation that the partner can't follow because you did it silently is less valuable than an approximate calculation narrated clearly.

The candidate who says "I'm going to estimate this as roughly $180 million, here's my logic, and that tells me we're about 40% of the way to our recovery target" is more impressive than the candidate who goes quiet for sixty seconds and announces "$182.4 million" without explanation.

Consult the math. Don't just compute it.

If you're currently working on the Consulting Math module and want to share a specific question type that's giving you trouble, drop it in the comments. I'll walk through the equation setup and show you where the thinking should start. 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 the Data Conversion module, the fourth of the four Case Middle modules. If Consulting Math is about setting up the right equation and narrating your arithmetic, Data Conversion is about reading what a chart or dataset is actually telling you and translating that into an insight that moves the case forward. That's where we're headed next.

Quick update on the Q4 2026 cohort since a few people have been asking where things stand.

I work with ten candidates a quarter, that's it, and a handful of those seats are already filled. I've been talking with candidates coming out of INSEAD, Wharton, Berkeley Haas, and UBC, on top of a long list of people reaching out from other programs. In my experience the school on the resume isn't really what decides who gets in, some of my strongest placements came from candidates nobody would've picked on paper. It's more that the pool fills fast once people hear the intake is limited.

There are still a few seats open, but early bird registration closes July 5th, and the full program intake closes July 15th regardless. If you're seriously targeting MBB, Tier 2, or Big Four for late 2026 or 2027 and want to see if there's still room, DM me and I'll walk you through what's left and how the selection actually works.

What stage are you at right now in your own process?

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

Posts 15 and 16 covered Structured Brainstorming on a profitability case and a public sector case. Both asked you to brainstorm reasons why something declined. That's a forward-looking decomposition: you're explaining what caused a gap.

This is post 18 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 covers a harder version: brainstorming why something is a bad idea. That's a reverse framing, and it requires a different cognitive approach that most candidates aren't prepared for.

The case is the Vantage and GridCore merger from post 5. If you haven't read that post, the context is: Vantage, a US-based social media platform with two billion monthly active users, is exploring a vertical merger with GridCore, a global fiber optic infrastructure provider. The target is $6 billion in additional annual operating profits from year two. The issue tree, hypothesis, and sub-hypotheses are already established. Now the partner pivots.

The brainstorming prompt

"We've been building the case for why this merger could work. Before we go further, can you brainstorm the reasons why this merger might be a bad idea?"

That's a deliberate flip. And it's one of the most common pressure tactics in final round M&A cases. The partner wants to know whether you can hold a position and then genuinely challenge it, not just agree with whatever direction they point you in.

Most candidates freeze here. They've been building the bull case for ten minutes. Shifting to the bear case feels like abandoning what they've constructed. It isn't. It's a demonstration of intellectual flexibility that partners specifically value, because real consulting engagements require exactly this: stress-testing your own recommendations before a client does.

Step 1: Absorb and anchor

Write it down: "Brainstorm why the Vantage and GridCore merger is a bad idea."

Reiterate: "So you'd like me to brainstorm the specific reasons why this vertical merger between Vantage and GridCore might fail to deliver the $6 billion target or create value overall. Is that the right scope?"

The partner confirms.

Notice the reiteration does something important here. It anchors the brainstorm to the specific financial target. You're not brainstorming why mergers in general are bad ideas. You're brainstorming why this specific merger might fail to achieve this specific $6 billion number. That's a much sharper scope, and it immediately raises the quality ceiling of everything that follows.

Step 2: Clarify and orient

Two circles: "bad idea" and the two companies.

"When you say bad idea, are you focused on the financial case, the integration risk, or both? I want to make sure I'm covering the right dimensions."

The partner says: both.

"And just to confirm: Vantage is the primary acquirer here, so I should think about this from Vantage's perspective primarily, while also considering what the merger does to GridCore's existing business?"

The partner confirms.

That second clarification is critical. It tells you something the brainstorm structure depends on. Vantage and GridCore are fundamentally different businesses. One is B2C, the other B2B. One sells to consumers, the other to enterprise clients. That means the risks of the merger are different for each entity, and your brainstorm has to hold both in mind simultaneously. That's the specific challenge of multi-company M&A brainstorming that doesn't appear in profitability or public sector drills.

Step 3: Brainstorm with contrast pairs, reversed

Here's the cognitive move most candidates miss. To brainstorm why something is a bad idea, you first have to know why it would work and then systematically challenge each element. The issue tree from post 5 said the merger creates value through cost synergies, revenue synergies, and risk mitigation. The bear case is: what if each of those value drivers fails, or worse, creates new problems?

That gives you four buckets at level one, each representing a dimension where this merger could go wrong.

The New Company

Before thinking about products or customers, the merger creates a new organizational reality. Vantage and GridCore have to become one company. That single fact generates three distinct failure modes.

Can They Merge? Vantage is a B2C software platform that moves fast, ships frequently, and runs on a consumer marketing culture. GridCore is a B2B infrastructure provider that operates on long project cycles, enterprise contracts, and engineering-led decision making. Three things could prevent them from becoming one functioning entity. First, a Culture Gap: consumer tech and heavy infrastructure attract different people, reward different behaviors, and measure success differently. The friction from that alone could consume years of leadership bandwidth. Second, a Structure Mismatch: one organization is likely decentralized and innovation-driven, the other centralized and operations-driven. Forcing them into a single structure either kills GridCore's operational discipline or throttles Vantage's speed. Third, Regulatory Risk: a merger of this scale, a dominant consumer platform acquiring a critical global infrastructure provider, will attract antitrust scrutiny across multiple jurisdictions simultaneously. That scrutiny could delay or fundamentally constrain the deal.

True Deal Cost: two complex global organizations merging on a tight timeline creates a cost base that could significantly erode the projected $6 billion before a dollar of synergy is realized. Complex Integration means the advisory, legal, and operational costs of executing this merger are themselves substantial. And the Tight Timeline compounds that: if Vantage is under pressure to show results by year two, the integration will be rushed, which historically increases the probability of value destruction rather than value creation.

Revenue Synergies: the entire financial case rests on unlocking $6 billion through premium services, pricing power, and new market access. If any of those three levers don't materialize at the projected scale, the deal's financial logic collapses. This flows directly into the next bucket.

What They Sell

Split by entity because the service risks are different for each side.

GridCore Side: GridCore currently serves a range of enterprise clients, many of whom are direct competitors of Vantage. The merger creates an immediate conflict of interest. Two specific risks follow. Loses Clients: those enterprise clients will not willingly continue purchasing infrastructure services from a company now owned by their main competitor. As contracts expire, they will not renew. Quality Drops: the management attention consumed by integration will inevitably reduce the operational focus on serving existing clients, and service quality for remaining customers may deteriorate. In a B2B infrastructure business, that's an existential risk.

Vantage Side: the bull case assumed Vantage would gain premium service capabilities and new market reach through GridCore. Two specific risks. No Premium Launch: the product development and pricing complexity of launching premium connectivity services is likely underestimated. Vantage has never sold infrastructure-based services and has no experience with the enterprise pricing models that would be required. No New Markets: GridCore's infrastructure footprint may not overlap with the specific geographies where Vantage's growth opportunity is actually concentrated. If the maps don't align, one of the core revenue synergies evaporates entirely.

The Market

Again, split by entity.

GridCore Side: a B2B infrastructure provider's competitive position depends on being seen as neutral, reliable, and independent. Once GridCore is owned by Vantage, that neutrality is gone. Network Stalls: competitors of Vantage will actively work to build or fund alternative infrastructure providers, and GridCore's pipeline of new network expansion projects will freeze as potential clients delay commitments. Loses Position: the infrastructure market will reorganize around GridCore's compromised status, and the company that was growing its network footprint may find itself unable to win new contracts.

Vantage Side: the time and capital consumed by this merger is time and capital not invested in Vantage's core platform. Rivals Catch Up: competitors who aren't distracted by a major acquisition will continue shipping features and acquiring users. Tech Disruption: satellite internet infrastructure is becoming increasingly viable in exactly the markets where traditional fiber is scarce. If satellite connectivity becomes cost-competitive with fiber within the merger's payback window, the strategic rationale for acquiring GridCore weakens considerably. Vantage may be solving yesterday's connectivity problem at tomorrow's price.

Who They Serve

GridCore Side: enterprise clients operate on long-term contracts that eventually expire. Clients Walk Out: as those contracts come up for renewal, clients uncomfortable with GridCore's new ownership structure will simply not renew. The attrition may be gradual but it will be systematic. Projects Abandoned: clients who had committed to new expansion projects with GridCore may walk away from those commitments, creating both revenue loss and potential legal complications around contracted timelines.

Vantage Side: two billion monthly active users who mostly don't think about how their service is delivered. Consumers Unaffected: the B2C customer base is the one dimension of this merger where the risk is genuinely low. Consumers care about whether the product works, not about who owns the infrastructure behind it. Stating this explicitly is itself an insight: the bear case weight sits almost entirely on the B2B and integration dimensions, not on Vantage's existing user base. Partners notice when a candidate can identify where the risk isn't, not just where it is.

Step 4: Prioritize and drive forward

"Based on what I've laid out, three areas feel most consequential. First, integration risk at the merged entity level, specifically culture and regulatory challenges: two organizations this different, operating across this many jurisdictions, have an inherently high failure rate when it comes to integration, and that risk sits upstream of all the synergy projections. Second, GridCore's B2B client attrition: if even two or three major enterprise clients exit after the merger closes, that creates a multi-billion dollar hole in GridCore's revenue that directly offsets projected synergies. Third, Vantage's inability to access new markets through GridCore's footprint: if the infrastructure maps don't overlap with Vantage's actual expansion priorities, the strategic rationale for the deal weakens considerably. I'd want to stress-test all three before drawing a conclusion."

What made this brainstorm different

Four things happened in this brainstorm that don't happen in a standard profitability or public sector drill.

The reverse framing required building the bull case first and then systematically challenging it bucket by bucket. That's not a natural instinct under pressure. It requires deliberately switching cognitive modes mid-case.

The four-bucket structure at level one, merged entity, services, industry and competitors, customers, is derived from first principles by asking: in what dimensions could this deal go wrong? Each bucket represents a different layer of reality the merger has to navigate. That's an owner thinker asking "what does this deal actually depend on?" not a memorizer retrieving a template.

The per-entity split under services, industry, and customers reflects the fact that Vantage and GridCore have fundamentally different business models. A brainstorm that doesn't separate B2C risks from B2B risks will miss the most important distinction in the case.

The explicit acknowledgment that Vantage's consumer-side risk is low is itself an insight. Most candidates assume every bucket needs a long list of problems. The owner thinker is honest about where the risk actually concentrates and where it doesn't. That judgment is what partners are testing for.

If you're prepping M&A brainstorms and want to share a question you've been working on, drop it in the comments. And if you found this through another community, the full Case Playbook series is at r/ConsultingOffer.

The next post in The Case Playbook applies the same four-step brainstorming approach to a completely different case type: an asset-level public infrastructure case. In posts 6 and 13 we built the issue tree and sub-hypotheses for the Solvik water plant case. Post 19 picks up from there and runs the brainstorm on a technical system most candidates have no prior exposure to. If the M&A brainstorm showed you how to handle two industries simultaneously, the Solvik brainstorm shows you how to handle an unfamiliar physical asset using nothing but first principles and contrast pairs.

Posts 14, 15, and 16 covered the architecture of Structured Brainstorming, the four steps, contrast pairs, and two full drills across a private company and a public sector case. If you've followed those posts, you now know how to run a clean brainstorm when the conditions are favorable.

This is post 17 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 covers what happens to that brainstorm when the conditions are deliberately made unfavorable. Because in final rounds, they will be.

The four steps don't change. But the environment does. And most candidates have never practiced running a clean brainstorm while a partner is actively trying to throw them off balance.

Why partners apply pressure during brainstorming

This is worth understanding before we get into the tactics themselves.

Partners work with C-suite clients. CEOs, finance ministers, board members. These clients are not always patient. They don't always show enthusiasm. They sometimes challenge ideas mid-conversation. They occasionally check their phones while you're presenting. They might push back sharply on a point you felt confident about. And in some cases, they'll test whether you actually believe what you're saying or whether you'll fold the moment someone senior raises an eyebrow.

The brainstorming module in a final round is a compressed simulation of that environment. The partner is not being difficult because they're unkind. They're being difficult because that's what the job requires, and they need to know whether you can operate effectively when the person across the table isn't making it easy.

From what I've seen coaching candidates through final rounds, the ones who get rattled during brainstorming almost always had the right ideas. They lost points not on content but on composure. Understanding what's coming is the first step toward not being surprised by it.

The pressure tactics you should expect

Time compression. The partner tells you to go faster. "Can you pick up the pace?" or "We're short on time, just give me the top ideas." This is a test of whether your process collapses under time pressure or whether you can deliver a compressed but still structured output. The owner thinker hears this and scales down, not abandons. Two levels of contrast pairs instead of four. Two priorities instead of three. The structure stays. The depth adjusts.

Interjections mid-brainstorm. The partner interrupts while you're still generating ideas. "Why did you put that there?" or "Can you say more about that?" or simply asking a clarifying question that pulls you out of your flow. The test is whether you can respond, engage briefly, and then return to exactly where you were in the brainstorm without losing the thread. Your notes are your anchor. If you've been writing as you go, you can look down, find your place, and continue. If you haven't been writing, the interjection becomes disorienting.

Asking for more ideas. "Can you generate a few more?" This typically happens when the brainstorm felt thin, or when the partner wants to see whether you've genuinely exhausted the contrast pair or whether you stopped prematurely. If you've been working through the structure systematically, you should have depth left at lower levels. If you rushed to the bottom, you have nowhere to go.

Disinterested body language. The partner looks away. They seem distracted. They don't react when you say something you expected to land. This is one of the most effective pressure tactics because it's entirely non-verbal and candidates often interpret it as "I'm saying the wrong things." Most of the time, they're not. The partner is watching to see whether you maintain your pace and confidence when you're not getting external validation. Keep going. The moment you change what you're saying based on their apparent reaction rather than the logic of the problem, you've signaled that your confidence is externally dependent.

Physical movement. In in-person interviews, partners sometimes move around the room, come closer to look at your notes, or simply don't sit still. It's uncomfortable. It's meant to be. Your notes on the page are your case. Keep your attention there. What someone else is doing in the room is irrelevant to the problem you're solving.

The scaling principle: brainstorming isn't always a five-minute module

Here's something the previous posts didn't cover explicitly that's worth naming clearly.

The four steps scale. They're not fixed to a specific time window.

A standalone brainstorming question in Case Middle typically runs three to five minutes. You run all four steps, go four or five levels deep using contrast pairs, and drive out through prioritization. That's the full version.

But brainstorming also appears as a nested moment inside other modules. You're analyzing a chart. The data shows NordPlay's subscription revenue dropped 20% in one quarter. The partner pauses the analysis and says: "Can you brainstorm a few reasons why that might have happened?"

That's not a five-minute brainstorm. That's a sixty-second brainstorm. And the way you handle it is different.

Because you're already deep in the case context, you don't need steps one and two. You have all the context. You skip straight to step three, apply one contrast pair to the element in front of you (was this a pricing problem or a volume problem?), generate two or three ideas at one or two levels deep, and immediately prioritize one to follow up on. The whole thing takes sixty seconds and you're back in the chart analysis.

The four steps don't disappear in a nested brainstorm. They compress. Two of them get skipped because the context already provides what steps one and two would have given you. The remaining two run faster because the scope is narrower.

Understanding this scaling principle matters because candidates who don't know it either over-engineer nested brainstorms (treating a sixty-second moment as if it needs a five-minute structure) or under-engineer them (just saying "it could be a revenue issue" and moving on without any contrast pair at all).

Bespoke brainstorming versus generic brainstorming

This is the most important point in this post and the one that most case prep resources don't say directly enough.

Partners are not looking for good ideas in general. They're looking for good ideas that are specific to this case, this client, this industry, this context.

The difference is substantial. A generic brainstorm on why a company's revenue declined produces: pricing, volume, product mix, competition, market conditions. Every candidate with a case prep background produces that list. It requires no engagement with the specific details of the case.

A bespoke brainstorm on why NordPlay's net profits declined produces: premium subscription tier pricing misaligned with how the mobile gaming demographic values content, development pipeline delays creating a cost-without-revenue lag, app store fee escalation as international expansion increased distribution costs, AI-enabled competitive titles eroding NordPlay's differentiation in casual gaming. That's specific to NordPlay's business model, distribution channel, and competitive environment. It requires the candidate to have actually engaged with the case context they built during the clarifying question phase.

That's the payoff of the activation phase in steps one and two. When you slow down, reiterate, and clarify, you're not just buying time to calm down. You're re-engaging with the specific details of this case so that the brainstorm that follows draws on that context rather than on generic knowledge.

The owner thinker generates bespoke insight because they've been thinking about this specific client's problem since minute one. The memorizer generates generic insight because they're running a template over a problem they haven't fully engaged with.

What to do with this before your next practice session

Take a brainstorm you've already practiced on a case from this series. Run it again, but this time have your practice partner apply one pressure tactic while you're in step three: either interrupt you mid-brainstorm with a clarifying question, or tell you to go faster.

The goal isn't to practice ignoring the pressure. It's to practice returning to your anchor after it. After the interruption, look at your notes, find where you were, and continue from that exact point. After being told to go faster, drop one level of depth but keep the contrast pair structure intact.

That recovery instinct is what partners are actually testing. Not whether you're unaffected. Whether you can bounce back.

If you're currently prepping for final rounds and want to share what the pressure moments have felt like in practice, drop it in the comments. I'd be curious which tactic is most disorienting for people in this community. And if you found this through another community, the full Case Playbook series is at r/ConsultingOffer.

The next post in The Case Playbook takes Structured Brainstorming into harder territory. Posts 15 and 16 asked you to brainstorm reasons why something declined, a forward decomposition with a clear direction. Post 18 flips that entirely: the partner asks you to brainstorm why something is a bad idea. That reverse framing requires a different cognitive approach, and most candidates aren't prepared for it. The case is the Vantage and GridCore M&A merger from post 5, and the brainstorm runs across four buckets covering the merged entity, what they sell, the market, and who they serve.

In post 15, I walked through the full four-step brainstorming approach on the NordPlay Studios profitability case. Private company, familiar business model, clear P&L framing. If you followed that post, you saw how contrast pairs replace memorized category lists and how the activation phase of steps one and two buys the owner thinker time to engage before the brainstorm begins.

This is post 16 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 applies the exact same four steps to a public sector brainstorm on the Norwegian sovereign wealth fund case from post 3. If you haven't read that post, the context is simple: the Finance Minister of Norway has asked you to help understand why the fund's annual contribution to the national budget declined from $18 billion to $12 billion over eighteen months and how to restore it. The problem statement is established. The issue tree is built. Now the partner pivots to brainstorming.

The point of this post is the same point post 3 made about clarifying questions: the methodology doesn't change based on case type. Only the vocabulary does.

The brainstorming prompt

You're eight minutes into the Norway case. The partner has received your issue tree and sub-hypotheses. Then they shift.

"We've established the $6 billion annual shortfall. Before we look at the data, can you brainstorm the specific reasons why the fund's contribution to the national budget might have declined by this amount?"

Notice the scope. You're not being asked to solve the problem. You're being asked to generate a structured set of possible explanations for why a government fund's annual transfer to the national budget fell by a third. That's your anchor for the brainstorm.

Step 1: Absorb and anchor

Your pen goes down immediately. You write what the partner said.

"Brainstorm why the fund's annual contribution to the national budget declined by $6 billion."

You reiterate: "So you'd like me to brainstorm the specific reasons why the sovereign wealth fund's annual contribution to the national budget fell from $18 billion to $12 billion over the past eighteen months. Is that the right scope?"

The partner confirms.

Twelve words written. One sentence confirmed. And your thinking brain has had fifteen seconds to shift from the analytical mode of the issue tree into the generative mode the brainstorm requires.

This is the activation phase. Public sector prompts often carry unfamiliar vocabulary: contribution rates, fiscal transfer mechanisms, fund governance structures. Writing and reiterating gives you a moment to absorb the specific element you're brainstorming before you commit to any direction. The memorizer jumps to an answer. The owner thinker anchors first.

Step 2: Clarify and orient

You have two circles: "contribution to the national budget" and "declined." You want to understand the mechanism before you decompose it.

"When you say the fund's contribution declined, can you help me understand the mechanism? Is the contribution a fixed percentage of the fund's total value, a discretionary transfer set by parliament each year, or something else?"

The partner clarifies: the fund transfers a set percentage of its total value to the national budget annually.

That clarification is the entire structure of your brainstorm. You now know there are exactly two explanations for why the contribution could have declined: the fund earned less, or the policy rate changed. Everything else is a sub-level of those two.

Step 3: Brainstorm with contrast pairs

The most natural first contrast pair is already in front of you from the clarification: fund performance versus contribution policy. That's not a category you retrieved. It's the logical decomposition of how a percentage-based transfer mechanism works. Either the base shrank or the rate changed.

Fund performance:

Zoom in. What could cause the fund's total value to decline? Apply another contrast pair: market-driven factors versus management-driven factors.

Market-driven factors: the fund's investment returns fell because of conditions outside its control. Global equity market downturns reduced the value of the fund's stock portfolio. Bond yields compressed, reducing fixed income returns. Commodity price movements affected sectors the fund was exposed to. Currency fluctuations reduced the value of foreign assets when translated back to Norwegian krone. These are all external forces.

Management-driven factors: the fund's returns fell because of decisions made about how it was managed. Asset allocation shifted toward lower-returning instruments. Risk parameters were tightened, reducing exposure to higher-yield assets. Drawdowns were made from the fund for purposes other than the annual budget contribution, reducing the base from which the percentage is calculated.

Now go one level deeper on the highest-impact bucket.

Under market-driven factors: a gradual decline over eighteen months with acceleration in the past six months, which is the pattern the Finance Minister described in post 3, is more consistent with a sustained market environment shift than a single event. The most likely candidate is a prolonged period of below-average returns across major asset classes, compounded by the fund's exposure to global equity markets which represent a significant share of most sovereign wealth fund portfolios.

Contribution policy:

Zoom in. What could cause the contribution rate to fall? Another contrast pair: deliberate policy change versus governance constraint.

Deliberate policy change: parliament or the finance ministry made a decision to reduce the contribution rate. This could be a fiscal policy response to economic conditions, a decision to let the fund recover before drawing at the standard rate, or a strategic shift in how the fund is managed over the long term.

Governance constraint: the rate wasn't changed by choice but by rule. Some sovereign wealth funds have built-in mechanisms that automatically reduce contribution rates when the fund's value falls below certain thresholds, to protect the fund's long-term sustainability. If such a rule exists and was triggered by a decline in fund value, the reduction in contribution would be automatic rather than discretionary.

That distinction matters enormously for the case. A deliberate policy change is reversible by policy decision. A governance constraint requires understanding what threshold was breached and what the recovery path looks like before contributions can return to prior levels.

Step 4: Prioritize and drive forward

You've generated a structured brainstorm across three levels. Now you select.

"Based on what I've laid out, I'd want to prioritize two areas. First, the fund performance side, specifically the market-driven factors: the eighteen-month gradual decline with recent acceleration is most consistent with a sustained investment return compression rather than a policy decision, and I'd want to see the fund's asset allocation and return data before drawing conclusions. Second, governance constraints on the contribution rate: if there's an automatic reduction mechanism built into the fund's operating rules, that would explain why the contribution fell even if the policy intent hadn't changed. Those two feel most likely to contain the $6 billion explanation, and they have very different implications for what the recovery path looks like."

That's how you drive out of brainstorming on a government finance case. Not by stopping the list. By selecting with reasoning and framing what the selection implies for the next step.

What makes this brainstorm different from a private company case

The vocabulary is different. The underlying logic is identical.

Fund performance versus contribution policy is the same structure as revenues versus costs in the NordPlay brainstorm from post 15. Both are the natural first-level decomposition of the problem statement. Both emerge from asking the simplest possible logical question about the element in front of you.

Market-driven versus management-driven is the same structure as external versus internal in any private company cost analysis. Deliberate policy change versus governance constraint is the same structure as can't versus won't.

The contrast pairs are the same. The thinking process is the same. The vocabulary is different because you're inside a government finance case rather than a gaming company case. But the owner thinker doesn't need a different toolkit. They need the same thinking applied to a different context.

The governance constraint insight is the equivalent of the influential contributor insight in the peer's version of this drill. Both come from looking below the surface of the obvious decomposition and asking: is there a structural mechanism here that most candidates would miss? That's the insight the partner is waiting for. And it comes from curiosity, not from a memorized list.

If you're prepping public sector 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 where the insight opportunities are. And if you found this through another community, the full Case Playbook series is at r/ConsultingOffer.

The next post in The Case Playbook covers what happens to your brainstorm when the conditions are deliberately made unfavorable. Posts 14, 15, and 16 showed you how to run a clean brainstorm when everything is cooperative. In final rounds, it won't be. Partners apply specific pressure tactics during brainstorming, time compression, interjections, disinterested body language, and more, and most candidates have never practiced staying anchored through any of them. Post 17 covers what those tactics are and how the four steps keep you oriented when the environment turns hostile.

In post 14, I introduced the architecture of Structured Brainstorming: four steps, the concept of contrast pairs, and why the activation phase of steps one and two matters more than most candidates realize. If you haven't read that post, start there because this post assumes you already have that foundation.

This is post 15 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 applies the four steps to a live brainstorming question on the NordPlay Studios profitability case we've been building through the series. You'll see exactly how an owner thinker runs through each step, where most candidates lose points, and what genuine insight looks like versus a list of ideas that passes for brainstorming.

The brainstorming prompt

Seven to eight minutes into the NordPlay case, after clarifying questions and the issue tree are done, the partner pivots.

"We've established that NordPlay's net profits fell by $400 million over two years. Can you brainstorm the reasons why that might have happened?"

That's it. Short prompt, big scope, unfamiliar pivot from the structured analysis you've been doing.

Here's what happens in the next ninety seconds if you're a top performer.

Step 1: Absorb and anchor

Your pen goes down immediately. You write what the partner said.

"NordPlay net profits fell $400 million over two years. Brainstorm why."

Twelve words. You read it back: "So you'd like me to brainstorm the root causes of why NordPlay's net profits declined by $400 million over the past two years. Is that correct?"

The partner confirms.

What just happened is more important than it looks. You've done three things simultaneously. You confirmed you're brainstorming the right question. You've bought your thinking brain fifteen seconds to shift from analytical mode to generative mode. And you've signaled to the partner that you have a process, even under a surprise pivot.

The memorizer hears "brainstorm why profits fell" and immediately starts listing: revenue issues, cost issues, competition. They're already talking before they know what they're solving for.

The owner thinker writes it down first. That deliberate pause is the activation phase. You're giving your first principles thinking time to engage before your mouth opens.

Step 2: Clarify and orient

You have two circles from writing the prompt. "Net profits" and "NordPlay specifically." You clarify both briefly.

"Just to confirm, by net profits you mean after tax, after all operating and non-operating costs? I want to make sure I'm capturing the right variable."

The partner confirms: yes, net profits including tax.

"And are we focused specifically on NordPlay's own operations, or should I consider upstream factors like platform economics and app store relationships?"

The partner says: focus on NordPlay's direct operations for now.

That second clarification is critical. It narrows the scope of the brainstorm before you begin. You're not going to spend time on macro industry dynamics if the partner wants you focused on the business itself. A minute of scope clarity saves five minutes of misdirected brainstorming.

Now you know exactly what you're solving for: why did NordPlay's own net profit operations produce $400 million less than two years ago? That's your anchor. The brainstorm radiates from it.

Step 3: Brainstorm with contrast pairs

You take a breath. You look at the anchor: NordPlay net profits fell $400 million. The most basic contrast pair is immediate.

Net profit is revenues minus costs. So the $400 million decline came from revenues falling, costs rising, or both. That's your first level, derived from basic arithmetic, not from any memorized category.

Now you zoom into each side and apply contrast pairs at the next level.

Revenue side:

Revenues for a B2C mobile gaming company are volume times price times product mix. Each of those has a natural contrast pair.

Volume: did fewer people play, or did the same people play less? That splits into acquisition (getting new players in) and retention (keeping existing players). Under acquisition, you might see competitive alternatives pulling users away, a shift in demographics toward age groups NordPlay doesn't serve well, or a decline in marketing effectiveness. Under retention, you might see content fatigue where existing games stop generating playtime, or the absence of new releases to sustain engagement.

Price: did prices change, or did the pricing model become misaligned with what the market will pay? NordPlay operates across freemium, ad-based, and subscription models. If the mix shifted toward lower-monetizing models, or if subscription pricing was held flat while competitors moved toward more flexible models, that's a pricing architecture problem, not just a price level problem. That's the insight the partner is waiting for, not "prices were too high or too low."

Product mix: did the mix shift toward lower-margin products? Games in development generate no revenue but carry cost. If NordPlay has been investing heavily in a new title that hasn't launched, that creates a lag in the revenue line while fixed development costs stay high. That's an insight most candidates miss entirely because they're thinking about the revenue line in isolation rather than in relation to the product pipeline.

Cost side:

Costs split naturally into fixed and variable. That's the contrast pair.

Fixed costs: headcount, software licenses, infrastructure, and R&D. With over 3,000 developers and designers, NordPlay's salary and benefits line is significant. If they've been expanding the team ahead of revenue growth, or if they've been carrying senior talent at premium rates while output hasn't kept pace, that's a fixed cost problem. R&D deserves its own call-out: in gaming, R&D is not optional. But if R&D spend has been increasing without clear commercial output, that's worth examining.

Variable costs: app store distribution fees, contractor spend, marketing, and tax. This is where one of the sharpest insights lives. App store fees from Apple and Google are typically 15 to 30 percent of revenue. As NordPlay expanded into new markets, their distribution costs would have scaled with revenue. But if their product mix shifted toward lower-margin titles while fees stayed proportional to revenue, the net effect is a margin squeeze that doesn't show up as a simple cost increase. It shows up as a margin problem disguised as a revenue problem. That's a level-four insight. Most candidates never get there because they stopped at "variable costs increased."

One more variable cost worth naming explicitly: tax. Since we're looking at net profits, tax is included. If NordPlay expanded into new geographies with different tax structures, or if they haven't been optimizing their entity structure for the markets they operate in, there's a real tax efficiency opportunity that could partially explain the $400 million decline.

Step 4: Prioritize and drive forward

You've generated a structured brainstorm across four levels. Now you pick two or three to move forward with and explain why.

"Based on what I've generated, I'd want to prioritize three areas. First, the product mix and pipeline question: I suspect a portion of the $400 million is explained by development costs on titles that haven't yet generated revenue. Second, the pricing model alignment: if the freemium-to-subscription mix has been shifting without intentional management, that could explain a meaningful revenue per user decline. Third, app store distribution fees relative to margin: as NordPlay scales internationally, the fee structure becomes increasingly consequential and I'd want to understand how that's been managed. Those three feel most likely to explain the largest share of the gap."

That's how you drive out of brainstorming. Not by stopping the list, but by selecting, justifying, and pointing toward the next step. The partner now knows exactly where you want to go and why.

What partners are actually grading

The brainstorm above contains several things that most candidates never produce. Let me name them explicitly.

The distinction between games in development and released games. That's industry-specific acumen. A candidate who has never thought about how gaming companies manage their product pipeline would miss this entirely.

The pricing architecture insight. The difference between "prices are too high or too low" and "the pricing model is misaligned with how users value different types of content" is the difference between an observation and an insight. Partners grade on insights.

The app store fee margin insight. Connecting distribution fee structure to margin rather than just to cost is a second-order observation. Most candidates see "variable costs increased" and stop there.

The tax call-out. Because the partner specified net profits, tax is in scope. A candidate who doesn't know the difference between operating profit and net profit won't catch this.

None of these insights came from a memorized list. They came from an owner thinker reasoning through their own business, asking "what could actually explain this decline?" at each level of the brainstorm.

That's the difference between a brainstorm that generates ideas and one that generates insight.

If you're currently prepping the brainstorming module and want to share a recent brainstorm question you've been working on, drop it in the comments. I'll tell you where the contrast pairs would apply and where the insight opportunities are. And if you found this through another community, the full Case Playbook series is at r/ConsultingOffer.

The next posts in The Case Playbook go deeper into Structured Brainstorming across different case types and contexts, including nested brainstorming sequences and brainstorming in public sector cases where the vocabulary shifts but the contrast pair approach stays identical.

The first thirteen posts in The Case Playbook covered everything from the five mental moves in Case Start through building and driving an issue tree across different case types, private company, public sector, and asset-level infrastructure. If you've been following the series, you now have a solid picture of what Case Start looks like and how to maintain your orientation through Case Middle using the hub and spoke model.

This is post 14 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 opens a new chapter in the series: Structured Brainstorming.

As we covered in post 9, Case Middle has four modules that cycle in different combinations: Problem Solving, Chart and Data Analysis, Speed Math, and Structured Brainstorming. Of those four, Structured Brainstorming is the one that repeats most often in final rounds, sometimes two or three times in a single case, including nested sequences where the partner takes you deeper inside a brainstorm you've already started. It's also the module most candidates underprep because it doesn't feel like it requires the same rigor as math or chart analysis.

That assumption is wrong. And it's costing people offers.

Most candidates treat brainstorming as the easy part of a case interview. It's not structured math, not chart analysis, not a formal issue tree. It's just ideas. How hard can it be?

This post opens the Structured Brainstorming module of the series. We're not walking through a full case here. We're introducing the architecture of how brainstorming works in a consulting case, why most candidates do it wrong, and the concept that changes how you think about it.

The short answer to "how hard can it be?" is: harder than it looks, and easier than most prep resources make it. The reason most candidates struggle is that they've been told to memorize brainstorming categories and retrieve them under pressure. That approach produces exactly the kind of generic, interchangeable output that makes a partner lose interest within the first minute.

What brainstorming is actually testing

When a partner asks you to brainstorm, they're not looking for a list of ideas. They're looking for evidence that you can generate structured, insightful thinking in real time on an unfamiliar topic.

Structured means the ideas are organized in a logical way, not scattered. Insightful means the ideas reveal something non-obvious about the problem, not just a restatement of what everyone already knows. In real time means you can do this without a long pause or a rehearsed script.

Those three things together are what distinguish top performers in the brainstorming module. And none of them come from memorizing a list of brainstorming categories.

The memorizer's mistake

Many case prep resources give candidates a list of brainstorming structures. Stakeholders vs elements. Financial vs non-financial. Supply chain vs demand chain. Internal vs external. Organic vs inorganic.

These are not wrong. In fact, they're patterns that show up repeatedly in consulting work because they reflect real ways problems tend to decompose. But here's the problem with teaching them as a list to memorize and retrieve: the moment a candidate hears a brainstorming question, their brain goes into retrieval mode. Which category fits here? Stakeholders? Supply chain? The thinking that should be generating genuine insight is instead cycling through a mental index.

The memorizer produces a list of ideas organized by a category they retrieved. The owner thinker produces a list of ideas organized by a breakdown they derived. The output might look similar on the surface. But the partner can feel the difference, because one of them sounds like a consultant thinking and the other sounds like a candidate performing.

The four steps of structured brainstorming

Here's the architecture. Four steps, each with a specific purpose.

Step 1: Absorb and anchor

When the brainstorming question lands, write down what the interviewer said. All of it. Then reiterate it back to confirm you've understood what you're being asked to do.

This sounds simple. Under pressure, in the middle of a case that's been running for fifteen minutes, when you've just finished analyzing a chart and the interviewer pivots to "can you brainstorm some ideas about X," it's not simple. Most candidates panic slightly at the pivot, miss a detail in what the interviewer said, and end up brainstorming the wrong thing.

Writing and reiterating buys you something more valuable than confirmation. It buys your thinking brain time to engage. This is the activation phase. You are deliberately slowing down before the brainstorm begins so that the owner thinker can show up instead of the memorizer.

The memorizer hears the question and immediately starts listing. The owner thinker writes it down, reads it back, and gives their first principles mind a moment to orient to the specific problem in front of them.

Step 2: Clarify and orient

Once you've absorbed the question, circle anything you don't fully understand. Ask about it. Not because you need a long explanation, but because clarifying the scope of a brainstorm before you begin is the difference between generating useful ideas and generating a lot of ideas that miss the point.

If the partner asks you to brainstorm "reasons why premium subscribers might churn," you want to know: are we focused on the product experience, the pricing, the competitive alternatives, or all of the above? That one clarification might cut your scope in half and double the quality of your output.

This step is still part of the activation phase. You're continuing to buy time for first principles thinking to engage. You're also demonstrating Curiosity, one of the six ABCDEF dimensions we covered in post 6, by showing genuine interest in understanding the specific problem rather than jumping to a generic answer.

By the end of step 2, you should have a clear sense of what element you're zooming into. That's your brainstorming anchor. Everything in step 3 radiates from it.

Step 3: Brainstorm with contrast pairs

Here's where the owner thinker and the memorizer diverge completely.

The memorizer picks a category from their list and populates it. The owner thinker looks at the element they've zoomed into and asks the most basic logical question possible: what are the two natural sides of this thing?

Almost every element in a consulting brainstorm has a natural binary. Internal factors and external factors. Things that are within the client's control and things that aren't. Preventive causes and corrective responses. Supply side issues and demand side issues. Organic levers and inorganic ones.

These aren't frameworks. They're contrast pairs. And the reason they work is that a binary split is automatically exhaustive. If you've covered both sides of a contrast pair, you've covered the full space of that element. Nothing is left out.

The contrast pair emerges from the element, not from a memorized list. That's the critical distinction. You're not retrieving "internal vs external" as a category. You're looking at the specific element in front of you and asking: what are the two natural poles of this thing? The contrast pair you land on is derived from first principles, not retrieved from memory.

Let me show you a brief example from the NordPlay case we've been building through this series. If the partner asks you to brainstorm reasons why NordPlay's premium subscription revenue declined, you zoom into that element: premium subscription revenue. The most natural contrast pair is: did fewer people subscribe, or did the same people pay less? That's a volume vs pricing split, derived from first principles. Under volume: acquisition declined, or retention declined. Under pricing: the price point changed, or the perceived value relative to price changed. Two levels deep, fully exhaustive, derived in real time from the problem itself.

That's what structured brainstorming looks like from the owner thinker's perspective. Not a list. A structured decomposition built from the inside out.

Step 4: Prioritize and drive forward

Brainstorming is a module inside the case, not the end of the case. Once you've generated your ideas, you need to pick two or three to move forward with and explain why.

This step tests judgment more than creativity. The partner isn't looking for you to have listed every possible idea. They're looking for you to demonstrate that you can distinguish between ideas that matter and ideas that don't, given the specific context of this case.

The prioritization should be anchored in your main hypothesis. Which of these ideas, if true, would have the largest impact on the problem you're solving? Those are the ones worth pursuing. The rest you can acknowledge and set aside.

This is how you drive out of brainstorming cleanly. You don't just stop listing. You select, you justify, and you move the case forward. That momentum signals to the partner that you haven't lost the thread of the main hypothesis, even while operating inside a creative module.

Why contrast pairs beat memorized categories every time

Here's the practical reason beyond the philosophy.

When you memorize brainstorming categories and retrieve them under pressure, you're doing two things simultaneously: running the brainstorm and managing your memory. That split attention degrades both. The brainstorm gets shallower. The memory retrieval creates visible hesitation.

When you derive a contrast pair from first principles, you're doing one thing: thinking about the problem. All your cognitive resources go into generating insight rather than managing recall. The brainstorm gets deeper. The delivery gets smoother.

That's the real argument for the owner thinker approach. It's not just philosophically better. It's practically more effective under the conditions of a final round case interview.

If you're currently prepping for the brainstorming module and want to share what a recent brainstorm question looked like, drop it in the comments. I'll tell you what contrast pair I'd apply and why. And if you found this through another community, the full Case Playbook series is at r/ConsultingOffer.

The next posts in The Case Playbook go deeper into Structured Brainstorming with full case examples showing contrast pairs applied across different case types and brainstorming contexts. If the architecture makes sense but you want to see it running in a live case, that's what's coming next.

Most candidates who reach final rounds have solid Case Start. Their clarifying questions are clean. Their issue tree is tight. Their problem statement lands well. And then Case Middle begins, and something shifts.

This is post 12 in The Case Playbook, a series built for non-traditional candidates breaking into McKinsey, BCG, Bain, Tier 2, and Big 4 consulting firms. The previous posts covered how to build and drive an issue tree through Case Middle. This post covers three things that happen inside Case Middle that most candidates are completely unprepared for.

None of them are about structure. All of them are about what happens when the case stops following the script.

Thing one: the waltz

Most candidates practice cases as a linear sequence. You build the issue tree, you test sub-hypothesis one, you get data, you analyze it, you test sub-hypothesis two, and so on until you reach Case Wrap-Up. Clean, sequential, predictable.

Final rounds with partners don't work that way. Partners interject. They push back mid-analysis. They play devil's advocate on your numbers. They raise a risk while you're still in the cost synergy bucket. They ask you to defend a claim you made three minutes ago while simultaneously asking where you're going next.

This is not the partner trying to derail you. This is the partner testing whether you can do what real consultants do: hold a position, absorb a challenge, respond with confidence, and keep driving without losing the thread.

I call it the waltz. You're doing ninety percent of the work. But the partner is steering at certain moments, and you have to feel the redirect and respond to it without stopping the music.

Here's what it looks like. You're presenting your cost synergy sub-hypothesis on the Vantage and GridCore merger. You've identified transaction cost savings and operational efficiency gains. The partner interrupts: "I'm not sure those transaction costs are as large as you think. GridCore's contracts with Vantage are actually quite favorable already. Does that change your view?"

The memorizer freezes. Or worse, immediately abandons their position: "You're right, let me reconsider the cost bucket entirely."

The owner thinker says: "That's an important data point. If the existing contracts are already favorable, the transaction cost savings may be smaller than I projected. That would shift more of the $3 billion year-one target onto the operational efficiency side and potentially pull some of the burden forward onto year-two revenue synergies. I'd want to see the actual contract terms to size that before revising my hypothesis."

Notice what happened. The owner thinker acknowledged the challenge, updated their thinking in real time, explained the downstream implications, and kept driving. They didn't crumble. They didn't ignore the pushback. They absorbed it and moved forward.

That's the waltz. And you can only do it if the issue tree is genuinely internalized, because you need to know instantly what the downstream implications of any new information are.

Thing two: nested brainstorming

Partners love brainstorming more than most candidates realize. And in final rounds, they often run nested brainstorming sequences that go two or three rounds deep without switching to another module.

Here's how it typically unfolds. The partner asks you to brainstorm reasons why premium subscribers might have churned from Vantage's platform. You build a mini issue tree for the brainstorming question: product quality, pricing relative to competitors, platform experience. You go two levels deep and discuss the most likely drivers. That's level one.

Then the partner picks one of your ideas, say platform experience, and asks you to brainstorm specifically what platform experience issues would cause a premium user to churn. That's level two, nested inside level one.

Then they pick one of those ideas, say latency and loading speed, and ask what the root causes of latency issues would be in a platform like Vantage's. That's level three, nested inside level two.

Most candidates get through level one fine. By level two they're starting to feel disoriented. By level three they've completely lost the connection back to the main issue tree and the $6 billion question they were supposed to be solving.

The fix is understanding what nested brainstorming actually is. It's not a departure from the case. It's the partner drilling into one specific branch of your issue tree to test how deep your thinking goes on that branch. Every nested level is still in service of the main hypothesis.

When you stay connected to that, level three of a nested brainstorming sequence feels no different from level one. You're still an owner thinking about one specific part of their business problem. The question just got more specific.

Thing three: process without insight is worthless

Here's the most important thing in this post, and the one most case prep resources skip entirely.

The issue tree, the hypothesis, the sub-hypotheses, the surgical data asks: all of that is process. It sets you up to do the real work. But the real work is insight. And if you can execute the process perfectly and then fail to generate genuine insights from the data you receive, you haven't done anything useful.

Partners grade on insights. Not on structure. The structure earns you the right to be taken seriously. The insights determine whether you get the offer.

What's a genuine insight in a consulting case? It's not "revenues declined because prices fell." That's an observation. An insight is "revenues declined because the pricing model is misaligned with how the premium segment actually values the product. The issue isn't the price level, it's the pricing architecture." That's something the client couldn't have told themselves. That's what they're paying for.

From what I've seen coaching candidates through final rounds, the ones who get the offer are almost always the ones who generate one or two observations in Case Middle that make the partner lean forward. Not because they followed the process correctly. Because they said something the partner found genuinely interesting.

That requires two things the process can't give you. Business acumen, the ability to read between the lines of a data set using what you know about how businesses actually work. And judgment, the ability to distinguish between a data point that matters and one that doesn't.

Both of those develop through exposure. Reading about industries. Thinking about how businesses make money. Talking to people who work inside the kinds of organizations you're studying. You can't cram them in two weeks of case drilling.

But here's what you can do. Every time you analyze a chart or data set in practice, force yourself to go one level deeper than the obvious observation. The obvious observation is what the data shows. The insight is what it means for the hypothesis you're testing and what it implies for what you should look at next.

That habit, applied consistently across hundreds of practice reps, is what turns a technically competent case candidate into someone who generates genuine insights under pressure.

The common thread

The waltz, nested brainstorming, and generating real insights are three different things. But they share a common root.

They all require the same underlying capability: staying genuinely oriented inside a complex, unpredictable conversation while simultaneously thinking two levels deeper than what's on the surface.

That's not a case interview skill. That's a consulting skill. And it's what partners are specifically looking for in final rounds, because it's what they need in a junior consultant who's going to be sitting in client meetings without a senior person in the room.

The issue tree gets you into the conversation. Navigating the waltz, handling nested brainstorming, and generating real insights are what close it.

If you're in active final round prep and any of these three things are giving you trouble, drop it in the comments. And if you found this through another community, the full Case Playbook series is at r/ConsultingOffer.

The next post in The Case Playbook continues the Solvik water infrastructure case from post 6. If you've been following the series, you already have the problem statement from that post. Post 13 picks up exactly where that left off, building the hypothesis, issue tree, and sub-hypotheses on an asset-level public infrastructure case, and adding three nuances specific to that case type that most candidates miss entirely. Asset-level cases are a specific pressure point in final rounds, and understanding how the owner thinker approaches them is what separates candidates who hold up across any case type from those who only feel confident on familiar ground.

Most candidates prepping for elite consulting firms cases are, in my view, training the wrong cognitive habit. Not because they're lazy or unprepared, but because the standard advice points them straight toward memorizing frameworks, and that creates a very specific failure mode that's really hard to see from the inside.

Here's what I keep seeing coaching candidates: someone has done 50, 60, 70 cases. They know profitability trees, they know the 3Cs, they know Porter's Five Forces. And they still score a 2 or 3 on structure. Because when they hear "Belgian brewery considering the non-alcoholic market," they immediately reach into memory and pull out: "market attractiveness, competitive landscape, company capabilities, financial feasibility." Four generic buckets. Same as the candidate before them. Same as the one after. When three consecutive candidates present the exact same structure in the exact same order using the exact same language, the signal to the interviewer is clear: this was retrieved, not built. That candidate is not scoring a 4 or a 5.

What separates the candidates who actually hit those scores is something I call the Owner Principle. Before building any structure, you internalize the problem as your own. Not "what framework fits here" but "what would I actually need to figure out if my money were on the line?" That shift sounds small. The cognitive difference is enormous. It moves you from retrieval to what's actually required in the interview: generating insight from ambiguous information under time pressure.

I just released a full video on this, with a complete case walkthrough showing exactly what that looks like in practice, including multi-level structuring, how to signal the hypothesis gate to the interviewer, and how to drill into a branch when they redirect you. Link in comments.

What stage are you at in your case prep, and which part of structuring feels shakiest right now?

There's a specific kind of confusion I hear from candidates who make it to final rounds and don't get the offer. They say something like: "The case felt different. I couldn't get my footing. It was like the rules changed."

This is post 11 in The Case Playbook, a series built for non-traditional candidates breaking into McKinsey, BCG, Bain, Tier 2, and Big 4 consulting firms. The previous posts covered how to build a bespoke issue tree from first principles and drive it through Case Mid. This post covers what happens to that process when you move from a round one associate interview to a final round with a partner.

The issue tree itself doesn't change. What changes is everything around it.

Round one gives you scaffolding. Final rounds take it away.

In round one, the structure is handed to you. The interviewer reads a prompt. You ask clarifying questions. There's a natural pause where everyone in the room understands you're going to take a moment to build your issue tree. You write, you walk them through it, you move forward. The format has clear boundaries and the candidate knows what's expected at each stage.

Final rounds with partners are different. The conversation is fluid from the moment you sit down. The partner might spend ten minutes walking you through the client context in a conversational way, asking follow-up questions, building the picture together with you. And then at some point, mid-conversation, they'll say something like "so how would you think about structuring this?" That's your cue. But there's no pause. No clean handoff. No moment where the room goes quiet and you get two minutes to write.

The math isn't harder. The case types aren't more complex. What's harder is that the scaffolding around the issue tree has dissolved. You're expected to build structure inside a conversation that never announced itself as a case interview.

From what I've seen coaching candidates through final rounds, this is the gap that costs people offers more than any technical weakness. They know how to build an issue tree. They just can't do it without the formal prompt-and-pause structure they trained on.

Who is sitting across from you, and why it changes everything

Round one interviewers are typically associates or junior consultants. Their job is to check fundamentals. Can you follow a prompt? Can you build a clean issue tree? Can you hold your composure under ambiguity? That's a baseline filter and it has a structured format because associates are themselves still working within structured processes.

Partners operate differently. They spend their days in client boardrooms where no one pauses the meeting to let the consultant write a structure. A CFO raises a problem mid-conversation and expects a response that demonstrates both strategic thinking and forward momentum simultaneously. Partners aren't testing whether you can execute a case interview format. They're testing whether you can operate in the environment they live in every day.

That's why the issue tree in a final round has to feel conversational. Not because the structure matters less, it matters just as much, but because it has to emerge from a dialogue rather than be produced during a formal pause.

What the owner thinker does differently

Here's the reframe. In round one, the paper is a tool that helps you organize under pressure. Use it when you have it. But the paper was never the source of the structure. The thinking process is.

An owner doesn't pause mid-conversation to write a structure before responding to a problem their CFO just raised. They think in structures naturally because they've internalized how to decompose problems. When your finance director walks in during a meeting and says "contribution revenues are down," you don't ask them to wait while you find a pen. You ask: is this a volume problem or a rate problem? That's an issue tree. Built in your head in three seconds because the logic is internalized.

That's what partners are testing in final rounds. Not whether you can write a clean structure on paper. Whether the structure lives in you.

Let me show you what this looks like.

The partner says: "We have a client, a mid-sized European infrastructure firm. They've been seeing margin pressure for about eighteen months. We've done some preliminary work but haven't cracked what's driving it. How would you think about approaching this?"

The round one candidate hesitates. Do I write now? Is this a formal case? What's the prompt? In that hesitation, they've already signaled that they need the structure to be handed to them.

The owner thinker responds immediately: "Eighteen months of margin pressure is interesting. Before I structure this, I want to make sure I'm solving the right question. Are we trying to identify the root cause and quantify it, or does the client already have a hypothesis about which side of the P&L is the problem?"

The partner gives more context. The owner thinker is already building the issue tree in their head: revenue dynamics on one branch, cost structure on the other, with a third consideration around whether the pressure is cyclical or structural. When the partner says "how would you think about this?", the response is immediate and conversational: "My instinct is to split this into two questions. Is the margin pressure coming from the revenue side, pricing, contract structure, volume mix? Or is it cost-driven, input costs, operational inefficiency, overhead creep? Those have very different root causes and very different fix timelines. I'd want to understand which side is larger before going deeper."

No paper required. No pause. The structure emerged from the conversation because the thinking process is internalized.

Why drilling alone won't get you there

Most case prep advice won't tell you this directly, but I will.

The fluidity of final round issue trees isn't something you can develop by doing more case drills. Drilling builds the mechanics. Fluidity comes from something different: having experienced conversations where structure has to emerge on the fly, without a safety net.

The best sparring partners for final round prep are not other candidates who have cracked cases as analysts. They're people who have managed real client relationships, who have been in boardrooms where a CEO pivots mid-sentence and the consultant has to restructure their thinking in real time. That experience is what teaches you to build an issue tree inside a conversation rather than after it.

A coach who broke into McKinsey as a fresh analyst knows the mechanics. A coach who spent years managing senior client relationships knows the fluidity. Those are different things, and at the final round stage, the second one is what you need to practice against.

One practical thing to do this week

Take any problem statement you've already built in this series, the NordPlay case, the Norway case, either one, and practice delivering the issue tree verbally with no paper, as if you're mid-conversation with a partner who just asked how you'd think about it.

Not reciting it. Conversationally walking through the two main branches and why you'd start where you'd start. Keep it under a minute. If it sounds rehearsed, keep going until it feels like you're just thinking out loud.

That's the gap between round one and final round performance on the issue tree. Not the content. The fluency.

If you're currently in final round prep and want to share what the issue tree moment is feeling like in practice, drop it in the comments. I'd be curious what specific part of that transition is hardest for people. And if you found this through another community, the full Case Playbook series is at r/ConsultingOffer.

The next post in The Case Playbook covers what happens inside Case Middle when the case stops following the script. Most candidates practice cases as a clean linear sequence: build the issue tree, test sub-hypothesis one, get data, analyze it, move to sub-hypothesis two. Final rounds don't work that way. Post 12 covers three specific things that happen in Case Middle that most candidates are completely unprepared for, and none of them are about structure.

In post 3 of The Case Playbook, I walked you through the five mental moves on the Norwegian Ministry of Finance case. By the end of that post, you had a clean problem statement: find the root cause of why the sovereign wealth fund's annual contribution to the national budget declined from $18 billion to $12 billion over the past eighteen months, and identify how to restore it to at least $18 billion annually within three to five years.

This is post 10 in The Case Playbook, a series built for non-traditional candidates breaking into McKinsey, BCG, Bain, Tier 2, and Big 4 consulting firms. Posts 7 and 8 covered building and driving the issue tree using NordPlay Studios, a private company profitability case. This post does the same thing on the Norway case, to prove what we said in post 3: the methodology works identically regardless of case type. Only the vocabulary changes.

From problem statement to hypothesis: the same five second move

The problem statement is on the page. The interviewer is waiting. Before you touch the issue tree, you state a hypothesis.

"My hypothesis is that it's possible to find the root causes of why the fund's annual contribution fell by $6 billion and restore contributions to $18 billion annually within three to five years."

That's it. One sentence. But it reframes everything that follows. You're not exploring. You're testing. The issue tree is how you test it.

Building the issue tree from first principles

The problem statement is a $6 billion annual decline in sovereign wealth fund contributions. The owner thinker asks the most basic question possible: where could a $6 billion decline in fund contributions actually come from?

Think about it the way you'd think about it if this were your own investment portfolio. You're not a sovereign wealth fund expert, but you are the owner (The Finance Minister) . Your fund manager walks in and tells you annual distributions dropped by a third. What do you ask? Did the fund earn less money, or did the withdrawal rate change? That's the only logical decomposition. Either the fund's total value declined (so the same percentage yields less), or the contribution rate itself was reduced.

That gives you the first branch: fund performance (the asset side) and contribution policy (the rate side). Both need to be examined to explain the $6 billion gap.

The second branch is the same as every case: what stands between us and the recovery? The ministry has a three to five year target. What constraints and risks could prevent them from hitting it? Political considerations around fund management, global market conditions outside the government's control, and the structural mechanics of how quickly contributions can be restored once the root cause is addressed.

So the issue tree has two main branches. Branch one: find the root cause of the $6 billion decline. Branch two: identify what it will take to restore $18 billion annually within three to five years.

Level two under branch one breaks into fund performance (market returns, asset allocation, drawdown events) and contribution policy (rate changes, one-off adjustments, governance decisions). Level three gets specific to what the ministry would actually have data on: equity portfolio performance, bond yields, commodity exposure on the asset side; and fiscal policy decisions, emergency fund withdrawals, and parliamentary budget agreements on the policy side.

Three levels. Built from the problem statement. No memorization required.

Four sub-hypotheses, each tied to a surgical data ask

Once the issue tree is communicated, you tell the interviewer how you're going to test it. Four sub-hypotheses, one per major bucket.

Sub-hypothesis one: the $6 billion decline came from deteriorating fund performance. To test this I need the fund's audited annual returns for the past three years, broken down by asset class. I expect to see a decline in total portfolio value that, at the current contribution rate, explains some or all of the $6 billion shortfall. Do you have access to the fund's financial statements or the Ministry's investment reports?

Sub-hypothesis two: the $6 billion decline came from a policy change in the contribution rate. To test this I need the historical contribution rate applied to the budget over the past three years and any parliamentary or executive decisions that modified it. I expect to see either a rate reduction or a one-time adjustment that explains the gap.

Sub-hypothesis three: I can identify solutions to the top root causes and design a credible path to restoring $18 billion annually within three to five years. Once the root causes are ranked, I'll assess which levers the ministry actually controls and what realistic timelines look like.

Sub-hypothesis four: the recovery can be achieved through root cause fixes alone, without requiring additional revenue sources or structural reforms beyond the fund itself.

Here's the part that separates good case work from great case work. Before any data arrives, you've told the interviewer exactly what you're looking for and why. When they hand you a chart showing the fund's equity portfolio performance over thirty-six months, you're not staring at it wondering where to start. You already know the needle you're looking for: a decline in total portfolio value that maps to the $6 billion annual contribution gap. That's the surgical approach. You're walking into the grocery store with a precise list, not wandering the aisles.

From what I've seen coaching candidates through government and public sector cases, this is precisely where Case Mid starts to unravel for most people. The issue tree looked good. The sub-hypotheses were stated. But when the data arrives, especially in a case they find less familiar, the candidate forgets what they were testing and starts reacting to whatever the chart shows. The thread goes cold.

Staying oriented when Case Mid switches modules

One more thing worth naming explicitly. In a government case at the final round level, Case Mid often runs longer and switches modules more abruptly than in a private company case. You might go from a data analysis on fund performance to a brainstorming question about policy levers to a speed math question on contribution rate scenarios, all in sequence, with no natural break.

The candidates who hold up through that sequence are the ones who have one anchor: the issue tree. Every module produces something that maps back to a branch. The chart analysis feeds sub-hypothesis one. The brainstorming feeds sub-hypothesis three. The speed math tests what a rate adjustment would need to look like to close the remaining gap.

After each module, you come back to the issue tree out loud. "Based on what the fund performance data shows, my revised hypothesis is that roughly $4 billion of the $6 billion decline is explained by the equity portfolio drawdown in the past eighteen months. I still need to understand the policy side to account for the remaining $2 billion." That's one sentence. It takes ten seconds. And it signals to the partner that you haven't lost the thread, regardless of what they've thrown at you.

The memorizer treats each module as a new test. The owner thinker treats each module as more data being fed into the same question they've been solving since minute four.

If you're prepping this case or a similar public sector case and want to share where you're getting stuck, whether it's the issue tree build, the sub-hypothesis logic, or the transitions in Case Mid, drop it in the comments. The community is here for exactly this kind of conversation. And if you found this through another subreddit, the full Case Playbook series is at r/ConsultingOffer.

The next post in The Case Playbook covers something that catches most candidates off guard in final rounds. The issue tree you've been building and driving through Case Middle doesn't change when you move from a round one associate interview to a partner round. But everything around it does. The format is more fluid, the structure is less explicit, and the partner expects you to hold your process together inside a conversation rather than a formal case structure. That's what post 11 is about.

In the previous post I wrote about how to build an issue tree that actually fits the problem, bespoke to the specific numbers and constraints you extracted in the clarifying question phase, three levels deep, derived from first principles rather than retrieved from memory. If you haven't read that one, start there because what I'm about to cover assumes you already have a well-built issue tree on the page.

This is post 8 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 covers what happens the moment the issue tree is on the page and Case Mid begins.

This post is about what happens next. And here's the thing most candidates miss: building the issue tree is not the hard part. Using it is.

From what I've seen coaching candidates through final rounds, roughly eighty percent of them spend real energy building a tight issue tree and then effectively abandon it the moment Case Mid begins. The interviewer hands them a chart, they analyze the chart, they give a number, and they wait. The issue tree is sitting on their page untouched. The thread they spent three to four minutes establishing has gone cold.

That's the gap this post addresses.

From issue tree to hypothesis: the five second move

Before you leave the issue tree and move into Case Mid, you need to do one more thing. State a main hypothesis.

Not a conclusion. A directional bet. Something like: "My hypothesis is that it's possible to find the root causes of why NordPlay's net profits fell from $2.4 billion to $2 billion and restore them to $2.4 billion within one year."

Five seconds. One sentence. But it changes everything about what follows.

Here's the first principles reason why this matters. When you state a hypothesis before you've seen any data, you're telling the interviewer something important: you're not going to spend the next twenty to twenty-two minutes of Case Mid wandering through data looking for something interesting. You have a position. You're going to test it. If the data supports it, great. If it doesn't, you'll revise. That's how real consulting works, and partners recognize it immediately.

The memorizer builds an issue tree and asks "where should I start?" The owner thinker builds an issue tree, states a hypothesis, and says "here's what I expect to find and why."

Sub-hypotheses: how you actually test the main hypothesis

You don't test the main hypothesis directly. You can't. It's too big. What you do is break it into sub-hypotheses, one for each branch of the issue tree, and test those in sequence.

For NordPlay, the issue tree has two main branches. Branch one is finding the $400 million decline. Branch two is fixing it and restoring profits to $2.4 billion within one year. Those become the spines of your sub-hypothesis structure.

Under branch one, you have revenues and costs. So sub-hypothesis one is that the $400 million decline came from revenues. Sub-hypothesis two is that it came from costs. Under branch two, you have fixing the root causes and restoring the number. Sub-hypothesis three is that you can identify solutions to the top root causes and restore $400 million in net profits within one year. Sub-hypothesis four is that you won't need to look beyond the identified root causes, and that revenues and costs together will close the full gap.

Four sub-hypotheses. One for each major bucket in the issue tree. Each one is a testable, specific claim about where the answer lives.

Now here's what most candidates don't realize: those sub-hypotheses tell you exactly what data to ask for. You don't need to wait for the interviewer to hand you something. You ask for it directly.

"My first sub-hypothesis is that the $400 million decline came from revenues. To test that I'd want NordPlay's P&L with a revenue breakdown for the last two years. I'd expect to see a dip in one or more of product mix, pricing, or volume that explains some or all of the $400 million. Do you have that?"

That's a surgical ask. You've told the interviewer what you're looking for, why you're looking for it, and what you expect to find. That's Drive and Acumen running simultaneously.

The hub and spoke: revising as you go

Here's the part that separates a good candidate from a great one in Case Mid.

As you test each sub-hypothesis, you come back to the main hypothesis and revise it. Not discard it. Revise it. Because the data is going to give you partial answers, not complete ones, and your job is to update your position as evidence accumulates.

Say you test sub-hypothesis one on revenues and the data shows that $250 million of the $400 million decline came from a pricing problem in NordPlay's premium subscription tier. You now have $250 million explained. Your revised main hypothesis is: the root cause is partially identified, $250 million is from pricing, and I still need to find the source of the remaining $150 million.

You go to sub-hypothesis two on costs. The data shows $100 million in cost increases from third-party app store fees that grew as NordPlay expanded globally. Now you have $350 million explained. Revised main hypothesis: $350 million of the $400 million decline is identified, $50 million is still unaccounted for.

You go to sub-hypothesis three on solutions. You can fix the pricing issue and renegotiate or internalize some of the distribution costs, which together should recover at least $350 million. But there's still a $50 million gap. So sub-hypothesis four activates: you brainstorm alternative revenue levers, maybe a new enterprise licensing model or an accelerated international expansion, to close the remaining gap.

That's the wave. You leave the issue tree, gather data, come back, revise, leave again, gather more data, come back, revise again. The issue tree is your control center throughout. It's not a deliverable you produced at minute four. It's the navigation system you're using for the full case.

What this looks like when it goes wrong

A candidate I worked with last year was targeting McKinsey and had made it to the final round three times across different cohorts, two rejections. His case openings were strong. His issue trees were tight. But when I watched him in Case Mid, he would analyze a chart, give a good insight, and then sit there waiting for the interviewer to tell him where to go next.

He was treating each activity in Case Mid as a standalone test rather than as a sub-hypothesis being tested against his main hypothesis. Every time the interviewer handed him something new, he started from zero.

We spent one session rebuilding his approach around the hub and spoke model. After each data point or analysis, he practiced coming back to his issue tree out loud: "Based on what I found in the revenue analysis, I'm revising my main hypothesis to..." It took one session and a few practice cases for it to feel natural. His next final round, he got the offer.

The issue tree doesn't work if you treat it as a formality. It works when you use it as a living document that gets sharper as the case progresses.

If you're currently prepping for Case Mid and want to share what's tripping you up, drop it in the comments. And if you found this through another community, the full Case Playbook series is in r/ConsultingOffer.

The next post in The Case Playbook takes a step back and shows you the full architecture of a consulting case interview at McKinsey, BCG, Bain, and Tier 2 firms: seven modules across three sections, what's guaranteed in every case, what varies, and why most candidates only ever prepare for two of them. If the hub and spoke model makes sense to you but you're still not sure how all the pieces fit together, that's the post that connects everything.

Most candidates prep for case interviews by practicing cases. That sounds obvious. But here's what I've noticed after coaching dozens of candidates through final rounds: the majority of them practice the mechanics and completely ignore the layer underneath, which is what the partner sitting across from them is actually evaluating.

This is post 6 in The Case Playbook, a series built for non-traditional candidates breaking into McKinsey, BCG, Bain, Tier 2, and Big 4 consulting firms. The previous posts covered the five mental moves and how to apply them across different case types. This post goes one level deeper into what partners are actually scoring during Case Start.

It's not just "can this person structure a problem." That's the floor. By the time you're in a final round, the partner already assumes you can do that. What they're watching for is something harder to name and harder to train for. And if you don't know what it is, you can't perform it deliberately.

Let me walk you through it using a real case, and I'll show you exactly what a top performer is doing at each stage of the Case Opening.

The case: Solvik

Here's the prompt:

"Our client is the mayor of Solvik, a mid-sized Norwegian city with just over one million residents. The city operates two water infrastructure facilities that together supply clean water to all residents. One of the facilities, the Voss plant, has been experiencing serious operational problems over the past several months, causing significant service disruptions. The mayor needs your help to understand and fix this as quickly as possible."

Vague. No numbers. New industry. A public sector client most candidates have no professional familiarity with.

This is by design. The partner chose this case because it's unfamiliar. And the first thing they're watching is how you respond to that unfamiliarity in the opening seconds.

What's actually being evaluated: the ABCDEF framework

From what I've observed coaching candidates and from my own time working inside consulting firms, partners evaluate Case Start across six dimensions simultaneously. I think of them as the six qualities every consulting engagement actually requires, and the case interview is just a compressed simulation of all six at once. I call it the ABCDEF framework.

A is for Acumen. Not industry knowledge. You're not expected to know how water treatment plants work. What partners are looking for is whether you can take general knowledge, simple logic, and real-world context and apply it to an unfamiliar situation in real time. The owner thinker does this naturally. They don't wait to be an expert before they engage. They reason from what they know.

B is for Bearing. Composure and emotional control under pressure. Every candidate who gets to a final round is nervous. Partners know this. What they're watching is whether you have a way of absorbing that stress without letting it degrade your output. The candidates who perform best in final rounds don't feel no stress. They feel it and keep going anyway.

C is for Curiosity. Are you genuinely interested in the client's problem? Does the way you ask questions suggest you actually want to understand, or are you just checking boxes? Partners can feel the difference between mechanical questioning and real engagement. It's not subtle.

D is for Drive. In a real engagement, you will often be in a room with a client without a senior person present. You have to be able to move a conversation forward, keep momentum, and not wait for someone to tell you what to do next. The Case Opening is the first test of this. Are you leading, or are you being led?

E is for Empathy. This one surprises people. Consulting is not a purely analytical job. You're working with clients who are under pressure, who may not have articulated their problem clearly, and who are trusting you to help them. The best candidates make the client feel heard and understood, not interrogated. In the Case Opening, this shows up in how you confirm information, how you frame your viewpoints, and how you respond to what the interviewer tells you.

F is for Finesse. Are you smooth? Does the transition from prompt to clarifying questions to problem statement feel natural and engaging, or does it feel like a process being executed? Partners work with C-suite clients daily. They need to know you can hold a sophisticated conversation under pressure without it feeling like a rehearsal.

Those six dimensions are what's being evaluated across the three to four minutes of Case Start. The mechanics of the five mental moves are in service of those six qualities. They're the vehicle, not the destination.

What this looks like on the Solvik case

Back to the case. The prompt mentions clean water, a Norwegian city, and an operational problem at one specific facility. No numbers yet.

The owner thinker hears this and immediately registers two things before they've said a word. First, this isn't solvable yet. The information is too vague to structure anything meaningful. That recognition is itself a form of Acumen: you understand what you don't know and why it matters. Second, you can already sketch the rough shape of the question. A public utility is underperforming, the client wants it fixed fast, and the question is probably going to be: find the root cause of the supply drop and restore it to baseline within a tight timeline. You don't know the numbers yet. But you have the template.

That early pattern recognition is what drives Bearing in the opening. You're not pretending to be calm. You're calm because you have a way of thinking about ambiguous situations that works every time, regardless of industry.

When you reiterate the prompt, you're demonstrating Curiosity and Drive simultaneously. You're showing you were tracking every word, and you're moving the conversation forward without being asked to.

On clean water, rather than asking "who uses this water?", the owner thinker offers a viewpoint: "In any Norwegian city of this scale, clean water supply is a hundred percent public utility. The primary end users are residents for drinking, cooking, and sanitation. I'll assume that's the scope here unless you tell me otherwise." That's Acumen plus Bearing plus Finesse in one move. The partner just needs to confirm or redirect. You've done the cognitive work for them.

On the operational problem, rather than asking "what does unreliable mean?", the owner thinker says: "When I hear that the Voss plant is experiencing problems, my read is that this translates into a loss of supply capacity. I'd want to understand what full capacity looks like and where the plant is operating now." Clean. Direct. Specific. You've converted the vague English into a math question without being asked to. That's Drive.

After the interviewer confirms the numbers, say full capacity was 90 million liters per day and current output is 54 million liters per day, you observe rather than just record: "A thirty-three percent drop is significant for any public infrastructure. With two facilities serving Solvik, I'd assume the Voss plant serves roughly half the population, which means somewhere around five hundred thousand residents are experiencing reduced supply. Can you confirm that?" That's Empathy. You're making the scale of the problem real, showing the mayor you understand what this actually means for people, not just for a number on a spreadsheet.

That's what all six dimensions look like running simultaneously in a real Case Opening.

The problem statement lands here: 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 to 90 million liters per day within the mayor's stated timeline of four weeks.

Forty words. Quantified. Time-bound. Solvable.

The emotional reality nobody talks about

Here's something most case prep resources skip entirely. You are going to be nervous. Even the strongest candidates I've worked with describe the moment a partner reads an unfamiliar prompt as a kind of shock. Your brain registers the unknown industry, the vague language, the absence of numbers, and something tightens.

The mistake is trying to suppress that. The owner thinker doesn't suppress it. They redirect it. The act of picking up the pen and writing is a mechanism. It gives the nervous system something concrete to do while the brain catches up. The act of reiterating out loud is a mechanism. It buys you thirty seconds to organize without silence.

The candidates who project composure under pressure in a Case Opening aren't the ones who feel no pressure. They're the ones who have a system that runs even when they're stressed. The five mental moves are that system. You don't have to think about what to do next. You just run the next move.

By the time you reach the problem statement, in my experience coaching this, the stress has almost always subsided. Not because the situation got easier. Because forward motion creates its own momentum.

If you're in active final round prep and want to share which of the six dimensions is giving you the most trouble, drop it in the comments. I'd be curious what patterns are showing up for people at this stage. And if you found this through another subreddit, the full Case Playbook series is in r/ConsultingOffer.

The next post in The Case Playbook moves from Case Start into what comes immediately after: building an issue tree that actually fits the problem. Most candidates treat the issue tree as a deliverable they produce once and then forget. The next post shows you why that's the single biggest mistake you can make in Case Mid, and what to do instead.

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?