“We were lucky.”

That’s how one participant described their team experience at the end of a leadership program I helped facilitate at the Banff Centre. After just five days, their team had become highly cohesive. Purpose was clear, conversations were productive, and trust was strong. They were, in every meaningful sense, functioning as a real team—a high performance team.

But rather than attribute that outcome to anything intentional, participants often explain it away. “It was just the right group of people.” Or “it’s because we were focused on just team development – and for an entire week.”  But that way of thinking is a common mistake—and the reason most teams never become teams.

The Assumption

Most organizations treat collaboration as a function of people, commitment, and time. Hope for the right mix of people, encourage engagement and give enough time—eventually collaboration will emerge.

Sometimes it does. Often it doesn’t.

What We Did

In Banff, we didn’t wait for collaboration to happen—we designed for it. Over five days, participants didn’t just learn about teams; they were placed inside a structure that required them to function as one.

We moved deliberately through a sequence. It began with individual reflection and feedback, then shifted to establishing shared purpose and meaning. From there, teams created a charter, clarified roles and expectations, practiced disciplined communication, and engaged in structured reflection. Along the way, they worked through real challenges that required genuine interdependence.

At no point did we assume the team would “figure it out.” The conditions were intentionally designed so that collaboration wasn’t optional—it was necessary.

What Actually Created the Shift

The strength of those teams didn’t come from motivation alone. It came from structure.

Purpose was made explicit rather than assumed. Interaction was intentional, with participants learning how to listen, inquire, and advocate without defaulting to debate or defensiveness. Reflection was built into the experience, creating space to process rather than simply act.

Equally important, interdependence was real. Tasks required collaboration, and success depended on others. Even the environment reinforced the work, with the physical space and program design supporting how people interacted and learned together.

The Result

In five days, a group of individuals became a team—not because they were unusually committed, and not because they had more time than others, but because the conditions required collaboration to emerge.

The Real Insight

Organizations don’t lack time, capable people, or effort. What they lack is design.

When collaboration fails to materialize, the default explanation is almost always human: people aren’t engaged, they’re too busy, or they just need more time. But those explanations miss the point.

Time Doesn’t Create Collaboration. Design Does.