Leadership simulation training

We design and build these, including the software that runs the larger ones, which mostly means we have watched them fail. The failure is nearly always the same shape: an elaborate scenario, a tense ninety minutes, and then eight minutes of debrief because the scenario over-ran. The simulation worked. Nobody harvested it.

This guide is written from that side: what a simulation genuinely tests, which format fits which objective, how to design a decision that is actually hard, and when running one makes your training worse.

What a simulation tests that a course cannot

A course can establish that someone knows the theory of delegation, or can recite the escalation policy. A simulation tells you what they do at five o'clock on a Friday when the policy is inconvenient. Specifically, it surfaces:

• What they do first. Order of operations is the honest statement of priority. Everything else is what people say their priorities are.
• What they do with information that contradicts a plan they have just announced. This is the single most revealing moment in any simulation.
• Who they ask. Whether the quiet person was ever brought in, and whether anybody checked a source rather than trusting the loudest summary.
• How they behave when they are wrong in front of people whose opinion they care about. Reversing a public position is a skill, and uncomfortable enough that most people avoid learning it on the job.
• What they drop when time gets short. The first thing abandoned under pressure is the thing they privately consider optional. Very often it is the communication.

None of that is knowledge. Which is why a simulation is a poor instrument for teaching a framework and an excellent one for finding out whether anybody uses the framework they were taught last year.

The formats, and what each one is good at

"Leadership simulation" covers at least six different things sold under the same words. They are not interchangeable, and picking the wrong one is the most expensive mistake on this page.

Two rules of thumb from the table. Solo formats give clean evidence and weak learning; team formats give messy evidence and far better conversations. And any format governed by a countdown teaches speed. If judgment is the objective, a facilitator should control the pace, not a clock.

Make the decision genuinely hard

Most scenarios fail at the design stage, because the right answer is visible from the brief. Participants spot it in four minutes, then spend the session performing the reasoning they think you want. A decision is only worth simulating if it has five properties:

1. Competing goods, not good against bad. Nobody learns anything from choosing honesty over fraud. The useful choice is honesty against loyalty, or the deadline against the person who will break to meet it.
2. Incomplete information, obtainable at a cost. Give teams a way to buy a fact with time or points. Whether they pay for it is the finding.
3. A commitment that is recorded. Written down, timestamped, visible to the room. People defend a position very differently once they have signed it.
4. New information after the commitment. This is the heart of it. The test is what someone does when the ground moves under a decision they have just defended in public.
5. Consequences that arrive late. If the outcome lands thirty seconds after the choice, participants stop deciding and start guessing what the facilitator wants.

Score the reasoning, not the result. Reward the result and you have taught a room that a lucky gamble and a sound decision are the same thing.

The poker player Annie Duke calls that error resulting: judging a decision by how it happened to turn out. It is endemic in real organisations, and a simulation is one of the few safe places to demonstrate it, by letting a well-reasoned choice lose and a reckless one win.

A decision-making simulation you can run on Monday

This one needs no software, no actors and no budget. It is deliberately small so you can test the mechanics before commissioning anything larger.

• Group: 12 to 30 people, in teams of four to six.
• Time: 60 minutes, of which 25 are debrief. That ratio is not a typo.
• Materials: a one-page brief per team, three slips of paper per team, one facilitator.

The brief. Each team is the leadership of a department. A project the client is expecting on Friday will not be ready. Three options, all of them defensible: tell the client today and lose the date; push the team through the weekend and hit it; ship what exists and describe it as a phased release.

1. Round one, ten minutes. Each team commits in writing to one option plus one sentence of reasoning, and hands the slip in. No discussion between teams.
2. Round two, ten minutes. You release new information to everyone at once: the client's programme manager already knows, and one named person on the team has quietly been carrying two roles since April. Teams may hold or reverse, again in writing.
3. Round three, five minutes. You read out the consequence of each option, arranged so that one badly reasoned choice comes off well. Nobody scores.
4. Debrief, twenty-five minutes. Slips face up on the table so every team can see what everyone else committed to and when.

What it surfaces: who actually made the call, how much of round one was ego defended into round two, and whether anyone noticed that the named person in the new information was a human being rather than a variable.

The debrief question that does the work: "At what point did you know you were going to change your mind, and what stopped you saying it out loud earlier?" Ask it, then wait. The silence is part of the exercise. If you want the wider method, how to debrief an activity covers the sequence in detail.

An activity without a debrief is entertainment. Pleasant, well-reviewed on the feedback form, and gone by Thursday.

When a simulation makes training worse

The honest list. Any one of these is a reason to do something else instead.

1. When it is secretly an assessment. If people suspect they are being scored for promotion they will perform rather than behave, and you have paid for theatre. State which it is, in writing, before anyone walks in.
2. When the room has no psychological safety. A simulation exposes judgment in front of colleagues. In a team where mistakes are punished, that is not development, it is a trap with catering.
3. When the scenario is beneath the room. Senior people handed a dilemma they resolved a decade ago will play along politely and learn nothing. Pitch the difficulty at the edge of their competence or do not run it.
4. When the score is the outcome. See above. Outcome scoring reliably teaches gambling.
5. When nobody will facilitate the debrief. Without someone able to sit in an uncomfortable pause, the session ends on a scoreboard and the learning stays in the room.
6. When the real purpose is to sell a decision already taken. A simulation that can only arrive at the answer leadership has already chosen is a recognised genre, and the room spots it within twenty minutes. It costs more trust than the exercise was worth.

Measuring it without inventing numbers

You will meet claims that people retain ninety per cent of what they do, usually drawn as a pyramid. Those percentages trace back to no study anybody can produce. Do not build a business case on them, and be wary of a vendor who does.

Something more defensible: before the session, name two or three observable behaviours in the language people actually use. Fewer decisions escalated without a recommendation attached. Bad news reaching the client within a day. Ask line managers about those behaviours six to eight weeks later. Modest, and real. The Kirkpatrick model is the standard frame for deciding which level you are evidencing, and Kolb's cycle explains why reflection is the stage everybody cuts when the room runs late.

When to build one rather than buy one

Off-the-shelf simulations are worth the money when the skill is generic: a difficult conversation, a prioritisation squeeze, a standard negotiation. Buy one, run it well, spend your effort on the debrief instead.

It is worth building your own when the decisions that matter are specific to you: your regulatory exposure, your escalation culture, the trade-off your managers get wrong every quarter. That is what our bespoke gamified learning apps exist for. Participants play on their own phones, a facilitator drives the pace from one screen and releases each reveal to every phone at once, and decisions are scored on reasoning rather than speed. HEARTWARE runs five rounds in ninety minutes on judgment in the AI era: teams decide what to trust, verify and own, and can question the characters in their own words rather than picking from a menu.

Before commissioning anything, play the Weekly Challenge. It is free, takes ten minutes, and carries the same debrief logic in miniature. If it does not change how you think about a decision you made last week, a bigger version will not either.

For the method underneath all of it, experiential learning is the model, and our soft skills programmes are where simulations sit inside a longer arc rather than a one-off event.

Tour De Force runs this as live, experiential training for teams worldwide — online and in person. Talk to us, or play Gamified learning appsThe Weekly Challenge to see the method in ten minutes.