Redrock · McKinsey Solve

The McKinsey Redrock study game: complete guide

Updated 2026 · ~8 min read

Overview

Redrock is a case-study-style module within McKinsey Solve. Where Ecosystem tests optimization under constraints, Redrock tests your ability to research a business situation, analyze quantitative data, and synthesize a written recommendation — the core skills of a consultant. You'll be given a fictional business scenario (often a wildlife conservation or research-themed narrative), a document library, and a dataset, and you'll need to answer a series of sub-questions before drafting a short report.

Related: Redrock is one of four Solve modules — see the McKinsey Solve overview for how it fits in, and compare with the optimization-focused Ecosystem and Sea Wolf guides. We don't sell a Redrock solver, but our Ecosystem + Sea Wolf bundle covers the two solvable games.

The three phases

Phase 1 — Investigation

You're given a research objective and a library of documents (articles, memos, tables). You need to identify which sources are relevant to the objective and extract the key facts and figures. Time-box yourself: it's easy to over-read. Aim to extract the data points you need and move on.

Phase 2 — Analysis

You'll answer a series of quantitative sub-questions using the data you collected. These typically involve arithmetic, percentages, growth rates, and basic comparisons. The interface lets you type calculations and select the data points you're using. Show your work clearly — the scoring rewards not just the right answer but a defensible calculation path.

Phase 3 — Report

Finally, you synthesize your findings into a short structured report — typically an executive summary, key findings, and a recommendation. The report is graded on structure, clarity, and whether the recommendation follows logically from the analysis.

How it's scored

  • Accuracy of calculations in the analysis phase.
  • Source relevance — did you pull from the right documents?
  • Report structure and synthesis — pyramid principle, clear recommendation.
  • Time efficiency — how long you took across phases.

Strategy tips

  1. Skim the objective first. Know what you're solving for before you read any documents.
  2. Don't read everything. Pull only what's relevant to the objective.
  3. Write down intermediate numbers. The analysis phase often chains calculations — keep a scratchpad.
  4. Structure the report pyramid-style. Lead with the recommendation, then the supporting findings.
  5. Time-box each phase. A common failure mode is over-investing in investigation and running out of time for the report.

Looking for solvers?

Redrock doesn't have a deterministic "solver" the way Ecosystem and Sea Wolf do — but our Ecosystem and Sea Wolf solvers are great prep for the rest of Solve.