Insight · Vol. 09

The room, the peak, and the lesson nobody scheduled.

Building an exercise used to take weeks. Running one used to feel like a test. We rebuilt both, and found the real lesson hiding in the loudest thirty seconds of the room.

We used to think building a simulation took weeks. Then we built oli.

Now it takes an afternoon. Describe the scenario. Answer a few questions. Watch it come together in front of you.

The hard part was never the idea. It was always the time between the idea and the room. That gap just got a lot smaller.

We built oli to remove friction from one side of the exercise: getting it built. We didn’t build it to change how people feel while they’re in the room. That happened on its own.

The calm stretches of a simulation tell you how a team behaves. The peak tells you who they actually are under it.
The verdict

The peak isn’t chaos. It’s data.

Nobody was thinking about the learning objective. That’s the point.

Someone told us recently that a session was the most fun they’d had at work all year. That wasn’t the goal. It was still the best compliment we’ve had.

Turns out people actually enjoy being tested, when the test respects their time and their intelligence. Pressure and no fun get confused a lot. They’re not the same thing.

Nobody in that room was thinking about learning outcomes. They were thinking about the decision in front of them. Two hours later they’d made calls under pressure, disagreed with each other, and changed their minds at least once. That’s not a training session. That’s just how people actually learn. We just built the room for it to happen in.

  1. 01 The room stays calm, at first. Objectives are clear, roles are assigned, everyone knows their job.
  2. 02 Then the scenario moves faster than the plan. Someone crosses out the objective on the board. The room gets loud, fast.
  3. 03 The peak passes, and the room settles. What's left behind is a record of exactly who did what in those thirty seconds.

Where the real signal lives. It’s not in the calm parts.

Once the room is easy to build and people are actually engaged in it, something else becomes possible: you can look closely at what happens inside it. Every exercise has a moment where the noise spikes.

What spikes 01

Everyone talking at once. Everyone reaching for the same piece of information at the same time.

What spikes 02

Everyone suddenly aware the clock is real. The scenario stops being an exercise for a moment.

What it reveals 01

Who spoke first. Who got interrupted. Who went quiet exactly when it mattered most.

What it reveals 02

Who reached for data before opinion. Who reached for opinion before data.

The calm stretches of a simulation tell you how a team behaves. The peak tells you who they actually are under it. That’s usually where the real lesson is hiding.

Easier to build. More honest to sit through.

None of this was the plan when we started. It’s what happens when you take the friction out of the parts that don’t matter, so you can look harder at the part that does.

01

From idea to exercise in an afternoon.

oli turns a scenario description and a handful of questions into a running simulation, so the gap between having the idea and running the room stops being the bottleneck.

02

Pressure, without punishment.

An exercise built to respect people’s time and intelligence gets real engagement in return, not just compliance. That difference shows up in the data.

03

Interaction Maps for the loud thirty seconds.

Who spoke, who was interrupted, who went quiet, mapped across the exact moment the room got loud. Not just a summary of the whole session.

04

Influence Metrics that separate signal from noise.

The peak looks like chaos in the room. The analytics engine turns it into a clear record of who actually moved the decision.

The closer

We didn’t set out to make the room more human. We just stopped getting in its way.

Want to see what that room looks like?

See what your team’s peak moments would actually reveal.

Book a demo and we’ll show you how oli builds the exercise, and how the analytics engine reads the room once the pressure hits.