Stable vs Fluid Teams

There is a small island in the middle of the South Atlantic Ocean called Tristan da Cunha. It is often described as the most isolated inhabited island in the world: home to only 250 people, nearly 2,800 km from the nearest continent, reachable only by a supply ship that sails from Cape Town roughly ten times a year and takes about seven days each way. The population is closed enough that only four or five family names exist on the island, and diseases like asthma affect more than half of the population due to the limited genetic diversity from a founder effect. You cannot simply move there, buy property, or open a business; permanent residency is extremely restricted and practically impossible for outsiders to obtain. One of the inhabitant described life there as follows: "it’s about living with the land, making do with what you have, and looking out for each other, no matter how small the island or how big the challenge. There’s no Tesco, no Amazon Prime deliveries, no endless options when it comes to food or entertainment. But what we do have is a tight-knit community, a deep respect for the environment, and a tradition of self-reliance that runs through everything we do. Life may be slower, simpler, and at times a little more chaotic, but there’s a kind of beauty in it—a beauty that’s harder to find in the hustle and bustle of modern life. And while you won’t find any Instagram-worthy beaches or fast-food outlets, you’ll find something much more rare: a place where everyone knows your name, and you’re never really alone."

At first, it looks like a paradox: an isolated place with only a few people who are far less lonely than most of modern society. One reason modern life produces more loneliness despite far more people and options is choice. When you have many possible options (for goods or relationships), you commit less deeply to any one of them, because you know that there's an alternative. This is sometimes called choice overload, or the paradox of choice. However, in a stable, closed community like Tristan da Cunha, relying on other people isn't optional, it's a necessity, and "thick" relationships dominate. When your livelihood depends on collective effort (fixing the only boat, sharing a harvest, responding to an emergency with no outside rescue coming quickly), individual interest and group interest naturally align. In modern society, those thick relationships have transformed to "thin" ones: single-purpose, optional, transactional. According to evolutionary psychologists, humans evolved in small groups of roughly 150 people, where survival depended directly on the group. Modern environments let a person survive in near-total social isolation, something we have not yet adapted to, and the result is a mismatch: deep belonging in small, stable groups has been eroded by choice overload and mobility, while the psychological need for that belonging hasn't changed at all.

The Same Pattern Shows Up in Teams

This pattern, it turns out, shows up in teams almost unchanged. Stable teams, the workplace equivalent of Tristan da Cunha, tend to perform better on tasks that require members to trust each other enough to admit mistakes, ask for help, and speak up. Organizational psychologists call this psychological safety, and it relies on mutual trust that come almost for free once people have worked alongside each other for years.

Contrast this with fluid teams, much more typical of modern organizational life, where interdependence is often artificial: you can fail without much personal cost, or succeed without much collective effort, because the team forms fast and doesn't stay together long. These teams can still function well, but the trust they have is different. Researchers call it "swift trust", built on professional role and category rather than personal history. A film crew, a surgical team, or a project task force can coordinate effectively on day one because everyone trusts the role, not the person. But this kind of trust rarely accumulates into the deeper kind that stable membership builds. The same errors that get discussed in a stable team often stay hidden in a fluid one.

Why is trust important? Many studies show that in teams with weak trust, mistakes are quietly corrected or remain hidden, because admitting an error, especially your own, feels risky in a group where you can't be sure how it will be received. It is not competence that mainly drives whether people challenge a decision, but rather whether the relationship has enough accumulated trust to make that feel "survivable", or at least less psychologically costly. A team that never challenges anything, or does not know its errors, stops learning, and mistakes unanimity for correctness when that "unanimity" is really just everyone independently deciding it wasn't worth the social cost to object.

The Downsides of a Closed Team

However, stable groups aren't automatically better; there are real caveats to the stable-team advantage. A large scale study shows that performance rises as the team settles in, peaks around two to three years, and then declines because the team stops reaching outside for information and develops a bias against outside ideas. In general, overly stable groups have less tolerance for dissent, more pressure to conform, slower diffusion of new ideas, and conflict that's harder to escape because you can't simply leave the group. Groupthink and a lack of diverse viewpoints are real risks once people have worked together for years.

Some typical warning signs of an overly closed team:

What's missing across all of this is the same thing: diversity of thought, and tolerance for productive friction.

The Downsides of a Fluid Team

The opposite extreme has its own failure list:

What's missing across all of this is close to the mirror image of the closed team's problem: interdependence, accumulated trust, and group (or institutional) memory.

Pulling Toward the Middle

Just as Tristan da Cunha isn't the "good" form of society and individualism isn't the "bad" one, a fully stable team isn't simply better than a fully fluid one. They're two different sets of trade-offs. Necessity-driven interdependence builds specific capacities (trust, mutual reliance) at the direct cost of others (diversity of thought, tolerance for outside ideas).

Why is this a trade-off? A smaller group becomes more predictable over time simply because, in a physically closed place, membership doesn't fluctuate. Members converge on a shared "mind", shared assumptions, vocabulary, instincts, which makes them predictable to each other. That predictability lets trust-relevant evidence build: each time someone performs well (ability), keeps their word (integrity), or acts in another's favor at a cost to themselves (benevolence), it confirms they can be relied on. That same convergence is mechanically opposed to diversity: minds can't reliably think alike and reliably think differently at once. Moreover, the bias toward exploitation over exploration under scarcity and high stakes is rational, and can be explained, at the level of individual psychology, by prospect theory and status quo bias: the certain, immediate payoff of the known method is worth more, psychologically, than a probabilistically better but uncertain alternative, especially when a failed experiment could be fatal rather than just costly. Although the environment has changed since then, our instincts around risk and dissent haven't caught up nearly as fast.

Calibrating the Trade-off

Most real teams aren't purely one extreme or the other. They are mostly hybrid and sit somewhere on a spectrum between Tristan-da-Cunha-style enmeshment and individualist-society-style diffusion. A good team leader's job isn't to pick one culture and install it. It's to notice which failure mode the team is currently drifting toward, and pull it back the other way. Provide enough shared stakes and trust to get Tristan-level cooperation under pressure, while keeping enough openness to outside ideas and tolerance.

Before turning to more specific levers, it helps to separate two viewpoints on this same dynamic, at the level of the organization rather than the individual: one about structure (from sociology), one about behavior (from organizational learning).

In organizational learning, this is known as the trade-off between exploitation and exploration: every group has to balance refining and efficiently using what already works against searching for new alternatives whose payoff is uncertain. Exploitation has faster, more certain, easier-to-measure payoffs, so it often wins over exploration even if the team members are risk-tolerant. However, it is not always the best strategy, especially in the long term. Katz's aforementioned seminal work on long-tenured R&D project teams found a curvilinear performance curve; team performance rises in the first few years, and then declines. In this framing, a stable team is an exploitation engine: performance rising as execution gets more efficient, then falling as the team loses the capacity to look out. In contrast to this, a fluid team is an exploration engine, constantly importing untested combinations of ideas, with the mirror-image failure: too much churn, and the team never settles long enough to actually bank the returns on anything it discovers. A research lab that always refines its existing research without discovering new fields is, by this definition, a pure exploitation engine.

The same trade-off has a name in social science that connects back to the thick versus thin relationships mentioned earlier: bonding versus bridging capital. Bonding happens when you connect with people similar to you; bridging happens when you connect across difference. A closed group has bonding capital in abundance and almost no bridging capital, since essentially nobody new arrives and nobody leaves to bring outside experience back. PhD students who become permanent members of the very lab where they earned their degree, without ever leaving, are a textbook case of this. A healthy team or organization needs both bonding and bridging capital: bonding gives people a secure base and a sense of belonging, while bridging is what lets a team innovate and solve bigger problems by pulling in outside expertise. But Katz's study shows that teams that quietly stop maintaining external relationships perform worse over time, even while everything inside the team looks perfectly fine.

These two viewpoints are similar but not the same. Exploitation and exploration describe where a group's effort actually goes: toward refining what it already knows, or toward searching for something new. Bonding and bridging describe the shape of its relationships: dense ties within the group, or sparser ties reaching outside it. One is about behavior; the other is about structure. A group can have one without the other. For example, someone on the team has contacts in five other labs or companies, attends outside conferences, reads broadly, but none of that outside knowledge ever gets pulled into the group's actual work. Structurally the group looks well-bridged; functionally it's pure exploitation. Conversely, a team can be tightly bonded, with almost no external ties, and still be internally exploratory: a small, closed group that spends its energy on novel internal work, arguing out new approaches among themselves rather than importing them. So bridging is better understood as a channel that makes exploration cheaper and more likely, not as exploration itself.

Practical Levers

Most practical levers fall into one of two categories: structural levers, which change the shape of the network itself (who is tied to whom, who depends on whom, who holds authority or knowledge), and cultural or people levers, which change what the group chooses to do with the network it already has. Many cultural, or people, levers encourage members to speak up honestly about mistakes and potential failures by lowering the social cost of doing so; others help spread new ideas and approaches within the team. Here are a few specific, practical levers a team or lab can pull, depending on which side it's drifting toward.

Structural levers

Cultural and people levers

Ranking the levers

I think the problem isn't that people are unaware of these levers, but that they apply them in an ad hoc manner rather than systematically. Round-robin discussion or reading groups in a team with zero real task interdependence is likely to produce much weaker results than the same technique in a team where the outcome actually matters to everyone in the room.

In general, structural levers tend to have broader, more durable, self-sustaining impact, since they're built into the structure and don't depend on anyone's memory or discipline. However, they're typically also more expensive to install. Cultural and people levers tend to be cheaper, with more immediate, but narrower and more fragile impact: they aren't really self-sustaining and erode if nobody actively maintains them.

I haven't found a study that ranks these levers by potential impact, or one that establishes a causal relationship between them, maybe because it's too context-dependent; it depends on the local constraints and the personality traits of the group members (e.g., you can't apply task interdependence if the system deliberately discourages cooperation among PhD students to hold them individually accountable, or the "Devil's advocate" lever fails in a group whose members are, on aggregate, high in conflict avoidance). Still, I'd love any framework that provides a methodology to do so.