McKinsey Solve FAQ

Redrock is an interactive, scenario-based case study that tests quantitative reasoning, data interpretation, and structured problem-solving. It is often considered the core of McKinsey Solve because it is the longest and most demanding game. Success depends on maths fundamentals and data interpretation under intense time pressure.

Redrock is broken into four phases:

(1) Investigation: read the case and drag key data into the journal;
(2) Analysis: answer typically three questions, with subquestions, using the case, notes, and calculator;
(3) Report: complete written fill-ins and/or visual chart tasks that synthesise prior work;
(4) Case: answer about six standalone quantitative questions not tied to the earlier narrative.

The Redrock Study is 35 minutes in total. There is no hard time-limits between sections and you can divide the time as you see fit.

Users that have practied with our simulators are typically able to get through the game with plenty of time to spare because they are familiar with the format. Users who are unfamiliar with the test typically spend ~5-10 min reading Investigation, ~12-15 min Analysis, ~5-10 min Report, ~12-15 min Case.

Analysis format can vary: sometimes each question is on its own page and you cannot return after advancing; sometimes all questions are on one page so you can revise before continuing. Most recently we have seen that all the analysis questions are on a single page.

During the Analysis Phase you can access the Investigation text. Once you enter the Report Phase, you cannot return to investigation nor analysis phase; capture what you need in the journal first.

Once you enter the Case Phase, you cannot return to any of the previous phases.

You cannot change answers once you have pressed the submit button and navigated away from the page.

In the latest McKinsey Solve, the three questions of the Analysis Phase appear on the same page. This allows you to read and answer the questions altogether. The advantage of this is that you have a longer window to catch any mistakes you have made before submitting your answers. In Previous formats of the test, you had to submit each question before moving on to the next, meaning you had less time to catch your own mistakes.

In the Report Phase, the Written Report and Visual Report are separate pages and work in a similar way to the Analysis questions. You answers all the questions on the page and then submit it, at which point you can't change your answer.

The Case Phase is unique: each question is on an individual page and must be submitted before moving on to the next question, unable to return nor change you answer. You must continue linearly along the questions and cannot navigate between questions within the phase.

Use the onscreen calculator provided in the game. External calculators or working entirely off-platform can hurt your process score. McKinsey built the in-game calculator into the flow and tutorial to observe methodology, so show your work through their interface.

Process score refers to the metrics that McKinsey factors into your Solve score aside from the answers you submit. We don't exactly know for sure what is included in this, or if it even exists, however given the format being used for the assessment, it is speculated that they play a part in your overall performance.

The journal is your workspace to save draggable case facts, rename entries clearly, reorder, and highlight critical values. Similar to the calculator, the journal can potentially impact your process score so you should actively use it.

Unlike the onscreen calculator – which may prove an inconvenience to use – the journal will actually improve your performance as it decreases cognitive load or the need to manually make notes.

Common pitfalls: Not staying time disciplined and spending too long on a question your stuck on; ignoring journal/calculator; rushing without sense-checking your answers. Keep track of time; use the onscreen tools; sense-check your answers.