05 · Building Trust¶
Trust is the currency servant leadership runs on: without it, delegation (Module 6) reads as abandonment, feedback (Module 8) reads as attack, and empathy (Module 4) reads as manipulation. Trust isn't built through one grand gesture — it's built (and destroyed) through a large number of small, consistent moments. This module gives you a concrete model for what trust is made of and how to repair it when it breaks.
1. The trust equation¶
A widely used model (from The Trusted Advisor by Maister, Green, and Galford) expresses trust as a ratio:
| Component | What it means | Leadership example |
|---|---|---|
| Credibility | Do you know what you're talking about, and do you tell the truth? | Admitting "I don't know, let me find out" instead of bluffing |
| Reliability | Do you consistently do what you say you'll do? | Following through on small commitments (a promised follow-up, a 1:1 that isn't cancelled) as much as big ones |
| Intimacy | Do people feel safe being honest and vulnerable with you? | Sharing your own uncertainty or mistakes first |
| Self-orientation | How much are you focused on your own interests vs. theirs? | Making a call that's best for the team even when it costs you something |
Because self-orientation is the denominator, it has an outsized effect: even high credibility, reliability, and intimacy collapse trust if people sense the leader is ultimately optimizing for themselves. This is the mathematical version of Greenleaf's core claim in Module 1 — a leader who is visibly self-serving cannot be a servant leader, no matter how competent or consistent they are.
2. Trust is built in small moments, not big ones¶
The single highest-leverage trust-building behavior most leaders underrate: doing exactly what you said you'd do, on small things, every time. Showing up on time to a 1:1, following through on "I'll get back to you by Friday," remembering a detail someone mentioned last week — these compound. A leader who nails the big dramatic gestures (a public defense of a team member) but flakes on small commitments (repeatedly rescheduling 1:1s) ends up with less trust than one who's unremarkable in public but rock-solid on the small stuff, because reliability is judged on frequency, and small moments vastly outnumber big ones.
3. Repairing broken trust¶
Trust breaks in two very different ways, and they need different repairs:
| Break type | Example | Repair |
|---|---|---|
| Competence break | You made a call that turned out wrong, or missed something important | Own the miss specifically, explain what you'll do differently, follow through visibly next time |
| Integrity break | You said one thing and did another, or weren't honest | Acknowledge the specific gap directly (not a vague "sorry if that landed wrong"), and understand that integrity breaks take much longer to repair than competence breaks, because they call your character into question rather than your judgment |
A repair attempt that minimizes ("it wasn't that big a deal") or shifts blame ("well, you should have double-checked too") generally makes an integrity break worse, because it reads as another small integrity break layered on top of the first one.
4. A worked example¶
A manager, Elena, tells her team she'll advocate for a headcount request in the next budget cycle. The request gets cut and she doesn't tell anyone until someone notices the org chart didn't change two months later.
- Trust-damaging response: "It wasn't really up to me, leadership just didn't approve it" — technically true, but the delay and the deflection both register as a self-orientation problem: it looks like Elena avoided an uncomfortable conversation rather than prioritizing the team's need to know.
- Trust-repairing response: As soon as the decision was final, Elena tells the team directly: "The headcount request didn't get approved this cycle. I should have told you as soon as I knew instead of letting two months pass — that's on me. Here's exactly what I pushed for, here's why it was cut, and here's when I'm raising it again." This names the competence issue (the ask was cut) and the separate integrity issue (the delay in telling them) without blending them into one vague apology.
How It Actually Works¶
Trust between a leader and a team is best modeled as an equilibrium in a repeated game, not a fixed personal attribute someone either has or lacks. In game theory, a single interaction (a one-shot Prisoner's Dilemma) rationally favors defection — betray the other party, since there's no future interaction to punish it. But when the same two parties interact repeatedly with an unknown end point, cooperation becomes the rational equilibrium strategy (this is the folk theorem result, and it's the same logic behind the famous success of "tit-for-tat" in Axelrod's iterated tournaments): each party cooperates because the discounted value of future cooperation exceeds the one-time gain from defecting now. This is precisely why trust is "built in small moments, not big ones" — every small kept commitment is another round of the repeated game resolving toward cooperation, and it's why a single significant betrayal can undo dozens of small deposits: it changes the other party's estimate of your strategy going forward, not just their feeling about one incident.
Why competence and character are separate trust variables, not one scale. The trust equation typically separates reliability/competence (will they do it well?) from integrity/benevolence (are their intentions toward me good?) because they fail independently and are diagnosed by different evidence. A leader can be highly competent and still be distrusted because their incentives are read as misaligned with the team's (low benevolence) — this is a common failure for leaders who deliver results but are perceived as doing so at the team's expense. Repair strategies differ accordingly: a competence failure is repaired by demonstrated capability over time; a benevolence/integrity failure requires an explicit acknowledgment and a visible change in incentive alignment, because no amount of competence signals resolve a fear about intent.
Repairing broken trust is slower than building it because of negativity bias. Loss-aversion research (Kahneman & Tversky) shows people weight a negative signal roughly twice as heavily as an equivalent positive one when updating a belief. After a violation, a leader needs roughly proportionally more consistent positive evidence than the original violation cost — not because people are being unfair, but because the updating process itself is asymmetric by design (a useful survival bias in general: overweighting threats has higher evolutionary payoff than overweighting good news).
Exercise¶
Using the trust equation, rate yourself honestly (1-5) on each of credibility, reliability, and intimacy with one specific team member, colleague, or direct report — then rate your self-orientation in that relationship (1 = clearly focused on their interests, 5 = clearly focused on your own). Write 2-3 sentences on which component is your weakest, and one concrete, small, repeatable action you'll take in the next two weeks to strengthen it — not a grand gesture, but something you can do consistently.