The MBA Student vs. The Consultant

In a case interview, your interviewer slides an exhibit across the table—a chart showing declining market share. The average candidate immediately dives in: "I see that our market share has dropped from 25% to 20% over the last three years, with the sharpest decline in the Northeast region."

This is correct, but it’s an observation, not analysis. It's the response of a student reading a textbook. An elite candidate, a consultant-in-training, does something critically different first. They pause, look at the chart, and then at the interviewer, and begin to interrogate the data itself.

Data presented in a case is not gospel. It's a tool, and like any tool, you must inspect it before use. Taking exhibits at face value is a classic trap. Mastering the art of Data Interrogation signals a level of professional skepticism and intellectual rigor that separates top-tier candidates from the rest.

Why Interrogate? The Payoff is Asymmetric

Spending 15-20 seconds questioning the data before analyzing it has a massive ROI. You aren't being difficult; you are being diligent. This brief exchange demonstrates several partner-level qualities:

• Intellectual Rigor: You show that you don’t take information for granted and understand that all data has context and potential flaws.
• Risk Mitigation: You avoid building a brilliant recommendation on a faulty foundation, a costly mistake in the real world.
• Strategic Partnership: You immediately shift the dynamic from a Q&A test to a collaborative problem-solving session with your interviewer.
• Efficiency: A single clarifying question can reveal a misunderstanding (e.g., "market share by volume, not revenue") that prevents you from wasting five minutes on the wrong analytical path.

The 3-Step Data Interrogation Method

You don't need a lengthy cross-examination. A few targeted questions, delivered with professional curiosity, are all it takes. Structure your inquiry around three core areas.

1. Source & Scope

Before you analyze the "what," understand the "who" and "when." The origin and boundaries of the data are paramount.

• Who created this? (Internal client team? A third-party research firm? Government data?) This tells you about potential biases.
• When was it collected? (Is a 3-year-old customer survey relevant in a fast-moving tech market?)
• What is the scope? (Is this data for one geography? A single product line? Or the entire business?)

In-Case Example: "This is a very helpful chart on customer segmentation. Before I interpret it, could I quickly clarify the source of this data and if it represents our global customer base or just North America?"

2. Methodology & Definitions

The "how" is just as important as the "what." Seemingly simple terms can have complex or misleading definitions.

• How was this collected? (A customer satisfaction score from a pop-up survey is very different from one derived from transactional data on returns.)
• How are key terms defined? (What constitutes an "active user"? How is "profit" calculated—is it gross margin or EBIT?)

In-Case Example: "I see the axis is labeled 'Profitability.' To make sure I'm precise, is this reflecting gross margin per unit, or does it include operating costs like marketing and SG&A?"

3. Gaps & Biases

Top candidates think about what isn't on the page. They actively look for missing pieces and inherent biases that could skew the narrative.

• What might be missing? (The chart shows our top two competitors, but what about the fast-growing startup we discussed earlier?)
• Is there a potential bias? (This survey data on product features only includes current, loyal customers, creating a survivorship bias. What about the customers we lost?)

In-Case Example: "This breakdown of our sales channels is clear. I notice it doesn't include our new online partner channel. Is that intentional because it's still small, or is that data we might look at later?"

The Bottom Line: From Data-Reader to Data-Strategist

Don't deliver your Data Interrogation like an accusation. The goal is to be an inquisitive partner, not a skeptical opponent. Frame your questions with collaborative language: "To make sure I understand correctly..." or "Just to clarify for my own thinking..."

By briefly and respectfully questioning the data you are given, you demonstrate a core consulting mindset. You prove that you are not just an analyst capable of reading a chart, but a strategist who understands that the quality of an insight is determined by the quality of its inputs. This is how you stop acting like a candidate and start acting like a consultant.