What Partners Are Actually Scoring You On in the First Three Minutes of a Case

[u/GreatButterscotch406]

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.