Tips 1–5 · Apply to all three mini-games
Universal tips that apply across the whole assessment
These five habits compound across Sea Wolf, Red Rock, and Sustainable Future Lab. If you only have time for one section before your test, make it this one.
Process beats answers — every time
McKinsey scores the signals you generate (revisits, exhibit clicks, calculator usage, ranking changes), not just the final answer. A "right" answer reached by guessing scores worse than a "wrong" answer reached by visibly working through exhibits. Slow down and let the platform see your work.
Never blank-leave a screen
Even on a screen you don't understand, submit your best guess. Blank submissions cost more than wrong submissions in every mini-game. If you're stuck, commit to something defensible, revisit if time permits, and move on.
Revisit exhibits before final commits
Before you confirm a Red Rock card placement or a Sea Wolf submission, pop back to the exhibit panel for ten seconds. Roughly one in three candidates change their answer after revisiting — and the change is usually correct. The platform also logs the revisit as a positive signal.
Pace by section, not by the clock
Don't watch the global timer. Divide your time mentally per mini-game (rough rule: 30/30/20 minutes) and force yourself to move on at the boundary. Candidates who finish Sea Wolf with 20 minutes to spare almost always regret it after rushing Red Rock.
Treat the timer as a budget, not a deadline
A deadline says "finish before the buzzer." A budget says "spend this much on each task." The budget mindset stops you over-investing in the early easy screens — a common failure pattern where candidates burn 40% of their time on the first 20% of the assessment.
Tips 6–9 · Sea Wolf (ecosystem)
Sea Wolf: trait discipline and clean food-web reasoning
Sea Wolf is the most format-stable mini-game in the 2026 Solve and rewards drilling more than the other two. These four tips target the specific failure patterns the trait/penalty system punishes hardest.
Run a trait checklist before submitting your food web
Before final submit, scan the trait panel and verify every required trait is represented in your selection — and zero undesired traits are present. The 20%-per-undesired-trait penalty is the single largest controllable score loss in Sea Wolf.
Categorize aggressively — under-categorization beats over-
When in doubt about whether a species belongs in a category, include it. Sea Wolf's scoring is much harsher on missing necessary species than on including marginal ones. Cast the wider net.
Use the filter step as a sanity check, not a guess
The filter screen exists to let you re-confirm trait matches — not to introduce new guesses. If you find yourself making fresh selections at the filter step, you skipped trait analysis earlier. Go back to the trait panel, not the filter.
Practice on the real format, not on legacy Imbellus content
The 2026 Sea Wolf differs from the 2019 Imbellus ecosystem case (no terrain bonus, different trait taxonomy, generic site labels). Drilling old YouTube playthroughs will burn habits you then have to unlearn. Use a 2026-format free play instead. Full mechanics breakdown in the Sea Wolf guide.
Tips 10–13 · Red Rock (case-style)
Red Rock: exhibit fluency and calculator discipline
Red Rock is the most common weak spot in the 2026 Solve and where exhibit fluency separates candidates. These four tips alone resolve the majority of Red Rock score loss.
Read every exhibit before you drag a single card
Red Rock punishes pre-mature commitment harder than any other mini-game. One disciplined five-minute pass through all exhibits before you touch a value card will typically outperform any amount of mid-task replanning. Treat the exhibit pass as a mandatory phase, not optional.
Use the calculator FAB for every multi-step number
The orange calculator FAB exists because mental arithmetic under timer pressure introduces small errors that compound. Use it for any calculation with more than one step — even ones you "could do in your head." Calculator usage is itself a process signal McKinsey scores.
Commit priorities, then verify, then commit again
Drag your value-card priorities in your best first-pass order. Then re-read the case prompt. Then re-check your ordering against the prompt's stated objective. The second verification catches roughly 30% of misalignment cases candidates would otherwise submit.
The report rewards consistency between phases
Your report selections should follow logically from your value-card priorities. If you prioritized Card A in phase 1, your report should reference data supporting Card A — not contradict it. Inconsistency between phases is a scoring tell McKinsey weights heavily. Full mechanics in the Red Rock guide or try a free Red Rock play.
Tips 14–16 · Sustainable Future Lab
SFL: consistent judgment under branching scenarios
SFL rewards coherent decision patterns more than 'correct' answers. These three tips keep your judgment internally consistent across the branching simulator — which is what the scoring engine actually measures.
Stay internally consistent across branches
SFL is a branching judgment simulator. The scoring engine doesn't reward any single "correct" answer — it rewards a coherent decision pattern. If you prioritized cost in branch 1, prioritize cost in branch 3. Whiplashing your values mid-simulation tanks the score.
Rank priorities by the stated mission, not your gut
Each scenario opens with an explicit mission statement. Re-read it. Your priority ranking should reflect that mission, not what you'd personally do as a manager. Candidates who substitute their intuition for the stated mission consistently underperform.
The end-of-simulation survey is scored
The reflection survey at the end of Sustainable Future Lab is not optional content — it contributes to the process score. Answer it deliberately, not as a finished-the-test formality. Read the full SFL guide or run a free SFL simulation.
Tip 17 · Game-day logistics
The one tip that costs zero minutes and saves about 5%
The fastest score gain you can make is removing avoidable friction on test day. None of this is about Solve mechanics — it's about not handicapping yourself before the timer starts.
Set up your environment like it's a job interview
Real laptop (not tablet, not phone). Stable wired or strong wireless connection. Phone in another room. A 90-minute window blocked on your calendar with a 15-minute buffer either side. Water within arm's reach. Bathroom break beforehand. Browser tabs closed except the assessment. Candidates who get this right gain roughly 5% on the process-signal side just by not losing time to logistics — and the gain costs you zero minutes of prep.
Warning list
Five mistakes that tank an otherwise-good score
The mirror image of the 17 tips above. If you find yourself doing any of these on a free play, you've identified your highest-priority fix.
Panic-randomizing under the timer
When the clock turns red, candidates start clicking randomly. The platform logs this. Stick to your section budget — if you're behind, abbreviate, don't randomize.
Ignoring exhibits in Red Rock
Roughly half of failed Red Rock attempts had exhibits the candidate never opened. If you only fix one thing, fix this.
Over-thinking SFL
SFL rewards consistent judgment, not optimised judgment. Candidates who spend 90 seconds per branch decision score worse than those who decide in 30 and stay consistent.
Cramming the night before
Replaying a bad seed at 11pm anchors you on failure for the real test. Day 7 in our prep plan is intentionally light.
Taking the assessment on a tablet or phone
The Solve UI is built for a real keyboard, trackpad, and full screen. Tablet rendering issues alone have cost otherwise-strong candidates 5–10% in scoring time.
Want the structured version of how to avoid these? Read the long-term prep guide or compare practice tools in the 2026 prep-tools comparison.
FAQ
Can you actually 'study' for McKinsey Solve?
Not the way you'd study for a knowledge test — there's no syllabus to memorise. What you can do is build pattern fluency: see enough versions of each mini-game that the format stops surprising you, then drill the specific habits below (pacing, exhibit reading, calculator discipline) so they fire under timer pressure. That's what moves scores.
What's the single highest-impact McKinsey Solve tip?
Read every exhibit before you make a decision in Red Rock. Most score loss in the 2026 format comes from candidates committing to value-card priorities, calculator inputs, or report selections before they've seen the exhibit that would have changed the answer. One disciplined pass through the exhibits typically outperforms ten replays.
Are there hacks or shortcuts that beat McKinsey Solve?
No. McKinsey scores process signals (revisits, exhibit interactions, calculator usage, timing), so any 'hack' that skips steps actually hurts your score. The tips on this page are not hacks — they're the deliberate habits that produce the process signals McKinsey is looking for.
Do these tips change for experienced-hire candidates?
The mechanics don't change — the same 17 tips apply. What changes is allocation: experienced hires tend to over-trust intuition on Sustainable Future Lab (tips 14–16) and under-prepare for Red Rock's exhibit volume (tips 10–13). If you're an experienced hire, weight your prep toward Red Rock and treat SFL as a discipline drill, not a confidence game.
How do I know which tip applies to my weakest game?
Do one free play of each mini-game first. Whichever one leaves you with the worst time-pressure feel is your weakest — drill the corresponding section of this page (Sea Wolf 6–9, Red Rock 10–13, SFL 14–16) and ignore the others on your next two sessions.
Tips don't move scores. Reps with these tips do.
Run your next free play with this page open in a second tab. Score the gap between what you did and what tips 1–17 said. That gap is your prep list.