Skip to main content
SWStudyWalks Search

Distrust and Repair

The narration between entries paraphrases; it never reads an entry aloud before the entry plays. Every entry in this lecture plays exactly as it does on its own page — same file, same speed, nothing laid over it.

What you can do after this

  1. Explain why distrust is a distinct state rather than the absence of trust, and how its filter works
  2. Tell integrity violations from competence violations, and say why each needs a different repair
  3. Explain how distrust is usually born, and how it spreads
  4. Apply the book's five-step repair process, and recognise a non-apology
  5. Describe the three phases of recovering from your own failure, and what repair cannot do

What it covers

20 entries in 7 topics. Each number links to that entry on its own.

  1. 1. What distrust is

  2. 2. Violations

  3. 3. How distrust is born

  4. 4. Principles of repair

  5. 5. The repair process

  6. 6. Leading after your own failure

  7. 7. What repair cannot do

Check yourself

What did Lewicki, McAllister and Bies argue about distrust?

That it is not merely the absence of trust but a distinct state of its own.

What did Kim and colleagues find repaired trust after integrity violations, compared with competence violations?

Apology worked better after competence violations; denial of blame worked better after integrity violations.

Where does the book say distrust is usually born?

In the gap between what a leader says and does, especially under pressure, rather than from conflict.

Why does the book's fifth repair step leave forgiveness to the other person?

Because the timeline of forgiveness belongs to the person who was harmed, and pressuring them is itself a form of control.

What is the book's conclusion from Director Okwu's story?

Some violations produce damage a repair framework can reduce but not undo.

Lecture transcript

The narration as recorded, in order. Where an entry plays, the transcript links to it rather than reprinting it — the entry plays from its own file, unaltered, and says the same thing on its own page.

This is Unit Eleven of The Lost ARC, on distrust, and on the repair of trust after it breaks. The last lecture closed on the asymmetry of trust: built in small increments, destroyed catastrophically. This one follows what happens after the destruction. Carry one question through it: if a leader apologises well and does everything right afterward, does the trust come back? The book's hardest story answers it, at the end. By the end you will be able to explain why distrust is a distinct state, and how its filter works. To tell integrity violations from competence violations. To explain how distrust is usually born, and how it spreads. To apply the book's five-step repair process, and recognise a non-apology. And to describe the three phases of recovering from your own failure, and what repair cannot do.

Three entries on what distrust is: a state of its own, able to coexist with trust, and able to filter what people see.

Distrust is its own state.

ARC 251 Distrust Is Not the Absence of Trust

Roy Lewicki, Daniel McAllister and Robert Bies argued in nineteen ninety-eight that distrust is not merely the absence of trust but a distinct state: an active expectation that someone will act with harmful intent, incompetence or indifference to your welfare. The book draws the implication that trust and distrust are separate dimensions, not two ends of one line.

How the two can coexist.

ARC 252 Trust and Distrust Coexist

Because trust and distrust are separate dimensions, the book says, a person can hold both toward the same person at once: trusting a colleague's technical skill while distrusting their motives, or a leader's vision while doubting their willingness to protect the team. That, the book warns, makes distrust harder to address than the either-or most leaders assume.

How distrust changes perception.

ARC 253 The Distrust Filter

The book describes distrust as a filter: once activated, it reads ambiguous actions as threatening and discounts evidence that would disprove it, so a neutral email reads as hostile and a genuine gesture is met with suspicion. The book draws on Elizabeth Phelps's work on the amygdala and emotion; the filter's details are the book's own reading.

Two entries on violations: the two kinds, and why a bad one weighs more than a good deed.

Two kinds of violation.

ARC 254 Integrity Versus Competence Violations

Peter Kim and colleagues found in two thousand four that trust was repaired better by apology after competence violations, but by denial of blame after integrity violations: a leader who misjudged and a leader who lied need different routes back. The book's reading is that integrity violations are taken as evidence about character, which is why they are far harder to repair.

Why bad weighs more than good.

ARC 255 Bad Is Stronger Than Good

Roy Baumeister and colleagues' two thousand one review concluded that bad is stronger than good, as a general principle across a broad range of psychological phenomena: bad impressions form faster than good ones, and resist disconfirmation longer. The book's application is that a single betrayal can outweigh months of trust-building behaviour.

Four entries on how distrust is born: the book's story of one evasion, the question it answered, and how quiet violations spread.

The book's story of distrust.

ARC 256 Andre and Ms. Collins

In the book's composite story, Andre fixes and documents a data error within forty-eight hours, and his trusted manager tells senior leaders only that they are still looking into it, leaving unsaid a twelve-second truthful sentence that would have credited him. Andre stops volunteering ideas, documents everything, and resigns three months later; his manager is confused.

The question that moment answered.

ARC 257 Integrity Under Pressure

The book's lesson from Andre is that one moment can answer a question a person never consciously asked: when it costs her something, will she tell the truth about me? Two years of honest conversations were outweighed by one evasion under pressure, and no later positive interaction could revise the answer, because it spoke to integrity under pressure.

How most violations happen.

ARC 258 Quiet Violations

The book argues that distrust is usually born not from conflict but from the gap between what a leader says and does, especially under pressure: a credit not given, a truth not spoken, a commitment not honoured, a person not defended. The damage outweighs the act, the book says, because the act reveals something the person hoped was not there.

How distrust spreads.

ARC 259 Distrust Spreads

The book warns that distrust is contagious: when one person starts protecting themselves, others notice the shift and follow, even without knowing why, so careful language, more documentation and less discretionary effort spread through a team in weeks. The leader often misreads the withdrawal as a performance or motivation problem, never linking it to the moment trust broke.

Four entries on repair: a repair that failed, then the book's first three principles.

A repair that failed.

ARC 260 The Repair That Failed

In the book's composite story, Director Anand dismisses a junior analyst, Clara, in public, then apologises the same afternoon with textbook precision. Clara accepts the apology, forgives him, and never again offers an unconventional idea. At her exit interview she says that some things, once broken, heal into a different shape; the book declines to improve on her sentence.

The first principle: match the violation.

ARC 261 Matching Repair to the Violation

The book's first principle of repair, drawing on Peter Kim, Kurt Dirks, Cecily Cooper and Edward Tomlinson, is that the type of violation decides the strategy. A competence failure is repaired by a sequence of better decisions; an integrity failure needs acknowledgment, responsibility and sustained change. Improvement alone cannot repair an integrity violation, because the question was about character.

The second principle: timing.

ARC 262 Repair Early

The book's second principle is timing: begin repair as soon after the violation as possible, before distrust starts filtering every interaction. A leader who waits a month finds that the ambiguous weeks have already been read as confirming the worst. The longer the delay, the book says, the more imagined evidence accumulates, without any new violation.

The third principle.

ARC 263 Repair Is a Process

The book's third principle is that repair is a process, not an event: no single honest conversation undoes a significant violation. It takes repeated, consistent demonstrations of changed behaviour, long enough to override the distrust filter. And repair after an integrity violation takes longer, and is less certain, than building the original trust took.

Three entries on the book's repair process, the apology that fails, and a leader who repaired.

The book's five-step repair process.

ARC 264 The Five-Step Repair Process

The book sets out its own five-step repair process, based on the research and the author's experience, taken in order with none skipped. First, acknowledge the violation specifically, naming what you did and its impact. Second, accept responsibility without qualification. Third, describe specific, observable changes the other person can check you against. Fourth, demonstrate them consistently over time, without expecting quick results. Fifth, make space for the other person's process, because the timeline of forgiveness belongs to the person harmed; pressuring someone to forgive is itself a form of control.

The apology that fails.

ARC 265 The Non-Apology

The book singles out the performative apology as a failed repair: saying you are sorry the other person felt that way manages responsibility instead of accepting it. Saying that in hindsight you would have handled it differently sits against saying you made the decision and it was wrong. People detect the difference, the book says, and the detection decides whether the repair lands.

A leader's repair.

ARC 266 Director Paxton

In the book's composite story, Director Paxton tells her team no positions will be cut, then learns two weeks later that three will be. Within forty-eight hours she holds a team meeting: a specific acknowledgment, the full details, and a commitment to label uncertain information as uncertain. Trust returned, the book says, gradually and incompletely, with residual wariness as permanent scar tissue.

Two entries on the leader as the one who broke trust: the response that decides what follows, and three phases of recovery.

When the leader is the violator.

ARC 267 When the Leader Is the Violator

The book treats significant failure as certain for every leader; the response decides whether it becomes a turning point or a pattern. Denial and blame-shifting turn one failure into a character signal; honest accountability turns it into evidence of integrity. The book notes that the second response can even strengthen trust, because it shows a leader who can face uncomfortable truths.

Three phases of recovery.

ARC 268 Three Phases of Recovery

For leaders recovering from their own failure, the book lays out three phases. Acknowledgment: name what happened, what you did and its consequences, specifically and to the people affected, as an apology owed to them rather than a lesson owed to yourself. Understanding: analyse what produced the failure, the wrong assumptions, ignored information and missed warnings, focusing on what you did rather than who you are. Reconstruction: sustain changed behaviour for months, sometimes years. The book separates diagnosis from self-recrimination: shame paralyses, while insight enables change.

Two entries to close: the book's hardest story of repair, and a diagnostic. The opening question is answered here.

The payoff: the book's hardest story of repair.

ARC 269 Director Okwu

The Lost ARC's hardest story of repair is Director Okwu, a composite leader who does everything its own framework asks and still does not get back what he broke. Facing a budget shortfall, he eliminates three positions by email on a Friday afternoon, without consulting his team. By Monday people walk past his office, and two senior analysts start documenting their work as if they expect to leave. On Thursday he delivers a model apology: specific, unqualified, with named changes and an invitation to accountability. Maren, who had argued hardest for transparent decisions, says nothing, and leaves four months later, telling her exit interview the apology was good but too late. Engagement recovers to within a few points, and Okwu keeps every commitment, yet two more people leave within eighteen months and the meetings keep a faint layer of caution. That answers this lecture's question. The book refuses to call it a success: the best response available, worth doing, and insufficient. Some violations produce damage a repair framework can reduce but not undo.

How to tell whether people feel safe.

ARC 270 Do People Feel Safe?

The book's distrust chapter ends with five diagnostic questions. When did someone last bring you a mistake voluntarily, and what did your response teach them? Do people share concerns openly, or save honest opinions for conversations you are not in? What would your team say if asked anonymously whether they trust you? Are your words and actions consistent? And when information is uncertain, do you share what you know, or wait? The matching practice is one honest step toward repair in one relationship, knowing a single conversation cannot erase distrust, but can interrupt it.

Look at what you can now do. You can explain why distrust is a distinct state that can coexist with trust, and how its filter reads ambiguity as threat. You can tell integrity violations from competence violations, and match the repair to the kind. You can explain how distrust is usually born, in the quiet gap between what a leader says and does, and how it spreads. You can apply the five-step repair process, and recognise the non-apology that manages responsibility. And you can describe the three phases of recovery, knowing, as Okwu's story shows, that repair can reduce damage but not always undo it. The next lecture turns to culture. The full framework, with every story and tool, is in The Lost ARC by Justin Ryan Carver, available on Amazon.

This is free, and stays free. If it helped, here is what keeps it running.