Skip to content
Published on

A Team Built on Trust — How to Build Trust

🇰🇷KO🇺🇸EN🇯🇵JA
Split View필사 모드
Authors

Opening — Silence in the Meeting Room

There were two teams. Team A's meetings were always lively. People said "I don't know this" without hesitation, objected with "I think that decision is wrong," and, when they made a mistake, confessed first: "I broke things in yesterday's deploy."

Team B's meetings were quiet. Nobody said they didn't know, nobody objected, and when an incident struck they passed the blame around. On the surface Team B looked more harmonious — there was no conflict, after all.

But a year later, the team that produced the better results was the noisy Team A. Team B's silence wasn't peace; it was fear. Afraid of being laughed at for saying something wrong, of looking incompetent for admitting ignorance, of falling out of favor for objecting, everyone kept their mouth shut. In that silence, problems festered.

The difference between the two teams can be summed up in one word: trust. This essay covers, concretely, why trust is the foundation of performance, what trust is made of, and above all how you can build it.

The Relationship Between Trust and Performance

It's easy to think of trust as merely a "nice to have," but the data says otherwise. Trust is a direct driver of performance.

On high-trust teams, information flows fast. Bad news travels fast too. A warning like "I think this is about to go very wrong" reaches the top. On low-trust teams, by contrast, information clogs. People hide information to protect themselves, and bad news stays buried until it explodes.

You can also see trust's effect through the lens of transaction cost. Without trust, everything has to be checked, documented, and approved. With trust, "Got it, I'll leave it to you" is enough. Trust is the lubricant that reduces the friction of collaboration.

How a team operates by level of trust

Low trust                        High trust
   │                                │
hide information ◄──────────► share information
check everything ◄──────► delegation and autonomy
defensive posture ◄─────────► candor
bad news arrives late ◄───► bad news arrives fast
slow decisions ◄─────► fast decisions

Balance is needed, though. Unconditional trust is naivety. Healthy trust comes with verification. As the maxim "trust but verify" suggests, trust is not exemption from accountability but something that travels alongside it.

The Three Components of Trust

Trust is not a vague feeling but a structure you can analyze. Let me split it into three axes often cited in trust research: competence, consistency, and benevolence.

Competence — Can They Get It Done?

No matter how nice someone is, if they can't do the work, trust about the work doesn't form. It's the foundation of the belief "if I leave it to this person, it'll get done well." Competence is a necessary but not sufficient condition for trust. With skill alone and no consistency or benevolence, you become "a scary person."

Consistency — Are They Predictable?

It's hard to trust someone who is different today than tomorrow. Working with someone whose standards shift with their mood and who reacts differently to the same situation means always reading the room. Consistency provides the stability of "I can predict how this person will react." Steadily keeping small promises is the heart of consistency.

Benevolence — Are They on My Side?

The belief that "this person won't exploit me or harm me." Even with competence and consistency, if benevolence is in doubt, trust collapses. Benevolence shows up in small places: whether they steal your credit, whether they turn their back when things get hard, whether they sincerely want you to grow.

Trust = Competence × Consistency × Benevolence

If any one of the three is 0, since it's multiplication, trust approaches 0.
- Competent and benevolent but inconsistent → too flighty to rely on
- Competent and consistent but no benevolence → capable but frightening
- Consistent and benevolent but not competent → a good person you can't assign work to

Meeting Regularly to Talk

Trust is not a one-time event but the product of repeated interaction. People come to trust those they face often. So the simplest and most powerful way to build trust is to create regular occasions to talk.

The 1-on-1 is the prime example. Once a week or every two weeks, a time to talk person to person rather than report progress. What matters here is frequency and consistency. If you keep canceling because you're busy, you send the message "you're not a priority for me."

Here's an example of a good 1-on-1.

[A 1-on-1 that became a status report]
Lead:   How's progress this week?
Member: Yep, finished task A, B is about 70%.
Lead:   Great. Counting on you next week too.
(Over in 5 minutes, no trust built)

[A 1-on-1 that became a conversation]
Lead:   Anything stuck or frustrating in your work lately?
Member: Honestly, task C feels beyond my ability and I'm a bit anxious.
Lead:   Thank you for being honest. Which part is hardest?
        Is there something I can help with?
(Vulnerability surfaces, help flows, trust builds)

The key is for the leader to speak little and ask much — and to actually respond to what comes up. Listen and then do nothing, and honest talk won't come up next time.

Keeping Promises — The Smallest Unit of Trust

Trust accrues not from grand gestures but from the accumulation of small promises. If you said "I'll send it by tomorrow," send it by tomorrow. Be on time for meetings. Don't disclose what you were told in confidence.

Interestingly, people are more sensitive to the breach of small promises than big ones. Big promises are forgiven as having unavoidable circumstances, but repeatedly breaking small ones like "I'll reply in 5 minutes" hardens the impression that "this person just doesn't keep their word."

The most important skill in keeping promises is, in fact, "making fewer promises." Someone who answers every request with "sure, will do" ends up breaking many promises. Promising only as much as you can keep and keeping it reliably builds far more trust. And if you can't keep a promise, telling people early and honestly does the least damage to trust.

Vulnerability and Admitting Mistakes

A counterintuitive fact: people trust those who candidly reveal their weaknesses more than those who strain to look strong. Patrick Lencioni, in The Five Dysfunctions of a Team, called the foundation of trust "vulnerability-based trust."

When a leader says "I don't really know this" or "the last decision was my mistake," paradoxically the team's trust rises. Because in that moment others, too, become able to say they don't know what they don't know and to call a mistake a mistake. When a leader pretends to be perfect, members feel they must pretend to be perfect too — and then real problems get hidden.

Let me distinguish good and bad ways to admit a mistake.

[Bad admission — excuses and deflection]
"I made a mistake, but really the requirements weren't clear."
"Sorry. But the timeline was way too tight."

[Good admission — admit, impact, plan]
"I skipped pre-deploy testing. That caused a 30-minute outage.
 The cause was this, and to prevent recurrence I've added this item to the deploy checklist."

A good admission has three parts: what went wrong (admit), what impact it had (impact), and what will be done going forward (plan). No excuse creeps in.

Psychological Safety — Edmondson's Research

A concept you can't leave out of any discussion of trust is psychological safety. Defined by Harvard's Amy Edmondson, it means "a shared belief that the team is safe for interpersonal risk-taking."

Put simply, the belief that you won't be punished or humiliated for asking a "dumb" question, admitting a mistake, voicing dissent, or asking for help. Edmondson made an interesting discovery in her original hospital research. She first assumed "better teams will make fewer mistakes," but the data was the opposite: better teams reported more mistakes.

The reason was simple. Better teams didn't make fewer mistakes; they reported mistakes more honestly. Unsafe teams hid mistakes. A hidden mistake isn't learned from, and it recurs.

Psychological safety and trust are similar but distinct. Trust is an interpersonal matter — "do I trust that person?" Psychological safety is a team-level culture — "is it OK for me to take risks in this group?" The two reinforce each other.

A leader's language that raises psychological safety
- "This work is complex, so we can all make mistakes. Let's learn together."
- "Good question. Honestly, I was wondering that too."
- "Dissent is welcome. Who has a different view?"
- "It's OK to fail. What matters is what we learned."

A caution: psychological safety does not mean "anything goes with no standards." Edmondson stresses that high psychological safety must go hand in hand with high standards. Safe but low-standard makes a complacent team; high-standard but unsafe makes an anxious team. Only when both are high do you get a learning, growing team.

Trust on Remote Teams

As remote and hybrid work became routine, the conditions for trust changed too, because the chance hallway conversations and the closeness built over shared lunches disappeared. Remotely, you have to design trust deliberately.

The heart of remote trust is transparency and asynchronous communication. Since you're not in the same space, what people are doing isn't visible. So it becomes important to record work in the open, leave decisions in documents, and share progress voluntarily. This isn't surveillance; it's an act of trust that bridges invisible distance.

Practices for building trust on remote teams
- Make work visible asynchronously: record progress in issue trackers, public channels
- Don't force cameras on, but set up regular face-to-face time
- Trust based on "output," not "hours worked" (no micromanaging)
- An async-first culture that respects time zones and circumstances
- Keep a separate light chit-chat channel to maintain human connection

The most common trust killer remote is micromanaging. Because you can't see, anxiety drives you to keep checking — and frequent checking sends the message "I don't trust you." Remotely, evaluating by results rather than process is the starting point of trust.

Repairing Trust — After It Breaks

Trust is hard to build and easy to break. But once broken, it's not over forever. Repair is possible. It just takes time and consistent action.

When trust breaks, the most common mistake is trying to paper over it with words. "Sorry, I won't do it again" won't bring trust back. Trust was broken by action, so it must be repaired by action.

Stages of repairing trust
1. Admit: concretely, without excuse, admit what you did wrong.
2. Understand: sincerely understand and express the impact on the other person.
3. Responsibility: promise concrete actions for repair.
4. Consistency: keep that promise steadily over a long period.
5. Patience: give the other person time to trust again. Don't rush them.

The last point especially matters. The offender wants to be forgiven and move on quickly, but the speed of trust repair is set by the wounded party. The attitude "I apologized, why are you still like this?" wrecks the repair again. Trust repair isn't done by keeping one promise; it's complete when you repeat it many times and a new pattern forms — "this person really has changed."

A Practical Checklist

  • Fix regular 1-on-1s with team members on the calendar, and don't cancel even when busy.
  • In the next meeting, as the leader, try saying "I don't know this" first.
  • Set one small promise (a delivery deadline, etc.) and keep it without fail.
  • When a mistake happens, share it in the "admit-impact-plan" format without excuses.
  • In meetings, explicitly ask "any dissent or different perspectives?"
  • Before checking a remote colleague's work, ask yourself whether you're trusting them by results.
  • If there's broken trust, start repairing it with consistent action instead of words.

Closing

Trust is a team's invisible infrastructure. In normal times you barely feel its presence, but when a crisis hits, the difference between a team that has it and one that doesn't becomes stark. A team with trust closes ranks in a crisis; a team without it scatters.

The good news is that trust is not innate but made. Not by grand vision statements or team-building workshops, but by the small daily actions of keeping promises, saying you don't know, admitting mistakes, and respecting colleagues' time.

If you envied Team A's noisy meetings, you can start today by keeping one small promise. Trust is built that way — one step at a time.

References

Discuss on Twitter • View on GitHub