Hi,

I recommend the following approach:

1) Start with "Case in point" book - you can download this book for free everywhere. It's not the best guide on how you should approach the cases, however, it will give you the basic understanding.

2) Start practicing cases with partners here or find them locally. !!! Find experienced partners or coaches who can provide a good feedback!!!

3) Purchase and read Viktor Cheng Book (Amazon Kindle store) and listen to LOMS (his website).

4) Start with the following cases (in the order of priority, relevant for pwc) and apply some high-level recommendations on structuring:

1. Market sizing - structuring from the supply or demand side. Structuring using a formula or using an issue tree
2. Profitability - basic profitability framework. Remember about different revenue streams and product mix
3. Market context cases (Market Entry, New product, Acquisition, etc). Always start with the big picture "market". Finish with something specific to the case (e.g. How to enter?"). Structure it as if you are defining the work streams for the real project.
4. Operational math problem (e.g. Should we increase the speed of an elevator or just buy a second one? How should we reduce the queues? Etc.) - Structuring as a process / value chain, with inflows, operations, and outflow

Here is a good list of articles regarding the different parts of the case:

1) Start with clarifying questions:

https://www.preplounge.com/en/consulting-forum/clarifying-questions-1786#a3956

2) Communicating while structuring. Here is a long post by me on how to communicate the structure during the case study:

https://www.preplounge.com/en/consulting-forum/how-to-communicate-its-structure-for-the-case-study-1313#a2806

3) Using hypothesis. I made a post about hypothesis here:

https://www.preplounge.com/en/consulting-forum/how-to-state-a-hypothesis-and-match-to-the-structure-1156#a2268

4) Communicating while making calculations:

• Always tell the interviewer your approach
• Check with the interviewer that your approach is correct
• Come to the interviewer with some preliminary answers
• Check your assumptions with the interviewer

5) Communicating during the analysis of graphs / tables

• Take a minute to look at the graph. Read the graph title. Look at the graph type and define the type (pie chart, line chart, etc). Look at the legend (ask for clarifying questions if necessary). Identify whats going on on the graph. Look for: Trends, % structures. Look for unusual things - correlations, outliers,
• Make 3-4 conclusions from the graph. Think out loud on potential hypothesis on what could be the root cause / what are the consequences
• Prioritize the most important for your current analysis and move forward with the case

6) Communicating while having questions on creativity

• Ask an interview for a minute to think
• Think of several buckets of ideas (e.g. organic growth / non-organic growth / differentiation). Remember to think as big as possible
• Narrow down to each bucket and generate as many ideas as possible
• Present the structure (buckets) and then your ideas

7) Communicating your conclusion. You can find a good example I've posted here:

https://www.preplounge.com/en/consulting-forum/how-much-answer-first-should-the-conclusion-be-1231#a2493

8) Communicating your FIT stories

Use the top-down approach while communicating your stories. "The Pyramid Principle" is the must-read by ex McKinsey on this topic.

I recommend using the STAR framework:

• In Situation, you should briefly provide the context, usually in 1 or 2 sentences
• Task usually includes 2 or 3 sentences describing the problem and your objective.
• Then you provide a list of specific actions you took to achieve the goal. It should take 1 or 2 sentences per action (Usually 3-4 actions). Note that the interviewer can stop you any minute and ask for more details.
• The results part should have 1 or 2 sentences describing the outcomes. This part is finalizing your story - make sure it can impress the interviewer and stay in the memory.

Best!