How to Give and Receive Feedback Without Taking It Personally

Giving and receiving feedback without taking it personally starts with the interpretation you bring before a single word is spoken. Assume the other person is busy, direct, or focused on the problem rather than attacking you. Separate the work from the person, be specific rather than vague, and remember that the sting usually comes from imagined intent, not the comment itself.

The problem is often not what was said. It is the intention we invented behind it.

Feedback is one of the few tools that can genuinely make us better at what we do, and yet almost everyone dreads it, on both ends of the exchange. Giving criticism well is hard because we worry about damaging a relationship or triggering defensiveness. Receiving it well is hard because our first instinct is to protect our ego rather than absorb the lesson. Most advice on feedback focuses on technique: how to phrase a comment, when to deliver it, how to structure a review. Technique matters, but it sits on top of something more fundamental, which is the interpretation we bring to the exchange before a single word is spoken.

1. The interpretation problem

Adam Schwab’s essay on Hanlon’s Razor gets at this directly, even though it is not written about feedback at all. His argument is that most of the transgressions we perceive against us are constructed in our own minds rather than intended by the other party. When someone cuts us off in traffic, our instinct is to assume malice, when the far more likely explanation is carelessness, distraction, or simple bad driving that has nothing to do with us personally. Schwab pushes the idea one step further than the classic razor. Rather than stopping at stupidity as the more charitable alternative to malice, he suggests we go further still and search for the most generous interpretation available. That reframing does most of the emotional work before any conversation even happens.

Criticism and feedback live inside exactly this same trap. When a colleague sends a blunt comment on a piece of work, the instinctive read is often that they are being dismissive, competitive, or trying to make a point at our expense. In reality, they are usually just busy, imprecise with language, or focused on the problem rather than on how the delivery lands. None of this means intent never matters. Sometimes feedback really is shaped by status, politics, bias, or frustration, and pretending otherwise would be its own kind of naivety. A surprising amount of the unnecessary pain in feedback comes not from the words themselves, but from the intention we assign to them, and that portion is the one worth doing something about. The work of receiving feedback well starts before the feedback arrives, with a default assumption that the other person is trying to help rather than trying to wound.

2. Giving criticism starts with the same generosity

The instinct to assume the worst runs in both directions. When we are the ones giving feedback, we often over prepare for a fight that the other person was never going to start. We soften language so much that the actual point disappears, or we frame comments defensively because we expect resistance before any has been shown. Schwab’s line about conversation and confrontation is worth carrying over almost unchanged here: you can always escalate a conversation into a confrontation, but you can never walk a confrontation back into a conversation. It is a one way street, so the safer default is to start on the generous, conversational side and only escalate if the situation genuinely calls for it.

In practice, that means opening feedback with the assumption that the person did their best work given what they knew at the time, rather than assuming carelessness or indifference. It means separating the work from the person, so a criticism of a decision does not read as a criticism of character. And it means being specific rather than vague, since vague criticism is what invites the recipient to fill in the gaps with the worst possible interpretation. A precise, generous comment leaves less room for imagined malice than a sweeping, ambiguous one.

A simple structure helps turn that intention into words. Describe the observation, not the character judgment. State the impact, in concrete terms rather than adjectives. Then ask a question or make a request, rather than delivering a verdict.

• Observation: what actually happened, described plainly.
• Impact: what it cost, delayed, or put at risk.
• Question or request: what you would like to happen next.

Something like “the deployment failed twice this week, which delayed the release by four hours, so what do we need to change before the next one” does more work than “this keeps going wrong.” The first is a shared problem to solve. The second is a judgment to defend against.

This sits close to the well known Situation Behavior Impact model developed by the Center for Creative Leadership, which asks the person giving feedback to describe the situation, the observed behavior, and the impact it had. The addition worth keeping here is the final question or request, because feedback that only describes what happened tends to close a conversation, while feedback that ends with a genuine question tends to open one.

3. Receiving criticism is where the razor earns its keep

Receiving feedback is where Hanlon’s Razor does its heaviest lifting, because this is the moment our ego is most active. Schwab’s observation is that when we place ourselves at the center of the universe, we assume everyone is thinking about us, so any negative comment becomes a direct attack rather than an ordinary, unremarkable observation. The same pattern shows up in a performance review, a code review, or a note from an editor. A comment that was meant as a neutral observation about the work gets processed as a verdict on our worth.

The corrective is the same one Schwab applies to road rage. When we over personalize someone else’s words, we hand them control over how we feel. Untangling that starts with a simple question: what is the most generous, most probable explanation for why this person said what they said? Usually the answer has nothing to do with us specifically. The reviewer is tired, working from a template, under a deadline, or simply direct by temperament. None of that excuses feedback delivered badly, in the same way that a careless driver is still a bad driver. But it does remove the sting of imagined intent, which is usually the part that actually hurts.

A short sequence makes this easier to practice under pressure, in the moment when the instinct to defend is strongest.

• Pause. Let the first reaction pass before it becomes the answer.
• Separate fact from intent. What was actually said, as distinct from what you assumed it meant.
• Ask for specificity. “Can you give me an example” almost always calms the emotional temperature of a conversation.
• Extract the signal. Feedback delivered badly can still contain a point that is true.
• Decide. Feedback deserves consideration, not obedience, so the final call stays yours.

4. Feedback is information, not instruction

Assuming positive intent is not the same as accepting every piece of feedback as correct, and conflating the two produces its own quiet damage. Some feedback is right. Some is partially right. Some is simply wrong, shaped by a narrow view of the situation or by the reviewer’s own preferences rather than by the merits of the work. Treating every comment as an instruction to be obeyed teaches people to abandon their own judgment the moment someone else expresses doubt, which is neither humble nor useful.

The healthier frame is that feedback is information you are obligated to consider, not an order you are obligated to follow. You owe the other person genuine attention to what they have said, and a fair hearing of the reasoning behind it. You do not owe them automatic compliance. The mature response sits between reflexive rejection and reflexive acceptance, and it looks less like a decision and more like curiosity: turning the comment over, testing it against what you know, and only then deciding what changes and what stays.

5. A special case: technology choices and “tried and trusted”

Technology decisions are an especially sharp test of all this, because a system someone built or championed tends to carry years of accumulated identity along with it. When a colleague questions the choice of database, the age of a framework, or the wisdom of a system that has run reliably for a decade, the comment lands very differently depending on who hears it. To the person raising the question, it is usually just an observation about risk, cost, or a changed set of constraints. To the person who built or defended the system, it can feel like a verdict on years of judgment, which is exactly the kind of ego driven overreading Schwab describes with road rage. Nobody woke up intending to insult a decade of work. They are usually just responding to something that has changed since the decision was made, and that has nothing to do with the person who made it.

The phrase “tried and trusted” is worth sitting with for a moment, because it does honest work and dishonest work at the same time. Sometimes it is a genuine, well earned argument for stability, built on real operational history and real scar tissue from past failures. Other times it is an emotional attachment dressed up as a technical case, deployed to end a conversation rather than to inform it. The two are easy to confuse from the inside, because both produce the same confident sentence. A useful check is the same one that applies to receiving any criticism well: ask whether the objection to change would survive being said by someone with no history attached to the original decision. If the answer is yes, the caution is probably sound engineering judgment. If the answer is no, the caution is probably an ego defending its own past choices.

You are not the architecture you chose five years ago. That distinction matters more than it sounds. A good engineer, a good architect, or a good leader should be able to hold two thoughts at once without contradiction: given what I knew then, that was the right decision, and given what I know now, I would choose differently. Changing your mind in light of new information does not retroactively invalidate the judgment that made the original call, because the constraints, the scale, and the available alternatives were different at the time. What actually damages credibility is not the reversal. It is the refusal to reverse when the evidence is plainly there, because that refusal is no longer about the technology at all. It is about protecting a version of yourself that no longer needs protecting.

6. The cost of avoidance

There is a cost to getting this wrong that rarely shows up immediately, which is exactly what makes it dangerous. If someone who wants to give you feedback comes to believe that you will take it as a personal attack, the rational response on their side is not to keep trying. It is to stop. They stop raising the concern directly and start working around you instead, routing decisions through other people, quietly adjusting their own plans to avoid depending on yours, or simply staying silent in the meeting where the problem was visible to everyone but you.

That silence does not feel dramatic at the time, which is precisely why it is so corrosive. Alignment erodes first, because people are no longer correcting each other’s misconceptions in real time. Transparency follows, since information that used to flow directly now moves sideways instead, through side channels and private conversations you are not part of. Trust is the last thing to go, and once it does, things tend to wobble quickly rather than gradually, because by the time the avoidance becomes visible, it has usually been the operating pattern for a while. This applies just as much to a team or an organization as it does to a friendship or a family. How you receive criticism is not a private matter that only affects your own feelings. It is one of the quiet variables that determines whether the people around you keep telling you the truth.

7. Where charity has limits

None of this means every piece of feedback deserves the benefit of the doubt forever. Schwab’s own framing includes a caveat worth keeping: a generous interpretation does not excuse a genuine pattern of bad behavior. A driver who cuts people off once might be careless. A driver who does it constantly is simply a bad driver, and the same logic holds for colleagues. One blunt comment from someone is not evidence of malice. A consistent pattern of feedback that is needlessly harsh, personal, or delivered to embarrass rather than to help is a different problem, and pretending otherwise is not generosity, it is avoidance. The goal is not infinite charity toward every interaction. The goal is to start from a generous baseline rather than a defensive one, and to let repeated evidence, not a single data point, decide when that baseline should change.

8. Feedback as a practiced skill, not a personality trait

The reason this matters is that neither giving nor receiving criticism well is something people are simply born good at. Both are practiced skills that improve with deliberate attention, and both are undermined the moment either party assumes the worst about the other’s intent. A team that defaults to generous interpretations of each other’s feedback ends up with faster, more honest conversations, because nobody is spending energy managing imagined slights. A team that defaults to suspicion ends up with feedback that is either withheld entirely or delivered so cautiously that it loses its usefulness, which is the same avoidance described above, just moving in slow motion.

Underneath all of this sits a broader leadership point. A high feedback culture requires low identity attachment. If changing your mind feels like losing status, people defend decisions rather than improve them. If admitting a mistake feels career limiting, mistakes get hidden rather than fixed. If criticism of the work feels like criticism of a person’s worth, feedback stops being a technical conversation and becomes a political one. The strongest teams do not simply teach people to phrase feedback nicely. They make being corrected socially safe, so that the honest version of events is also the easy one to say out loud.

Politics offers the clearest negative example of what happens when nobody applies this principle, and Schwab notes as much himself: imagine political opponents starting from the most favorable reading of the other side’s argument rather than the least favorable one. It almost never happens, and the result is a public conversation that generates more heat than insight. Feedback within a team or a working relationship does not have to follow that pattern.

The objective is not to become less sensitive to criticism. It is to become less confused about what criticism means. Someone finding a flaw in your work has not found a flaw in you.