11 McKinsey Solve tips that actually move your score

The process score changes how you should play

McKinsey Solve (the gamified assessment that replaced the Problem Solving Test) records two things at once. The product score is what you would expect: did the food chain survive, were the Redrock calculations right, did the microbe trio treat the site. The process score is the part older guides miss: the game tracks how you got there. How often you changed direction, whether you backtracked, how you prioritised information, how long you hesitated before committing. Candidate reports on Reddit and prep forums describe this tracking in detail, and coaches corroborate the experience of being scored on approach rather than answers alone.

The practical consequence: frantic brilliance reads worse than steady competence. A candidate on r/consultingcareers who has sat Solve multiple times describes the assessment as measuring structured decision-making under time constraints, accuracy under speed, and tolerance for messy or ambiguous data. Play like someone the algorithm would hire: deliberate, sequenced, unhurried even when the clock is not.

Five tips that apply to every module

1. Set a per-question budget and protect it. Decide before the run what one question may cost you. When the budget expires, pick the most defensible option and move on. Coaches on PrepLounge tell candidates who left sections unfinished the same thing: not finishing is survivable, sinking 12 minutes into one monster question is not.
2. Never leave a question blank. There is no penalty for a wrong answer beyond the wrong answer. An educated guess at least feeds the process score a decision.
3. Front-load the easy points. Read the whole question set fast, bank the quick wins, and only then spend time on the hard middle. Redrock and Sea Wolf both front-load answerable material.
4. Keep one scratch pattern for numbers. Write ranges, sums, and converted units in the same layout every time. Most Redrock misses reported on Reddit are transcription errors, not reasoning errors.
5. Treat 80% as a win when it is the cap. Multiple candidates report sites where no combination reaches 100%. Chasing the last 20 points burns minutes the next site needed.

Redrock: four tips

Redrock Study gives you roughly 35 minutes to investigate a research scenario, analyse the data, and answer case questions. Candidates consistently describe it as the section where time pressure bites hardest, not because the math is hard but because the clock punishes re-reading.

1. Collect with the final questions in mind. The Research Journal is not a scrapbook. Before dragging a data point in, ask whether it could plausibly feed a calculation. A former consultant's r/managementconsulting tip still holds: add all available data points in investigation, but read each analysis question twice before answering.
2. Convert the target ranges into sums. Where a question gives you per-unit targets, multiply bounds out once and compare totals. It kills the most common arithmetic slip.
3. Sanity-check direction, not precision. Before submitting, ask: is this number the right order of magnitude and moving the right way? Candidates who post about failing Redrock usually describe a transcription or unit error, not a broken method.
4. If the report runs long, cut analysis time, not the report. The written report is scored on structure and completeness; an unfinished report costs more than a rough paragraph.

Sea Wolf: five tips

Sea Wolf asks you to select microbes with the right attributes and traits to treat contamination across three sites, in about 30 minutes. It compresses four phases: profiling the site, categorising microbes, building a prospect pool, and final selection.

1. Get through profiling and categorising fast. Candidate reports are specific: profiling deserves about 30 seconds (one standout priority, one avoid factor), and categorising is a throughput problem where micro-hesitations quietly burn minutes. Save your accuracy budget for final selection.
2. Filter on the undesirable trait first. A microbe with a trait the site penalises is dead on arrival no matter how good its numbers look. Remove those before comparing attributes.
3. Compare sums, not averages. If the site wants an average attribute in a range, multiply the range bounds by three and compare against your trio's sum. Faster, and no division errors under pressure.
4. Accept the cap. Candidate reports and PrepLounge threads report site 3 capping at 80% in real sittings. When every combination falls short, take the best defensible trio and bank the minutes.
5. Rehearse the pacing, not just the logic. Prep coaches recommend at least one or two timed Sea Wolf simulations before test day specifically so the pacing shock does not hit you live. Logic you can learn from a guide; rhythm you have to feel.

Sustainable Futures Lab: two tips

On 85-minute invitations, a third game appears: Sustainable Futures Lab, about 20 minutes of judgement calls inside one evolving team scenario (a ranking task, then twelve single-choice questions). No calculations. It reads more like a PEI embedded in a game than a maths test.

1. Pick the professionally boring answer. Candidates who played it on Reddit describe the strong option as the commercially sensible, sequenced one: acknowledge the constraint, bring the team along, protect the deadline. The dramatic pivot option is usually the trap.
2. Stay consistent. Prep sources and candidate reports agree the game evaluates behavioural patterns across the full 13-question run, not each answer in isolation. Deciding with a clear direction and holding it under new information outscores oscillating between philosophies.

Frequently asked questions

Can you fail McKinsey Solve?

There is no published pass mark. Coaches on PrepLounge and threads on r/McKinseyAndCompany describe the score as one input read alongside your CV, experience, and referrals: not finishing a section is not automatically disqualifying, a weaker Redrock can be offset by strong Sea Wolf, and even 10th-decile candidates have waited weeks for an interview invite. Play well, then let the rest of your application carry its weight.

Is it possible to get 100% on every Sea Wolf site?

Often, no. Candidates report some sites are capped at 80%, meaning no microbe combination reaches 100%. The game is checking whether you identify the best available trio and move on efficiently. Grinding for a perfect score that does not exist is exactly the behaviour the process score punishes.

How much time do I get on McKinsey Solve?

The invitation email states it: 65 minutes covers Redrock Study (about 35 minutes) and Sea Wolf (about 30 minutes); 85 minutes adds Sustainable Futures Lab (about 20 minutes). Ecosystem Creation was phased out around mid-2025 and only lingers in legacy material.

Does McKinsey track how you play, not just your answers?

Yes. Candidate guides and prep sources describe a process score alongside the product score: every click, drag, hesitation, and backtrack feeds how the algorithm reads your approach. That is why steady, decisive play is the recurring theme of every high-scoring candidate account.