McKinsey Solve: Proven Tips to Master the Problem Solving Game

If you’re preparing for the McKinsey Solve, also known as the McKinsey Problem Solving Game (PSG), you already know it’s unlike any traditional assessment. This gamified test challenges your ability to think critically, manage time, and make smart decisions under pressure, all while navigating complex digital ecosystems. Success isn’t just about knowing the rules; it’s about mastering strategy, structure, and focus. Whether you’re targeting your first consulting role or aiming to sharpen your performance, understanding how to approach each part of the game can make all the difference.

TL;DR - What You Need to Know

• The McKinsey Solve (PSG) is a gamified digital assessment that measures analytical thinking, decision-making, and systems reasoning through interactive mini-games.
• You’ll face two timed modules, Ecosystem Building and one other scenario, completed in 70 minutes to test structured problem-solving under pressure.
• Success depends on mastering five key skills: critical thinking, situational awareness, systems thinking, decision-making, and meta-cognition.
• Effective time management and clear note organization are essential; spend no more than 30 minutes per mini-game and track progress closely.
• Prepare strategically by practicing game simulations, refining mental math, and developing a hypothesis-driven mindset for the McKinsey Problem Solving Game.

What Is the McKinsey Solve (PSG) and Why It Matters

The McKinsey Solve, also called the Problem Solving Game (PSG), is a digital, scenario-based assessment used to evaluate candidates’ critical thinking, decision-making, and problem-solving abilities. It replaces the paper-based Problem Solving Test and plays a key role in McKinsey’s hiring process by identifying candidates with strong analytical and strategic reasoning skills.

The McKinsey Solve is not a typical test of knowledge or memorization. Instead, it evaluates how you think, analyze data, and make structured decisions under pressure. Created in partnership with Imbellus, the game simulates real-world problem scenarios that consultants face, testing your ability to break down complexity and adapt to changing information.

Understanding its purpose helps you prepare strategically. McKinsey uses this assessment as a first filter before interviews, ensuring candidates demonstrate not just intelligence but also practical reasoning and systems thinking. This means that your approach, decisions, and time management matter as much as your final answers.

During the Solve, you will encounter data-heavy environments and dynamic systems that challenge your ability to identify key variables and relationships. Unlike traditional multiple-choice tests, every action you take is recorded and analyzed through behavioral metrics, such as:

• How efficiently you process information
• How logically you test hypotheses
• How effectively you balance short-term and long-term decisions

Performing well on the McKinsey Solve is often the first major step toward securing an interview. Candidates who treat it as a skills-based challenge rather than a guessing game tend to outperform others. By mastering the structure and purpose of the Solve, you position yourself for success in both the test and the consulting interview stages that follow.

How the McKinsey Problem Solving Game Works

The McKinsey Problem Solving Game consists of two interactive mini-games completed in about 70 minutes. Each game tests different aspects of analytical thinking, decision-making, and systems reasoning. The first game is always Ecosystem Building, followed by one of several modules like Redrock Study or Plant Defense, depending on McKinsey’s current test rotation.

The McKinsey Problem Solving Game, often referred to as the McKinsey PSG or McKinsey Solve, is designed to assess how you think rather than what you know. It’s a digital assessment that simulates real-world consulting problems, allowing McKinsey to evaluate your problem-solving process objectively through in-game data.

Candidates typically face two main scenarios within a 70-minute window:

• Ecosystem Building: Always the first game. You create a balanced ecosystem by selecting species that can survive together based on energy flows, calorie requirements, and environmental factors.
• Redrock Study Task or Plant Defense: The second game varies. Redrock focuses on data analysis and hypothesis testing, while Plant Defense emphasizes strategic thinking and resource allocation.

McKinsey may occasionally test alternative modules like Migration Management, Disease Management, or Disaster Management, though these appear less frequently. Each version requires you to analyze incomplete information, test assumptions, and make trade-offs, skills that mirror consulting work.

The game’s format tracks how you solve problems, not just whether you get the right answer. It records every decision and mouse movement to assess your:

• Information prioritization
• Logical sequencing
• Adaptability under time pressure
• Ability to synthesize complex systems

Success in the McKinsey Problem Solving Game comes from balancing accuracy with efficiency. Spending too much time analyzing every detail can be as damaging as making rushed choices. The key is structured reasoning, approaching each challenge as if it were a client problem, with a clear hypothesis and measurable outcomes.

What Skills Does the McKinsey PSG Actually Test

The McKinsey PSG tests five key cognitive skills: critical thinking, decision-making, situational awareness, systems thinking, and meta-cognition. Each mini-game evaluates how you process complex information, prioritize data, and make logical choices under time pressure, skills that mirror real consulting challenges and predict success in McKinsey’s problem-solving environment.

The McKinsey Problem Solving Game, or PSG, is designed to measure your thinking process, not your academic knowledge. McKinsey uses it to evaluate how effectively you can interpret information, identify relationships between variables, and make strategic decisions with incomplete data.

Here are the five cognitive skills McKinsey assesses through the game:

• Critical thinking: The ability to draw logical conclusions and form sound judgments from diverse data.
• Decision-making: Evaluating multiple options and choosing the most effective course of action.
• Situational awareness: Understanding how different factors interact and anticipating the outcomes of your choices.
• Systems thinking: Recognizing cause-and-effect relationships within complex, interdependent systems.
• Meta-cognition: Managing your own thought process, including hypothesis testing, note-taking, and reflection.

Each skill connects directly to consulting work. For instance, in the Ecosystem Building module, you demonstrate systems thinking by balancing energy flow between species. In the Redrock Study Task, you show decision-making and critical thinking as you analyze research data to form conclusions.

McKinsey evaluates both process score (how you think) and product score (your final results). This dual approach helps identify candidates who can reason effectively even if they don’t achieve a perfect outcome.

Ultimately, mastering these skills is about more than passing the game, it prepares you for the structured thinking McKinsey values in its consultants. The best performers approach every scenario with a clear framework, logical steps, and an ability to adapt as new information emerges.

How Difficult Is the McKinsey Solve Game

The McKinsey Solve Game is challenging because it blends analytical reasoning, time pressure, and uncertainty. Most candidates find it harder than traditional tests since every move is tracked to measure decision quality, efficiency, and adaptability. Success depends on structured thinking, practice, and staying calm when facing incomplete or evolving information.

The McKinsey Solve is intentionally designed to be demanding. It replicates real consulting scenarios where data is incomplete, time is limited, and multiple solutions may seem viable. Unlike standard aptitude tests, it doesn’t rely on fixed questions, you must analyze patterns, test hypotheses, and adapt strategies dynamically throughout the game.

Several factors contribute to the game’s difficulty:

• Dynamic variables: Every test instance is different, so memorization doesn’t help.
• Time constraint: You have 70 minutes total, often leaving little margin for error.
• Cognitive load: You must juggle multiple data points, relationships, and feedback loops simultaneously.
• Behavioral tracking: McKinsey evaluates how you think, not just what you choose, making random guessing ineffective.

Candidates often underestimate how mentally intense the experience feels. Each decision, such as selecting species in Ecosystem Building or analyzing research data in Redrock Study, requires logical trade-offs. If you lose focus or overanalyze, time quickly becomes your biggest enemy.

The key to managing difficulty lies in preparation. Familiarize yourself with each mini-game type, develop quick note-taking habits, and refine your mental math skills to reduce stress during gameplay. The goal isn’t perfection but consistency and structure, traits that mirror the analytical discipline McKinsey looks for in consultants.

Time Management Tips to Master the McKinsey PSG

Effective time management is crucial for performing well in the McKinsey PSG. Divide your 70 minutes wisely, spend no more than 30 to 35 minutes per mini-game, track the clock regularly, and plan your approach before starting. Structured pacing helps prevent rushing decisions and ensures enough time for review before submission.

Time pressure is one of the most common reasons candidates underperform in the McKinsey Problem Solving Game. Without a pacing plan, you can easily spend too long analyzing data in the first game and run out of time for the second. The test measures how you prioritize and manage limited resources, time being the most valuable one.

Here are key time management strategies to help you stay in control:

• Set time checkpoints: Aim to complete each mini-game in under 30 minutes to leave extra time for review.
• Monitor your progress: Glance at the timer every few minutes to stay aware without losing focus.
• Plan before you act: Spend the first two minutes reviewing objectives and constraints before diving into data.
• Avoid perfectionism: Remember that McKinsey values efficiency and logical reasoning more than flawless outcomes.

For example, in Ecosystem Building, you could allocate 10 minutes to mapping species relationships and another 15 to final adjustments. In Redrock Study, limit your deep data exploration, filter for the most relevant variables early, then move quickly to forming and testing hypotheses.

Finally, simulate time pressure during your preparation. Practicing with mock tests or timed scenarios builds familiarity and helps you develop the discipline needed to perform calmly and efficiently under real conditions.

Setup and Technical Preparation Before the Solve Game

Before starting the McKinsey Solve Game, ensure your computer, internet, and browser meet the required technical standards. A stable connection, updated software, and distraction-free setup help prevent performance issues or disqualifications. Completing McKinsey’s system check in advance ensures your test runs smoothly from start to finish.

Technical preparation can make or break your McKinsey Solve performance. Because the game runs on a browser-based 3D engine, even small technical glitches, like lag or dropped connections, can affect how your results are recorded. McKinsey rarely allows retests, so verifying your setup in advance is essential.

Follow these key setup guidelines before test day:

• Use a reliable computer: Avoid older devices with low processing power or limited RAM. The test is graphics-intensive and may lag on weak systems.
• Update your browser: McKinsey recommends the latest versions of Chrome, Firefox, or Edge for optimal compatibility.
• Check your internet connection: Aim for a stable connection of at least 5 Mbps to avoid interruptions during gameplay.
• Disable background apps: Close unnecessary tabs, downloads, and software that might drain memory or cause lag.
• Ensure full-screen mode: This improves game visibility and prevents accidental window switching.

McKinsey also provides a technical check link before your scheduled test. Run this at least one day early to confirm that your system meets all requirements. If any error appears, contact the support team immediately, waiting until test time can risk your session being invalidated.

Beyond hardware, your environment matters. Choose a quiet, well-lit space where you can focus for the full 70 minutes without interruptions. Keep your notepad and pen ready for quick note-taking; this reduces reliance on digital tools and helps maintain concentration.

Candidates who invest 10 minutes verifying their setup often outperform others simply because they experience fewer disruptions. Treat your technical prep as part of your overall test strategy, not an afterthought.

How to Take Notes and Organize Information Effectively

In the McKinsey Solve, organized note-taking is essential for filtering key data and forming logical hypotheses. Use pen and paper instead of spreadsheets to map relationships, calculate values, and track progress. This helps maintain focus, minimize distractions, and improve accuracy throughout the McKinsey Problem Solving Game.

The McKinsey Solve involves handling large amounts of complex information. Without a structured approach to note-taking, it’s easy to lose track of relationships or make avoidable calculation errors. Unlike case interviews, there’s no room to pause and backtrack, so effective organization becomes your greatest advantage.

Here’s how to manage your notes efficiently during the test:

• Start with a structure: Divide your paper into sections for data, hypotheses, and decisions. This makes it easier to revisit ideas quickly.
• Summarize, don’t transcribe: Write only essential numbers and patterns. Copying every detail wastes time and breaks your flow.
• Use symbols and abbreviations: Short codes (like “C” for calories or “E” for energy) help speed up data tracking in the Ecosystem mini-game.
• Link related data: Draw arrows or simple flow diagrams to visualize dependencies, especially for systems-based games like Ecosystem or Plant Defense.
• Review before deciding: Scan your notes for consistency to catch gaps or contradictions before finalizing your answers.

Although McKinsey allows spreadsheets, many candidates find switching between windows inefficient and distracting. Spreadsheets may slow down your browser, especially on low-memory systems. Pen and paper, on the other hand, provide flexibility, you can sketch maps, food chains, or quick equations without breaking focus.

Practicing your note-taking method before the test is equally important. Try simulating a mini-game scenario and time how long it takes to extract key information. This helps you develop a personal system for filtering noise, prioritizing data, and maintaining logical flow, three critical habits McKinsey measures indirectly during the game.

Good note organization doesn’t just support accuracy; it reflects the structured, methodical mindset consultants rely on daily. Treat it as part of your overall strategy, not a side task.

Proven Strategies for Each McKinsey Mini-Game

Each McKinsey Solve mini-game tests different cognitive skills, requiring tailored strategies. Focus on sustainability in Ecosystem Building, logical analysis in Redrock Study, and layered defense planning in Plant Defense. Mastering each scenario’s unique logic helps you demonstrate structured thinking, adaptability, and decision-making under time constraints.

The McKinsey Solve includes several mini-games, each designed to assess specific cognitive abilities under pressure. Understanding the mechanics and goal of each game allows you to approach them strategically rather than reactively.

Here’s a breakdown of the most common mini-games and proven strategies to tackle each effectively:

1. Ecosystem Building (always included)

• Prioritize species that provide more calories than they consume to sustain the food chain.
• Match animals to compatible habitats and avoid overlapping food sources.
• Build from top to bottom: select apex predators last after ensuring sufficient prey.
• Keep the system balanced rather than perfect, aim for survival, not optimization.

2. Redrock Study Task (data analysis and logic)

• Quickly identify which data tables or sources are relevant to the question.
• Form a clear hypothesis before diving into details to avoid analysis paralysis.
• Use elimination: discard irrelevant clues early to save time.
• Keep your Research Journal structured by labeling and grouping related findings.

3. Plant Defense (strategic resource allocation)

• Defend the central plant from predators by focusing protection inside-out.
• Observe predator movement patterns before committing resources.
• Use strong defenders on frequently attacked squares and adjust placement as waves evolve.
• Prioritize survival efficiency, not total elimination.

Other less frequent mini-games like Migration Management, Disease Management, and Disaster Management occasionally appear in pilot rounds. The key is to maintain composure and rely on hypothesis-driven thinking. Even if you’re unfamiliar with a module, apply a consulting mindset: define the objective, identify key variables, test assumptions, and decide logically.

Across all games, success depends on your ability to:

• Recognize data patterns and interdependencies.
• Manage limited time while testing multiple scenarios.
• Stay adaptable when facing uncertainty or missing data.

Practicing these structured strategies before the assessment ensures that your approach remains consistent even in unpredictable modules. The goal is not to predict every scenario, but to train how you think, the true focus of the McKinsey Problem Solving Game.

Common Mistakes That Lead to Low PSG Scores

In the McKinsey PSG, common mistakes include poor time management, skipping the tutorial, disorganized note-taking, and overanalyzing data. Candidates also lose points by ignoring key variables or failing to test hypotheses systematically. Avoiding these pitfalls helps you maintain structure, efficiency, and a higher overall problem-solving score.

Even well-prepared candidates often fall into avoidable traps during the McKinsey Problem Solving Game. Since the PSG evaluates both your reasoning process and final outcome, errors in approach can lower your process score, even if your final answers seem correct.

Below are the most frequent mistakes that reduce scores, and how to avoid them:

• Rushing through the tutorial: Many players skip instructions to save time but then misinterpret mechanics mid-test. Always take a few minutes to understand task rules before starting.
• Spending too long on one task: Getting stuck on details in Ecosystem or Redrock wastes valuable time for the second module. Stick to your pacing plan.
• Ignoring key metrics: Overlooking calorie balance, terrain conditions, or predator movement leads to logical inconsistencies. Always double-check core variables.
• Unstructured note-taking: Failing to organize data causes confusion when switching between datasets. Use a clean layout with categories and symbols.
• Overreliance on instinct: Guessing without testing hypotheses often leads to logical gaps. Always verify your reasoning, even under time pressure.
• Neglecting the review stage: Candidates who rush to submit without checking errors risk small calculation mistakes that impact results.

Each of these errors reflects habits that McKinsey consultants work to avoid in real client projects. The PSG is designed to reveal whether you can balance analysis and execution under stress, a key indicator of consulting readiness.

To improve, review your mock test performance and identify patterns in how you make decisions. Did you lose time rereading data? Miss a key variable? A structured post-analysis is as valuable as the practice itself.

Avoiding these mistakes doesn’t guarantee a perfect score, but it ensures your thinking process aligns with what McKinsey values: logical structure, precision, and self-awareness.

Can You Use Tools Like Excel During the McKinsey Solve

McKinsey allows using basic tools like Excel or calculators during the McKinsey Solve, but they offer little advantage. Switching between tabs wastes time and can slow your system. Most candidates perform better with pen and paper for quick calculations, note-taking, and mapping relationships within the Problem Solving Game.

One of the most common questions candidates ask before the test is whether they can use Excel or other digital tools to speed up calculations and data organization. While McKinsey technically allows these tools, their usefulness during the Solve is limited by time, interface, and focus constraints.

Here’s what you need to know about tool usage:

• Excel is permitted but inefficient: Switching between the browser and Excel interrupts your focus and can delay your reaction time in time-sensitive scenarios.
• System performance matters: On mid-range or older computers, running both the game and Excel can cause lag or even crashes, especially during high-data modules like Redrock.
• Note-taking flexibility: Pen and paper are more practical for drawing diagrams, visualizing relationships, and calculating on the fly.
• Built-in calculator use: In Redrock, use your keyboard’s numpad or the on-screen calculator for quick math, both are faster than switching applications.

The key advantage of handwritten notes lies in speed and structure. You can easily sketch out food chains for Ecosystem Building or grid layouts for Plant Defense without tab switching. This keeps your attention fully within the game environment.

If you’re comfortable multitasking and have a powerful computer setup, Excel might help with basic arithmetic or data tables, but it’s not essential to success. McKinsey’s focus is on how you think, not what tools you use. Clarity of reasoning always outweighs technical shortcuts.

Ultimately, choose whichever method keeps you most organized and focused. The best candidates rely on simplicity, minimizing distractions, maintaining consistent structure, and using only what enhances performance.

How to Prepare Strategically for the McKinsey Solve Game

To prepare for the McKinsey Solve Game, practice with simulations that mirror its logic, build core skills like critical thinking and time management, and review common mini-game mechanics. Focus on strategy over memorization, understanding how to structure decisions and test hypotheses will help you perform consistently across any McKinsey PSG scenario.

Preparation for the McKinsey Solve goes beyond reading about the game. The best candidates develop habits that improve both speed and reasoning quality under pressure. Since the test evaluates how you think, your preparation should target analytical structure, focus, and adaptability rather than rote memorization.

Here’s how to prepare effectively:

• Familiarize yourself with game mechanics: Learn the objectives of key mini-games like Ecosystem Building, Redrock Study, and Plant Defense. Knowing their logic reduces hesitation during the real test.
• Practice under timed conditions: Simulate the 70-minute test window to train your pacing and decision-making under time pressure.
• Sharpen mental math: Strengthen quick calculations, especially useful for calorie and resource comparisons in Ecosystem and Redrock.
• Refine your note-taking system: Build a layout for hypotheses, data, and outcomes so you can think visually and avoid confusion.
• Analyze your practice results: After each simulation, review your process to find patterns in where you lose time or misjudge information.

McKinsey evaluates both process score and product score, so your preparation should emphasize structure. Always approach problems with a hypothesis-driven mindset: define the question, identify data, test assumptions, and draw clear conclusions.

If you’re short on time, focus on high-impact drills, data interpretation, mental arithmetic, and logical reasoning tasks that reflect the PSG’s analytical nature. These exercises prepare you not only for the game but also for case interviews, which rely on the same structured problem-solving approach.

Finally, remember that confidence grows with familiarity. The more you practice decision-making frameworks and note organization, the more naturally you’ll perform during the actual assessment. Preparation isn’t about mastering the game, it’s about training your mind to think like a McKinsey consultant.

Frequently Asked Questions

Q: How do I know if I passed the McKinsey Solve game?
A: You’ll know you passed the McKinsey Solve game if you’re invited to the next interview round. McKinsey doesn’t release PSG scores, but strong performance in the gamified assessment, especially in systems thinking and decision-making, usually leads to a quick follow-up within one to two weeks.

Q: What is the pass rate for the McKinsey Solve game?
A: The pass rate for the McKinsey Solve game is estimated around 20 to 35%. Only top candidates who demonstrate strong critical thinking, time management, and situational awareness across the mini-games move forward in the hiring process.

Q: What if I fail McKinsey Solve?
A: If you fail the McKinsey Solve, you can typically reapply after 12 to 18 months. Use that time to refine your McKinsey Solve preparation, focus on hypothesis testing, quick mental math, and structured problem-solving to improve your next PSG performance. 

Q: Does everyone get McKinsey PSG?
A: Not everyone gets the McKinsey PSG. The digital assessment is usually sent to applicants who pass the initial resume screen, often for early-career or consulting roles like Business Analyst or Associate.

Q: How long does McKinsey take to respond after PSG?
A: McKinsey typically takes one to two weeks to respond after the PSG test. Response time may vary by region or recruiting cycle, so if you don’t hear back within three weeks, it’s fine to follow up with the recruiting team.