There is a moment that happens in almost every team building session. Someone has a realisation. Maybe it’s about how they’ve been communicating, or how they’ve been avoiding a particular conversation, or how they’ve been leading without listening. The room gets quiet for a second. Heads nod.
And then everyone goes back to the office. And nothing changes.
This isn’t a failure of insight. The insight was real. The problem is that insight, on its own, doesn’t rewire how people actually behave with each other. For that, you need something different: repetition, adaptation, and what sports scientists call healthy tension.
What elite teams actually do
In 2009, researchers studying the New Zealand All Blacks, one of the most consistently high-performing sports teams in history, found something that challenged conventional thinking about team cohesion. The team’s culture wasn’t built on inspirational speeches or singular breakthrough moments. It was built on a practice they called “sweeping the sheds” where senior players clean the changing room after every match, regardless of result. A small, repeated act. Unremarkable in isolation. Transformative in accumulation.
What the researchers observed was that rituals like this, small, consistent, shared behaviours, did more to shape team identity and interaction patterns than any single high-intensity event. The insight (“we are a team that holds ourselves to a standard”) was secondary. The behaviour that expressed it, repeated endlessly, was what made it real.
This is what behavioural science has been telling us about teams for decades. Patterns of interaction, who speaks first, who defers to whom, how disagreement is handled, how mistakes are absorbed, are not formed in a single session. They are formed through repetition. They are stress-tested through tension. And they evolve through adaptation.
The problem with designing for “aha moments”
Most team experiences are designed backwards. They start with the insight they want participants to have, then build an experience that delivers it. The assumption is that if people understand something whether it be about psychological safety, about communication styles, or about trust — they will behave differently.
But understanding is not the same as doing. And doing once is not the same as doing habitually.
Research by Dr. Tomas Chamorro-Premuzic, organisational psychologist and author of Why Do So Many Incompetent Men Become Leaders?, draws a sharp distinction between learning events and behaviour change. Learning events increase knowledge. Behaviour change requires what he calls “deliberate practice in context”, repeated exposure to realistic situations where new patterns can be practised, tested, and refined. A single workshop, however well-designed, is a learning event. It is not deliberate practice.
The implication for how organisations design team experiences is significant. If you want your team to communicate more directly, you don’t just need an activity that surfaces the insight that direct communication matters. You need repeated opportunities, across time and under varying conditions for people to practise being direct with each other and to receive feedback in real time.
Healthy tension is not a side effect. It’s the mechanism.
There is a tendency in team building design to smooth things over. To create conditions where people feel good about each other, feel safe, feel connected. These are not bad outcomes. But they are incomplete ones.
Elite sports teams and the research around them consistently point to something counterintuitive: the interaction patterns that drive high performance are forged not in harmony, but in productive friction. Not conflict for its own sake, but the kind of tension that emerges when people who genuinely care about an outcome disagree about how to reach it.
A 2014 study published in the Journal of Applied Psychology found that teams with higher levels of task conflict — disagreement about ideas, approaches, and decisions — outperformed teams with lower conflict levels, provided the team had strong relational trust as a foundation. The tension was not the problem. Tension without trust was the problem.
This is the design insight most team experiences miss. The goal is not to eliminate tension. The goal is to build the relational infrastructure that allows tension to be productive rather than corrosive. And that infrastructure, like any infrastructure, takes time, repetition, and use to build.
What this means for how you design team experiences
If you are a leader commissioning a team experience, or a facilitator designing one, the most useful question to ask is not: what insight do we want the team to have?
It is: what will this team do differently next week?
Not next quarter. Next week. Because behaviour change that cannot be traced to the week after an experience is unlikely to compound into anything lasting.
This reframe changes what you look for in a well-designed programme. You look for experiences that are structured around realistic team dynamics, not sanitised simulations. You look for repetition, not just one activity, but a sequence of related challenges that allow patterns to be practised and adjusted. You look for tension that is deliberately introduced and then processed not avoided or immediately resolved. And you look for adaptation: moments where the team has to respond to changing conditions, read each other in real time, and adjust.
The All Blacks didn’t become the All Blacks in a single training session. They became who they are through a culture of repeated, small, consequential behaviours practised until they became instinctive.
The best team experiences don’t replicate that culture. But they can introduce its logic: that transformation is not a moment. It is a pattern. And patterns are built, one repetition at a time.