Proven McKinsey Solve Tips to Ace the Problem Solving Game

Proven McKinsey Solve tips to ace the Problem Solving Game start with a constraint: do not prepare from leaked gameplay scripts. Treat McKinsey Solve, still often searched as PSG, as an unfamiliar problem-solving environment where your job is to understand the objective, respect the rules, track constraints, interpret feedback, and make defensible decisions under uncertainty. McKinsey describes Solve as a gamified assessment in the consultant recruitment process, so the best preparation is game-agnostic: practice structured thinking, careful reading, quantitative discipline, and clear tradeoffs before the assessment starts. Old PSG advice can help you understand why candidates feel anxious, but it should not become your source of truth for current format, timing, scoring, or module names. Your invite and McKinsey's official pages matter more. If you pass the assessment stage, the same habits carry into McKinsey case interview prep and PEI, where your reasoning becomes visible in conversation.

If you are already preparing for the broader process, pair this guide with McKinsey case interview prep so Solve does not become an isolated project.

What McKinsey Solve is and what it is not

McKinsey presents Solve as a gamified assessment used in consultant recruiting to showcase problem-solving abilities, with performance considered alongside the broader application and any other assessments on the candidate journey. That official framing matters because it keeps your prep honest: you are preparing your thinking, not trying to predict private assessment content from forum fragments or old screenshots.

The phrase Problem Solving Game is still useful for search because many candidates learned about the assessment under that name. PSG advice can also be directionally helpful when it reminds you to be structured, calm, and analytical. The problem starts when old advice turns into certainty: guaranteed modules, fixed patterns, pass thresholds, or exact scoring claims. Unless your current McKinsey invite says it, do not treat it as current fact.

The official McKinsey Solve assessment page is the cleanest starting point. Read it, then use this article for legal, game-agnostic preparation: objective framing, constraint tracking, signal reading, tradeoff judgment, and post-assessment interview readiness.

Official rules and verification checklist before you play

Before you open the assessment, slow down and verify the basics. Your goal is to remove avoidable uncertainty without asking for confidential content.

Use this checklist:

• Confirm whether your role uses Solve, another test, or a different assessment path.
• Read your invite for deadline, setup, permitted materials, browser or device requirements, and retake rules if mentioned.
• Check whether you need an accommodation, and ask recruiting through the official channel before the deadline.
• Review McKinsey's integrity expectations before starting.
• Avoid relying on third-party claims about timing, scoring, current module names, or pass thresholds.
• Set up a quiet environment and close anything not explicitly permitted.

McKinsey's assessment integrity expectations are clear enough for practical purposes: do your own work, do not use unauthorized assistance, do not record or screenshot assessment content, do not share assessment material, and do not bring in outside tools unless McKinsey has allowed an accommodation. That includes AI help during the assessment. Prepare before the assessment; during the assessment, follow the rules.

If you want to test whether this prep approach works under pressure, Road to Offer helps by drilling the transferable skills behind Solve without pretending to reproduce McKinsey's private assessment.

Proven McKinsey Solve tips that stay inside the rules

The best Solve tips sound simple because they are habits, not hacks.

Start with the first instruction screen. Do not skim because it looks game-like. Translate the prompt into plain English: What is the objective? What is scarce? What changes after I act? What evidence would show that a decision is working? If scratch work is permitted, write only a clean tracking sheet: objective, constraints, facts, assumptions, options, decision rule, and next action.

Separate known facts from assumptions. Known facts are details the assessment gives you directly. Assumptions are your interpretation of what those details might mean. Confusing the two is how candidates overfit to a visible pattern and miss the actual objective.

Use tradeoff language internally: choose the option with the strongest objective fit under the current constraints, even if it is not perfect on every dimension. That mindset is closer to consulting judgment than chasing a clever-looking move.

Watch cause and effect after each decision. If the environment changes, update your model. If nothing useful changes, do not spiral. Keep moving with a defensible rule.

McKinsey's broader interviewing guidance says candidates for client-facing roles may complete a test or game, and most client-facing roles continue into personal experience and problem-solving interviews. That is why McKinsey case interview insights matter here: the same structure, hypothesis discipline, and synthesis habits show up later in a different format.

Sample game-thinking table for objectives, constraints, signals, and tradeoffs

The table below is generic problem-solving practice. It is not a claim about current McKinsey Solve modules.

This is where Road to Offer is useful: it gives you repeatable micro-practice for the muscles that matter, while leaving McKinsey's private assessment private.

Questions to ask your recruiter or yourself before the assessment

Recruiter-safe questions are about logistics, eligibility, and accommodations. They are not about private assessment content.

Ask only if the invite is unclear:

• Which assessment applies to my role?
• What deadline and technical requirements should I follow?
• Who should I contact if I have a technical issue?
• What is the correct process for requesting an accommodation?
• Are there any official preparation materials I should review?

Then ask yourself readiness questions:

• Can I restate an unfamiliar objective before touching the details?
• Can I identify constraints without turning them into a memorized framework?
• Can I interpret visual or quantitative information without overfitting to one signal?
• Can I make a good tradeoff when the answer is not perfect?
• Can I move on cleanly after a decision instead of trying to make every move feel certain?

These questions are not only for Solve. They are also early preparation for phone and video case interviews, where calm setup, note discipline, and clear communication matter because the interviewer can see your reasoning in real time.

Common PSG prep mistakes that waste time

The first mistake is memorizing old module rumors. The better replacement is to practice objective and constraint tracking. If the assessment changes, the habit still travels.

The second mistake is over-optimizing paid simulators. A simulator may reduce anxiety, but it can also train you to recognize one interface instead of solving unfamiliar problems. Use any practice tool as a thinking drill, not as proof that you know what McKinsey will show you.

The third mistake is ignoring the rules because the assessment is remote. McKinsey treats assessment integrity seriously. Do not use AI, outside help, unauthorized websites, calculators, prepared notes, screenshots, recordings, or shared prompts unless McKinsey explicitly permits something for your situation.

The fourth mistake is practicing only full cases. Full cases matter, but Solve readiness often depends on smaller skills: reading instructions, choosing a decision rule, interpreting data, doing clean math, and synthesizing a move. Road to Offer drills help practice those underlying skills without presenting themselves as a Solve simulator.

The fifth mistake is treating Solve as the whole recruiting process. McKinsey's interviewing page points candidates toward later personal experience and problem-solving interviews, and the official practice cases show how organized reasoning carries into client scenarios. Use first vs second round interviews to understand how the bar changes once you move beyond screening.

Practice drill plan for Solve readiness and later McKinsey interviews

Separate Solve readiness from post-Solve interview readiness.

For Solve readiness, use short drills that isolate the core habits. Start with structure: turn an unfamiliar prompt into objective, constraints, facts, assumptions, and next action. Then move to charts: read a visual or data input, identify the strongest signal, and avoid overfitting. Add math practice for clean comparisons under pressure. Finish with synthesis: state the decision, the reason, the tradeoff, and the uncertainty you are accepting.

If your Solve prep has turned into reading old PSG threads, use the Free drill picker and practice the underlying skill instead.

For post-Solve readiness, shift into case interviews and PEI. Run free case practice once the micro-skills feel stable. Use the PEI and fit interview workbook so personal experience prep does not get pushed to the last minute. If you are preparing across firms, MBB case interview prep and free McKinsey interview prep tools give you the broader path.

MIT's consulting guidance connects consulting recruiting with quantitative ability, problem solving, communication, leadership, and case-interview thought process. That is the point: Solve prep should make you sharper for the whole process, not just more familiar with one assessment label.

Once you have drilled the micro-skills, use Road to Offer to test whether they hold inside a full case flow.

Sources and Further Reading (checked 2026-06-02)

• McKinsey & Company - Solve, McKinsey's assessment game
• McKinsey & Company - Interviewing at McKinsey
• McKinsey & Company - Assessment Integrity Expectations
• MIT Career Advising & Professional Development - Consulting
• Yale Office of Career Strategy - Consulting
• McKinsey & Company - Beautify Practice Case