Werde aktiv in unserer Community aus über 451.000 Gleichgesinnten!

Verabrede dich zum Casen über das Meeting-Board, nimm an Diskussionen in unserem Consulting Q&A teil und finde gleichgesinnte Case-Partner, um dich auszutauschen und gemeinsam zu üben!

What does it mean to "Lay down a case structure" at the early stage of a case?

Case Interview
Letzte Aktivität am 16. Dez. 2018
3 Antworten
2,0 T. Views
Anonym A fragte am 14. Dez. 2018

In many consulting case guides it is suggested to take some time at the beginning of the case to "lay down a structure". Could you please make some practical examples?

Furthermore, I would like to know your thoughts about creating a structure at the beginning of the case vs not taking time at the beginning but structuring the analysis during the case resolution

Übersicht der Antworten

Upvotes
  • Upvotes
  • Datum aufsteigend
  • Datum absteigend
Beste Antwort
Sidi
Experte
antwortete am 15. Dez. 2018
McKinsey Senior EM & BCG Consultant | Interviewer at McK & BCG for 7 years | Coached 350+ candidates secure MBB offers

Hi Anonymous,

structure is an absolutely crucial element towards success in a case interview. However, I want to emphasize one BIG misconception that I unfortunately see with many many candidates:

Structure DOES NOT equal frameworks!

The different frameworks that you can find in pertinent case literature provide a very good basic toolbox in terms of which areas to look into for certain types of problems. However, they are very poor regarding HOW TO APPROACH a case and HOW TO DRAFT A ROADMAP for solving the case. This approach and roadmap needs to be rooted in rigorous and specific logic. Unfortunately the "framework learning philosophy" brought forward by, e.g., Case in Point, is the very reason why an overwhelming majority of candidates will not get an offer.

Moreover, there is a further fundamental misconception among many folks trying to build their case solving muscle: assuming that there is an essential difference between what is often called "Profitability Cases" and, for example, "Market entry", "Company acquisition", "Product launch", etc. But the truth is: at the core, there is absolutely no difference between these questions! The core of the issue is absolutely identical:

Can the client create value or not?

Hence, juggling around with different frameworks, trying to map and match them to these questions is just demonstrating this fundamental non-understanding of the candidate. I will say it again and again: cases should be approached and solved from first principles!

  • One of these first principles is that you start EVERY case from the core question that you need to answer! This core question is the starting point of a rigorous logic tree, and each element that you want to analyze needs to clearly relate back to the core question! This principle forms the basis of any structure.
  • Another first principle is, e.g, to define the criterion or criteria that need to be met in order to anwer this core question in one way or another.

The big advantage is that this is making "frameworks" unneccessary for the structuring of cases! You need to learn and internalize the logic, then you have a bullet-proof toolbox under your belt, far more rigorous then a "framework-learning" approach.

Just one example below which I described in an earlier post. This is about capacity expansion and vertical integration. Please think it through - I hope you will realize that the same logic, centered around value creation, can be applied to virtually ANY situation in which a client wants to assess a strategic option (entering new market, launching new product, m&a considerations, etc.). It also works indepent of whether Profit is the primary objective or not. As long as the objective(s) is/are clear, the criterion to answer the core questions can be adapted accordingly.

EXAMPLE:

Question:

Our client is a large producer of PET. PET is a type of plastic that is used mainly for producing bottles, such as the ones you find in grocery stores. The main component of PET is PTA. Our client has a PET plant in the US and serves clients both in the US and Europe. They have made the decision to build a PET plant in Europe to be closer to the clients. They have asked you to evaluate whether they should also backward integrate and purchase a PTA plant and locate both plants next to each other.

Approach:

This is a strategic investment decision. A very clear approach would be:

1. Core Question: "Should the client invest into purchasing a PTA plant next to the new PET plant in Europe?"

2. Identify criterion to make this decision: The additional value we can create over the client's investment horizon has to be significantly higher than the investment cost. Moreover, the risks need to be manageable.

3. Compile base information: Purchasing Price of PTA plant / yearly operating cost of PTA plant if purchased / capacity of PTA plant vs. PTA need / investment horizon of client

4. Deep dive into the value bucket by means of a profitability tree: what are the levers of value here? Compare Scenario A (PTA plant in Europe) to Scenario B (no PTA plant in Europe). Probably the value lever lies on the cost side: how much savings potential due to decreased/eliminated transport costs? How much savings due to eliminated import tariffs? etc.

5. Calculate annual value (delta between Scenario A and B). If a PTA plant in Europe indeed increases annual profits by a certain amount, you then divide the purchasing price of the PTA plant by this additional yearly profit. This gives you the break even point (point in time after which the investment becomes profitable). If this point comes earlier than the investment horizon, then this is a beneficial investment and the client should proceed with the purchase (purely based on financials).

6. Don't forget to compile potential risks and mention them in your summary

Cheers, Sidi

P.S.: A rare exeption are pure operations cases, where I usually recommend a different approach. Just as operations projects in real life at MBB firms need to be approached and conducted differently from strategic projects.

War diese Antwort hilfreich?
Anonym antwortete am 16. Dez. 2018

Hey there,

I would suggest you read Victor Cheng's "Case interview secrets" for the basics of how to structure at the start of a case. He will go into more detail than experts can here, and you can come back here once you've read it if you have any additional or specific questions.

I also have a version of the book that I summarised into easy to use and digest notes. Send me a PM and I'd be happy to share!

War diese Antwort hilfreich?
4
Vlad
Experte
antwortete am 15. Dez. 2018
McKinsey / Accenture Alum / Got all BIG3 offers / Harvard Business School

Hi,

  1. You start not with the structure - you start with clarifying the objective.
  2. Laying down the case structure is an absolute must for the case. You should always do that!
  3. However, you should not stop on that! You should be continuously structuring through the case while digging deeper into the problem!

Example:

If you have a revenue growth case, you can structure it in the following way:

Analyze the market:

  • Size and growth rates
  • Segments (geographical, customer, product)
  • Distributors / Suppliers
  • Regulation
  • Key market trends

Analyze the competitors:

  • Market shares, growth rates, profits
  • Product / customer / geographical mix
  • Products (Value proposition)
  • Unit economics (Value proposition vs. price vs. costs)
  • Key capabilities (Distribution, supply, assets, knowledge, etc)

Analyze our company:

  • Market share, growth rates, profit
  • Product / customer / geographical mix
  • Products (Value proposition)
  • Unit economics (Value proposition vs. price vs. costs)
  • Key capabilities (Distribution, supply, assets, knowledge, etc)

How to increase revenues:

  • How to increase the scope: Product / customer scope, geographical scope
  • How to improve value proposition (How to fix your weaknesses and improve your strengths; Potential increase in price and volumes)
  • How to answer the competitors (Unique or hard to build property and contracts; Customers / suppliers / complements with lock-in; Reputation and relationships; Organizational capabilities; Product features and know-how)
  • Other benefits of scale (Spreading Fixed costs, Change in technology, Bragaining power)

Best!

War diese Antwort hilfreich?

Sidi

McKinsey Senior EM & BCG Consultant | Interviewer at McK & BCG for 7 years | Coached 350+ candidates secure MBB offers
429
Meetings
5.843
Q&A Upvotes
78
Awards
5,0
134 Bewertungen