McKinsey Sustainable Futures Lab: a practice guide to the newest Solve game

Where it sits in the assessment

The Sustainable Futures Lab is the third game, after Red Rock Study and Sea Wolf, and it runs about 20 minutes. It only appears on the longer invitation: a 65-minute invite means Red Rock and Sea Wolf; an 85-minute invite adds Future Lab. Your invitation email states the duration, so you can tell in advance exactly which games you'll face.

Because it only launched in March 2026, be careful with older advice. Reddit threads and guides from before 2026 don't mention it at all, and some describe the retired Ecosystem game as if it were still on the test. It isn't; it was dropped in 2025.

The format: 13 prompts, one evolving story

You lead an environmental research team through a single continuous scenario:

1. One priority-ranking prompt: a drag-and-drop ordering of objectives that sets your baseline.
2. Twelve branching decisions: each presents a situation with four options. Your choice triggers a consequence and reshapes the situation you face next. Two candidates who diverge at decision three are living different stories by decision eight.

Five stakeholders (think funders, partners, your own team) react to what you do. Their relationships with you shift as the scenario unfolds, and later decisions land differently depending on the goodwill you've built or burned.

How it's scored: consistency, not correctness

There is no mathematically right answer, which is exactly why people flounder. What's being measured is whether your judgment hangs together across five dimensions: prioritization, deciding under uncertainty, reading messy information, balancing trade-offs, and handling stakeholders.

Flip-flopping is the failure mode. If you play the cautious consensus-builder for four decisions and then lurch into unilateral risk-taking because an option looked clever, the inconsistency is the signal, not either choice on its own.

What a decision actually looks like

To make "consistency" concrete, picture one branching decision. Your field team reports early, unverified data suggesting a restoration site is failing. You're given four options:

1. Halt the project and reallocate the budget immediately.
2. Commission a two-week independent study before deciding.
3. Push forward on the original plan and monitor.
4. Tell the funder and let them make the call.

None of these is "correct." What matters is that it fits the leader you've already been. If your priority ranking put "evidence quality" at the top and you commissioned studies in two earlier decisions, option 2 is consistent. If you've been the decisive, act-on-partial-signal leader all game, option 1 or 3 fits, and suddenly deferring to the funder in option 4 would read as a break in pattern. The assessment isn't grading the choice; it's watching whether your choices trace one coherent philosophy across all twelve.

How the five stakeholders work

Five relationships run underneath the whole scenario: typically your team, a funder, a partner organization, the public, and leadership. Each starts at a neutral level and moves up or down with your decisions. The mechanic that catches people out: a relationship you've neglected can quietly close off options later. Burn the funder early and a decision that needed their backing may not be available when you reach it. You can't keep all five happy (the game is built so that pleasing one often costs you another), so the goal isn't maximum goodwill everywhere, it's spending goodwill in a pattern that matches your stated priorities.

The mistakes that quietly tank the score

• Choosing the "smartest-looking" option each time. Optimizing every decision in isolation produces a jagged, inconsistent path, exactly what the scoring penalizes. Pick a posture, then choose the option that fits it, even when a flashier one is on the table.
• Ignoring the consequence text. After each decision the game tells you how stakeholders shifted. That's the board state, not flavor text. Skipping it means walking into later decisions blind.
• Trying to keep every stakeholder happy. Impossible by design. Consistent trade-offs beat universal approval every time.
• Contradicting your own priority ranking. The drag-and-drop that opens the game is a public commitment. If you ranked stakeholder trust first and then repeatedly sacrifice it for speed, that gap is the inconsistency being measured.

How to prepare

• Pick a posture in the first two prompts, then hold it. Decide what kind of leader you're being (transparent, evidence-first, stakeholder-balancing, whatever feels natural) and let that filter every later choice. Your priority ranking in prompt one is a commitment; treat it as one.
• Read the consequence text. Each decision's outcome tells you how stakeholders moved. That's not flavor. It's the state of the board.
• Don't optimize for being liked. Keeping every stakeholder happy at all times isn't possible by design. Trade-offs are the point; consistent trade-offs are the score.
• Run it more than once. The mechanics (branching, stakeholder tracking, pacing across 12 decisions) stop costing you attention by the second or third run, which frees you to actually think. That's the entire case for practicing it at all.

Keep going

Read the full McKinsey Solve guide, or go deeper on the other two games: the Red Rock Study walkthrough and the Sea Wolf strategy guide. When you're ready, play Future Lab.