Hello all,
So, recently I realised that I like to always first write the key questions in my case structure and then divide the structure into the key buckets in order to first give a very high-level picture of what we are trying to achieve. I wanted to know your reactions to this kind of approach.
Eg: Let's say we have to see why a newly launched product has failed to deliver the expected sales and recommend what can be done about it. So, this is how I would go about the structure:
1. What are we selling? - Company - Product/ Price - Revenues- Distribution (related deep-dive questions)
2. How does it fit with the market? - Market attractiveness, Customers, Competition (related deep-dive questions while drawing a comparison)
>>> Deriving a conclusion on the basis of fit mis-match!
3. How can we improve sales? - Comparison of operational capabilities with that of competitors/ market/ customer expectations and solution building
4. Conclusion/ Recommendation
Any suggestions are more than welcome!
Thank you.
That‘s awesome, personally I share absolutely the same opinion! How do several candidates get into MBB with such approaches though (like „first I‘m gonna look at a, then at b etc“)? (Personally I know a classmate who passed McK 1st round this way, and even got a few prep sessions from actual McK consultants...) Is the logic you explain indeed what all interviewers are looking for (and with other mindsets there is no chance to pass the interview)?
(edited)
Mit tip: stop asking yourself what an interviewer might be looking for! What he/she IS definitely looking for is the rigor in your thinking. And this is demonstrated by setting up a clear criterion-based logic to answer the precise question at hand, and not by defining whatever buckets. People have been brainwashed into this thinking since the canonical casebooks packed with frameworks were published 10 or 15 years ago. But it's a very flawed (and very junior) way of thinking and places the candidate at an enormous risk, since you will always need luck to solve a case, let alone perform well during the process.
(edited)