Sometimes when I ask a clarifying question in a mock interview, I would get him by the interviewer with
"We'll come to that later"
"There's an exhibit for that later"
"It's too early for this"
If there's any rule of thumb to use here for clarifying questions, I would really appreciate it.
Hi there,
Great question — this is a subtle but important skill.
A simple rule of thumb is:
A good clarifying question should change how you structure or approach the case.
If it doesn’t affect your structure, it’s probably too detailed or too early.
Here’s how to think about it.
They are meant to clarify:
These are “high-level alignment” questions.
They are not for:
If the information is something you would analyze after presenting your structure, it’s probably too early to ask.
That’s when interviewers say:
Before you ask, quickly ask yourself:
If it’s about solving — wait.
Good clarifying question: “Are we focusing on one country or globally?”
Too early: “What’s the breakdown of costs by supplier?”
The first defines scope. The second belongs in analysis.
You don’t need many clarifying questions. In most cases, 1–2 sharp ones are enough. After that, move confidently into your structure.
If you’re getting “too early” feedback often, it likely means you’re jumping into diagnosis before laying out your approach.
Happy to help you practice a few examples if useful.
Best,
Evelina
Great question — this is something many candidates struggle with.
A good rule of thumb: a clarifying question should help you define the problem, not solve it prematurely.
If you hear things like:
…it usually means the question was moving into analysis mode, not clarification mode.
Here’s a simple distinction:
Good clarifying questions
Too-early questions
Another practical test:
If your question would change how you structure the case, it’s likely a valid clarifying question.
If it’s just curiosity about data, it’s probably too early.
Strong candidates clarify the playing field first — then move into structured analysis.
Hi! A clarifying question is only strong if it’s necessary for you to build the logic of the case.
If it doesn’t change how you structure your approach, it’s probably premature.
That’s the core filter.
Most candidates ask clarifying questions because they feel they’re “supposed to ask some.” But that’s the wrong mindset. You’re not trying to show activity, you’re trying to ensure you can build a rigorous decision logic.
Here’s where things usually go wrong.
For example, early in a market entry case, people ask about competitors, growth rates, margins, etc.
But at that point, you haven’t even defined:
So from the interviewer’s perspective, you’re jumping ahead.
Clarifying questions are not there to gather data. They’re there to make sure your structure is valid.
Suppose you’re about to structure a “Should we do X?” case.
You can already define:
None of that requires knowing specific numbers yet.
If your question doesn’t affect one of those elements, it’s probably not needed at that stage.
A good self-check is:
If the interviewer answered this question, would my structure change?
If not, it’s not a clarifying question, it’s curiosity.
In diagnostic cases especially, candidates often jump to broader explanations before isolating the numerical driver.
But until you know where the issue sits in the driver tree, most high-level questions are noise.
Strong process discipline means:
If you skip step 3, you’ll feel slightly out of sync with the interviewer.
So what are strong clarifying questions?
They typically fall into three categories:
A) The objective isn’t operationalized.
If the goal is something vague (e.g., market share, quality, productivity), you need to clarify how it’s defined. Otherwise you can’t build a driver tree.
B) The success criterion is unclear.
If you can’t define what “good” looks like, you can’t define your decision rule.
C) The business model isn’t clear.
If you don’t understand how the company makes money, you can’t break down profit or revenue correctly.
Notice the pattern:
All of these affect your logic. None of them are about gathering data for analysis.
A simple rule of thumb
Before asking anything, run this quick test:
If the answer is no to all three, wait.
Once you start thinking this way, you’ll notice two things:
And interviewers react very differently to that.
They’re not looking for someone who collects information.
They’re looking for someone who can build a clean logic before touching data.
I hope this helps! :)
Sidi
____________________
Dr. Sidi S. Koné
Hello,
This is a very common issue — and it usually means the question is analytical, not truly clarifying.
Rule of thumb:
A good clarifying question helps you understand the objective, scope, or constraints — not solve the case prematurely.
Good clarifying questions:
Questions that trigger “we’ll come to that later”:
Simple test:
If your question changes how you would structure the case → good clarifying question.
If it just satisfies curiosity or jumps ahead → too early.
Sequence to follow:
Most candidates rush into analysis instead of first building a clean problem definition.
As a coach, I’m here to help you — we can refine your case-opening discipline, sharpen your instincts on timing, and make sure your clarifying questions consistently add value instead of slowing you down.
That experience is incredibly confusing and common. When an interviewer shuts down a clarifying question, it rarely means the topic itself is irrelevant; it means the question was out of sequence according to their internal structure.
The essential rule of thumb is to distinguish between scoping questions and data-seeking questions. Your initial clarifying questions, asked immediately after the prompt, must exclusively focus on defining the problem and setting the boundaries of the engagement.
A good clarifying question addresses a core ambiguity in the prompt: What is the exact definition of "profit" we are optimizing? What geography are we focusing on? What is the client's non-negotiable constraint? These questions help you build a relevant framework.
A bad (i.e., premature) clarifying question asks for a specific piece of information or an operational detail that would naturally be contained in a future exhibit. If you ask, "What are the competitors charging?" or "What percentage of costs are fixed?" you are asking the interviewer to pull data that they intended to release later to test your framework or prioritization skills. The logic here is simple: If your question requires the client to conduct analysis or pull up a spreadsheet, save it for when you are actively testing a hypothesis within your framework.
Focus only on defining the goal, the constraints, and the ambiguous terminology. If it sharpens your framework, ask it. If it asks for an input number, it's too early.
All the best!
Clarifying questions are meant to make sure you understand the problem before you start solving it. They are not meant to gather all the data you will need for the case. That is the key distinction most people miss.
Questions that work
Questions about the objective. What does success look like? Are we trying to increase profits, revenue, market share? This is almost always a good question to ask upfront.
Questions about scope. Are we looking at one geography or global? One product line or the whole business? What time horizon are we working with?
Questions about definitions. If the interviewer uses a term you are not sure about, ask. "When you say 'premium segment,' how are you defining that?"
Questions about context that changes how you structure. Is this a turnaround situation or a growth situation? Is the company profitable today?
Questions that get shut down
Asking for data you should be working to figure out. "What are the profit margins by segment?" You will likely get that in an exhibit or need to calculate it yourself.
Asking for the answer disguised as a question. "Is the problem on the cost side or revenue side?" That is what you are supposed to figure out.
Going too deep too early. "What is the customer churn rate in the northeast region?" That is way too specific before you have even structured the problem.
A simple rule of thumb
Ask yourself, do I need this to understand the problem or do I need this to solve the problem? If it is the first, ask. If it is the second, hold it and work toward finding it through your structure.
Two or three clarifying questions at the start is usually enough. Then move into your structure. You can always ask more targeted questions as you work through the case.
Feel free to reach out if you want to practice this.
Let's take a step back and look at what is the point of a clarifying question.
Basically, you shouldn't ask clarifying questions by default. You should ask because there's something you genuinely want to clarify (e.g., you didn't hear something right, you want the interviewer to repeat a particular part of the prompt) OR you want to probe something (e.g., you have a sense of where the case might be going and ask a leading question to see if there's potential there).
So if you ask questions that are aiming for the above, it's perfectly fine.
When the interviewer says you'll come to that later, it means you've likely already touched on something that is relevant.
If you have any follow-up questions, don't hesitate to reach out directly.
Best,
Cristian
hey there :)
A good rule of thumb from my side is that a clarifying question should help you understand the objective, the definition of success, or the context before you structure. If your question is about detailed data, numbers, or specific drivers, it is often something that will come later in exhibits.
Before asking yourself if this changes my initial structure or just fills in a detail. If it changes the direction, ask it. If it is just curiosity or early analysis, park it and move on.
If you want, share an example and I can give you concrete feedback.
best,
Alessa :)
Hi there,
Clarifying questions should be around the objective, timeline, potential constraints, and on your understanding of the scope of their business. This understanding should help you frame your structure, not already eliminate some branches.
