So What Test in Consulting: 5 Steps to Real Insight
Author: Taylor Warfield, Former Bain Manager and interviewer
Last Updated: September 21, 2026
The so what test in consulting is the habit of pushing every finding one step further by asking what it means for the client and what they should do about it, which is what turns a raw number into an insight worth paying for. This guide covers how the test works, the five steps to apply it, and how interviewers use it to separate strong case candidates from weak ones.
Before reading on:
Most candidates struggle to land interviews and even fewer turn them into offers. Watch my free training to learn how to triple your chances of landing interviews and increase your chances of receiving an offer by 8x.
Key Takeaways
The so what test asks one question of every finding: what does this mean, and what should the client do differently because of it?
- An observation describes what happened, while a so what explains what it means and what to do next
- Consultants run the test at three levels: the whole project, each individual analysis, and every slide
- The fastest route to a so what is to compare the number to a benchmark, then ask why until you reach a cause someone can act on
- In case interviews, every calculation, exhibit, and brainstorm needs an implication attached to it before you move on
- The most common failure is stating a number correctly and then going silent, which reads as an analyst rather than an advisor
What Is the So What Test in Consulting?
The so what test in consulting is a check you run on every finding before you share it. State what the data shows, then answer what it means for the client and what they should do differently because of it. If you cannot answer both, you have reporting rather than analysis.
The phrasing comes from how senior consultants review work. A former McKinsey consultant has written about partners flipping through client decks and asking where the so what was on each page, and describes the underlying principle as synthesis rather than summary.
Here's an example. "Our close rate on contract-stage deals is 50%" is a fact.
"Our close rate is 50%, down from a historical 60%, and if the two drivers behind that drop go unaddressed we lose share within a year" is a so what. Same data. Completely different value to the person listening.
The test is not a formatting rule or a slide-writing trick. It's a thinking discipline that happens to show up in how consultants write, and that's why it transfers so cleanly from client work into the interview room.
Why Do Consulting Firms Care So Much About the So What?
Firms care because the so what is the only part of the work a client cannot produce internally. There are four reasons it gets drilled into new hires from week one.
The client already has the data. A retailer knows its own same-store sales. What it does not have is an outside view of what those numbers imply and which of six possible responses is the right one.
It kills work that does not matter. Asking "what will this tell us?" before starting an analysis is the cheapest way to avoid burning a week on a model nobody will act on. In my experience at Bain, the managers who protected their teams' weekends were the ones who asked that question early.
It forces a position. You cannot state an implication without committing to a point of view, and committing is what clients pay for. Vague findings let everyone nod and change nothing.
It's how you get judged. Performance reviews for junior consultants almost always contain a line about whether the person can get from analysis to insight without being pushed. The same standard shows up in skills for management consulting assessments during recruiting.
What Is the Difference Between an Observation and a So What?
An observation reports what the data says. A so what states what it means and what should change because of it. The table below shows the same three situations handled both ways, using illustrative figures.
Situation |
Observation only |
So what |
Declining profits |
Profits fell 12% last year |
Profits fell 12% entirely because raw material costs rose while prices stayed flat, so a price increase recovers more margin than any cost program available this year |
Customer churn |
Churn is highest among customers in their first 90 days |
Churn is concentrated in the first 90 days, which points to onboarding rather than product quality, so fixing the first three touchpoints is cheaper than a product rebuild |
Market entry |
The market is growing at 9% per year |
The market grows at 9% but the top two players hold 80% share, so entering organically takes years and an acquisition is the only route that hits the client's three-year target |
Read the middle column again. Every statement is true, accurate, and useless. That's the trap most candidates and most first-year analysts fall into.
How Do You Apply the So What Test in Five Steps?
Apply the so what test by stating the finding, benchmarking it, tracing it to an actionable cause, converting that cause into a specific action, and sizing what happens if nobody acts. Each step takes seconds once you've built the habit.
-
State the finding in plain numbers: write the raw result before you interpret anything, because interpreting a number you have not stated cleanly leads to sloppy claims
-
Benchmark it: compare the number to last year, to a competitor, to another segment, or to the client's own target, since a number with nothing to compare it against carries no meaning
-
Ask why until you reach something actionable: keep going until you hit a cause a manager could assign to someone on Monday, which usually takes two or three rounds rather than five
-
Convert the cause into a specific action: "improve the customer experience" fails, while "cut first-response time on support tickets from 18 hours to 4" passes
- Size the cost of doing nothing: attach a consequence and a rough timeframe, because urgency is what moves a recommendation from interesting to funded
Step two is where most people skip. A number in isolation cannot be good or bad, and candidates who state a result without a comparison have not actually finished the analysis.
Step five is the one that separates senior thinking from junior thinking. Anyone can identify a problem, but naming what it costs to ignore it is what gets a client to move.
How Does the So What Test Show Up in a Case Interview?
It shows up after every single thing you say out loud. McKinsey describes its problem-solving interview as a business case used to evaluate analytical thinking and your approach to complex problems, and the so what is how that thinking becomes visible to the interviewer.
After every calculation
Getting the arithmetic right earns you nothing on its own. Finish your case interview math and immediately say what the answer means for the case question you're solving.
Weak: "The breakeven volume is 400,000 units." Strong: "Breakeven is 400,000 units, which is roughly double current volume, so this launch only works if the client can win share from the incumbent rather than grow the category."
After every exhibit
Candidates lose more points on charts than anywhere else because they narrate instead of interpret. When you receive case interview graphs, find the one data point that changes your answer and lead with that, rather than walking through every bar in order.
A useful discipline is to limit yourself to two observations per exhibit and force an implication onto each one. Two sharp reads beat six flat ones.
After you present your structure
A structure is a plan, and a plan needs a reason. After you lay out your case interview frameworks, say which branch you want to start with and why you expect it to hold the answer.
That single sentence signals prioritization, which is the skill interviewers are actually grading when they watch you build a structure. Stating an early case interview hypothesis is the cleanest way to do it.
After a brainstorm
Listing eight ideas and stopping is a wasted opportunity. Close any brainstorming in case interviews question by naming which one or two ideas you'd pursue first and what makes them the highest-value options.
Interviewers remember the prioritization far longer than they remember the length of your list.
In a written case or slide exercise
Written exercises grade the so what test more directly than live cases do, because your slide titles are the answer. A firm running a case interview presentation round is checking whether someone could read only your titles and follow your entire argument.
Title a slide "Regional Sales Performance" and you've described a topic. Title it "Two regions drive 90% of the decline, both after the pricing change" and you've stated a finding.
The rule graders apply is one idea per page, fully stated in the title and fully supported by the chart underneath it. Anything on the page that does not back up the title should be cut.
In your final recommendation
This is the highest-stakes moment for the test. A strong case interview recommendation leads with the answer, gives two or three supporting reasons tied to what you actually found, names the biggest risk, and ends with a next step.
Case interviews reward this habit more than almost anything else. If you want to build it quickly, my case interview course walks through proven strategies in as little as 7 days.
What Are the Most Common So What Mistakes?
Having coached hundreds of candidates one-on-one, I see the same five failures repeatedly. Four of them come from trying too hard rather than not trying at all.
Mistake #1: Restating the number in words
"Revenue declined by 15%, so revenue is down" adds nothing. If your implication could be deleted without losing information, it is not an implication.
Mistake #2: Inventing an insight the data cannot support
Candidates who know they're supposed to produce a so what will sometimes manufacture one from a single data point. Claiming a competitor is "clearly winning on brand" when all you have is a market share figure is a fast way to lose credibility with an interviewer who knows the case cold.
Mistake #3: Saving it all for the end
Some candidates stay quiet through the analysis and then deliver one polished summary at the close. Interviewers are grading you continuously, and thirty minutes of silence followed by a strong finish still reads as thirty minutes of weak performance.
Mistake #4: Stating an implication with no action attached
"This suggests the cost structure is a problem" is halfway there. Finish the thought by naming what the client should do about the cost structure and roughly what it's worth.
Mistake #5: Applying it to trivia
Not every number deserves an implication. Forcing one onto a minor assumption clutters your communication and buries the findings that actually matter, which is the opposite of what the test exists to do.
How Do You Practice the So What Test?
Practice it outside of cases first, because the skill is easier to build when you're not also managing structure, math, and nerves at the same time. Four drills work better than anything else I've used with candidates.
Tip #1: Run the newspaper drill
Open any business article, read one statistic, and say out loud what it means for the company involved and what its management should do. Give yourself ten seconds per statistic.
Do this five times a day and the reflex becomes automatic within two weeks. It costs nothing and it removes the pause that interviewers read as hesitation.
Tip #2: Rewrite your own case notes
After a practice case, look at your notes and mark every line that's purely descriptive. Rewrite each one with an implication attached.
Candidates are usually shocked by the ratio. A page that felt insightful during the case often turns out to be 80% description.
Tip #3: Cap yourself at two observations per exhibit
Artificial constraints force prioritization. Working through case interview examples with a two-observation limit teaches you to find the data point that matters instead of the data points that are easiest to describe.
Tip #4: Get feedback from someone who has interviewed candidates
You cannot reliably grade your own so whats, because the gap between "sounds smart" and "is useful" is invisible from the inside. Working with a former interviewer through interview coaching surfaces the difference in one session.
Bain's careers site notes that in case interviews the firm looks at whether you make sensible assumptions and build constructively on ideas, which is the so what test described in hiring language. The so what test in consulting is the shortest path from correct analysis to an offer, and the single action that moves you fastest is this: after every number you say out loud, force yourself to add one sentence starting with "which means." Do that for two weeks and interviewers will stop hearing an analyst and start hearing a consultant.
Frequently Asked Questions
What does the so what test mean in consulting?
The so what test is a check consultants run on every finding before sharing it. You state what the data shows, then answer what it means for the client and what they should do differently because of it. A finding that survives both questions is an insight. A finding that does not is reporting, and clients do not pay consulting rates for reporting.
Is the so what test the same as the Pyramid Principle?
No, but they work together. The Pyramid Principle, developed by former McKinsey consultant Barbara Minto, is about the order you communicate in: answer first, then supporting arguments, then evidence. The so what test is about the content of that answer. The Pyramid Principle tells you to put your conclusion at the top, and the so what test is how you figure out what that conclusion should be.
How do you find the so what in a chart or exhibit?
Read the axes and units first, then find the single largest gap, spike, or trend break in the data. Compare that number to something, whether a prior year, a competitor, or another segment on the same chart. Then connect it back to the case question. Most candidates describe five things on a chart, and strong candidates name one and explain why it changes the answer.
What do you do if the data has no so what?
Say so and move on. An analysis that confirms the situation is normal is a real finding, because it eliminates a branch of the problem and lets you spend your remaining time somewhere more productive. The mistake is inventing significance the numbers do not support. Interviewers and clients both catch manufactured insight quickly, and it costs you more credibility than an honest dead end.
Do case interviewers actually score you on the so what?
Yes, though it rarely appears under that label on the scorecard. It sits inside categories like business judgment, synthesis, and communication, and it is usually the reason a candidate with clean structure and correct math still gets rejected. When an interviewer writes that a candidate was mechanical or did not show commercial instinct, the missing ingredient is almost always the so what.
Everything You Need to Land a Consulting Offer
Need help passing your interviews?
-
Case Interview Course: Become a top 10% case interview candidate in 7 days while saving yourself 100+ hours
-
Fit Interview Course: Master 98% of consulting fit interview questions in a few hours
- Interview Coaching: Accelerate your prep with 1-on-1 coaching with Taylor Warfield, former Bain interviewer and best-selling author
Need help landing interviews?
- Resume Review & Editing: Craft the perfect resume with unlimited revisions and 24-hour turnaround
Need help with everything?
- Consulting Offer Program: Go from zero to offer-ready with a complete system
Not sure where to start?
- Free 40-Minute Training: Triple your chances of landing consulting interviews and 8x your chances of passing them