When trust is already broken

The 3-step framework to repair it (and how to know when to stop trying)

Most trust breaches do not arrive with an announcement. They arrive as silence. A senior engineer who used to push back stops pushing back. A peer who used to forward you context starts cc-ing your manager instead. A direct report who used to ask for feedback stops asking. By the time the breach surfaces, in a resignation conversation or a 360 result, the damage is already months old.

In the first article in this series, I argued that trust is a skill, not a trait. 14 specific behaviours, 8 rational and 6 emotional, that you can practice on purpose. The same logic runs in reverse. Repairing broken trust is also a skill, also learnable, and it follows a sequence that works when you follow it and fails when you skip steps.

This article gives you the sequence. Three steps. Three short scripts for the hardest moments. And the criteria for the situations where repair is not the answer, and walking away is. I will be honest about that last part, because most articles on this subject are not.

First, name what actually broke

Most managers misdiagnose the breach. They reach for the word “communication”, because it is the safe word, and ask HR to suggest a training. That almost never works, because “communication” is rarely what broke.

What broke is something specific. One of the 14 behaviours from the first article. A missed commitment is Reliability. Withholding information that affected someone’s work is Openness. Deciding their priority for them without asking is Respect, or Listening, or both. Treating them differently than their peer is Fairness.

You cannot repair a breach you have not named. Find the specific element. Write down what you said or did and the moment the other person stopped trusting you. If you can write that paragraph in plain language, you are ready for step one. If you cannot, you are not.

Can trust be rebuilt at all?

Yes, sometimes. Not always.

Trust can be rebuilt when three conditions hold. One, the person who caused the breach acknowledges what actually happened, in the unsanitized version. Two, both sides are willing; if the other person has emotionally walked out, no framework will bring them back. Three, there is time. Repair is measured in months, not in one well-crafted Slack message.

If you are not sure whether those conditions are met, start the conversation anyway. The first sentence will tell you. The other person’s eyes, body, and pause length will tell you more than any 360 review ever did.

The three steps: Acknowledge, Account, Act

Three steps, in order. Each one has to be complete before you move to the next. Skipping steps is the reason most repair conversations fail.

Step 1. Acknowledge. Name, specifically, what happened. Drop the corporate hedging language. No “if there were any issues”. No “I hear there were concerns”. No “mistakes were made”. Those phrases are the corporate equivalent of pleading the fifth. The acknowledgment has three parts: what you said or did, what the impact was, and that you own it. No qualifier. No “but I had reasons”. Until that lands, nothing else you say will be heard.

Step 2. Account. Give the other person a causal picture they can believe, without using that picture to escape responsibility. The construction is simple. “Here is what was happening for me. That does not justify it. I want you to understand how it happened.” The point of the account is to remove the worst story the other person might be telling themselves about why you did what you did. You are not trying to look better. You are removing a story that, if it stays, makes repair impossible.

Step 3. Act. Propose a specific change, in plain language, that the other person can verify. Not “I will communicate better.” That is a wish. A commitment is something the other person can check on a given Tuesday. Then, and this is the part most people forget, you actually do it. Over weeks and months. Without being thanked for it. Without expecting acknowledgement that you have changed. Trust is not repaired in the conversation; it is repaired by what you do in the 90 days after.

Write the commitment in your own notebook. Set a recurring reminder. If you have to break the new commitment, surface it before it happens, not after. The next breach inside a repair window is the one that ends the relationship.

The hardest moment: apologizing without losing authority

Many of the leaders I work with, especially first-time managers in tech and finance, freeze on the repair conversation because they think apologizing publicly will cost them authority. The opposite is true. A clean, specific apology, delivered once, raises your authority. Vague apologies, or apologies that turn into reassurance-seeking, lower it.

Three scripts I have given to leaders in coaching. Read them out loud, in your own voice, with the names of the actual people involved. They get easier with one or two reps.

Script 1. You missed a commitment to a direct report.

“I told you I would have the feedback by Friday. I did not. I know you were waiting on it. The reason, not the excuse, is that I under-planned my week. What I will do differently: from next week, if I am going to miss a promise to you, you will hear from me before the deadline, not after. Is there anything I need to hear from you on this?”

Script 2. You lost your temper in a meeting.

“In yesterday’s meeting, I raised my voice and I cut you off. That was not okay, and I apologize. What was going on for me does not justify it. Going forward, if I feel that way again, I will stop the meeting or leave the room. Whenever you are ready, I want to hear what the impact of that moment was for you.”

Script 3. You made a decision affecting them, without consulting them.

“The decision to move you off the project was mine, and I made it without talking to you first. That was wrong. You deserved to hear the reasoning from me before it was announced. Here is the reasoning now. Going forward, any decision that affects your role, you hear it from me first.”

One rule that holds for all three. Say it once. Do not over-apologize. Repeated apologies shift the emotional labour onto the person you are apologizing to, and they end up reassuring you. That is the opposite of repair.

When to stop trying

This is the part no consultant wants to write, because it is bad for business. I am writing it anyway, because it is true. Sometimes, repair is not the answer. Three signals tell you when.

One. The breach keeps repeating. If you have done the full three-step framework properly, twice, and the same pattern returns, you are not in a repair situation. You are in a values-mismatch one, and continuing to repair will hurt both of you.

Two. The other side will not engage. If you try to have the conversation and they refuse, deflect, or quietly disappear from your one-to-ones, repair is not available to you alone. You can be ready on your side; you cannot force the other person.

Three. The breach was ethical. Harassment, dishonesty about money, a serious violation of confidence. These are not repair situations. They are boundary situations. Walk away, document, and use the proper channels.

Trust repair is a skill, not an obligation. Knowing when to stop is part of the same skill.

A 30-day rebuild plan

When the three steps have been delivered, the work has barely started. Here is the structure I give clients for the 30 days that follow.

Days 1 to 7. Do nothing dramatic. Show up the same as before, deliver on small commitments, do not over-perform repair behaviour. Overcompensation reads as guilt looking for forgiveness.

Days 8 to 21. Find two or three small moments where you can demonstrate the specific behaviour you committed to. Not announce it. Demonstrate it.

Days 22 to 30. One short check-in. Three minutes. “How is it landing on your side since we talked?” Listen. Do not defend. Take whatever they say at face value. If they say it is better, it is better. If they say it is not yet, ask what one more thing would help.

What to do with this

Repair uses the same vocabulary as building trust in the first place. You name the behaviour that broke. You acknowledge it specifically. You give the other person a causal picture without an excuse. You commit to a different behaviour. Then, for 30 days, you do that behaviour.

If you have read this far, you are probably either inside a breach or watching one develop. Both are workable. Pick the conversation that is hardest to have, the one you have been avoiding. Have it this week. Use the script above that fits closest, in your own words.

If you would like a structured version of this work for your team or your leadership population, that is what we do at Mindset Consulting. Either way, the next step is yours..