Clarifying Questions: The First Ninety Seconds of a Case

After the prompt, you're expected to play back your understanding and ask a small number of questions before structuring. This window exists because real engagements begin the same way: the stated problem is rarely the precise problem, and scoping errors compound silently.

The window is short—two or three questions, ninety seconds. It is not for gathering data, testing hypotheses, or delaying the framework. It's for making sure the structure you're about to build points at the right target.

The highest-value clarification is almost always the objective: 'When you say the client wants to improve profitability—is there a target, and by when?' The difference between 'stop the decline this year' and 'double margin in five years' produces entirely different trees.

Also surface hidden objectives. Owners may care about sale value, family control, or headcount protection as much as profit. One question—'beyond the financial goal, are there constraints or other objectives I should respect?'—covers it.

Confirm the boundaries: which geography, which business unit, which time frame? And pin any word in the prompt that could mean two things. 'Declining sales'—units or revenue? 'The European market'—EU, or the continent? Interviewers plant these ambiguities deliberately.

A scope question can also reveal the case's shape early. Asking 'is the decline company-wide or concentrated somewhere?' sometimes earns a data point that focuses your entire structure—a legitimate, encouraged move.

If the client's industry is unfamiliar, one honest question—'how does this business primarily make money?'—beats pretending. A candidate who confirms that an airline earns disproportionately from loyalty programs, or that a razor company lives on blades, structures better than one bluffing on assumptions.

Keep it to one question. The interview tests structured thinking on imperfect information, not industry knowledge; asking for a briefing signals discomfort with exactly the ambiguity consulting is made of.

Delivery matters. Bundle the playback and the questions into one fluid moment: 'So we're helping a mid-size brewer reverse a two-year profit decline—before I structure, three quick things: is there a target and timeline, is the decline concentrated in any region, and do they own distribution?' Then stop talking and write down the answers.

The anti-pattern is fishing: vague questions ('can you tell me more about the company?') that outsource thinking to the interviewer. Every question should have a reason you could state—if asked 'why do you want to know?', the answer should be ready.

Sometimes the interviewer deflects: 'good question—assume what you think is reasonable.' This is an invitation to demonstrate judgment. State your assumption, give a one-line justification, and flag that you'd validate it: 'I'll assume the target is restoring the historical eight percent margin within two years.'

Deflections are also information: the interviewer is telling you that dimension isn't where the case lives. Note it, assume sensibly, and move your attention elsewhere.