Structuring a case interview - Order of data gathering and structure

There are a few things you will want to understand before developing a framework:

(1) Make sure you really understand the problem. Often, this comes down to understanding the business model, at least roughly, but this is not always true (operations cases are a common exception).

(2) Often, the goal will be stated only roughly and I recommend trying to quantify it. For example, you will want to know by how much they need to cut costs, or by how much they want to grow revenue.

(3) Ask for the time frame, as it will influence which recommendations make sense.

Most cases have a common logic behind them - which is why set frameworks such as those by Consentino work (to a certain point, at least). With experience, you will eventually also pick up on things that seem out of the ordinary and will then make a habit of asking for those. It's like a gut feeling which, for me, really happened after around 30 cases and now lets me postulate more concise frameworks.

(edited)

Send it :)

Hello Markus,

After restating the problem, I always suggest to ask every information you need to clarify the case and be sure that you get the core of the problem (e.g. technical terms you are not sure about).
As soon as you have a clear view of the problem you can write down a structure, present it to your interviewer and start asking for information you need. Basing on these information you can then decide which part of the issue tree you want to drill down.

Regarding the CV: feel free to sent it to me ;)

Best,
Luca