Most collaboration advice treats trust, communication, and teamwork as separate skills you can pick up in any order. They aren't. They form a stack — and skipping a level doesn't make you faster. It makes the level above it unstable.
The stack has five levels: Competence, Reliability, Communication, Trust, and Synergy. Each one depends on the ones below it — not loosely, but through a specific mechanism. Here's what actually connects them.
Foundation Layer: Competence and Reliability are a joint gate, not a sequence
Competence and reliability aren't the same thing, and neither strictly produces the other. Reliability is consistency of behavior — showing up, following through, doing what you said. Competence is quality of output — doing it well. A brand-new employee can be completely reliable while still being low-skill at the actual work. They're two different questions: will you do the work, and can you do it.
A team doesn't advance past level one until both questions have a good-enough answer. And they can partially substitute for each other, up to a point: a highly competent but somewhat unreliable person can still succeed, and a highly reliable but still-developing person can still succeed. What can't work is low on both. The real gate isn't competence in isolation — it's whether the cost of a mistake during someone's learning curve is something the team can absorb. A new hire still learning your CRM software can afford to be reliable-but-still-learning; a mislabeled contact is a two-minute fix. A new hire learning to process wire transfers can't afford the same patience — one incompetent rep before the learning curve completes can be unrecoverable, no matter how reliable the person has otherwise been.
The rule: competence and reliability form a joint threshold, not a one-way pipeline — and how much either one can carry the team depends on what a mistake would cost.
Level 2: Reliability enables Communication
Unreliability doesn't stop people from talking to each other. Managers don't go silent on employees who miss deadlines — they check in more. What changes isn't whether you communicate, it's what kind of communication you're having.
Reliable relationships get open, low-friction communication — ideas exchanged on their own merits. Unreliable ones get communication that's really monitoring wearing a friendlier face: every message carries an unspoken "and will you actually do this?" underneath it. Reliability is what lets a conversation be about the substance instead of the follow-through.
The rule: unreliability doesn't eliminate communication — it degrades it into monitoring.
Level 3: Communication enables Trust
Communication alone doesn't produce trust. Plenty of relationships involve frequent, detailed, even scrupulously honest communication without any real trust behind it — a vendor negotiation can be fully transparent precisely because neither side trusts the other and everything has to be put in writing.
What actually converts communication into trust is consistency between what someone says and what they do — especially in the moments where it would've been easy to fudge it and no one would have noticed. That's the evidence trust is built on. Communication is just the channel it travels through.
The rule: communication is necessary but not sufficient for trust — trust forms when words and follow-through match, particularly under low scrutiny.
Level 4: Trust enables Synergy
Synergy — genuinely new solutions neither person would have reached alone — requires exposing half-formed ideas and letting your thinking get changed in front of someone else. That's risky. Without trust, people protect themselves instead: they defend pre-formed positions, hide the weak points in their own thinking, and the conversation collapses into negotiation instead of synthesis.
One good idea can still emerge from strangers under the right pressure — a deadline, a shared constraint, dumb luck. But that's a one-off. What trust actually buys isn't the possibility of synergy; it's the repeatability of it. Without trust, every breakthrough is an accident. With trust, it becomes something the relationship produces on demand.
The rule: trust doesn't make synergy possible once — it makes synergy repeatable.
| Transition | What actually unlocks the next level |
|---|---|
| Competence + Reliability | Both clear a joint threshold; errors during the learning curve are cheap enough to absorb |
| Reliability → Communication | Conversation stops being monitoring in disguise |
| Communication → Trust | Words and follow-through match under low scrutiny |
| Trust → Synergy | Synergy becomes repeatable, not a one-off accident |
The exception: what Herb Brooks proves about timelines
The stack usually builds over a season — games, setbacks, repeated proof. But it doesn't have to take that long. It has to happen in that order.
Herb Brooks had a handful of months to build a team that could beat the best hockey program in the world. He said, "I'm not looking for the best players. I'm looking for the right players." No American player in February 1980 was already competent enough to beat the Soviets — that team had no equal at the level of skill, experience, or tactical sophistication. So Brooks wasn't choosing between competent-but-unreliable and incompetent-but-reliable. He was selecting for something else entirely: coachability, discipline, willingness to subordinate ego to a system, and the capacity to absorb a brutal training load without breaking. Call it meta-competence — competence at becoming competent, fast.
That's still level one. Brooks didn't skip competence and jump to reliability or trust. He gated selection on a form of competence the stack doesn't usually have to name explicitly, because most collaborations have the luxury of time and don't need it. Then he closed the gap through volume and difficulty — teaching the team an entirely new hybrid style, a blend of the Soviet and Canadian schools, through repeated, punishing training before he asked anything of their trust or cohesion as a unit.
What changed under time pressure wasn't the order of the stack. It was what "competence" meant at the selection stage, and how much intensity was required to close the gap fast.
Time pressure doesn't let you skip levels. It changes what you're allowed to select for at level one, and how hard you have to work to close the gap.
Why the order matters
Every level in this stack is a proxy for the one below it, refined. Reliability turns isolated competence into an asset the team can plan around. Communication is reliability made open. Trust is communication made consistent. Synergy is trust made productive. Try to build synergy with someone before trust exists, and you get negotiation instead. Try to build trust before communication is honest, and you get compliance instead. The failure mode is always the same: reaching for the output of a level you haven't actually built the foundation for.
If you want to see the individual pieces of this stack worked out in more depth, they're covered across a few companion pieces: How to Disagree Productively, Tactical Empathy, The Difference Between Compromise and Synergy, How to Extend Trust in Stages, The Economics of Trust, and When Collaboration Is a Waste of Time.
No comments:
Post a Comment