{"id":2648,"date":"2026-01-27T06:54:00","date_gmt":"2026-01-27T04:54:00","guid":{"rendered":"https:\/\/andresass.com\/nicht-kategorisiert\/vertrauen-reparieren-fuehrung\/"},"modified":"2026-05-15T15:47:35","modified_gmt":"2026-05-15T13:47:35","slug":"rebuilding-trust-leadership","status":"publish","type":"post","link":"https:\/\/andresass.com\/en\/insights\/rebuilding-trust-leadership\/","title":{"rendered":"Rebuilding trust: How to work together again after a breach"},"content":{"rendered":"\n

Why \u201clet\u2019s just move on\u201d does not work<\/h2>\n\n

It happened. A promise was broken. A decision was made over people\u2019s heads. Information was withheld. Someone was publicly humiliated. The collaboration that used to work is now poisoned. <\/p>\n\n

The first impulse: carry on. Stay professional. Let\u2019s just move on. That does not work. <\/p>\n\n

\n

Building trust takes years. Destroying it takes seconds. Repairing it is possible, but it takes more than goodwill and an apology. Damaged trust does not disappear by being ignored. It keeps working in the background: less openness, more hedging, shorter conversations, longer emails. <\/strong><\/p>\n<\/blockquote>\n\n

A division head I supported had announced a reorganization a year earlier in which several team leads were to lose their roles. He had promised to inform everyone affected personally beforehand. What happened: the news leaked through the grapevine before he could hold the conversations. Three of his best people heard from others that their position was being eliminated. A year later, the reorganization was complete, the structures worked, but the relationship with those three people was never the same again. \u201cI thought time would heal it,\u201d he told me. \u201cIt didn\u2019t.\u201d <\/p>\n\n

The anatomy of a breach of trust<\/h2>\n\n

Not every breach of trust is the same. To repair trust, you need to understand what exactly was damaged. Harvard Business School organizational researcher Sandra Sucher distinguishes three levels: competence trust (the belief that someone can deliver), integrity trust (the belief that someone is honest and keeps their word), and benevolence trust (the belief that someone will not stab you in the back). <\/p>\n\n

Type of trust<\/th>Damaged by<\/th>Core question<\/th><\/tr><\/thead>
Competence<\/td>Mistakes, poor quality, missed deadlines<\/td>Can she deliver?<\/td><\/tr>
Integrity<\/td>Lies, broken promises, hidden agendas<\/td>Can I believe him?<\/td><\/tr>
Benevolence<\/td>Betrayal, disloyalty, acting at others\u2019 expense<\/td>Will she stab me in the back?<\/td><\/tr><\/tbody><\/table><\/figure>\n\n

This distinction is crucial because the repair looks different. Competence trust can be rebuilt through proven performance. Integrity trust requires time and consistent behavior. Benevolence trust is the hardest to repair because it touches the deepest level. <\/p>\n\n

Why we suppress breaches of trust<\/h2>\n\n

Addressing breaches of trust is uncomfortable, and that is why we do not do it. We hope time will heal what we do not want to bring up. We fear being seen as resentful, because \u201cbeing professional\u201d supposedly means letting things slide. We simply do not know how to have the conversation<\/a>, because it requires vulnerability from both sides. And we fear escalation: what if bringing it up makes everything worse? <\/p>\n\n

All four reasons are understandable. None of them makes suppression a good strategy. What is not addressed keeps working. The costs show up in collaboration that is never as good again. In the energy that flows into hedging<\/a> instead of work. In relationships that slowly erode. <\/p>\n\n

How to repair trust<\/h2>\n\n

Repairing trust is a process, not an event. It starts with acknowledgement: acknowledging that something happened, without downplaying, justifying, or explaining it away. \u201cThis happened. This was not okay.\u201d This acknowledgement must come from the person who damaged the trust. Without this step, there is no foundation.<\/p>\n\n

Then comes understanding: what exactly happened, from both perspectives? What was the intention, and what was the impact? Understanding does not mean excusing. It means fully grasping the situation. From that comes responsibility: not \u201cI\u2019m sorry if you feel hurt,\u201d because that is not taking responsibility, but \u201cI made a mistake. That was my decision. I will bear the consequences.\u201d <\/p>\n\n

It is easy to tell a genuine apology from a worthless one. Everything after \u201cbut\u201d cancels the apology. \u201cI\u2019m sorry, I had no choice\u201d removes responsibility. \u201cI\u2019m sorry, can we move on now\u201d uses the apology as a shortcut. A genuine apology names the specific behavior, acknowledges the impact, takes responsibility, and comes without justification. <\/p>\n\n

The final step is a new agreement: how will we treat each other going forward? What must not happen again? What do we expect from each other? These agreements are the foundation for the relationship after the breach. Sometimes making amends is part of it as well; the question \u201cWhat can I do to make up for the damage?\u201d shows that the apology is more than words. <\/p>\n\n

\n

Repairing trust requires both: an honest conversation about the past and clear agreements for the future.<\/strong><\/p>\n<\/blockquote>\n\n

Repairing trust within the team<\/h2>\n\n

Breaches of trust between individuals are complex enough. In a team, they become more complex because dynamics and observers are added. <\/p>\n\n

A team lead told me about a situation in which she criticized a team member in a meeting in front of the entire team. \u201cI thought I was making it transparent because it affects everyone,\u201d she said. \u201cWhat I didn\u2019t see: everyone else wondered in that moment whether it could happen to them too. I hadn\u2019t only damaged one person\u2019s trust, but the entire team\u2019s sense of safety.\u201d The psychological safety<\/a> she had built over months was damaged in five minutes.<\/p>\n\n

Clarify every breach of trust first in a one-on-one conversation before you take it to the team. No one wants to be humiliated in public. If you, as a manager, have damaged trust, you do need to address it with the team as well\u2014not in detail, but in substance: \u201cI made a mistake. That was not okay. It will not happen again.\u201d If a team member has damaged another\u2019s trust, your role is not to resolve the conflict<\/a>, but to create the framework in which it can be resolved. In cases of collective breaches of trust\u2014for example after a failed reorganization or a perceived betrayal by leadership\u2014you need a space in which the team can talk together about what happened. <\/p>\n\n

When trust can no longer be repaired<\/h2>\n\n

Not every breach of trust can be healed. If the other person is not willing to have the conversation or take responsibility, repair is not possible, because it requires two sides. If the same behavior repeats, it is a pattern\u2014and accepting patterns is not generosity, but naivety. Some breaches of trust are so fundamental\u2014deliberate fraud, systematic lies, active harm\u2014that no basis remains. And sometimes the cost of repair exceeds the value of the relationship. <\/p>\n\n

Not every relationship is worth repairing. Recognizing that is not weakness. It is clarity. If you conclude that a separation<\/a> is the right path, do it respectfully and without burning bridges. <\/p>\n\n

Reality Check<\/h2>\n\n

Take five minutes and think of a relationship in your professional environment where trust has been damaged:<\/p>\n\n

First: What exactly is damaged\u2014competence, integrity, or benevolence\u2014and have I truly addressed it, or only suppressed it?<\/p>\n\n

Second: Am I willing to take responsibility for my part, or am I waiting for the other person to take the first step?<\/p>\n\n

Third: If I do nothing, what will collaboration look like in a year?<\/p>\n\n

If the answer to the third question is \u201cworse than today,\u201d then today is the right day for the conversation.<\/p>\n\n

The Uncomfortable Truth<\/h2>\n\n

Repairing trust is harder than building trust. It takes more courage, more honesty, more patience. It requires talking about things that are uncomfortable and taking responsibility, with no guarantee that the other side will forgive. <\/p>\n\n

Managers who are successful in the long term can do both: build trust and repair trust. They know mistakes happen, including their own. And they have the courage to talk about them. Without trust, leadership<\/a> does not work\u2014nor does delegation, nor collaboration. <\/p>\n\n

Think of the one relationship you are avoiding right now. The conversation you have been putting off for weeks. Have it this week. Not perfectly, not with a script, but honestly. <\/p>\n\n

Further Insights<\/h2>\n\n

The conversation you are putting off<\/a><\/strong> \u2013 repairing trust starts with the conversation you have been avoiding so far. How to have it. <\/p>\n\n

Responsibility without those responsible<\/a><\/strong> \u2013 trust emerges where responsibility is clear and upheld.<\/p>\n\n

All Insights can be found in the overview<\/a><\/strong>.<\/p>\n","protected":false},"excerpt":{"rendered":"

A promise broken, information withheld, the first impulse: let\u2019s just move on. That does not work. Damaged trust does not disappear by being ignored. How to rebuild it systematically before collaboration erodes. <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[230],"tags":[237,235,253],"class_list":["post-2648","post","type-post","status-publish","format-standard","hentry","category-insights","tag-communication","tag-leadership","tag-team"],"_links":{"self":[{"href":"https:\/\/andresass.com\/en\/wp-json\/wp\/v2\/posts\/2648","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/andresass.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/andresass.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/andresass.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/andresass.com\/en\/wp-json\/wp\/v2\/comments?post=2648"}],"version-history":[{"count":8,"href":"https:\/\/andresass.com\/en\/wp-json\/wp\/v2\/posts\/2648\/revisions"}],"predecessor-version":[{"id":2845,"href":"https:\/\/andresass.com\/en\/wp-json\/wp\/v2\/posts\/2648\/revisions\/2845"}],"wp:attachment":[{"href":"https:\/\/andresass.com\/en\/wp-json\/wp\/v2\/media?parent=2648"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/andresass.com\/en\/wp-json\/wp\/v2\/categories?post=2648"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/andresass.com\/en\/wp-json\/wp\/v2\/tags?post=2648"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}