If you’re Googling McKinsey Solve because your invite just landed and you feel that “what even is this?” stress… this post is for you.

I’ll keep it tactical, based on what actually moves your score: pacing, decision hygiene, and avoiding the common time traps.

TL;DR (read this if you have 60 seconds)

What’s inside McKinsey Solve (most common)

• Red Rock Study (≈35 min): interactive case with exhibits + calculations + conclusions under time pressure.
• Sea Wolf (≈30 min): logic/optimization game across phases (fast classification + smart selection under constraints).

Best “high impact” prep

• Practice Red Rock-like cases (timed, with exhibits and ambiguity).
• Do at least 1–2 Sea Wolf simulations so the pacing shock doesn’t hit you on test day.

Free/fast practice links (simulators)

• Sea Wolf Solver (NOT recommended for use in the real test): https://seawolfsolver.com/
• Sea Wolf Game Simulator + Red Rock Study Simulator: http://solveprep.com/

What McKinsey Solve is really testing

People fixate on “math difficulty” or “secret formulas.” In reality, McKinsey Solve is mostly measuring:

1. Structured decision-making under time constraints
2. Accuracy under speed pressure (not perfection)
3. Noise tolerance (ambiguous phrasing / messy data)
4. Process discipline (how you move through info, not just your final click)

So your prep should train execution, not trivia.

Red Rock Study: How to Actually Score Better

The mental model: “Time is the currency”

Red Rock doesn’t usually beat people with hard math — it beats them with:

• rereading
• second-guessing
• overbuilding calculations
• getting lost in exhibits

Your goal is to stay decisive and clean, even when the question wording feels “off.”

Red Rock pacing rule (simple, effective)

Start with a budget per question and protect it like a hawk.

• If something takes longer than your budget: choose the most defensible option and move on.
• Your score often benefits more from finishing cleanly than from perfecting one monster question.

Red Rock workflow that reduces mistakes

Use this mini-loop for every question:

1. What is being asked? (write 3–7 words in your head)
2. Where is the data? (exhibit / table / case text)
3. One-pass calculation (no fancy spreadsheets in your brain)
4. 10-second sanity check
   • magnitude check (does this number feel plausible?)
   • unit check (%, €, absolute?)
   • direction check (increase vs decrease?)

This sounds basic, but it prevents the #1 Red Rock fail: a correct method applied to the wrong interpretation.

Red Rock: the “Ambiguity Trap” (and how to escape)

Red Rock questions are often intentionally phrased to slow you down.

Rule: If you can justify an interpretation quickly, commit and execute.
Do not pay a 60–90 second “mental tax” trying to reach philosophical certainty.

A good strategy is:

• pick the interpretation that aligns with the most standard business meaning
• calculate fast
• sanity-check
• submit
• move on

Red Rock: math you should be fluent in (no more, no less)

If you’re rusty, focus on these:

• % change (increase/decrease)
• weighted average
• ratios / proportions
• basic probability interpretation
• reading charts fast (trend, deltas, outliers)

Do not overtrain advanced math. Speed + accuracy on basics wins.

Best way to practice Red Rock

You need reps that mimic:

• exhibits
• time pressure
• “businessy” wording
• switching between data sources

Use a simulator and practice reviewing your errors, not just completing the case:

• What mistake pattern happened?
  • misread question
  • mis-copied number
  • wrong denominator
  • unit mismatch
  • rushed without sanity check

That error audit is where your score jumps.

Practice link (simulator): http://solveprep.com/

Sea Wolf: The High-Scoring Approach (Phase by Phase)

Sea Wolf is not “hard,” it’s compressed.
If you treat every phase like it deserves equal attention, you run out of time.

The scoring mindset

• Early phases: speed + consistency
• Final decision phase: accuracy + trade-off logic

In other words: save your brainpower for the decisions that matter.

Phase 1: Profiling (finish fast)

Target time: ~30 seconds

Pick:

• one standout priority (most constrained dimension / biggest risk)
• one “avoid” factor (what will tank you)

Then move.

Profiling is about showing direction, not solving the whole site upfront.

Phase 2: Categorization (speed is the whole game)

This phase is where people quietly burn minutes through micro-hesitations.

Target time: fast and decisive.

Tactics:

• Don’t bounce your eyes between targets and microbe stats repeatedly.
• Hold the key constraints in short-term memory (or write them down if allowed in your setup environment).
• Make decisions based on dominance:
  • obvious fits: keep moving
  • obvious rejects: discard instantly
  • “maybe” items: don’t overinvest — you can validate later

Categorization is a throughput problem.

Phase 3: Prospecting (good enough, not perfect)

Prospecting is where you want a shortlist of strong candidates quickly.

Tactics:

• Aim to find a few high-quality options, not “the single best”
• Don’t chase tiny improvements if you haven’t locked the big constraints

Think in terms of:
coverage + flexibility (options that keep multiple paths open).

Phase 4: Treatment / Final Selection (where you actually win)

This is where accuracy matters most.

Two practical tricks:

1) Compare sums instead of averages (faster)

If you’re combining 3 items and targets are given as ranges:

• multiply the target bounds by 3
• compare to your summed values

This avoids dividing under time pressure.

2) Avoid “solution-killing penalties”

If the game penalizes negative traits, treat them like risk multipliers:

• a small numeric improvement can be outweighed by a penalty
• your goal is a robust solution, not a fragile one

Best way to practice Sea Wolf

You need to feel the pace before the real test.

Do 1–2 full simulations timed:

• First run: learn pacing pain points
• Second run: optimize your phase times

Practice link (simulator): http://solveprep.com/

A note on “Sea Wolf solvers” (read before you DM me)

You’ll see people talk about tools that output answers. Using that in a real hiring assessment is cheating, can violate policies, and can backfire if there are detection mechanisms or follow-up evaluation.

I’m including this link only because people will search for it anyway, but my advice is simple:

If you need a solver to pass, you’re not solving the real problem — which is performing under time pressure.

Link: https://seawolfsolver.com/

If you want to maximize your odds sustainably, spend that energy on:

• timed reps
• error audits
• phase time budgets
• clean decision logic

That’s what translates to interviews and the job.

48-hour prep plan (if you’re late)

If your test is soon:

Day 1

• 1 Red Rock sim timed
• Review every miss: classify error type
• Drill your weakest math pattern for 30 minutes

Day 2

• 1 Sea Wolf sim timed
• Write down your phase times
• Repeat with a tighter time budget (second attempt)

Test day

• Sleep > cramming
• Warm up with 5 quick % change questions (10 minutes max)
• Go in with a clear pacing plan

If you want, reply with:

1. which games you got (Red Rock / Sea Wolf / other)
2. how many days you have
3. your biggest weakness (speed, math, ambiguity, focus)

…and I’ll comment a tailored pacing plan + what to practice first.

Good luck — and remember: McKinsey Solve rewards decisive, structured execution, not perfection.