Community

translate Automatic translation · View original

How do you give feedback when the relationship with that person is already damaged?

Canal Agile Coaching

1 August 2026
How do you give feedback when the relationship with that person is already damaged?
Giving feedback is already hard when things are going well. But what happens when there is a history of friction, misunderstandings, or accumulated distrust between you and the other person? Conventional wisdom about feedback (be specific, separate the behavior from the person, use the SBI model) assumes a functional relationship as the starting point. When that starting point doesn't exist, the technique alone is not enough. This article explores what changes when the relationship is already deteriorated and what we can do when repairing the bond is a precondition for any message to be heard.

The problem that feedback models don't solve

Most feedback frameworks circulating in the agile community (SBI (Situation-Behavior-Impact), the "sandwich" method, radical feedback) share a silent assumption: that there is a minimum base of trust between the person giving the message and the person receiving it. When that base exists, the technique helps structure the conversation. When it doesn't, the technique becomes an empty choreography that the other person detects immediately.

Douglas Stone and Sheila Heen, of the Harvard Negotiation Project, state this precisely in Thanks for the Feedback (2014): the factor that most determines whether someone accepts or rejects feedback is not the quality of the message, but the relationship with whoever delivers it. They identify three "triggers" that make us reject feedback: truth triggers (we believe the content is wrong), identity triggers (the message threatens the image we have of ourselves), and, crucially, relationship triggers: we reject the content because of who is saying it or how we feel treated by that person.

When the relationship is damaged, the relationship trigger dominates. The other person doesn't process your message; they process the history. However well-crafted your sentence is, what they hear is "here comes this person criticizing me again."

This explains a frustrating and common experience: you apply the technique perfectly and the conversation still ends up worse. You didn't fail in the execution. You failed in the diagnosis. You tried to give feedback when the prior problem was the relationship.

Separating the message from its emotional receiver

There is a fundamental difference between the content of a feedback message and the other person's willingness to receive it. Marshall Rosenberg, creator of Nonviolent Communication (Nonviolent Communication, 2015), insisted that behind every defensive reaction there is an unmet need. When someone hears your feedback as an attack, they are not reacting only to your words: they are protecting something they perceive as threatened, such as their competence, their sense of belonging, or their dignity.

In a damaged relationship, those needs are already on permanent alert. Every previous interaction the person interpreted as belittling, exclusion, or injustice has left a residue. Your feedback, however neutral, lands on that minefield.

This doesn't mean you should give up delivering the message. It means the order matters: before the content can be heard, the person needs to feel that you are not operating from the same place that caused the harm.

Repair before giving feedback (when possible)

The uncomfortable question is whether repair belongs to the moment of feedback or is prior work. In general, trying to repair the relationship and giving corrective feedback in the same conversation overloads the exchange. The person doesn't know whether you are offering a hand or preparing them for a blow.

Edgar Schein, in Humble Inquiry (2013), proposes a path: start from genuine inquiry rather than from assertion. Instead of arriving with a closed diagnosis, open with real questions, not rhetorical ones, about how the other person sees the situation. This serves two functions: it gives you information you might not have had and, above all, it communicates that the relationship is not one-directional. You are not coming only to correct; you are coming to understand.

Humble inquiry is not a manipulation technique to "soften up" the other person before delivering criticism. If used that way, it shows and makes the damage worse. It works when it is authentic: when you are genuinely willing to discover that part of the problem might be yours, or that your reading of the situation is incomplete.

In very deteriorated relationships, sometimes the most useful feedback you can give first is to acknowledge your own contribution to the deterioration. "I think over the last few weeks I've been more reactive with you than is fair, and I want to talk about how we're working together." This is neither weakness nor surrender; it is defusing the relationship trigger before touching the content.

When you have no formal authority: the case of the Agile Coach

A good number of people reading this work without hierarchical authority. A Scrum Master or Agile Coach who must give feedback to someone with whom the relationship is damaged, and over whom they have no formal power, faces an additional difficulty: they cannot rely on their position to make the message "carry weight."

Here, relational credibility is the only capital available, and it is precisely the one that has been eroded. Lyssa Adkins, in Coaching Agile Teams (2010), reminds us that the coach works from the relationship, not from the role. When that relationship breaks, the coach loses their main tool of influence.

In these cases, there are three realistic paths, and it is worth being honest about their limits.

The first is to invest in rebuilding the bond before attempting any substantive feedback, accepting that this may take weeks and that during that time the problematic behavior will persist.

The second is to involve a third party with a better relationship, such as another team member, a manager, or another coach, recognizing that you are not, at this moment, the right channel for that message. This requires humility: admitting that your effectiveness in this particular case is low.

The third, when the damage is structural rather than personal, is to take the issue to the system instead of to the person: turn an individual feedback into a team conversation about working agreements, where the message does not arrive marked by the history between two people.

None of these is a clean solution. All of them require giving up the fantasy that a good feedback technique solves a relational problem.

Psychological safety: the condition that doesn't depend only on you

Amy Edmondson, in The Fearless Organization (2018), showed that people's willingness to give and receive honest feedback depends on the level of psychological safety in the environment: the shared belief that the team is a safe space for taking interpersonal risks without fear of humiliation or punishment.

This has an uncomfortable implication for our topic: when a relationship is damaged, part of the problem may not be interpersonal but environmental. If the team operates in a climate of low psychological safety, where mistakes are punished and dissenting opinions are penalized, no individual relationship will be healthy. The damage you perceive between you and that person may be a symptom of a system that doesn't allow honest conversations.

Before investing energy in repairing a specific bond, it is worth asking whether the problem is that relationship or the environment that makes it impossible. If it is the latter, the most relevant feedback is not aimed at the person, but at the conditions of the team.

The AI context: when technological mediation replaces the difficult conversation

We live in a moment when more and more work interactions go through tools. Generative artificial intelligence has amplified an earlier temptation: delegating difficult conversations to text. It is perfectly possible today to ask an assistant to "write a diplomatic feedback message" for someone we don't dare to talk to.

Here a warning is in order. Technology can help you organize ideas or find more careful words, and that has value. But when the relationship is already damaged, a polished message sent through a written channel tends to make things worse: it removes tone, the chance to nuance in real time, and, above all, the signal that you are willing to expose yourself. The other person perceives the distance. A delicate piece of feedback delivered in writing, in a tense relationship, communicates "I didn't even want to talk to you about this."

Repairing a bond requires presence, not just lexical precision. AI can help you prepare; it cannot hold the conversation for you. And the rhetorical elegance of a generated text may even backfire: it sounds too perfect, too little human, for a situation that calls for exactly the opposite.

What to do when the relationship cannot be repaired

Let's be honest: not every relationship can be fixed. Sometimes the damage is deep, mutual, and persistent. Sometimes the other person has no interest in rebuilding anything. Sometimes the organizational context (internal competition, conflicting incentives, histories that go back to before you arrived) puts repair beyond your reach.

In those cases, forcing "constructive" feedback conversations is naive. What remains is professional management of disagreement: clarity about expectations, recording of agreements, escalation to whoever corresponds when the behavior affects the team, and protection of your own integrity. Not all feedback seeks to improve a relationship; sometimes it only aims to leave a record and set boundaries.

Recognizing this limit is not defeatism. It is the difference between investing your energy where it can bear fruit and wearing yourself out on bonds that won't change no matter how much technique you apply.

Final reflection

Perhaps the biggest mistake we make with feedback is treating it as a message problem when it is often a relationship problem. The techniques exist and are useful, but they operate on a base we take for granted and that, when it is missing, no formula can replace.

The question we should ask ourselves before preparing a difficult feedback is not "how do I say this?" but "is this relationship in a position to carry this message?" If the answer is no, the prior work is not writing better: it is repairing, involving others, changing the context, or accepting the limits of what is possible.

And you? Have you ever tried to give an impeccably built piece of feedback that failed because the relationship was already broken? What did you do afterward?

Take part in the poll

This article includes an active poll in the Scrum Manager community.

poll View the poll in the community