Clarifying Questions: What to Ask, What Not to, and When to Stop
Clarifying questions are the first thing an interviewer hears you think. Learn the four jobs they do, the test that separates a good question from filler, what not to ask, and when to stop and start structuring.
The clarifying phase is the shortest part of a case and one of the most revealing. In about a minute the interviewer hears whether you listen, whether you know what matters in this kind of problem, and whether you stay calm and organized before you have a framework to hide behind.
Candidates fail it in two opposite ways. Some ask nothing and charge into a structure for the question they assumed they heard. Others ask everything, ten questions in a row, which signals that they have no view of what matters and spends time they will want later. The skill is narrower than either: ask the few questions whose answers would change what you do next. The questions you choose are also part of the first impression an interviewer forms in the opening minutes.
The four jobs a clarifying question does
1. Objective
What does success mean, for whom, and by when? Without it you can solve the wrong problem perfectly. "Is the aim to restore margin to its earlier level, or to grow absolute profit over the next two years?"
2. Scope
Which products, geographies, customer segments and time horizon are in play? "Are we looking at the whole business or one product line?"
3. Definitions
Prompts use words loosely. "When you say the market, do you mean all coffee sold or only specialty?" "By decline, do you mean absolute profit or margin percentage?" A definition you leave unfixed is a misunderstanding waiting for minute fifteen.
4. Constraints
Budget, deadline, capabilities, options the client will not consider. "Is there a limit on investment, or an option already ruled out?" Ask this only if it is likely to change the recommendation. In many cases the interviewer volunteers constraints later.
The test: would the answer change your structure?
Before you ask, run a thirty-second thought experiment. Imagine two possible answers. If you would build the same structure either way, the question is filler.
Take the BrewHouse prompt from our profitability walkthrough: margin has fallen while same-store revenue is flat. "Has the store count grown over that period?" passes the test. If yes, new stores that have not matured become a branch of your structure; if no, that branch disappears. "Does BrewHouse sell coffee?" fails it, because no answer changes anything.
Market entry shows the same principle. Asking what the client hopes to achieve by entering (revenue, strategic position or defending an existing business) decides which evidence matters, which is why it appears among the failure modes in our market entry post.
You can even use it as phrasing: "I am asking because it would change whether I look at new stores separately." One clause of reasoning turns a question into evidence that you are already structuring.
Phrasing that sounds like a consultant
- Restate first. "Let me make sure I have the objective right: ..." One sentence invites correction and shows you listened.
- Signpost. "I have two questions before I structure." It tells the interviewer how long you will take and prevents the feeling of an interrogation.
- One question at a time, short and specific. Compound questions get half-answered.
- Offer a working assumption when you can. "I will assume we mean annual revenue in the US, unless you would like other regions included."
Two weak-to-strong rewrites show the difference:
- Weak: "Can you tell me more about the company?" Stronger: "Is the client one business or several, and do we care about all of it?"
- Weak: "What is the goal?" Stronger: "Is the aim to restore margin to its earlier level or to grow absolute profit, and over what period?"
What a clean exchange sounds like
Here is a short opening, invented for illustration. The prompt: a regional gym chain has seen profit fall over the last two years and has asked for help.
Candidate: Let me make sure I have this right. The client is a regional gym chain, profit has fallen over two years, and we are here to understand why and what to do. I have two questions before I structure. First, is the fall in margin, absolute profit, or both? Second, has the number of locations changed over those two years?
Interviewer: Both have fallen; profit is down about a third. The chain has opened six new locations over the two years, and the older ones look similar to one another.
Candidate: Thank you. So the objective is to explain a decline of about a third across the whole chain and recommend how to reverse it, with the six new locations a likely separate branch. Could I take a minute to structure my thoughts?
The whole exchange takes well under a minute. The candidate restated the prompt, signposted two questions, and made each one pass the test: the first fixes the profit measure, and the second reveals the new-location branch. The older locations looking similar also saves a question about spread across sites. The close restates the frame and asks for a minute, so the candidate starts structuring with an agreed objective instead of a guess.
What not to ask
- Things you can derive or estimate. In a sizing case, asking for the population of the country asks the interviewer to do your estimating. State an assumption and ask whether it is reasonable.
- Hints. "Is this a pricing problem?" is fishing. It shows you have no hypothesis, and an interviewer will often just say "what do you think?"
- Things the prompt already said. This reads as not listening. Restate instead.
- Questions with obvious answers. "Does the client want to make money?" costs ten seconds of credibility.
- Rapid-fire lists. Ten questions in a row tell the interviewer you are hoping one will hit.
- Data requests that belong after the structure. Ask for numbers once you know which numbers you need.
Sometimes the interviewer will answer a question with "what do you think?" or "assume whatever is reasonable." That is not a trap. State your assumption in a sentence, write it down, and keep going. If it turns out to matter, flag it again when you reach the recommendation.
Which clarifiers matter by case type
The entries below are the two or three that usually earn their place. They are starting points, not scripts. The same test applies: ask them only if the answer would change what you do.
| Case type | Clarifiers that usually matter | Example question, likely answer, and what it changes |
|---|---|---|
| Profitability | Which profit measure and what target; over what period; whole company or a subset | "Is the fall in margin, absolute profit, or both?" Likely answer: margin fell but profit dollars did not. Effect: you start from unit economics and mix, not volume. |
| Market entry | What the client wants from entry; whether the mode (build, buy, partner) is open; the geography and market definition | "Is the client entering to grow revenue or to defend an existing business?" Likely answer: to defend. Effect: competitor response and defensive value become branches, not just market size. |
| Pricing | Objective (profit, share or volume); new or existing product; whether price can vary by segment | "Is this a new product or an existing one?" Likely answer: existing, sold to current customers. Effect: volume response and customer reaction join your structure. |
| Cost reduction | Size and timing of the target; which costs are in scope; areas the client will not touch | "Is there a target and a deadline?" Likely answer: a fixed target within a year. Effect: quick wins weigh more than structural change. |
| M&A or investment | The strategic reason; the financial test (such as a return threshold); whether a target is already chosen | "Has the client already chosen a target?" Likely answer: yes, one. Effect: you evaluate that deal instead of building a list of candidates. |
| Market sizing | What exactly to size (units or revenue); the geography and time basis; how precise the answer must be | "Do you want annual revenue or number of units?" Likely answer: annual revenue. Effect: your build needs a price per unit. |
Pricing and cost-reduction prompts reward the same habit of fixing the objective first; see our posts on pricing questions and cost-reduction cases.
When to stop
Stop when all of these are true:
- You can state the objective in one sentence.
- The scope is bounded: you know what is in and what is out.
- Any definition that could trip you later is fixed.
- The next question you are about to ask would not change your structure.
In practice that is typically two to four short questions in a minute to a minute and a half, and one or two when the prompt is tightly specified. Then make the transition explicit: "Thanks, that is helpful. So the objective is X, we are looking at Y, and I should assume Z. Could I take a minute to organize my thoughts?" Restating the agreed frame protects you from drifting, and asking for the minute is what a consultant would do.
How to practice
Take ten case prompts from any source. For each, write down the three clarifiers you would ask and, next to each, the change to your structure that each possible answer would cause. Delete any question for which you cannot write a change. Then practice live: a partner reads the prompt and holds the full details, and you get ninety seconds to ask. Record it and listen for filler and compound questions.
Frequently asked questions
How many clarifying questions should I ask?
Typically two to four short questions; one or two is enough when the prompt is tightly specified. The number matters less than whether each answer would change your structure.
Is it ever fine to ask nothing?
Rarely. Even a fully specified prompt benefits from a one-sentence restatement of the objective, which is a form of clarification and takes about ten seconds.
Can I ask clarifying questions later in the case?
Yes. New exhibits and new information raise new questions, so keep them targeted and say what you are trying to find out.
Do I need to write down the answers?
Yes. Note the objective, the scope and any assumption you stated aloud. You will use them to check your structure and to frame your recommendation.
Anatomy of a Profitability Case: A Full Walkthrough
See the clarifying phase in context: a complete case worked from prompt to recommendation, with the moves an interviewer would grade.
One short, useful email per week.
New case frameworks, mock interview tactics, and recruiting intel from the CaseGrade team. Built for serious candidates — no fluff, no upsell every paragraph.
Unsubscribe anytime. We never share your address.
Keep reading
All articles →The Week Before Your First-Round Interviews: A 7-Day Checklist
The last week before a first round is for consolidating, not cramming. A day-by-day plan covering your final mock, logistics, firm refresh, interview-day routine and the notes to take afterwards.
Delivering a 90-Second Fit Story Out Loud
A story that reads well can still fall apart when you say it. Here is a five-beat structure with a word budget, a fully worked example, and the drills that turn a good story into a clean ninety-second answer.
Asking for a Consulting Referral (and What to Do If You Already Have One)
A referral is a favor from someone who puts a little of their reputation behind you. Here is when to ask, how to make the request easy to forward, two short email templates, and what to do if you already have one.