The 30-Minute Sustainable Futures Lab: What Is Reported

Everything about the layout of this format is second-hand. The lab team, the numbers and every worked example below are original and fictional, written to teach decision habits, not to reproduce any screen.

What is the 30-minute Sustainable Futures Lab, and who has reported it?

The 30-minute Sustainable Futures Lab is a candidate-reported version of the third Solve game, first described in late August and September 2026 by people with a 95-minute invitation, in which you lead four researchers over three simulated days; McKinsey has not confirmed it. Reports say you decide who to ask for information, where each researcher works, how to answer their problems and how to read how they are doing.

The evidence is thin and recent. Candidates describe it on public forums and in write-ups that rebuild the screens from their accounts, so the finer details differ between sources. On the official side, McKinsey's Solve page says candidates do not need to prepare, and its August 2025 FAQ says the length of your assessment is in your invitation. That is all McKinsey states that applies.

Do not assume the format is settled. A new version can be trialled for a while, then adjusted or dropped, and the public record is only weeks old. The dated Solve update log tracks changes as they are reported, and the Sustainable Futures Lab guide covers both versions side by side.

Has McKinsey confirmed any of this?

No: in the sources we hold, McKinsey confirms that Solve exists, that your length is in your invitation and that tasks start with an untimed tutorial, but it does not mention a 30-minute Sustainable Futures Lab, a three-day structure or four researchers. Every detail of the format rests on candidate accounts, which is why each visual below carries a status label.

One careful reading of McKinsey's own words helps. Its July 2025 game-based innovation lab post says Solve measures "analytical thinking and problem-solving as an additional data point in recruiting". That is a general statement about Solve, not a description of this format. For how the result is used overall, see whether Solve matters, and for the wider skills picture, what Solve measures.

How do you know whether your invitation includes the 30-minute version?

You cannot know for certain before you sit it: McKinsey says only that your Solve length is in your invitation email, and candidates link about 95 minutes to the newer lab, 85 to the standard lab and 65 to no lab. Treat that map as a reported pattern, then let the tutorial on screen settle which version you are playing.

1. Read the length in your invitation. This is the one number McKinsey says is authoritative. If the email states no number, ask your recruiter.
2. Compare it with the reported map. About 65 minutes is reported as no Sustainable Futures Lab, about 85 as the standard one, about 95 as the newer one.
3. Prepare for the version the map suggests, and keep the habits general. The map is a pattern from candidate accounts, not a rule.
4. Trust the on-screen tutorial last and most. It is untimed and explains the objective and navigation of whatever you actually get.

The arithmetic behind the map is simple, and it uses the reported minutes for each game. These are candidate figures, not McKinsey specifications.

The full map, with how it was assembled and where it breaks, is in the 65, 85 or 95 minute guide. What your invitation email contains is covered in the invitation guide, and the short Q and A in the Solve FAQ roundup handles neighbouring questions.

How does the reported three-day format work, day by day?

Candidates report that each of the three simulated days repeats the same four stages in order, explore, assign, support and reflect, and that what you learn and decide on one day carries into the next; this is reported, unverified and may differ on your screen. Day 1 is said to centre on the researchers, Day 2 on the workstations and Day 3 on balancing both.

Explore: buy only the facts that change a decision

Reports describe a small, limited number of information requests per day, with fewer on the last day, and a choice between asking a researcher and asking a workstation. The exact limits are unverified, so do not plan around a number. The habit is general: before you spend a request, name the decision it could change.

Assign: move people when the evidence says to

You place researchers at workstations and, reportedly, give a reason from a short list. Some accounts say a workstation holds only a couple of people and that the arrangement starts fresh each morning. Treat both as unverified. Whatever the rule, a placement should follow something you were told, not a hunch.

Support and reflect: decide, then remember what you saw

In support, each researcher brings a problem and you choose a response. In reflect, you rate how each person is doing, and accounts mention an option to say you do not know. How McKinsey treats any of this is unpublished. A rating you can trace to something you saw is easier to defend than one you invented.

How does it differ from the standard 20-minute Sustainable Futures Lab?

The standard Sustainable Futures Lab is reported as about 20 minutes with a ranking task and a run of linked decisions, while the newer one is reported as about 30 minutes of team leadership across three days; both pictures come from candidates, and McKinsey has confirmed neither. The longer clock buys you more to operate, not obviously more to think about.

Two short calculations show why the pace feels different. The standard version is reported as a ranking plus 12 decisions, so 20 minutes spreads over 13 screens of reading. The newer one has 3 days of four stages, so 30 minutes spreads over 12 stages of operating a board. Both are averages from reported figures, not timers you will see.

The lab also takes a bigger bite of the whole sitting. Using the reported minutes from the invitation sums above, the share of time spent in the lab rises from the standard version to the newer one.

The skills overlap even though the screens do not. Both reward stating the objective, respecting limits, updating when a fact changes and handling people without dropping the plan. The ranking task worked example covers the opening ranking of the standard version in detail, and the Solve timeline guide places the whole sitting in the application process.

What does one day look like when you work it through?

On this original, fictional Day 2, your four researchers supply 24 hours and the four workstations ask for 24, yet the best placement covers only 22 because people move in whole blocks; the numbers and rules are invented to show the reasoning, not to match any screen. A day's real task is turning what you learned into a placement whose cost you can state.

Our fictional lab studies a coastal marsh. Each researcher works 6 hours at one workstation, and each workstation holds at most 2 people. Your explore requests told you the demand for each workstation today.

Step 1: compare total supply with total demand

Supply matches demand exactly, which tempts you to keep everyone where they started. The split is the problem: Tide gauges needs 11 hours but a single researcher gives 6, while the Community desk wastes most of a block on 2 hours of work.

Step 2: cost each placement in covered hours

A workstation covers the smaller of its demand and the hours its people provide. Add that across the four workstations for each plan.

Step 3: state the trade you are making

Moving Kofi gives up the little work at the Community desk and gains most of the missing Tide gauges hours. Name the gain and the loss, then net them.

That net of 3 hours is a reason you can give for the move, and it follows from facts you collected, not a feeling. It also leaves a loose end for the next stage: the Community desk now has nobody, so one of the researchers' problems in the support stage may be about exactly that. Reading Solve tips alongside this helps you keep the objective visible while you decide.

Which decisions tend to go wrong, and what is the better move?

Four decisions tend to go wrong in a team-leading task like this one: spending requests to confirm what you believe, moving people for a reason you cannot state, answering a problem by asking for more analysis, and rating a person you have no evidence about. These are our editorial reading of reported accounts and of general judgment practice, not a McKinsey rubric. Each pair below uses the fictional marsh lab.

Spending requests to confirm, not to decide

With 3 requests and 4 workstations, a request that could not change your placement is a wasted share of your coverage. Count what your requests cover before you spend them.

Moving people without a stated reason

Placing someone because they seem keen is not a reason you could defend. The coverage numbers above are.

Answering a problem by asking for more analysis

A support problem usually arrives with incomplete facts. Asking for more analysis can look careful while leaving the person nothing to do next. A better answer names the trade-off, picks a course, says what would make you change it, and leaves the researcher able to act within the hour.

Rating a person you have no evidence about

If the reflect stage lets you say you do not know, as accounts report, saying so about a researcher you never asked or heard from is more honest than a confident guess. How McKinsey scores that option is unknown, so treat it as a habit about evidence, not a trick.

How should you spend the 30 minutes?

A reasonable coaching budget splits the reported 30 minutes evenly, about 10 minutes a day, with the support stage getting the largest slice; this is our editorial advice, not a McKinsey rule or a number you will see on screen. Candidates report, unverified, that the last day is where people rush, so a little early slack helps.

The tutorial is untimed, so use it to learn where each control lives rather than rushing through it. For the same idea applied to another game, see the Red Rock time budget, and which game to practise first if your invitation holds all three.

How do you prepare for a format McKinsey has not described?

Prepare transferable habits, not a memorised layout: McKinsey says no preparation is needed, and the 30-minute format is reported only second-hand, so the safest practice is the judgment habits it appears to use. Road to Offer offers all four practice formats: Red Rock, Sea Wolf, SFL Classic and SFL Island, with one complete free run each. Red Rock includes the full Study and six Cases, with highlighted calculations and charts in its worked review; Sea Wolf includes all three sites, with constraint and treatment visuals. These are independent exercises and do not promise identical McKinsey screens. This is our advice, not McKinsey's.

1. State the objective first. One line, in your own words, before any choice. The standard lab trains this directly, and the Sustainable Futures Lab method shows how.
2. Collect only what changes a decision. Before you ask for any fact, name the choice it could change. This is the habit behind the explore stage.
3. Cost a move before you make it. The marsh lab's covered-hours method is a template. Where there are no hours, use whatever limit applies.
4. Keep notes as you go, and keep them yours. McKinsey bans pre-prepared notes and lists pen and paper as the only tools in assessments. Follow your invitation on what is allowed in your sitting.
5. Decide, then say what would change your mind. A decision with a stated trigger beats a deferral.
6. Set your device and room up the day before. The system requirements guide and test-day checklist cover the facts McKinsey publishes.

If you want a rehearsal slot, the prep plan shows how to fit one around Red Rock and Sea Wolf, which the Red Rock method and Sea Wolf method cover. Candidates also discuss their own sittings in public threads, so the check of ten Reddit claims shows how to weigh them. If you need adjustments, read Solve accommodations, and for camera and monitoring rules, whether Solve is proctored.

Choose Sustainable Futures Lab practice

None of this predicts a result. For what a result can and cannot tell you, see the scores and results guide, and for the claims about pass rates that circulate, read what is known about the pass rate and retake rules. Candidates in other roles may sit different assessments, summarised in McKinsey online assessments by role, and the Solve overview places this lab in the whole sitting.

Sources and evidence boundaries

• Official, checked October 11, 2026: McKinsey's Solve page and its Solve FAQ (August 2025 PDF). They are the source for length in the invitation, untimed tutorials, no preparation needed, banned aids and the recruiter and support contact routes.
• Official, checked October 11, 2026: the assessment integrity expectations, which apply to assessments and interviews generally, and McKinsey's July 2025 game-based innovation lab post, the source for the quoted line on what Solve measures.
• Reported: the 95-minute invitation, the about 30 minutes of lab, the four researchers, four workstations and three simulated days, and the explore, assign, support and reflect loop. They come from candidate accounts first seen in late August and September 2026 and are unverified, and accounts differ on request limits, workstation capacity and rating options.
• Unknown in the public sources reviewed: any McKinsey description of this format, whether it is a pilot, who receives it, how it is scored, whether tutorial and tech check fall inside the invitation length, and how long it will stay in use. The marsh lab, its hours and every plan are original fictional teaching material, not Solve content.