Save the Titanic — team building case studies

Team Building Case Studies That Prove It Worked

You have run team building before, and three weeks later nothing had changed. Now you need proof before you spend the budget again — something you can put in front of the person who signs off. These are real teams, real organizations, and what changed after Save the Titanic.

A short call, shaped to your team and the problem it is stuck on. No pitch.

A leadership team works a problem together over blueprints in an upscale venue during the Save the Titanic experience

From Learn2 — creators of Save the Titanic

250K+

leaders developed by Learn2

100+

countries

35+

years, across 6 continents

95%

would recommend Learn2

Teams that have run Save the Titanic

Deloitte
American Express
Bell
BMO
TD Bank
PepsiCo
OLG
Manulife
Nokia
UBS
Unilever
Enbridge
Johnson & Johnson

Why most team building has no case study worth reading

Most team events are built to be fun for a day. People laugh, the photos look great, and by the next hard week the team decides exactly the way it did before. There is nothing to write up because nothing changed — you cannot show a case study for an afternoon that left no mark.

The reason is simple. A day of games never puts the team in a real decision with a real clock and something on the line, so the habits that decide the work never surface, and nothing gets a chance to change. The event was never designed to leave a result behind.

A case study exists the other way around. The team makes real calls together under pressure, sees exactly how it did it, and names one habit to carry into the work — and that change is what the organizations below kept coming back for.

See it in one minute

What these teams actually walked into

A one-minute look inside the experience — the pressure, the decisions, and the moment a room of colleagues starts working as one team.

The case studies

Real organizations, real Save the Titanic engagements. Every name here ran the experience — no stock logos, no borrowed numbers.

Deloitte participants study blueprints together as an officer leads the discussion during Save the Titanic

Partner development, year after year

Deloitte

Deloitte built Save the Titanic into the development track for their Partners. It ran for years as a required part of how senior people learned to lead together, not a one-time offsite. When a firm keeps bringing the same experience back for its most senior leaders, that is the case study — the experience earned its place in the program.

An American Express team works a decision at a round table with a facilitator during Save the Titanic

Cross-functional decisions under pressure

American Express

American Express teams used the experience to work on the hard part of cross-functional work: deciding together when the clock is running and every function sees the problem differently. Leaders left thinking more clearly under pressure, and the shared language from the day carried back into how the functions made calls together.

An OLG leadership team works together around a table during the Save the Titanic experience

One leadership team, many locations

OLG

OLG ran Save the Titanic with leadership teams across multiple locations. The teams took what surfaced in the room straight into their strategic planning, and reported faster, more collaborative decisions afterward. Running it in location after location is the proof it kept delivering — one strong day does not get repeated, a reliable one does.

A newly merged Manulife team works a problem together over blueprints in an upscale venue during Save the Titanic

Two merged teams become one

Manulife

Manulife had the classic post-merger challenge — two ways of working and one company. Their leaders used the shared pressure of the experience to build trust faster than any restructuring could, and gave both sides one common language for the decisions ahead. Two groups walked in, and one team walked out.

See the post-merger integration experience →
A Nokia senior team debates a decision during the Save the Titanic experience with a city skyline behind them

The senior team, in the room together

Nokia

Nokia put its senior leadership team through Save the Titanic and worked the problem together, under real pressure. For a team that size, the value is the honest read on how they actually decide when it counts — who steps up, who goes quiet, where a good idea gets lost — and the chance to change it the same day.

A grand ballroom of ArcelorMittal leaders with hands raised during the Save the Titanic experience

710 leaders, one shared experience

ArcelorMittal

ArcelorMittal ran Save the Titanic across their global leadership population. 710 leaders went through the same pressure and the same decisions, so the whole leadership layer came away with one reference point instead of a dozen different workshops. Decision-making speed improved 30 to 40 percent — the one case on this page with a figure attached.

See how the experience runs →

Beyond these, Save the Titanic has run with leadership and enterprise teams at BMO, TD Bank, PepsiCo and Bell, and it is offered through Duke Corporate Education's executive education portfolio.

Why an experience leaves a result behind

Why immersive experiences change behavior, and events do not

The reason the case studies above have something to show comes down to how people remember. Most team building is information transfer — a talk on trust, a slide on values, a round of icebreakers. People forget most of what they are told within days. The message fades on the same curve as everything else they heard that week, and the team walks back to its desks unchanged. That is the forgetting curve, and it is why a one-off event so rarely leaves a mark.

What a team did together does not fade like that. A call the team made side by side, under a real clock, with something on the line — that stays. It stays because they lived it, not because they were told it. This is the difference between information a team receives and an experience a team owns, and it is the whole reason immersive learning changes behavior when a talk from the front never does.

An immersive experience is participant-driven. Nobody stands at the front handing the team the answer. The team is given one hard problem and a clock, and the only way through is to share what each person knows and decide together. The real habits surface on their own — who steps up, who goes quiet, where a good idea gets lost — because the pressure is real enough that people stop performing and start behaving the way they actually do at work.

Then the facilitator makes the pattern visible while it is still fresh. In the debrief the team looks honestly at how it decided, names one habit to change, and practices it before the day ends. A habit built under pressure and named out loud is what a team carries back to Monday — and it is exactly what turns a good day into a result you can write up months later.

This is what immersive learning is built to do, and why it earns a case study when an event cannot. See the wider approach on the Learn2 immersive learning hub.

What actually changes

The same pattern shows up across every case — the change you can see in the work, not just on a feedback form.

Faster decisions

Teams think together faster. They trust each other's read, so they move without the endless second-guessing that used to eat the week.

Real alignment

People understand why a call was made, not just what it was. They stop pulling in different directions and commit to the same one.

Trust that holds

Teams that work a hard problem together under pressure trust each other more afterward. That trust shows up in the next hard week, not just the workshop.

It sticks

Months later teams still say “remember what we did in Save the Titanic?” and change how they work in the moment. A slide deck never gets quoted back like that.

Free Field Guide

The Team Development Results & ROI Guide

What's inside:

  • What to look for in a team building case study — the difference between a fun afternoon and a documented change, so you can tell real proof from a stock photo.
  • The outcomes that matter, and the feedback-form trap that makes a weak program look strong — the measures a budget-holder actually accepts.
  • A before-and-after frame you can forward to the person who signs off — how to tie the experience to the cost of the problem and prove the result.

Send me the guide.

One email. No account. Unsubscribe anytime.

Common questions about team building case studies

What is a team building case study?

A team building case study is an honest account of what changed for a real team after a real experience — who they are, what was not working, what they did, and what was different afterward. A good one names the organization and the outcome instead of hiding behind a stock photo and a slogan. The cases here are real Save the Titanic engagements, told name-and-outcome.

What outcomes should team building produce?

Outcomes you can see in the work, not just on a feedback form. Faster decisions when the clock is running, real alignment on the hard calls, trust that holds into the next tough week, and a shared language the team keeps using. If a team building event produces a fun afternoon and nothing else by Monday, it produced the wrong outcome.

How do you measure the ROI of team building?

You measure it where the money is: how much faster the team decides, how much rework a shared decision avoids, how much less a stalled call costs. The trap is measuring the day (did people enjoy it) instead of the change (did the team decide and deliver better after). Our free results guide walks through the before-and-after measures that a budget-holder actually accepts.

Do these team building case studies come with a PDF?

Yes. The free results guide on this page is a PDF you can forward to the person who signs off. It lays out what to look for in a case study, the outcomes that matter, and how to measure results before and after — so you can build the business case without starting from a blank page.

How do you build a business case for team building?

Start from the cost of the problem, not the price of the event. Name what the team's slow or split decisions are costing right now, tie the experience to that specific cost, and set a before-and-after measure so the result is visible. The go-deeper reading below and the free results guide give you the exact frame most budget-holders approve.

How do I know a case study applies to my team?

Look past the logo to the situation. A merged team, a leadership group that decides too slowly, functions that will not hand off cleanly — the case that matches your situation matters more than the case with the famous name. The fastest way to know is a short design call, where we shape the experience to the exact problem your team is stuck on.

Want a case study with your team's name on it?

Book a design call. We'll talk through your team, the problem it keeps getting stuck on, and your timeline, then shape a session that fits. Most teams run it within a few weeks.

Book a design call

Not sure which experience fits? Answer three questions and we'll point you to the right one.