How to read chart in consulting case interview?
This question is read-only because it has been merged with Chart and Graph Reading.
How to read charts in consulting case interviews?
I would follow 5 steps to read a chart:
- Take one minute of time to read the graph. It is always good to ask for a minute to digest the graph.
- Summarize what the graph is about. After you have analysed, present the interviewer the main elements of the graph.
- Restate the main question you have to answer. Missing this step is one of the most common mistakes done by candidates. Before moving to the analysis, you should have clear what you have to answer. The easiest way to clarify it is to repeat what you have to achieve with the graph analysis.
- Provide an analysis related to the question. After restating the objective, present to the interviewer the main insights that you can derive from the graph.
- Provide a conclusion for the graph that answers the original question and present the next steps to follow based on such conclusion. A good candidate would present the conclusion of the graph. A great candidate would do this and also present the next steps to follow to answer to the main client's request.
Hope this helps,
- first read "around the chart" then "into" it. Lots of context for the data is written around the graph.
- focus on "insights". Whenever I show a graph to someone where the profits were growing from yr1-5 and falling from yr5-7 but margins were falling much faster from yr5-7, and if they come back repeat that same info to me, they get rejected in my book. I can SEE the graph, tell me something DEEPER. For example, tell me that margins falling faster than revenue is likely because it's a fixed cost heavy biz.
- get good at narrowing down what you want to focus on in the graph. If your case is about P&L, focus on finding about profits, costs, F & Var costs, etc. Do not over-rotate on margins/profitability. Do NOT waste time trying to mentally calculate margins fell by 22.67% in year 2-4 -- it may impress the interviewer but not at the cost of you actually telling her something that takes the case fwd!
You can use the following approach:
- 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 of 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
Sources to learn from (prioritized):
- Study "Say it with Charts" book by Barbara Minto
- Learn basic statistics (Any GMAT or MBA prep guides)
- Check all available MBB presentations and publications. Practice to derive conclusions and check yourself with the actual ones from the article / presentation
- GMAT IR part (Official guide and Manhattan prep)
- "Consulting Bible" and "Vault guide for consulting" - check the chapters on cases with graphs in these books
I assume you are referring to chart reading in general and not to any specific types of charts.
In general, your interviewer may ask you to read a chart and interpret it in a consulting interview. These may be all types of charts, hence you should be familiar with the basics of chart reading. The key here is always to
- describe what you see: think aloud while trying to understand the chart. Thereby your interviewer will be able to follow your thought process
- contextualize the chart: put the chart into the overall case context - what was the main question? How does the chart fit it? Does it change any of your assumptions?
- interpret: interpret what you see and how it fits with the context. What implications may this have to the overall case? It makes sense to state some initial hypotheses. If there are numbers on the chart, use these numbers to quantify your hypotheses and to show your interviewer that you already think one step ahead.
There is a good tutorial on preplounge that explains the steps I just explained in more detail.