Repairing trust at work: what people get wrong

You made a mistake. People noticed. Now every message you send feels like it might be Exhibit A.

This is the part where well-meaning people accidentally make it worse. They over-explain. They apologise repeatedly. They try to sound sincere by sounding devastated.

Trust isn't rebuilt by sounding sorry forever. It's rebuilt by taking responsibility once, clearly, and then behaving in a way that makes the future feel safe.

What people get wrong about "repair"

An apology is a moment. Repair is a pattern.

The apology is for them. The pattern is for everyone who now has a question in their head: "Can I rely on you?"

What actually makes an apology effective (according to research)

Ohio State News summarises research by Roy Lewicki and colleagues on six elements of an effective apology. (source)

The useful takeaway for work: the two most important pieces were acknowledging responsibility and offering repair.

Notice what's missing from that list: a long explanation of how busy you were. Convenient.

The boring, effective structure

When you're under stress, keep the script simple:

1. Own it: what happened, in plain language.
2. Name impact: what it cost (time, risk, trust).
3. Repair: what you're doing to fix it now.
4. Prevention: what changes so it won't repeat.
5. Invite concerns: one question, then listen.

Useful line: "Here's what I'm doing so you don't have to worry about this happening again."

Word-for-word scripts (pick the one that matches the relationship)

To your manager

I missed [thing], and that caused [impact]. That's on me.

I've already [immediate fix]. To prevent a repeat, I'm changing [process/guardrail].

Is there anything you're worried about that I haven't covered?

To a peer you affected

I made your job harder this week by [specific]. I'm sorry.

I'm doing [fix] today. Next time I'll [prevention].

If it helps, I can also [support] to reduce the load this cycle.

To a stakeholder (keep it crisp)

Update: the delay was due to an error on my side. We've corrected it and the new delivery is [date/time].

We're adding [guardrail] so this specific failure mode doesn't repeat.

Two traps that make you look worse (even if you're a good person)

• Over-explaining: it sounds like you're negotiating blame. Keep the story short; make the plan long.
• Asking for forgiveness too early: it puts pressure on them to absolve you. Earn it with repair.

Competence mistakes vs integrity mistakes

Not all mistakes are equal in how they're received.

If this looks like a competence error (missed detail, missed dependency), people want to know you now have a guardrail.

If it looks like an integrity issue (you hid it, you spun it, you blamed someone), you need to rebuild credibility first: faster transparency, cleaner ownership, fewer excuses.

What to do after the apology (this is the repair part)

• Deliver one small win quickly. Reliability beats speeches.
• Over-communicate status, not feelings. "Here's where it is" beats "I feel terrible".
• Offer a check-in: Can we review how this went next week?
• Keep your promises tiny and specific. You're rebuilding trust, not writing a manifesto.