Clarifying questions

In Chapter 1, you learned to build a structure: a clean map for attacking a messy problem. But in a real case, there is one move before the map.

You clarify the question.

That sounds small. It is not. Clarifying questions are one of the easiest places to tell apart a candidate who is performing the steps of a case from one who is actually thinking. Some candidates treat them as a warm-up ritual: ask one or two polite questions, buy a little time, then rush into the framework. That misses the point entirely.

The intuition

Clarifying questions are how you sharpen the target before you aim.

Because here is the thing: a brilliant answer to the wrong question is still wrong. And the prompt you are handed is rarely the whole question. It might sound simple:

You could jump straight into revenue and costs. Sometimes that is fine. But a few well-aimed questions can make the entire case cleaner:

• Are we looking at the full chain or one region?
• Is the 15% drop in total profit, profit margin, or profit per store?
• Did this happen suddenly last quarter, or has it been trending for a while?
• How does the chain actually make money: in-store, delivery, subscriptions, packaged products?

Those are not filler. Each one changes the shape of the case. Clarifying is not about asking more. It is about asking what would make your next move smarter.

Why it matters

The interviewer wants to see that you can listen before you solve.

Real problems are messy because the first version of the question is usually not the real one. A client says "we need growth," but means profitable growth, in one region, over the next year. A client says "costs are too high," but the real question is whether costs are structurally higher than competitors or just temporarily inflated by a one-time event. Hearing the question behind the question is a big part of the job.

Bad clarifying questions make you sound like you are stalling. Good ones make you sound like someone who knows that defining the problem is part of solving it.

The core moves

Throughout this chapter, we will keep using the same example: a coffee chain whose profits dropped 15% last quarter. Your job is not to interrogate the interviewer. It is to ask just enough to aim your structure.

1. Clarify the objective: what does success mean?

Before you solve, make sure you know what the client actually wants. Are they trying to diagnose what happened? Restore profit to a specific level? Decide whether to close stores or change pricing? Work out whether this is a short-term blip or a long-term strategy problem?

That clarifies the decision. It tells you whether the case is mainly diagnostic, action-oriented, or target-driven, and that shapes everything downstream.

2. Clarify how the business makes money.

For familiar businesses you may not need much here, but even a coffee chain can earn money in very different ways, and that changes the case. Confirm two things: the revenue streams that actually matter, and the handful of drivers underneath them.

On streams, a coffee chain might make money from in-store drinks, food, delivery, loyalty, packaged beans, or franchise fees. A franchise-heavy model behaves nothing like a company-owned one. A delivery-heavy chain has different economics from a mostly in-store one.

If the interviewer says delivery is now 40% of sales, your case shifts: channel mix, delivery fees, and packaging costs suddenly matter far more.

3. Clarify the scope: where exactly are we looking?

Scope is the boundary of the case. It tells you what is in and what is out: all stores or some, one city or global, last quarter or a longer trend, company-owned or franchise, profit dollars or profit margin.

This one question is powerful, because the answer forks the whole case:

4. Clarify the metric: what exactly changed?

Prompts use words that sound obvious until you look closely. "Profit declined" could mean total profit dollars fell, or margin fell, or profit per store fell, or profit fell even though revenue grew.

That small question prevents a lot of confusion. A drop in total profit might point to fewer customers. A drop in margin might point to rising costs or discounting. The metric quietly points you toward the right diagnosis.

5. Ask only what changes your approach.

Not every possible question belongs at the start. Weak candidates ask everything they can think of:

Strong candidates ask the two or three questions that actually determine the opening structure. The filter is simple:

If yes, ask it now. If no, save it for later, when it is actually relevant. A few sharp questions beat a dozen scattered ones, every time.

What weak looks like

What strong looks like

Same case, very different impression. This candidate is not collecting background. They are clarifying the metric, the scope, and the business model, and every answer would change the structure.

Turn clarification into your structure

Clarifying questions should not become a separate performance. They should build a clean bridge into your structure.

Then move:

That summarize-then-move is the whole point. The clarification you just did is now visibly shaping the map you build next. Nothing was wasted.

Common traps

Practice clarifying before structuring in CaseLab

Use the same live, voice-interactive structuring drills introduced in Chapter 1, but shift the focus to the moment before the structure. You do not need to run a full case yet. Hear the case question, ask two or three clarifying questions out loud, then use the answers to build your structure.

Afterward, review the feedback the same way you would for the structuring drill: did your opening give the interviewer a sharper map to follow, or did your questions stay too generic?

Remember the whole lesson of this chapter: the goal is never to ask more questions. It is to ask the few that make everything after them sharper.