Hi Anonymous,
I would recommend you to focus on 5 areas to crack a written case; I have reported them below with some suggestions on how to prepare for each of them
1. Learn how to define a plan of action and stick to that
The first thing you should do in a written case is to define a plan and allocate in the best possible way your time. Assuming 60 minutes for the analysis, a good approach would include:
You should then practice to stick to the time allocated, in order to maximize your final performance.
2. Practice graph interpretation
You will normally have to analyse graphs in a written case. The best way to practice is to take graphs from online resources and use a timer to test in how much time you can understand the key message. McKinsey PST graphs could be a good practice for that.
3. Work on quick reading and quick understanding of key information
You will not have time to read and prioritize everything, so you have to understand where to focus. The ideal way to practice is to use long cases such as HBS ones, and practice on reducing the time needed to absorb the key information that can answer a defined question. Quick reading techniques could also help.
4. Practice quick math
You will normally have math to do in a written case. GMAT and McKinsey PST math should work well to prepare on this.
5. Learn how to communicate your slides/answers (if required)
You may have to present your findings at the end of the case. I would apply the same structures of final sum up in a live interview case, that is:
As you will not be able to double check hypothesis with the interviewer as in the live case before the presentation, it could make sense to clearly state when you are making hypotheses and that you will have to verify them with further analysis.
Hope this helps,
Francesco
(edited)
I have not done a BCG-specific written case, so take everything I say with a grain of salt.
Generally for written cases where a lot of information is presented to you up-front, it is important to not let the data guide your structure. What I mean by that is you should set up your problem solving structure and hypotheses before looking at the data in detail.
There is three problems with letting the data dictate your structure:
My recommendation would be to skim the data they provide you with after reading the objective, then setting up your issue tree/hypotheses. Use the provided data only to validate/dismiss your hypotheses, make assumptions or ask the interviewer when there is no data included to validate/dismiss a specific hypothesis.
Hope this helps and good luck!