Building high-performing teams: what the research actually shows works

High-performing teams share three measurable traits: psychological safety high enough that people speak up, a shared understanding of purpose stated in the same words by every member, and a structured way to practice new behaviors after any training event. Google's own internal research on team effectiveness, and twenty-five years of running experiential leadership programs, point to the same conclusion. Teams change when people are put into a real situation together, not when they sit through a slide deck about collaboration.

What the research says makes a team high-performing

Google's Project Aristotle, a multi-year study of more than one hundred eighty teams inside the company, set out to find the variables that separated its best teams from the rest. Team composition, seniority, tenure, and even individual talent turned out to matter less than one factor: psychological safety, the shared belief that a team is safe for interpersonal risk-taking. Teams where people felt safe to admit a mistake, ask a question, or challenge an idea consistently outperformed teams that looked stronger on paper.

Gallup's ongoing research into workplace engagement has found for years that fewer than a quarter of employees worldwide report being engaged at work. Disengagement shows up on teams as the quiet withdrawal everyone recognizes: people attend the meeting but stop contributing the idea that might have mattered. A high-performing team reverses that pattern, and it does so through structure, not slogans.

The mechanism behind both findings is the same. People contribute when the environment removes the cost of contributing. That is a design problem, not a personality problem, and it is the reason we build programs around situations that flatten hierarchy rather than lectures that reinforce it.

Why traditional team-building exercises fail to change behavior

Most corporate training does not survive contact with the calendar. Research on training transfer, a body of work going back to studies by Baldwin and Ford in the 1980s and echoed by decades of workplace learning data since, has repeatedly found that only a fraction of what gets taught in a classroom setting ever shows up in changed behavior on the job. The binder gets packed away. The deck gets forwarded once and never opened again.

The content is rarely the problem. Adults simply do not learn durable behavior from information alone. David Kolb's experiential learning model, first published in 1984 and still the reference point for adult learning design, describes learning as a cycle: concrete experience, reflective observation, abstract conceptualization, and active experimentation. Skip the experience and the reflection, and you are left with information that has nowhere to attach itself.

This is the specific gap Morrison Alley was built to close. We do not run a workshop about trust. We put a team inside a scenario with real stakes, where the outcome depends on whether they actually trust each other in that moment, and then we connect what happened back to the behaviors your organization needs on Monday morning.

What high-performing teams actually do differently

Across programs, four outcomes separate teams that hold together under pressure from teams that scatter.

Clarity of purpose. Every member of a high-performing team can state what the team exists to do, and they use close to the same words. Ambiguity about purpose is one of the most common reasons cross-functional teams stall, because members quietly optimize for different definitions of success.

Alignment on a shared vision. Alignment that is only ever discussed in a leadership offsite and never said out loud by the people who have to execute it rarely survives the first hard quarter. High-performing teams have agreed to the vision audibly, in the room, with each other.

Results, faster. A team pointed in one direction covers more ground than a talented team pointed in five directions. Coordination costs compound when priorities conflict, which makes this a matter of arithmetic rather than motivation.

Leadership that turns intention into impact. Plans do not fail from a lack of ambition. They fail because no one owned the next step, and the busy week that follows any planning session buried it. High-performing teams build the capability to act on intention before the moment passes.

Why getting a team out of the building changes things

Something measurable happens when a team leaves its normal environment and enters a novel one. The usual hierarchy loosens because the scenario does not care about org charts. People who rarely speak up in a status meeting start contributing, often because the challenge in front of them rewards a skill the meeting room never called for. The thing everyone has been politely avoiding for a year tends to surface, because the shared pressure of the moment makes avoiding it harder than saying it.

We design every program to use that shift deliberately, working from the center outward: who your people need to become, the program built to get them there, and the place chosen to make it land. That sequence is why no two Morrison Alley programs look the same. A team facing a trust deficit needs a different scenario than a team facing a strategic misalignment, even if both problems get labeled "communication issues" on an engagement survey.

The places matter as much as the challenge. We look for locations with a real, honest story: a locker room that held Babe Ruth, Michael Jordan, and AC/DC; a beach where Navy SEALs train; a room built around a space shuttle that has flown thirty-three missions. Your team steps into that story, and we tie it directly to what they are facing at work. If the connection is decorative, a team notices within the hour. The fit has to be earned.

People protect what they built together far more than they protect what was handed to them in a workbook.

Inside the scenario, we hand teams a problem they cannot solve individually. What comes out belongs to them: the working relationships they built under pressure, the commitments they made out loud, and the memory of the place where they made them.

How to make the change actually last back at work

The experience is the beginning, not the endpoint. No binder gets packed into a suitcase, and no deck gets forwarded around the office to gather dust. Before anyone leaves the room, we line up what happened during the program against the organization's own stated priorities, with named owners and specific next steps attached to each one.

After that, the work continues through structured practice and spaced reinforcement, with a clear read on whether the new behavior is actually showing up week by week once people are back at their desks. This is the piece most team-building programs skip entirely, and it is the reason so many well-intentioned offsites fade within a month. What a team practices repeatedly once they return to work is what actually changes. What they merely remember does not.

How long does it take to build a high-performing team?

There is no universal timeline, because the answer depends on where a team is starting from and how deep the misalignment runs. A team with a straightforward clarity problem can shift meaningfully in a single well-designed experience paired with a short follow-up cycle. A team carrying real, unspoken conflict typically needs a longer arc, including reinforcement sessions spaced over weeks or months, to make sure the behavior holds once the novelty of the original experience wears off. The honest answer is: long enough that the new behavior survives a genuinely busy week, because that is the real test.

Does team building actually improve performance?

It does, but the format matters more than the fact of doing it at all. Programs built around information transfer, where a facilitator talks and a team listens, show weak evidence of lasting behavior change, consistent with the training-transfer research already cited. Programs built around real consequences, active problem-solving, and structured reinforcement afterward show a different pattern, because they engage the full experiential learning cycle rather than only the informational stage of it. The format that changes teams is the one that puts them inside a challenge with something real on the line, followed by disciplined follow-through once they are back at work.

Where to start

Building a high-performing team starts with a conversation about your people before it starts with a location or an activity: which behaviors need to shift, and what change do you want still standing a year from now. If your team is ready to move past information sessions and into a designed experience that ties directly to your organizational goals, Morrison Alley builds that program from the center outward, starting with your people.

The research referenced here is set out in full, with sources, on our Why It Works page.

← All field notes