How To Get A New Team To Collaborate Fast

So you’ve got a new team. Maybe it came out of a reorg. Maybe you inherited it. Maybe you hand-picked every person on it yourself. Either way, on paper, this team is stacked—smart people, real experience, the kind of roster you’d brag about in a leadership meeting. And yet it isn’t working. Or maybe yours is the other version: the reorg fused two groups with very different cultures, and now they’re clashing hard and collapsing fast.

You’ve probably told yourself the thing every leader tells themselves in that moment: they just need time to gel. That instinct isn’t crazy. It’s just expensive—and it misreads what time actually does.

Consider what happens in a cockpit before a commercial flight departs. A captain and first officer—often meeting for the first time that day—run through briefings, checklists, and role confirmations. Within minutes, two people who may have never worked together are coordinating high-stakes decisions as if they’d been flying together for years. They don’t get weeks to build rapport. They don’t get a retreat. They get the length of a pre-flight briefing, and it works.

Which raises an uncomfortable question: if two strangers can collaborate fast in a cockpit, what exactly is the time you’re waiting on supposed to buy you?

Why New Teams Don’t Collaborate Fast

When a new team stalls, leaders reach for one of two things. Waiting—you’ve made the introductions, shared the reporting lines, maybe built a RACI chart nobody has opened since, and now you trust proximity to do the rest. Or forcing it socially: drinks, an offsite, two truths and a lie. Neither is a bad idea, exactly. Both are just aimed at the wrong target.

Start with a study that was supposed to be about something else entirely. In the 1980s, a NASA research team led by human factors expert H. Clayton Foushee set out to understand how fatigue affected pilots. They put twenty two-person crews into a full-mission flight simulator. Some flew the scenario hours after finishing a grueling three-day duty cycle—exhausted, running on fumes. The others flew it after three days off. Rested. Refreshed. Ready.

The result ran the wrong direction. An expert observer rated the exhausted crews significantly better across multiple flight-safety dimensions, and those crews flew significantly more stable approaches than the well-rested ones.

The explanation wasn’t fatigue. When the researchers re-sorted every crew by a different variable—whether the two pilots had actually flown together during their most recent duty cycle—that split produced far sharper differences than rested-versus-tired had. Crews with recent shared flying time made less than half as many errors. And the active ingredient was recency, not acquaintance: most pilots in the “hadn’t flown together” group knew each other perfectly well—they just hadn’t flown together in months. It’s a post-hoc reanalysis of a small sample, and the authors say plainly they can’t fully separate fatigue from familiarity.

But the direction is hard to ignore. The hours weren’t what made those crews better. It was what the hours produced—and that can be built on purpose, in a week, instead of accidentally, over six months.

There’s an entire line of thinking devoted to teams that never get the luxury of gelling at all. Debra Meyerson, Karl Weick, and Roderick Kramer named it swift trust—a framework rather than an experimental finding—describing how temporary groups presume trust at the outset, then verify and adjust it as they go. Film crews. Surgical teams. Disaster response units. Their advantage isn’t that they’re braver or friendlier than your team. It’s that the ambiguity most new teams marinate in for months has been engineered out of their first ten minutes.

That ambiguity shows up as one of two deficits. Or both.

The first is a clarity deficit. Your people don’t know enough about each other to work efficiently. Who has what expertise. Where one person’s responsibility ends and another’s begins. Who to route a problem to. So they guess, and their guesses are wrong often enough to generate duplicated work, uncovered gaps, and a general slowing of everything the team produces.

The second is an empathy deficit. Your people haven’t had enough experience with each other to understand how their colleagues think. They don’t know who needs to process out loud and who needs a day, or whose silence means disagreement and whose means they’re still reading. So they work around each other instead of with each other.

Both channels show up in the research. Studying joint-replacement procedures at a teaching hospital, Ray Reagans, Linda Argote, and Daria Brooks found that individual experience and experience working together each made a distinct contribution, even controlling for the other—and named both in the title of the paper: knowing who knows what, and knowing how to work together. One precision worth keeping: performance there meant procedure completion time. Speed, not patient outcomes.

The Click Framework: Clarity And Empathy

In my work with teams, I call the moment those two deficits close the Click—that shift when a group of capable individuals stops feeling like a group of capable individuals and starts operating like a team built for this.

Clarity is the structure—the granular version of the org chart that lets someone route a problem correctly on the first try instead of the third. Empathy is the relationship. And let me be precise about that second word, because it gets soft fast: empathy on a team is not friendship. It’s not liking each other. It’s knowing enough about how your teammates operate to communicate efficiently, anticipate reactions, and disagree without it turning into an incident.

Teams that Click have both. Teams that Click fast have both earlier. Here’s how to build them.

Get Uncomfortably Specific About Roles

The first move is the one most leaders think they’ve already made. Introductions and reporting lines are a start, but clarity lives a level deeper, at decision rights: What decisions are yours to make without asking me? What work do you own end to end? When do you need to pull someone else in—and specifically who?

The ambiguity most teams leave sitting inside those questions is staggering. It’s also the source of most of the friction later diagnosed as a personality conflict—usually two people who each believed something was theirs, or each believed it was someone else’s.

So spend a full meeting on it. Not fifteen minutes at the end of a kickoff. Have every person say out loud how they understand their role and how it connects to everyone else’s. Then find where two people described the same territory, and where nobody described territory that clearly belongs to someone. Resolve both in the room, early, while the dispute is still cheap. A prompt that works well here is “tell me the last decision you made that you weren’t totally sure was yours to make.” You’ll learn more from those answers than from any org chart you’ll ever draw.

Hand Out Your “Manual Of Me”

Role clarity tells your team who owns what. It doesn’t tell them how to work with the human being who owns it.

That’s what a Manual of Me is for—an exercise where each teammate writes the user’s manual for working with them. I use four fill-in-the-blank sentences as a baseline: I’m at my best when . I’m at my worst when . You can count on me for . I need you to . The goal is that each person does some real self-reflection and then hands over the operating manual their team would otherwise reverse-engineer through six months of trial, error, and mild resentment. Nobody has to guess whether their colleague hates being cold-called in meetings. They said so. In writing. On day two.

One tip: go first. Whatever level of honesty you model becomes the ceiling for everyone else’s. If yours reads like a performance review you wrote about yourself, you’ll get four more just like it.

Build Empathy Through The Work, Not The Icebreaker

Have the team dinner. It’s nice. It just isn’t what builds working empathy, because the understanding you need isn’t biographical. Knowing where someone went to school tells you nothing about how they handle being overruled.

The principle underneath it: people understand each other far better when they work through something together than when they take turns talking about themselves.

So build the empathy through the work. Give the team a real but low-stakes shared problem—a process to redesign, an analysis to run, a plan to pressure-test. Something that requires genuine contribution from multiple people and has an actual answer. The output isn’t the point. The point is that your team gets to watch each other think, disagree, push, and land somewhere while nothing is on fire.

Then reflect on how it went. Have each person share what they were thinking during the work, and where they felt misunderstood or ignored. The goal isn’t to assign blame or unmask one difficult teammate. It’s to practice giving feedback while the stakes are still low enough to survive it.

Run The Pre-Flight Briefing

The most consistent practice across fast-forming teams—in aviation, medicine, the military—is the briefing that happens before the work starts.

Researcher Robert Ginnett spent roughly 300 hours observing airline crews, comparing effective captains against less effective ones. What he described is that the pre-flight briefing was where the effective captains shaped how their crew behaved long afterward. It’s a descriptive study of ten captains, so it can’t tell us the briefing caused the difference. But the observation is striking: the best captains weren’t better in the moment of crisis. They were better before it. The briefing wasn’t preamble. It was the intervention.

Most business teams skip it entirely. They launch projects without launching the team, then discover around week five that nobody ever agreed on how decisions get made.

You don’t need much. Sixty to ninety minutes at the start of a project covers it, and the agenda is three questions:

• What are we trying to accomplish, and how does each person’s work connect to it? That’s your clarity anchor—everyone holding the same map.
• What do we each need from each other to do our best work? That’s your empathy anchor, and where those Manuals earn their keep.
• What are the norms we’ll operate by? How decisions get made. How disagreement gets surfaced. What “responsive” means here. Not a rulebook—a set of agreements everyone helped write and therefore has a stake in keeping.

And it isn’t only for big projects—plenty of teams would benefit from a lighter version every week. Whatever the cadence, write the answers down. Norms that live only in a conversation aren’t norms. They’re a nice memory of a meeting.

What Fast-Forming Teams Teach Us

The most important insight from teams that form fast isn’t that they’re exceptional. It’s that they’ve formalized what most long-term teams leave to chance. Most business teams do the opposite—and sometimes that works, slowly, inefficiently, and only after a great deal of unnecessary friction.

Your new team’s problem isn’t that they haven’t been together long enough. It’s that they don’t yet know who knows what, and they don’t yet know how to work with each other. Time is just the slowest, most expensive, least reliable way to fix that.

The captain and first officer who met this morning don’t get six months. They get a briefing—and by pushback they’re coordinating high-stakes decisions like they’ve been doing it for years, because someone built the conditions instead of waiting to see whether they’d appear.

The flight crew doesn’t have time to hope. Neither does your team. Build the clarity, build the empathy, and your team will collaborate fast because you made it possible—not because you got lucky.

---

If you want to explore how a keynote on team collaboration and the Click framework could help your organization’s teams work better together from day one, let’s talk. And if you’re curious about the full model behind Click, explore the Click keynote.