How Long Does the McKinsey Solve Game Take? A Complete Breakdown
The McKinsey Solve takes ~70 minutes total with ~35 minutes per game. Here's the full 2026 timing breakdown and how to manage the time pressure

McKinsey Solve Timing: Every Minute Counts More Than You Think
If you're preparing for the McKinsey Solve, one of the first practical questions you need answered is how long the assessment actually takes — and more importantly, how the time pressure shapes your score.
The McKinsey Solve gives you approximately 35 minutes per game across two modules: the Sea Wolf game and the Red Rock Study. Total active gameplay runs roughly 60–70 minutes, with an additional 10–15 minutes for login, system checks, tutorials, and confirmations. You should block 90 minutes end-to-end to avoid any time stress before the games even begin.
But the raw session length isn't what makes timing critical. The McKinsey Solve compresses an enormous volume of decisions into those 35-minute windows — far more than most candidates expect. Time management isn't a secondary skill on the Solve. It's one of the primary things being tested, and it's one of the biggest reasons otherwise strong candidates don't advance.
Full McKinsey Solve Timing Breakdown (2026)
The current Solve consists of two games only. Here's how the time distributes across the full session:
Phase | Estimated Duration | Notes |
|---|---|---|
Login and system check | ~5 minutes | Browser compatibility, webcam/mic setup |
Game 1 tutorial | ~3–5 minutes | Instructions and practice walkthrough |
Game 1 gameplay | ~35 minutes | Active timed assessment |
Transition between games | ~2–3 minutes | Brief instructions for second module |
Game 2 tutorial | ~3–5 minutes | Instructions and practice walkthrough |
Game 2 gameplay | ~35 minutes | Active timed assessment |
Final confirmation | ~2–3 minutes | Submission and wrap-up |
Total session | ~65–75 minutes | Block 90 minutes to be safe |
The order in which you receive Sea Wolf and Red Rock varies by candidate — McKinsey assigns the sequence, and you can't choose which game you play first.
Sea Wolf Game Timing: The Most Time-Pressured Module
The Sea Wolf game is widely considered the more time-pressured of the two Solve modules. Within roughly 35 minutes, you need to build a functioning marine ecosystem by selecting microbes that interact, survive, and thrive together — all while managing interdependent variables under a clock that feels faster than it should.
Where the Time Goes in Sea Wolf
A typical Sea Wolf session breaks down roughly like this:
Phase | Time | What's Happening |
|---|---|---|
Tutorial | ~3–5 min | Interface orientation, practice scenario |
Initial analysis | ~5–7 min | Understanding the ecosystem parameters, assessing available microbes |
Core decision-making | ~18–22 min | Selecting and placing microbes, evaluating outcomes, adjusting strategy |
Final optimization | ~3–5 min | Last adjustments and confirmation |
The core challenge is that Sea Wolf's ecosystem dynamics are complex enough that candidates who haven't practiced the mechanics often spend their first 10 minutes just understanding how the interface works. On a 35-minute clock, losing a third of your time to orientation is devastating.
Why Sea Wolf Punishes Unstructured Thinking
Sea Wolf is designed so that trial-and-error approaches run out of time. Candidates who pick microbes without a framework — testing combinations to see what happens — burn through minutes without building toward an optimal solution. The game rewards candidates who arrive with an internalized understanding of how the ecosystem variables interact, allowing them to make faster, more confident selections.
This is exactly why practicing with the Sea Wolf Solver before test day makes a measurable difference. Candidates who have already explored the optimization patterns don't waste precious minutes on orientation and guesswork — they execute a strategy they've already refined.
Red Rock Study Timing: Deceptive Breathing Room
The Red Rock Study feels less frantic than Sea Wolf on the surface. The ~35-minute window provides what seems like adequate time to analyze geological data sets, identify patterns, and make decisions. But this sense of breathing room is deceptive — and it's where many candidates lose points.
Where the Time Goes in Red Rock
Phase | Time | What's Happening |
|---|---|---|
Tutorial | ~3–5 min | Interface orientation, sample data walkthrough |
Data orientation | ~5–7 min | Scanning available data sets, identifying what's relevant |
Core analysis & decisions | ~18–22 min | Pattern recognition, hypothesis testing, answering questions |
Review & confirmation | ~3–5 min | Checking consistency of answers |
The Red Rock Time Trap
Red Rock's primary timing trap is information overload. The game presents more data than you need, and candidates who try to read and analyze everything almost always run out of time. The test isn't measuring whether you can process all available information — it's measuring whether you can identify which information matters and ignore the rest.
Candidates who spend 60–90 seconds structuring their approach at the start — deciding what data to prioritize and what to skip — consistently finish with time to spare. Candidates who dive straight into reading the data sets typically hit the wall around the 25-minute mark, then rush through their final answers under pressure.
Why Timing Is One of the Biggest Score Differentiators
Timing alone accounts for a disproportionate share of Solve failures. It's not that candidates lack the analytical ability to score well — it's that they run out of time before demonstrating that ability, or they rush their final decisions after spending too long on earlier tasks.
The most common timing mistakes across both games:
Spending too long on tutorials. The tutorials are important if you've never seen the games before, but candidates who've practiced with a McKinsey Solve simulation can move through them quickly. Those extra 3–5 minutes of saved tutorial time go directly into gameplay.
Over-analyzing early decisions. In both Sea Wolf and Red Rock, candidates tend to spend disproportionate time on their first few decisions — trying to be perfect before they've fully understood the game's dynamics. Experienced test-takers distribute their time more evenly, knowing that later decisions are just as important as early ones.
Second-guessing mid-game. Changing course halfway through Sea Wolf or revising Red Rock answers late in the session burns time without reliably improving outcomes. Candidates who commit to structured decisions early and move forward consistently outperform those who revisit and revise.
Ignoring the clock entirely. This sounds obvious, but a surprising number of candidates report not checking their remaining time until they're already behind. Build clock-checking into your rhythm — a quick glance every 5–7 minutes keeps you calibrated.
How to Manage Timing Effectively on the McKinsey Solve
Time management on the Solve isn't about working faster. It's about eliminating the activities that waste time without improving your score. Here's what that looks like in practice:
For Sea Wolf
Arrive with a framework, not a blank slate. The single most impactful thing you can do for Sea Wolf timing is to understand the ecosystem mechanics before test day. Candidates who walk in knowing how microbe interactions work — which combinations are productive, which conflict — make decisions in seconds that unprepared candidates agonize over for minutes. The Sea Wolf game guide covers these mechanics in detail.
Commit to decisions. Sea Wolf penalizes indecision more than imperfect choices. A good-enough microbe selection made quickly and built upon is almost always better than a theoretically perfect selection that takes too long to reach.
For Red Rock
Structure before you read. Spend your first 60–90 seconds deciding what you're looking for in the data — not reading the data itself. This upfront investment pays off dramatically in the subsequent 30+ minutes.
Triage the data ruthlessly. Not all information in Red Rock is relevant. Identifying what to ignore is as important as identifying what to analyze. If a data set doesn't connect to the questions you need to answer, skip it.
Practice the pacing. Red Rock's time trap is subtle enough that you won't feel it until it's too late — unless you've experienced it in practice. Running through Red Rock simulations under timed conditions builds the internal clock that keeps you on track during the real assessment.
For Both Games
Use the tutorials strategically. If you've already practiced with simulations, skim the tutorials for any differences from what you've practiced — don't re-read instructions you already know. If you haven't practiced, pay close attention, because the tutorial is your only chance to learn the interface before the clock starts.
Block 90 minutes, arrive calm. Rushing to log in, dealing with technical issues, or feeling time pressure before the games even start puts you at a disadvantage. Give yourself a 15–20 minute buffer so you enter the first game relaxed and focused.
First-Attempt vs. Practiced Timing Performance
The difference between a candidate's first exposure to the Solve and their performance after structured practice is stark — and most of that difference comes down to timing efficiency.
Timing Factor | First Attempt (Typical) | After Practice (10–20 hrs) |
|---|---|---|
Tutorial time | 5–10 min (reading everything carefully) | 2–3 min (skimming for key details) |
Sea Wolf first decision | 4–6 min (figuring out the interface) | 1–2 min (immediately oriented) |
Red Rock data triage | No triage — reads everything | Structured scan in first 90 seconds |
Mid-game clock awareness | Checks time too late | Regular 5–7 min check-ins |
Final 5 minutes | Panicked rushing | Calm review and confirmation |
Tasks completed | Often incomplete | Consistently finishes both games |
The candidates who score in the top 25–35% — the range needed to advance — aren't necessarily smarter than those who don't. They're more efficient. They've converted orientation time into execution time through practice, and that's often the difference between passing and failing.
Frequently Asked Questions
How long does the McKinsey Solve take in total?
The full McKinsey Solve session takes approximately 65–75 minutes, including login, tutorials, both games (~35 minutes each), and final confirmation. You should block 90 minutes to account for setup time and avoid feeling rushed before gameplay starts.
Can I pause the McKinsey Solve or take a break between games?
No. Once you begin the Solve, the timer runs continuously within each game. There is a brief transition period between the two modules with instructions for the second game, but you cannot pause gameplay, save progress, or take an extended break. Plan accordingly — use the restroom and eliminate distractions before you start.
Is Sea Wolf or Red Rock Study longer?
Both games are allocated approximately 35 minutes of gameplay time. However, Sea Wolf typically feels more time-pressured because its decision-making is more rapid and continuous, while Red Rock involves more analysis with a subtler time crunch. Candidates most often report running out of time on Sea Wolf.
Does the order of games matter for timing?
McKinsey assigns the game order — you don't choose which module you play first. Some candidates prefer starting with Sea Wolf (higher intensity first, while energy is fresh), and others prefer Red Rock first (build momentum with structured analysis). Since you can't control the order, the best approach is to practice both games enough that you perform consistently regardless of sequence.
How many practice hours does it take to improve my Solve timing?
Based on candidate-reported outcomes, 10–20 hours of structured practice with realistic simulations is the range where most candidates see meaningful timing improvements. The key is practicing under actual timed conditions — untimed practice builds familiarity with game mechanics but doesn't train the pacing instincts that determine your score. Focus on Sea Wolf and Red Rock equally.
Turn Timing From a Weakness Into an Edge
Most candidates walk into the McKinsey Solve having never experienced the time pressure of either game. That means their first exposure to the 35-minute clock is on test day — when it counts.
The SeaWolfSolver practice tools eliminate that disadvantage. The Sea Wolf Solver helps you internalize optimal ecosystem strategies so you execute rather than experiment on test day, and the full McKinsey Solve simulator replicates both games under realistic timed conditions. The Elite Bundle ($79) includes everything — solver, simulators, and all practice scenarios.
Ten to twenty hours of timed practice is the difference between watching the clock run out and finishing with confidence. Your Solve score depends less on raw ability and more on how efficiently you use 35 minutes.



