How I Prepared for the Three McKinsey Solve Games in 2026

Before taking McKinsey Solve, I expected that a few generic game strategies would be enough. After preparing seriously, I realized the assessment is less about gaming tricks and more about structured problem solving under time pressure. The best preparation was learning how to turn a messy scenario into clear steps, measurable constraints, and fast decisions.

This guide walks through the three McKinsey Solve games I prepared for in 2026: Ecosystem Building, Sea Wolf, and Redrock. It also explains the skills the assessment is trying to measure, how I practiced, and how to use AI interview preparation tools responsibly. ExtraBrain can help with mock interviews, structured practice, transcript review, and post-session reflection where the rules allow it, but candidates should not use any tool to violate McKinsey, employer, school, or assessment-platform policies.

McKinsey Solve overview

McKinsey Solve is a gamified problem-solving assessment used to evaluate how candidates reason through unfamiliar situations. The exact format can vary, so treat any candidate report as preparation context rather than a guaranteed preview. In my preparation, the assessment was organized around three timed sections: Ecosystem Building, Redrock, and Sea Wolf.

The common thread across all three sections was disciplined thinking. I had to identify the objective, separate signal from noise, manage constraints, and make decisions before time ran out.

What felt unusual about the format

Many interview assessments are direct math, case, coding, or behavioral screens. McKinsey Solve felt different because it wrapped business-relevant reasoning skills inside ecological and research scenarios. That made the assessment more engaging, but it also made it easy to get distracted by the game surface.

The winning mindset was to ignore the novelty and focus on the underlying structure:

• What is the objective?
• What constraints are fixed?
• Which variables can I control?
• What data matters most?
• What decision gives the highest chance of a stable outcome?

McKinsey Ecosystem Game strategy

The Ecosystem Game, sometimes called the Food Chain Game by candidates, asked me to build a sustainable biological habitat. The task involved selecting species, checking their environmental requirements, and placing them in a suitable location. After submission, the system simulated whether the ecosystem could remain stable.

The most important lesson was that every choice affects the whole system. A species can look attractive in isolation but still fail if it breaks the energy flow, competes for scarce resources, or cannot survive the selected terrain.

Step-by-step approach

I treated the ecosystem like a constrained optimization problem. Instead of picking interesting species first, I built from the bottom of the food chain upward.

1. Start with viable producers. Plants or other base-level species should match the selected environment and provide enough energy for the next layer.

2. Add herbivores that rely on those producers. I checked whether each herbivore had enough food, reasonable energy needs, and compatible environmental requirements.

3. Add carnivores only after the prey layer looked stable. Predators can make the ecosystem stronger, but they can also collapse it if there is not enough prey.

4. Avoid unnecessary overlap. Too many species competing for the same food source can create a bottleneck.

5. Check terrain and environmental constraints before finalizing. A strong food chain still fails if the species cannot survive the temperature, elevation, terrain, or location requirements.

6. Review energy flow from bottom to top. The chain should have enough energy at each level to support the next species.

Practical tips for Ecosystem Building

• Prioritize compatibility over variety. A smaller, coherent food web is usually better than a diverse but unstable one.
• Build a clean chain such as producer to herbivore to carnivore before adding complexity.
• Watch for species that appear useful but consume the same limited resource as several others.
• Track requirements in a simple grid during practice.
• Practice explaining why your ecosystem is stable, because that improves your reasoning even if the game does not ask for an explanation.

McKinsey Sea Wolf strategy

Sea Wolf focused on matching microorganisms to contaminated sites. The core challenge was comparing multiple attributes quickly and selecting organisms that met the site requirements.

I approached Sea Wolf as a filtering exercise. Each site had conditions such as temperature, pollutant type, and performance requirements. Each microorganism had attributes that needed to satisfy those conditions.

How I organized the information

The easiest way to avoid mistakes was to create a compact comparison table during practice. Even if the live interface differs, practicing with tables trains the same mental process.

The key was not to calculate everything from the beginning. I first eliminated impossible matches, then compared the remaining options. This saved time and reduced the chance of choosing a high-scoring microorganism that failed a mandatory condition.

Practical tips for Sea Wolf

• Filter by hard requirements first.
• Do not average candidates until invalid options are removed.
• Keep each site separate so you do not mix constraints.
• Use the same comparison order every time: environment, pollutant, efficiency, final ranking.
• Practice with timed drills that force quick elimination.

McKinsey Redrock strategy

Redrock felt closest to a consulting-style data task. It required reading charts, interpreting tables, completing analysis, and turning findings into a concise report or answer set.

I divided Redrock into three phases: investigation, analysis, and reporting. That structure helped me avoid getting lost in details.

Investigation phase

The first job was to understand the data before calculating anything. I looked at chart titles, axes, units, time periods, and category labels. This step sounds basic, but many mistakes come from reading the right number in the wrong context.

During practice, I paid special attention to:

• sudden changes in a trend line;
• unusually high or low values;
• differences between absolute change and percentage change;
• whether a table used counts, percentages, indexes, or rates;
• whether the question asked for the best answer, the most likely answer, or the answer supported by the data.

Analysis phase

For calculations, I relied on simple formulas and approximations. One common formula was percentage growth:

(current value - base value) / base value * 100

I also practiced estimating before doing exact math. If an answer choice was clearly impossible, I removed it first. That made the final calculation faster and safer.

Reporting phase

For written or structured responses, I used a simple problem-data-conclusion format. That meant I stated the issue, cited the key evidence, and then gave the conclusion.

A strong Redrock answer might follow this pattern:

This format kept my answers direct. It also made it easier to avoid unsupported speculation.

What McKinsey Solve evaluates

McKinsey Solve is not just a memory test. It is designed to observe how candidates think when the problem is unfamiliar, timed, and data-heavy.

Problem solving

The assessment rewards candidates who can break a complex situation into smaller decisions. In practice, that means defining the objective, identifying constraints, and choosing the next best action.

Strong problem-solving behavior includes:

• separating must-have constraints from nice-to-have criteria;
• choosing a workable strategy before exploring every possible option;
• using quick calculations when exact precision is unnecessary;
• recognizing when a decision creates downstream effects.

Critical thinking

Critical thinking matters because the assessment often includes tempting but incomplete information. The right answer is not always the most obvious number or the most visually dramatic chart. You need to ask what the data actually proves.

Helpful critical-thinking habits include:

• checking assumptions before acting;
• comparing relative and absolute changes;
• looking for cause-and-effect relationships without overstating them;
• using a structured framework such as MECE when organizing information.

Systems thinking

The ecological games especially test systems thinking. A choice that helps one species, site, or variable can harm another part of the system. That is similar to consulting work, where recommendations often create tradeoffs across customers, operations, cost, risk, and growth.

In Ecosystem Building, systems thinking meant understanding the food chain. In Sea Wolf, it meant matching a solution to several site constraints at once. In Redrock, it meant connecting data points without confusing correlation with causation.

Time management

Many candidates do not fail because they lack reasoning ability. They fail because they spend too much time trying to make every decision perfect. I practiced with strict timers so I could get comfortable making a good enough decision and moving forward.

How to practice for McKinsey Solve

The best preparation combined game-specific drills with broader consulting-style reasoning practice. I did not rely on one resource or one tactic. I built repeatable habits.

Practice with timed scenarios

Use timed practice blocks for each game type. For Ecosystem Building, practice selecting species under constraints. For Sea Wolf, practice filtering candidate options quickly. For Redrock, practice reading charts and writing concise conclusions.

A useful weekly practice plan could look like this:

Review your reasoning out loud

After each practice session, explain what you did and why. This exposes vague thinking quickly. If you cannot explain a decision in plain language, you probably did not fully understand it.

ExtraBrain can be useful for this part of preparation. As a free, local-first Mac desktop AI interview assistant and meeting copilot, ExtraBrain can support live transcription, screen-aware context, local Gemma 4 where installed and compatible, bring-your-own AI providers, and privacy controls. Used outside restricted assessments and where rules allow, it can help you turn practice sessions into transcripts, notes, follow-up questions, and structured review.

Use AI responsibly during preparation

AI tools should support learning, not replace honest work. For McKinsey Solve, the safest and most useful role for an AI interview copilot is preparation and review. That includes mock explanations, post-practice debriefs, framework coaching, and identifying where your reasoning became unclear.

ExtraBrain should be used only where interview, employer, school, workplace, meeting, and platform rules allow AI assistance, transcription, screenshots, or notes. A fully local ExtraBrain posture requires local Parakeet transcription plus local Gemma 4 on-device AI where installed and compatible, with no external provider requests. If you choose external AI or transcription providers, selected prompts, transcript text, screenshots, audio, or context may leave your device depending on your configuration.

Common mistakes to avoid

Treating the games like puzzles instead of reasoning tests

The games have puzzle-like interfaces, but the underlying assessment is about structured reasoning. Do not chase tricks at the expense of logic.

Ignoring mandatory constraints

A candidate option can be strong overall and still invalid. Always remove options that fail hard requirements before ranking the rest.

Overcalculating too early

Detailed calculations are useful after you know what matters. If you calculate every number before filtering, you waste time.

Failing to review practice attempts

Practice without review only builds familiarity. Practice with review builds skill. After each attempt, write down the exact reason for each mistake.

FAQ

How should I manage time during McKinsey Solve?

Use strict timers during practice. Start each game by identifying the objective and the hard constraints. Then make decisions in a consistent order instead of rethinking your process from scratch every time.

What is the best way to prepare for unexpected scenarios?

Practice varied scenarios and explain your reasoning out loud. Frameworks help because they give you a stable process even when the content changes. For example, you can use objective, constraints, options, evidence, and decision as a repeatable sequence.

Can ExtraBrain help me prepare for McKinsey Solve?

ExtraBrain can help with allowed preparation workflows such as mock interview practice, transcript review, structured answer outlines, and post-session debriefs. It is available for macOS today, including Apple Silicon and Intel Macs, with Windows and Linux planned. Use it responsibly and only where the relevant rules allow AI assistance, transcription, screenshots, or notes.

Is McKinsey Solve the same as a case interview?

No. McKinsey Solve is a gamified problem-solving assessment, while a case interview is usually a live discussion with an interviewer. However, both reward structured thinking, clear prioritization, quantitative comfort, and concise communication.

What should I do the day before the assessment?

Review your frameworks, do a short timed drill, and stop before you become mentally tired. The goal is to enter the assessment calm, structured, and ready to make decisions under time pressure.

Related ExtraBrain guides

• McKinsey case interview preparation
• McKinsey HackerRank assessment preparation
• McKinsey Sea Wolf strategy guide
• McKinsey interview questions
• ExtraBrain responsible use