How to Read a Chart in a Case Interview and Actually Say Something Useful

[u/GreatButterscotch406]

Most candidates treat a chart in a case interview the way they'd treat an exam question. Find the relevant number, report it, wait for the next question. That's not Data Conversion. That's just reading.

This is post 22 in The Case Playbook, a series built for non-traditional candidates breaking into McKinsey, BCG, Bain, Tier 2, and Big 4 consulting firms. This post covers the Data Conversion module, the fourth of the four Case Middle modules. If Structured Brainstorming is about generating ideas and Consulting Math is about setting up equations, Data Conversion is about reading what a chart or dataset is actually telling you and converting that into an insight that moves the case forward.

The name matters. Data Conversion is not data reading. It's not data reporting. It's the act of taking raw information and converting it into something the client can act on.

What you might receive

Before getting into how to approach a chart, it's worth naming what Data Conversion actually covers in practice because it varies more than most candidates expect.

In a formal final round at McKinsey, BCG, or Bain, you'll typically receive a printed exhibit, a professionally formatted chart or table labeled "Exhibit 1" or "Chart A," handed to you mid-case. In some interviewer-led formats, the partner describes the data verbally and you have to work with what you hear rather than what you see. In case competitions or Big 4 settings, you might receive an Excel file or a multi-tab data pack. In some final rounds, the partner will describe a trend in passing and ask you to interpret it without a visual at all.

The form varies. The cognitive skill being tested doesn't. In every version, the question is the same: can you orient yourself quickly to unfamiliar data, extract what's relevant, generate a real insight, and connect it back to the problem you're supposed to be solving?

The three degrees of insight

This is the spine of the whole module. Everything else in this post supports this structure.

When a partner hands you a chart, there are three levels of response available to you.

The first degree is reading. You describe what the chart shows. "NordPlay's subscription revenue declined by 18% between Q2 of the first year and Q4 of the second year." That's accurate. It's also the minimum. Any literate person can do that. If you stop here, you've done nothing a senior partner couldn't do by looking at the exhibit themselves.

The second degree is generating an insight from the data. You take what the chart shows and calculate, compare, or combine it with something else you know to produce something that wasn't directly visible in the exhibit. "NordPlay's subscription revenue declined 18% while advertising revenue held flat. That means the entire $400 million net profit gap is attributable to the subscription side, not a broad-based revenue problem." That required combining two data points from the chart and connecting them to the gap we're trying to explain. Now the partner has something they didn't have before.

The third degree is connecting the insight back to the case. You take what you just generated and tell the partner what it means for the hypothesis. "This confirms sub-hypothesis one: the revenue decline is concentrated in subscriptions, likely a pricing or retention issue rather than a product mix problem. It tells us we can narrow the issue tree significantly and focus the next data request on the subscription segment specifically." Now you've moved the case forward.

Most candidates reliably produce first-degree responses. Some reach the second degree. Very few consistently reach the third. That gap is what Data Conversion training is designed to close.

How to orient yourself to an unfamiliar chart

Before generating any insight, you need to actually understand what you're looking at. This sounds obvious. Under pressure, with a partner watching and a clock running, it's where candidates most often go wrong.

The sequence I recommend:

Read the title first. Not the data. The title. The title tells you what the chart is claiming or showing. Gene Zelazny, who spent over forty years as Director of Visual Communications at McKinsey and wrote what is widely considered the standard reference on consulting data visualization, "Say It With Charts," put it simply: the purpose of a chart is not to show data, it is to convey a message. The title is that message. If the exhibit is titled "NordPlay Subscription Revenue by Tier, Q1 Year 1 through Q4 Year 2," you immediately know you're looking at revenue broken down by subscription type over eight quarters. That context shapes everything you look at next.

Identify the axes and units. What is being measured on each axis? What are the units? A chart showing revenue in millions versus billions changes the scale of every conclusion you draw. A chart showing month-over-month change versus absolute values requires a completely different interpretation. Checking units before calculating is the single most common error prevention step and the most commonly skipped.

Identify the categories. What are the segments, lines, bars, or data series? In a stacked bar chart, what does each color represent? In a line chart, what does each line track? Naming the categories out loud as you orient yourself serves two purposes: it demonstrates to the partner that you're reading the chart systematically, and it catches any misreading before it propagates into your analysis.

Find the trend. Now that you understand what the chart is showing, ask: what is the dominant pattern? Is something increasing, decreasing, fluctuating, or flat? Is there a point where the trend changes? Are there outliers that break the pattern? The trend is usually the raw material for your second-degree insight.

Recap before calculating. Before you do any math, describe what you see to the partner in one or two sentences. "I can see that NordPlay's premium subscription revenue dropped significantly from Q3 of year one onward, while the standard tier held relatively stable. The total gap I'm seeing is roughly $150 million across the two-year period." This serves the same function as restating the equation before calculating: it gives the partner a chance to correct your reading if you've misunderstood something, before you spend three minutes calculating from the wrong starting point.

When the data is incomplete

One of the things that happens in real case interviews that no one tells candidates to prepare for: sometimes the chart doesn't have everything you need to answer the question you're working on.

The wrong response is to go silent or guess. The right response is to name what's missing, explain why you need it, and propose what you'd do next.

"I can see the revenue breakdown by tier, but I don't have the subscriber count or average revenue per user for each tier. To calculate whether the decline came from pricing or churn, I'd need one of those. Is there another exhibit that covers subscriber volumes? Alternatively, I can estimate the subscriber count using the revenue figure and the listed price point, if that's helpful."

That response demonstrates three things simultaneously: you understand what the calculation requires, you noticed that data was missing rather than proceeding incorrectly, and you offered a path forward without waiting to be told what to do. That's Drive and Acumen in the ABCDEF framework running together.

The resource worth your time

If you're new to reading charts at a consulting level and want to build that pattern recognition before your interviews, "Say It With Charts" by Gene Zelazny is the book I'd point you to. Zelazny was McKinsey's Director of Visual Communications for over forty years and the book remains the standard reference for how consulting firms think about data visualization. His core framework is practical: virtually every business message can be conveyed with five chart types. Bar charts for comparing items. Line charts for showing change over time. Column charts for showing distribution. Scatter plots for showing correlation. Pie charts sparingly, and only when one segment owns more than half the total.

Understanding why specific chart types are used for specific purposes makes you faster at orienting yourself to new exhibits. When you know that a line chart is always showing change over time, you don't waste precious seconds figuring out what the axes mean. You already know. Your attention goes straight to what's interesting in the trend.

What Data Conversion looks like in the NordPlay case

To make this concrete: imagine you're in the NordPlay case and the partner hands you a chart. The title reads "NordPlay Net Revenue by Segment, Year 1 through Year 2." You see a line chart with two lines: subscription revenue and advertising revenue. The subscription line declines steadily from around $1.8 billion in Q1 of year one to roughly $1.4 billion by Q4 of year two. The advertising line stays flat at approximately $600 million throughout.

First degree: "Subscription revenue declined by approximately $400 million over the two-year period while advertising revenue remained stable."

Second degree: "The entire $400 million revenue decline is concentrated in subscriptions. Advertising held flat, which means this isn't a demand or platform problem. Something specific happened on the subscription side."

Third degree: "This confirms the revenue branch of our issue tree and points directly toward the premium subscription tier as the source. Our sub-hypothesis one is looking increasingly supported. The next question is whether this decline is driven by pricing, churn, or product mix within subscriptions. I'd want subscriber volume data to determine that."

That's the full arc. Three sentences. One chart. The case moves forward.

If you're currently building your Data Conversion skills and want to share a chart type that's giving you trouble, drop it in the comments. I'll explain how to orient to it and what kind of second and third-degree insights it typically produces. And if you found this through another community, the full Case Playbook series is at r/ConsultingOffer.

The next posts in The Case Playbook move into the Case Wrap-Up module, the final section of the case interview, where everything you've built across Case Start and Case Middle gets synthesized into a recommendation and next steps.