Sustainable Futures Lab guide: the 3 days, stage by stage
What the 30-minute Sustainable Futures Lab in the McKinsey Solve is like: three simulated days, a team of four people and four stages per day.
Practice Sustainable Futures Lab for free
The Sustainable Futures Lab is the judgment game in the Solve. There are no calculations: you coordinate a team of four researchers over three simulated days, in about 30 minutes. What seems to count is who you ask, how you distribute the team, how you respond to their problems and how well you read each person.
McKinsey doesn’t publish the rules or the scoring of this game. Everything that follows comes from prep guides and candidate reports, which disagree on several details.
What it is and what it measures
The Sustainable Futures Lab (several guides write it as “Sustainable Future Lab”) is the newest game in the Solve and comes last, after Redrock and Sea Wolf. You are put in charge of a fictional environmental research team. You don’t need to know any science: the topic is just the setting.
The pieces of the game are always the same:
- 4 researchers: an ecologist, a biologist, a habitat planner and an engineer.
- 4 workstations: water, plants, animals and communications.
- 3 simulated days, and each day repeats four stages: explore, assign, support and reflect.
There is no calculator and there are no charts. What is assessed is behavior, and each stage seems to look at something different:
| Stage | What you do | What it seems to look at |
|---|---|---|
| Explore | You spend a few requests on asking questions | Which information you prioritize |
| Assign | You place each person at a station and give a reason | Whether you match people to what is needed |
| Support | You respond to the problems the team brings you | Your judgment when facing a dilemma |
| Reflect | You say how each person ended the day | Whether you paid attention to your team |
That reading comes from the guides, not from McKinsey. What they do agree on is that there is no single right answer per screen and that consistency across the whole game matters more than any one decision.
A word of warning: many guides online still describe an earlier format, 20 minutes long and text only. This guide and the site’s simulator cover the three-day format.
When you get it
The total length of your invitation is the best clue to how many games you will take.
| Invitation | Games |
|---|---|
| About 65 minutes | Redrock and Sea Wolf |
| About 95 minutes | Redrock, Sea Wolf and the Sustainable Futures Lab |
Always confirm the length in your own email, because McKinsey changes the format without notice.
Before day 1
The game starts with a tutorial, and according to the guides the clock doesn’t run while you do it. Use all of it: it is the only moment to learn the interface without spending time.
Then comes an opening exercise: you rank, by dragging them, the questions you would ask the team about the project, and you receive the answers. That gives you the context you will use for the three days: what has to be delivered, who is who, what each station does and what constraints the work has.
Two things on the screen are worth locating right away:
- The goal for the day. Each day starts with a different objective, and it is the filter for everything you decide that day.
- The notes panel. It keeps what the people and the stations have told you. It is your memory when the reflect stage arrives.
The four stages of each day
1. Explore
You have a limited number of requests for asking questions, and they won’t cover everything. There are usually three per day, and there are reports of days with only two (for example, the third). You have to use them all before moving on to assign. Each researcher and each station offers you two questions, and you choose one. According to the guides, a researcher answers only one question per day and not all of them are available every day.
The questions are of two kinds: about the work (what is needed, what could go wrong) and about the person (how they are, where they think they contribute most). Both are useful. The goal for the day tells you which to prioritize.
2. Assign
You drag each researcher to a station. A station can be left empty or have two people. At the start, each researcher is at the station that matches their experience, and the placement carries over from one day to the next if you don’t change it.
When you move someone, the game asks you to choose the reason from a fixed menu. The guides suggest treating that reason as part of your answer: it should fit what you actually found out while exploring.
3. Support
The researchers bring you work and team dilemmas, and you choose how to respond. The options are paragraphs, not one-line labels, and you have to read them in full.
Sometimes several problems arrive at once and you decide which to deal with first. According to the guides, that order matters too: what has a deadline goes before what can wait.
4. Reflect
At the end of the day you say how each researcher is doing. There is an “I don’t know” option, and using it when you really have no information is more consistent than guessing. What you know about each person comes from what they answered when you explored, how they reacted when you assigned them and how their problem ended.
What changes from one day to the next
The guides describe a progression in the goals:
- Day 1: the people. Understand what each researcher needs in order to work well.
- Day 2: the stations. Cover what each station asks for that day.
- Day 3: the balance. Take care of both at once, with the final deadline looming.
On top of that, what you did carries over: people stay at the station where you left them, and what happened with each one is the context for the following day.
How to decide well
- Read the goal for the day before spending a request. If the day is about people, ask the people. If it is about stations, start with the stations.
- Ask how people are doing, too. It’s easy to spend everything on tasks and reach the reflect stage knowing nothing about anyone.
- Only move someone with a reason. Every move has to respond to a need at the station or to something the person told you. If you have no reason to move someone, leave them where they are.
- Match the reason to what you know. The reason you choose has to be true according to the information you gathered.
- In dilemmas, look for the middle path. Moving forward with what there is and leaving room to correct course is usually better than asking for more analysis or imposing a decision.
- Let the person solve their own problem. Options where you decide for them, or speak in their place, are usually weaker than those that help them do it well.
- Deal first with what has a deadline. If several problems arrive, start with the one that is due soonest.
- Don’t guess when you reflect. Answer with what you saw. “I don’t know” is a valid answer.
Time management
Thirty minutes for three days gives you about 10 minutes per day, and each day has four stages. According to StrategyCase, many candidates lose the first day to learning the interface and finish the third in a hurry.
- Learn the interface in the tutorial, which doesn’t use up the clock.
- Budget your time per day. If day 1 goes past 10 minutes, you are using day 3’s time.
- Don’t reread the options looking for the perfect one. It doesn’t exist. Choose the one closest to how you would really act and move on.
- Read every consequence. It takes seconds and tells you how the person ended up, which is exactly what you will be asked at the end of the day.
Common mistakes
- Asking only about tasks and reaching the end of the day with no information about the people.
- Ignoring the goal for the day and playing all three days the same way.
- Moving people without a reason, or choosing a reason that doesn’t fit what they told you.
- Leaving a station uncovered on the day it needed it most.
- Always postponing: asking for more data when the deadline doesn’t allow it.
- Always forcing: deciding quickly and alone, running over people or data.
- Giving in to avoid friction or dropping the uncomfortable issue from the plan.
- Guessing when you reflect instead of using the notes.
- Using up the clock on day 1 and racing through day 3.
How to practice with the simulator
The site’s simulator follows this format: three days, four people, four stations and the four stages, with its own missions. The details the guides don’t settle, such as how many requests you get per day, are the simulator’s own call and are stated on its start screen.
- Play one mission in learning mode: at the end of each stage you see which information was key, which assignment the model suggested and which answer was the strongest.
- Move on to test mode, with the 30-minute clock and no hints.
- At the end, look at your score by stage. If explore or reflect come out low, the problem is attention to the team, not judgment.
- Check your pattern when responding to problems: if you keep drifting the same way (you postpone, force, give in or lose focus), that is the habit to correct.
- Keep an eye on your time per day. The reference is 10 minutes.
The guides agree that this is the most intuitive of the three games and that it shouldn’t take time away from Redrock and Sea Wolf. A couple of timed missions are enough to arrive knowing the interface.
To see all of this in action, the Sustainable Futures Lab solved walks through a full mission, day by day.
Sources
McKinsey doesn’t publish the rules or the scoring, so the information comes from prep sites (all of which sell courses or simulators) and doesn’t always agree.