I'm a consulting noob whose just starting to get serious about studying for case interviews. In order to get a good foundation, I've memorized pretty much all of the CIP frameworks along with Victor Cheng's Business Situation framework.
I figured I would use Cheng's Business Situation framework as a back up when I couldn't really put my finger on what type of case it is, but I'm often confused which aspect to start with out of the 3C's and 1P. (Customer, Product, Competition, Company)
I know a lot of people say that you should look at cases and come up with your own frameworks and such, but frankly I'm just having a really hard time doing so. As a result, I have a really difficult time solving cases that deviate (even slightly sometimes) from the frameworks I've studied.
Any suggestions? Any help would be greatly appreciated. Thanks.
maybe you should consider another vocation then? sorry if i'm being rude but if you can't do controlled case interviews then real world cases will be impossible.
the alternative is to learn every singly type of case. not as hard as you would think. this is a start.
http://www.scribd.com/doc/84373865/Kellogg-2011-Cases
[quote=darety]the alternative is to learn every singly type of case. not as hard as you would think. this is a start.
http://www.scribd.com/doc/84373865/Kellogg-2011-Cases[/quote]
For the love of God, don't do this.
Think about structuring your thinking.
Look at the first part as is it top line growth or bottom line growth which is the issue. Then just figure out their current situation, where they want to go (or where they should be going) and how to get there.
Address Internal Issues: People-Processes-Systems Address External Issues: Customers/Market, Competition
Provide 3 options, 1 is status quo, 1 is "full service" and 1 is "partial solution"
Look up on systems thinking and learn as much as you can about basic business models and how corporations work.
What's your academic background? That may help us help you. When working with computer science candidates, the analog is a difficult software design or coding problem. For hard science majors, its the scientific method in the lab. Regardless the discipline, most analytical (as opposed to creative or purely linguistic) disciplines require such a process.
The key process is breaking down a complex problem into its constituent parts, soliciting the necessary information, and making conclusions based on data to solve the problem. However, candidates appear to find it easier when that process is put in terms of something they're familiar with.
As such, try to move away from the memorize and apply technique (what we're taught in school from day 1) to the breakdown and utilize what I know (including the case framework perspectives) approach.
When the case deviates go with the flow of the deviation. Then when you've finished analyzing that aspect go back to your framework. Everytime you take on a section (Cust. Org. Comp. Prod.) of the framework be creative and relevant in your thinking, what is important?
However, just following frameworks gets you nowhere. Interviewers don't want to watch you sniffing in every corner just because the framework tells you to. When you've come across something interesting that can be resolved quickly check the other sections and then get to a recommendation.
Or you could create hundreds of detailed frameworks, but don't forget to include pauses for breathing. They're pretty important in cracking the case.
All,
I just started myself and was wondering if any of you had any tips / advice on how I can fully master case studies. I would really appreciate any insight that any of you provide on how to study, what methods should be used to make case studying a habit, and how to do cases analytically and not just based off frame works.
I've watched Victor's 6-hr videos and read CIP. Now I'm starting to do cases on my own.
Thank you so much in advance!!
Sorry for my English.
Perspiciatis aspernatur iusto eos ut. Itaque sint porro qui provident. Vel dolores accusantium necessitatibus. Rerum quas vel quo sunt quos. Sed dolor occaecati laborum dolorum. Quisquam ut pariatur facere porro excepturi unde temporibus aperiam.
Dolorem quis necessitatibus praesentium dolor. Temporibus ut perferendis praesentium quod. Fuga et odit provident impedit consectetur.
In dicta tempora et est inventore. Voluptatem nesciunt rem nam in. Sit at nam labore magni.
Blanditiis illum officiis veritatis est omnis. Neque libero laudantium veritatis ut debitis.
See All Comments - 100% Free
WSO depends on everyone being able to pitch in when they know something. Unlock with your email and get bonus: 6 financial modeling lessons free ($199 value)
or Unlock with your social account...