Most of what gets sold as team building is relationship development. Useful, but not the same thing.

Nobody on your leadership team wants to do another trust fall. You know it. They know it.

Picture the scene. You book the escape room. Everyone laughs for ninety minutes. Monday morning the same two VPs still won't give each other honest feedback, the same decisions still stall, and you're out a thousand dollars and an afternoon.

The problem isn't that the escape room was bad. It's that it was never going to fix what's broken.

‍

A Definition Worth Getting Right

Fahd makes a distinction in our leadership programs that reframes this whole conversation.

Doing a ropes course, bonding over a campfire, jumping in a hot tub after a long day: that's relationship development. It's genuinely valuable. Teams that like each other work better than teams that don't.

But it isn't team building.

Team building is the ability to identify where you are, what's not working, what is working, and what needs to change to make the team better. It's a diagnostic loop, not an event. Assess, name the problem, change something, then check whether the change worked.

Most of what gets sold as leadership team building is relationship development wearing a different name. That's why the escape room doesn't move anything. It was never pointed at the problem.

The exercises later in this piece do both. They build connection and they surface what's broken. That combination is what makes them worth the calendar slot.

‍

Why the Usual Version Fails

Search for team building activities and you'll drown in listicles. Forty-five games. Seventy-one icebreakers. Human knot, scavenger hunt, two truths and a lie.

They make the same three mistakes.

No debrief. The activity is the whole event. People play a game, feel a flicker of connection, then return to working exactly as before. Nothing transfers.

They avoid the real blockers. On a leadership team the problem is rarely that people don't know each other's names. It's candour, conflict, and trust. No game of charades touches that.

They substitute bonding for alignment. This is the expensive one, and it's the failure mode we see most often in executive retreats. Bonding feels like progress. Leaders leave energized and nothing has been decided, so the vicious cycles that were in the room on Friday are still there on Monday.

There's also a quieter cost. Forced fun breeds resentment, especially with senior people who are protective of their time and can tell when an afternoon is theatre. Get it wrong and you're further behind than when you started, because now the team associates "team building" with wasted time.

‍

What You're Actually Building

You're not building friendships. You're building a specific kind of trust.

Patrick Lencioni calls it vulnerability-based trust: the willingness to say "I was wrong," "I need help," or "I disagree" in front of your peers. Without it, leadership teams perform a polite theatre of agreement and make slow, hedged decisions that nobody actually owns.

Google's Project Aristotle studied 180 teams, 115 in engineering and 65 in sales, across 250 team attributes over two years. The finding that surprised them: who was on the team mattered far less than how the team interacted, and psychological safety was the strongest of the five dynamics they identified. Ahead of talent, resources, and tenure.

Amy Edmondson, who defined the concept in 1999, describes it as a shared belief that the team is safe for interpersonal risk-taking. When it's missing, people hide mistakes. Hidden mistakes compound.

The trust picture at the top is not encouraging. Gallup finds that only 21% of US employees strongly agree they trust their organization's leadership, down from a 2019 peak of 24%. Separately, and on a different measure, global employee engagement fell from 23% to 21% in 2024, with managers accounting for roughly 70% of the variance in team engagement.

Different numbers measuring different things, pointing the same direction. The people responsible for building trust are the ones with the least of it flowing toward them.

This is why psychological safety sits at the base of our Six Levels of High-Performing Teams. Skip it and every level above wobbles.

There's one more piece worth naming. In our keynotes Fahd argues that psychological safety alone isn't the goal. Combine psychological safety, empowerment, and productive conflict and you get the conditions for actual innovation. Safety without conflict produces a comfortable team that agrees on mediocre decisions. The exercises below are designed to get you both.

‍

Seven Exercises That Actually Work

None involve a ropes course. Each builds trust, surfaces conflict, or both.

One rule makes them work: always debrief. Budget more time for the conversation after than the activity itself. The exercise is the warm-up. The debrief is the work.

‍

1. The "How to Work With Me" manual

Each leader writes a one-page user manual for themselves. How they like to communicate, how they prefer feedback, what drives them up the wall, when they do their best thinking. Then they share it.

It removes the daily friction of guessing. Peers who coordinate constantly stop misreading each other. Pair it with a DISC workshop and the manuals get sharper, because people understand the styles underneath the preferences.

‍

2. The failure résumé

Every leader presents one real professional failure and what it taught them. Not a humble-brag. A real scar.

When the most senior people in the room admit they've face-planted, everyone else exhales. You're modelling the exact interpersonal risk-taking that psychological safety requires, and it flows downhill fast.

Fahd teaches this as the vulnerability loop: one person is vulnerable, another recognizes it and responds in kind, and it compounds. The hardest version, and the one that matters most from a leader, is taking responsibility for something that went wrong at work. "Last week I got frustrated in that meeting and I was short with you. That wasn't appropriate. I apologize." That costs something to say, which is exactly why it works.

‍

3. Personal histories

A Lencioni classic. Go around the table with three low-stakes questions: where did you grow up, how many siblings, what was hard about your childhood.

Twenty minutes, and it changes the temperature of the room. Teams stop seeing each other as job titles.

‍

4. The pasta tower, with a real debrief

Spaghetti, tape, string, and a marshmallow. Eighteen minutes to build the tallest free-standing tower with the marshmallow on top.

The exercise came from Peter Skillman, then VP of Design at Palm, and was systematized by Tom Wujec at Autodesk across more than seventy workshops between 2006 and 2010. The results are the interesting part.

Recent business school graduates are the worst performers of any group measured, at roughly 10 inches against an adult average of 20. Kindergartners average 26 to 27. Wujec also found that adding incentives made things worse rather than better: planning went up, tower height went down.

Most write-ups stop at "kids prototype, MBAs over-plan." True, but the finding Fahd uses in workshops is more useful.

CEOs score slightly above average. CEOs paired with their executive assistants score dramatically better. Why would adding an assistant improve a group of accomplished problem-solvers?

Because the missing ingredient isn't intelligence or expertise. It's facilitation. Specialized skills plus facilitation skills are what create better teams. The assistant coordinates, tracks time, and keeps the group working together rather than competing for the lead.

So the debrief question isn't "why did the kids win." It's: who was facilitating on your team, and were they doing it deliberately or by accident? For a room full of senior leaders who all believe they're the smartest person present, that lands differently.

We dig into this further in how to build a high-performing team.

‍

5. Mining for conflict

Pick one real, unresolved decision the team has been dancing around. Put it on the table and, with a facilitator, practise disagreeing openly about it.

Most leadership teams run on artificial harmony: agreement on the surface, resentment underneath. Fahd's line about this in keynotes is that these teams are like the MBA students building the pasta tower. They're not dealing with the problem at hand, they're dancing around it. And as long as they're dancing, nothing improves.

Uncomfortable the first time, addictive after that. If your team struggles to separate arguing about the work from arguing with each other, start with task conflict versus relationship conflict.

6. The clearing round

Structured peer feedback. Each person gives every teammate one genuine appreciation and one "I'd ask you to start or stop" request.

It makes candour routine and low-drama. When feedback is a scheduled ritual, it stops being a terrifying annual event.

‍

7. The pre-mortem

Take an initiative you're about to commit to. Imagine it's a year from now and it failed badly. Everyone writes down why.

It gives quiet skeptics permission to voice doubts before the team commits rather than after it fails. Our premortem workshop guide has the full format.

‍

What Happens When It Goes Wrong

An honest caveat, because most articles on this topic promise these exercises always work. Names and details changed, but this happened.

Fahd was running an executive retreat for a team with a known problem: a brilliant CTO whose ego was eroding trust across the leadership group. The founders knew. They'd decided brilliant was too valuable to lose. So the retreat was designed to rebuild connection, a full day of facilitated work on trust and vulnerability and shared purpose.

The day went well.

That night, after the founders went to bed, a few executives stayed up. One of them suggested doing one more exercise, informally: go around, share what you think your biggest superpower is. Low stakes. Connective.

The CTO's turn came. He'd had a few drinks. He leaned back and said: "My superpower is that I can do everyone's job here better than them."

Fahd tried to hand him an off-ramp. Maybe you mean you're highly adaptive, good at learning new domains. Maybe your real strength is elevating the people around you.

The CTO didn't want the off-ramp. He pointed at the Chief Design Officer with fifteen years of experience: I could design better than you. At the Head of HR with twenty-five years: I could do HR better than you. One by one, like issuing sentences.

Fahd shut it down. But the damage was done in about forty seconds, in a room that had spent all day building exactly the safety that made the moment possible.

Two things worth taking from that.

Vulnerability exercises don't create character. They reveal it. If someone on your leadership team is a genuine problem, a well-run exercise will surface that faster, not fix it. Which is information, but it's not the information the retreat was booked for.

Facilitation isn't optional at the executive level. The structured day worked. The unstructured midnight version, same people, same exercise type, no facilitator, produced the worst moment of the retreat. That gap is the entire argument for not running these off a blog post alone.

‍

How to Run These So They Stick

Debrief every time. The exercise is the warm-up. The conversation about what it revealed is the actual work.

Frame it as work, not play. These are sessions about how the team operates, because that's what they are. Forced fun breeds resentment; work on how we work does not.

Repeat them. Trust isn't a one-day event. The strongest leadership teams build small rituals into their normal rhythm: a clearing round each month, a failure story each quarter, a pre-mortem before every major commitment. You can see what that looks like in these psychological safety examples.

Close the loop. This is the step that turns relationship development into actual team building. A quarter after you run these, ask the diagnostic question again: what's working now that wasn't, what's still broken, and what do we change next? Without that, you did a nice exercise. With it, you have a system.

‍

The Payoff

Your leadership team is the small group that determines most of what happens everywhere else. When they can disagree in the open and still walk out aligned, every decision below them gets faster and every team under them gets safer.

That's worth an afternoon. The escape room wasn't.

Frequently Asked Questions:

‍