McKinsey Sustainable Futures Lab (SFL): Complete 2026 Guide
If your McKinsey Solve invitation specifies 85 minutes, you have a third game: the Sustainable Futures Lab. It comes after Redrock Study and Sea Wolf, takes 20 minutes, and is unlike either of the other two modules in almost every way.
There is no math. There is no optimisation. There are no clearly correct answers in the traditional sense. The Sustainable Futures Lab — often shortened to SFL — is McKinsey testing something they've always cared about but couldn't measure digitally until now: how you actually behave as a consultant when the problem in front of you isn't data, but people.
You may also see it referred to as the Sustainable Future Lab (singular), the McKinsey third game, or the McKinsey behavioural module. These all refer to the same assessment.
One important caveat before going further. The SFL is still in a phased global rollout. As of mid-2026, candidates in the US, Canada, Germany, the Middle East, and Southeast Asia are reporting it on 85-minute invitations. It is not yet universal. If your invitation email specifies 65 minutes, you will not face the SFL — put your preparation time into Redrock and Sea Wolf. Only prepare for the SFL if your invitation confirms it.
Why McKinsey built the SFL
McKinsey consultants spend a minority of their time doing quantitative analysis. They spend most of their time managing people: clients who push back, team members who disagree, stakeholders with conflicting interests, and deadlines that force hard trade-offs with no clean answer.
Redrock and Sea Wolf do an excellent job of measuring how clearly you think. They don't measure how you'd behave when the problem is people rather than data. The SFL fills that gap.
The closest analogue in McKinsey's traditional hiring process is the Personal Experience Interview — the part of the case interview where you discuss how you've handled real leadership and collaboration challenges. The SFL does something similar, but digitally, at scale, and before any human time is invested. Instead of telling an interviewer how you handled a conflict, you navigate one in real time.
This is not a return of the Ecosystem Building game that was phased out in 2025. That was an analytical food-chain optimisation puzzle. The SFL is an entirely different format — a situational judgement exercise embedded in a connected, evolving scenario.
The format
20 minutes, 13 sequential questions, one connected scenario.
The scenario is sustainability-themed — consistent with the ecological framing throughout Solve — and typically places you as a member of a research or advisory team working on an environmental project. The specific setting rotates across coastal habitat, urban climate, freshwater, and land-use contexts. What stays constant is the structure.
Two intro screens. Before the questions begin, you receive the mission briefing: the situation, your role, the team composition, the deadline, and the core constraints. Read these carefully. Everything that follows happens inside this context, and later questions will reference details introduced here.
Question 1 — drag-and-drop priority ranking. You're given four early actions and asked to order them from highest to lowest priority. This tests whether you take a hypothesis-driven approach — form a view early, then gather supporting information to test it — or whether you default to collecting data before committing to any direction. McKinsey's approach to consulting is hypothesis-driven. Establishing direction early is consistently rewarded.
Questions 2–13 — single-choice scenario decisions. Each question presents a new situation in the evolving mission: a team disagreement, a piece of new evidence, a stakeholder request, a resource conflict, a deadline pressure. You choose one option from 2–4 available responses, each written as a full paragraph describing a specific course of action ("You suggest..." or "You decide...").
After each answer, a consequence screen shows what changed in the mission as a result of your choice. The scenario then advances based on what you decided. Read each consequence screen carefully — later questions often reference what your previous decisions caused.
The interface is deliberately plain. There is no dashboard, no stakeholder satisfaction meter, no visible score. Just scenario text, options, and consequences.
With 13 questions in 20 minutes, you have under two minutes per question. The text is dense. Reading speed and decisiveness are both real constraints.
What McKinsey is actually measuring
The SFL evaluates you across five core traits, plus a dimension that cuts across all of them: ethical judgment.
Prioritisation
Can you establish direction without waiting for perfect information? Strong candidates form a hypothesis early and use incoming information to test and refine it — not to delay committing. Weak candidates wait until they feel certain before acting, which in a consulting context means never moving fast enough.
In practical terms: when the scenario presents an early decision about where to focus, the rewarded answer is usually the one that sets a clear working direction rather than the one that maximises information gathering before any direction is set.
Decision-making under uncertainty
Can you commit to a proportionate course of action when you don't have everything you'd like? This is closely related to prioritisation but distinct — it's about the quality of the commitment, not just its timing. Strong candidates make reversible decisions with the information available and adjust as more emerges. Weak candidates either stall or overcorrect — either paralysed by uncertainty or recklessly decisive.
Interpreting messy information
Can you read a situation accurately, including what isn't being said explicitly? A team member's hesitation might signal a real methodological concern — or it might signal something personal. A stakeholder's objection might reflect a legitimate risk — or it might reflect a misunderstanding of the analysis. Strong candidates synthesise multiple signals into a clear-eyed read of what's actually happening. Weak candidates take everything at face value or oversimplify.
Balancing trade-offs
Every SFL decision involves a trade-off. Speed versus thoroughness. Stakeholder inclusion versus project momentum. Team cohesion versus decisiveness. Strong candidates acknowledge trade-offs explicitly — even if only in their reasoning — and choose proportionately. Weak candidates reflexively pick the "safest" option to avoid conflict or cost, or reflexively pick the "boldest" option without considering downstream consequences. Both extremes are penalised.
Team and stakeholder effectiveness
Do you bring people along, or do you override them? Do you create an environment where team members contribute their best work, or do you suppress it? Strong candidates are inclusive without being indecisive and influential without being controlling. They hear concerns before dismissing them and distinguish between a team member who has a genuine insight and one who is simply resistant. Weak candidates bulldoze disagreement, silence quieter voices, or conversely defer to whoever pushes hardest regardless of the merit of their position.
Ethical judgment
The SFL occasionally surfaces situations where one available option involves something that would be ethically problematic — cutting corners in a way that harms people outside the project's scope, misrepresenting findings to stakeholders, prioritising short-term outcomes in ways that breach reasonable standards of conduct. These options are not presented as obviously wrong. They are framed as pragmatic, efficient, or expedient.
McKinsey is not only assessing whether you can balance competing priorities among reasonable options. It is also assessing whether you recognise when an option crosses a line — and decline to take it, regardless of the short-term efficiency it appears to offer. Candidates who select options involving clear ethical violations, or who consistently deprioritise the wellbeing of people outside the immediate project team, signal a judgment gap that no amount of analytical performance compensates for.
What the "right" answer actually looks like — and why
The SFL is explicit that there are no perfect answers. That is true in the sense that most options are reasonable and multiple approaches can be defensible. It is misleading if it suggests that all answers are equivalent. Some answers are clearly stronger than others, and they share a consistent underlying logic.
McKinsey is looking for candidates who think in second-order effects. Almost every SFL decision has an obvious first-order consequence and a less obvious second-order consequence. The options that look efficient on the surface often create downstream problems; the options that seem cautious often prevent compounding issues later. Candidates who evaluate only what happens immediately tend to choose differently — and worse — than candidates who think one step further.
Three examples illustrate the pattern:
Rushing vs. pausing. Your team is close to a deadline. New data arrives suggesting your current approach may be missing something. One option is to press on and deliver on time. Another is to pause briefly and reassess.
Pressing on looks decisive. But if the new data is valid, your deliverable is wrong. Wrong deliverables damage client trust, require rework, and ultimately cost more time than the pause would have. The second-order effect of rushing is worse than the first-order cost of pausing. The SFL consistently rewards candidates who recognise this — not because caution is always right, but because a wrong deliverable is a worse outcome than a delayed one.
Overriding team input. A team member raises a concern about the methodology. You're confident they're wrong and the deadline is tight. One option is to acknowledge the concern but proceed. Another is to dismiss it and move on.
Dismissing it looks efficient. But an unheard team member disengages. Their future contributions decline. Morale drops. The quality of the team's collective work deteriorates over the remainder of the project. The first-order gain in speed is outweighed by the second-order cost to team performance — and ultimately to the quality of the deliverable. Consulting teams that suppress internal dissent make worse decisions, not better ones.
Ignoring public stakeholders. Your project has public impact. Affected communities want to be involved. One option is to complete the internal analysis first, then present findings. Another is to engage stakeholders earlier, even if it slows the process.
Proceeding without engagement is faster in the short term. But if the work lands with communities who feel excluded from a process that affects them, backlash delays or derails implementation. Regulatory scrutiny increases. Reputational risk rises. The first-order efficiency of skipping consultation is consumed by the second-order cost of stakeholder friction. The better answer engages proportionately — not exhaustively, but enough to prevent the predictable downstream problem.
The pattern across all three: the stronger answer is rarely the most immediately efficient. It's the one that sustains team performance, stakeholder trust, and project quality over the full arc of the mission. Candidates who consistently choose immediate efficiency over downstream sustainability will see a weak SFL profile, even if their individual answers seem defensible in isolation.
One important nuance: this does not mean always being cautious or always consulting everyone. Endless consultation is also penalised. Stalling when a decision needs to be made is a weak pattern. The game rewards proportionate judgment — knowing when speed matters more than inclusivity, and when the downstream cost of exclusivity outweighs the immediate gain.
Consistency — the scoring dimension most candidates miss
The SFL does not score 13 independent questions. It scores a pattern across all 13.
Two candidates who choose the same answer on question 7 may receive meaningfully different overall assessments depending on what they chose in questions 1 through 6. Inconsistency is penalised — not because consistency is intrinsically virtuous, but because inconsistent decision-making signals an absence of coherent judgment. A candidate who overrides team input in question 3, then emphasises psychological safety in question 8, without a clear rationale for the shift, looks like someone who is reacting to each situation independently rather than applying a stable decision framework.
Before you begin, form a clear mental model of how you approach the recurring tensions in the SFL: team input versus momentum, evidence quality versus deadline pressure, stakeholder inclusion versus project pace. Apply it consistently. When new information arrives and the scenario shifts, adjust proportionately rather than reversing course entirely.
The consequence screen after each question is your most important feedback signal during the assessment. Read it slowly enough to understand what changed. If your last decision created a complication, the appropriate response is a proportionate adjustment in the next question — not a dramatic overcorrection that contradicts your earlier reasoning.
Common mistakes
Scanning for the right-sounding answer and picking fast. SFL rewards reading the scenario first, understanding the trade-off, then deciding. Picking the answer that sounds good in isolation — without reading it against the scenario context — is the most common error.
Reflexively picking the safe option. "Gather more data before deciding," "consult everyone before proceeding," "take no action until certain" all sound responsible. They consistently signal indecision and stalling when applied to situations that actually require a proportionate decision.
Reflexively picking the bold option. "Move forward immediately," "override the disagreement," "prioritise the deadline at all costs" all sound decisive. They consistently miss the downstream costs that the SFL is designed to surface.
Ignoring the consequence screen. It is the game's most direct signal about what your decision actually caused. Later questions reference it. Skipping it means entering the next question without understanding what situation you're actually in.
Treating the team as background. Team dynamics in the SFL are not decorative. Answers that silence quieter voices, bulldoze stakeholders, or deprioritise team morale generate downstream complications that the scenario will surface — often within one or two questions.
Changing reasoning approach mid-game. If you apply different logic to similar situations in questions 4 and 9, the inconsistency registers as a weak pattern even if both individual answers seem reasonable.
Ignoring deadlines in the scenario context. Some answers that sound thorough are simply too slow for the time window the mission describes. The briefing screen sets the constraints. Options that are thoughtful but infeasible given those constraints are not strong answers.
Selecting ethically questionable options because they sound pragmatic. The SFL occasionally includes options that would cause harm outside the immediate scope of the project or that misrepresent findings to stakeholders. The framing makes them sound efficient. They are not defensible answers.
How to prepare
The SFL is genuinely harder to prepare for mechanically than Redrock or Sea Wolf, because it tests judgment rather than skills you can drill in isolation. But it is not unprepared-for-able. What preparation develops is familiarity with the format and calibration of your intuitions about what proportionate consulting judgment looks like in practice.
Understand the format before test day. The consequence screen structure and the connected scenario are unfamiliar if you've never seen them. The first time you encounter a consequence screen should not be during the real assessment. Run at least two or three full SFL simulations under time pressure.
Read McKinsey's public material on their values and approach. Not to memorise talking points, but to calibrate your sense of how McKinsey expects consultants to balance speed, quality, client relationships, and team dynamics. The SFL is testing whether your instincts align with a high-performing consulting environment.
Train the habit of second-order thinking. When you encounter decisions in everyday work or practice scenarios, explicitly ask: what happens downstream if I choose this? What does the team's dynamic look like in two weeks if I override this disagreement today? This is a trainable habit, and it transfers directly to SFL performance.
Practise situational judgment questions. SHL situational judgment tests and GMAT Integrated Reasoning questions have a different format but build the same underlying skill: reading a situation, identifying the trade-off, and selecting proportionately rather than reactively.
Proportion your preparation appropriately. If your test is a week away, spend 70% of your prep time on Redrock and Sea Wolf. The SFL is 20 minutes of a total 85. If you have several weeks, give the SFL more attention once you're solid on the other two modules. Don't let it crowd out preparation for the higher time-weighted modules.