Expert with best answer


97% Recommendation Rate

364 Meetings

5,232 Q&A Upvotes

USD 229 / Coaching

Question merged

This question is read-only because it has been merged with How many clarifying questions are appropriate and when should they be asked?.

When to ask which questions: Which questions do you ask before you come up with a structure and which do you ask after?

Marilena asked on Mar 06, 2017 - 3 answers
Looking for partner to practice.

After a few mock cases, I found that I have difficulties deciding which questions to ask before I come up with a structure and which questions to ask after I come up with a structure.

I keep wanting to ask all the questions I have as soon as I hear the explanation of a case, but then I find myself already starting with the analysis by asking relatively specific questions.

Is there a rule for this?


3 answers

  • Upvotes
  • Date ascending
  • Date descending
Best Answer
replied on Mar 07, 2017
McKinsey / Accenture / Got all BIG3 offers / More than 300 real MBB cases / Harvard Business School
Book a coaching with Vlad

97% Recommendation Rate

364 Meetings

5,232 Q&A Upvotes

USD 229 / Coaching

Pre-structure questions

1) Clarify the business model. Even if you think you understand it, try to repeat it to make sure that you understand in correctly.

2) Clarify the objective. Here make sure that your goal is:

  • Measurable
  • Has a time-framed
  • Has / has no limitations

e.g. Should I invest 100k in this business for 1 year if I want to get 15% return?

3) Ask the questions that will help you build a relevant structure and remove ambiguity.

e.g. if the case is about oil&gas company which revenues are decling, ask if it is Up / mid / down-stream problem. In this case defining a revenue stream is critical to seting up the right structure.

Post-structure questions:

It's kind of hard to generalize all the cases. I will try to provide a general algorythm here:

  1. Ask for a piece of data / info you've defined in a structure
  2. Compare the data with historical trend / becnhmarks
  3. If you find something interesting ask for the root / cause or state the hypothesis
  4. If no root/cause at this point available - ask for segmentation to drill down further
  5. Once you are done with analysis in one branch of your framework (found the root-cause / found nothing interesting) - summarize what you've learnt so far and move to the next one

Again, the last one is super high-level and the devil is in details:)

replied on Mar 06, 2017
Former BCG consultant and teacher/adult trainer with experience in US, India, and Middle East
Book a coaching with Srihari

100% Recommendation Rate

20 Meetings

83 Q&A Upvotes

USD 189 / Coaching

Good news here - there is no hard and fast rule, although I'd say watch it on the time - you definitely shouldn't be asking 2 minutes of questions before you come up with your structure. Here is what you definitely need to do before the structure.

1) Replay your understanding of the situation

2) Clarify that you understand the exact objectives, ensure there aren't any others

3) (This is what I think you are asking about it) - ask any quick questions before your structure. I'd start by thinking "What would be general parts of the analysis that I would do?" And leave that to be covered in your structure and later. This would include any trend performance, number data, market/competitor/company information/performance, etc. It's hard to define everything that you would cover in your structure, so I'll move to some of the common things it would be okay to ask before the structure.

Definitions - if you simply don't understand a term or description that was given, it's okay to ask. In fact, it's best to ask early (either before or shortly after the structure). Asking later can look pretty bad, whereas asking early shows you aren't afraid to get clarification on things early and avoids the embarressment later. This is especially acceptable if it's a very technical/nuanced industry, or for example you are from a different country/industry etc and lack some basic context (for example, if you are an Indian national and don't know what exactly an American interviewer means by a "strip mall", better to clarify than assume it has something to do with stripping - you may laugh, but I've seen that go wrong in the past)

Scope of the problem/options - related to objectives, but you can clarify what exactly the focus/options for consideration are. For example, for an large MNC, you might want to clarify if adjacent markets/products/ or divesting is something the company can consider or if there are any "sacred cows" which can't be touched. Don't force this though, and only bring it up at this stage if you have some interesting potential insight or it would shape your framework. You can also address this within the structure itself and discover it through your analysis.

Major contextual scenarios/assumptions - If I were to give you a case on an oil producer, you may want to clarify the time period before assuming the structure. If we are in the post 2015 world with low oil prices, that's very different than 2013 with $100/barrel prices. You can see how the different contexts would influence your framework and where you focus your analysis. Again, don't force this, but if some elements of the context would greatly change how you approach the case, good to quickly ask. It isn't essential, but it can help shape your framework and make it more contextualized, less generic which is always a good thing.


The rule of thumb I'd give is to always stop short of getting data or analysis related to the case - if you find yourself asking for detailed information, that's too much before a framework. Think quick questions, especially with a focus on definitions you don't understand and any major scope/context questions if it would help you better frame the case.

Anonymous replied on Oct 05, 2017


You are right that there are a lot of possible fit questions. And while the fit interview may vary by firm, the fit questions sometimes are actually the same. It seems you are referring to the opening explanation of the case situation. In that scenario, you usually want to want to do the following:

  • Play back your understanding of the case, clarifying any points that you missed or didn’t understand
  • State your understanding of the objectives
  • Spend about 90 seconds gathering your thoughts and outlining your structure
  • Develop a logical, MECE structure that includes at least 2 but usually 3-4 logical buckets with 2-4 2nd level questions / thoughts

In the opening case scenario, you usually are not going to ask for more information. That will come after the first question. You should still feel free to ask for clarifying information should you see fit, but most likely the interviewer will defer.

It is also very important to understand that there is a big difference between first round interviews with Associates and Managers that “go by the book” and have recently received interview training and 2nd / 3rd round interviews with Associate Partners, Partners and Senior Partners, many of which had no formal interview training at the time when they joined the firm. This is why I encourage candidates to practice cases with a range of different people (i.e., other candidates, PrepLounge Experts that were Associates / Managers and PrepLounge Experts that were Associate Partners / Partners). You will not only experience a different interview style and receive different feedback, but it is also more cost effective for you and allows you to gain more practice experience.

Related BootCamp article(s)

Getting Up to Speed

In order to repeatedly demonstrate prerequisite skills under the pressure of a real case interview, you need to learn the basics and practice cases.