Mckinsey Solve Game Practice

How I actually prep for the McKinsey Solve part of the interview process

The McKinsey Solve game is an interactive, team-based case exercise that has replaced or supplemented the traditional pre-work case in some recruitment cycles. You sit in front of a screen, navigate a virtual office environment, and work through a business problem collaboratively with two other candidates. It tests your ability to analyze data, communicate findings, and contribute to a team under time pressure. It is not a puzzle game in the entertainment sense. It is a structured assessment designed to mirror how McKinsey consultants actually work. Most candidates waste weeks preparing in the wrong direction. They drill individual case interviews for hours and treat the Solve like it is just another solo case. That mismatch is what gets people filtered out early. The Solve requires a different muscle — collaborative synthesis, not solo brilliance.

Mckinsey Solve Game Practice essentials

Here is what practice should actually look like. Find a mock Solve session with three people, not two, because the dynamics shift noticeably when there is a third voice in the room. Set a timer for 45 minutes, which is roughly the real window. Use a case framework only as a safety net during the first hour of practice. By the tenth or so session, you will stop needing it, and that is when the real learning happens. I used to build elaborate issue trees before every mock. It slowed me down past the point of usefulness. Now I start with a rough sketch on the first two minutes and jump into the data. That approach cut my average analysis time from 30 minutes down to roughly 18 minutes per mock session, which left enough breathing room for the presentation part. The difference was not dramatic in a single run, but over a dozen practices it added up to a improvement in confidence during the actual game. There is a specific edge case that almost trips people up. During one of my practice sessions, the partner in the virtual office would not engage with our proposed recommendations until we explicitly connected each suggestion to the financial impact numbers sitting in the exhibit files. We kept going back and forth on strategy without anchoring to hard metrics. The workaround was simple: I created a one-page summary table that mapped every recommendation to a specific dollar figure from the exhibits before the partner even asked. That table became our anchor and the discussion moved forward in about four minutes instead of spiraling for twenty. It is a small thing, but it is the kind of thing that separates candidates who move to the next round from those who do not.

The data exhibits in the Solve are deliberately messy. You will see tables with missing values, charts that contradict each other slightly, and narrative text that buries the actual numbers you need. The counter-intuitive insight here is that spending more time reading every word usually hurts you. Most of the narrative text is filler designed to test whether you can extract signal from noise. A better strategy is to skim the narrative in 60 to 90 seconds, then go straight to the numbers and the charts. Mark the exhibit page numbers of anything with hard data and come back to the text only if you hit a contradiction. Another nuance that beginners miss is the partnership dynamic. The virtual partner is not trying to help you solve the case quickly. They are an assessment tool. If you push too hard to dominate the conversation, they will likely become silent or agree reluctantly, and the assessors will note your lack of collaboration. If you defer too much, you look passive. The sweet spot is proposing one clear idea per turn and explicitly asking for the other person's take before moving forward. This is not fluff. It is a measurable behavior that evaluators score directly. I want to be blunt about the limitations of this format as well. The Solve cannot reliably predict how someone will perform in a full consulting engagement because it compresses a week of work into 45 minutes. Candidates who are naturally good at quick presentations can outperform candidates who are deeply analytical but slower to synthesize. The game favors a certain communication style over raw depth. It is also sensitive to technical glitches — internet drops, browser incompatibility, or microphone issues can derail a session regardless of skill level. I have seen strong candidates fail outright because their browser blocked the embedded video component halfway through.

If you want to practice effectively without relying solely on third-party mock platforms, here is a practical setup. Use the free case interview databases from sites like CaseCoach or PrepLounge to find relevant case themes, then recruit two friends and simulate the full environment. Record your session on video. Watch it back and note every time you interrupted, every time you stayed silent, and every time you went down a data rabbit hole without tying it back to the question. This self-review usually takes about 20 minutes per session and is more valuable than doing an additional mock that you do not reflect on. Another resource that is genuinely useful is the McKinsey Solve prep guide that occasionally appears on their careers page. It is brief, but it outlines the scoring criteria more clearly than most paid coaching materials. Pair that with free webinars hosted by former consultants on YouTube, specifically the ones where they break down actual Solve scenarios rather than generic case frameworks. The most common mistake I see is over-reliance on memorized frameworks. The Solve does not reward rigid framework application. It rewards flexible thinking. If the problem is about market entry and you immediately launch into a full Porter's Five Forces breakdown, you will waste five minutes on analysis that the assessors are not scoring. Instead, diagnose the problem in the first three minutes and choose a lightweight framework that fits. A simple revenue driver tree often covers 80 percent of what you need in half the time.

Communication during the game matters as much as analysis. When you present your findings, lead with the answer, not the journey. Say the conclusion first, then give the two supporting numbers, then briefly mention your method. This mirrors how partners actually receive updates in a firm. It is faster, clearer, and easier for the assessors to score. Preparation timeline depends on your baseline. If you already have case interview experience, eight to ten solid mock sessions over three weeks is usually sufficient. If you are new to case interviews, plan for six to eight weeks with at least two mocks per week plus daily quantitative practice. The quantitative part is often overlooked. You should be comfortable doing quick percentage calculations, growth rate estimations, and basic break-even math without a calculator. A few minutes of daily mental math practice will save you significant time during the exhibit analysis phase. There is no single downloadable app or perfect simulator that replicates the real experience exactly. Most platforms offer approximations. The closest official resource is the McKinsey Solve practice module available through their careers portal, though access varies by region and recruitment cycle. Third-party platforms like Forage and CaseInterview.com offer Simulate-style exercises that capture much of the same dynamic at a lower cost. The Forage version is free and gives you a taste of the collaborative environment, though it is solo rather than multiplayer, which is a notable gap.

Ultimately, the Solve is a trainable skill. It does not require innate genius. It requires deliberate practice with feedback, awareness of your own behavioral patterns, and the discipline to cut through noise quickly. The candidates who succeed are the ones who treat it as a collaborative problem-solving exercise rather than a test to be cracked.