Guides

How to Take Criticism Without Getting Defensive

Oct 20, 2026 · 6 min read · from That Wasn't About Me

By Blake Tenney

The feedback is reasonable. You know it's reasonable. And still your chest tightens, your jaw sets, and some part of you starts building a case for why they're wrong before they've finished the sentence.

Defensiveness isn't arrogance — it's protection. Somewhere along the way, criticism got wired to danger: to being exposed, diminished, or cast out. So your nervous system treats a code review like a threat review.

Here's how to unwire it. Not by pretending feedback doesn't sting, but by giving yourself a better procedure for the moment it lands.

What defensiveness is actually doing

Defensiveness has a job: it keeps the conversation away from the part that hurts. Explaining, justifying, counter-attacking, going quiet — all of these are exits from the same room.

The cost is that you never actually hear the feedback. You hear the threat, respond to the threat, and walk away with neither the useful information nor the relationship intact.

The shift is small but total: treat criticism as data first, verdict never.

The four-step receiving method

Use this verbatim the next time feedback lands and your shoulders climb toward your ears.

  • Pause and breathe. One slow breath before you speak. This isn't calming theater — it gives your prefrontal cortex the two seconds it needs to come back online.
  • Repeat it back. “So you're saying the report buried the main finding until page four — is that right?” Repeating forces you to process the words instead of the threat, and it shows the other person they were heard.
  • Ask one question. “What would good look like here?” or “Where did you first notice it?” Questions turn a verdict into a collaboration. They also buy you time.
  • Decide later. “Thanks — let me sit with that.” You don't have to agree, fix, or respond in the moment. Most defensive spirals come from the pressure to resolve it now.

Sort the feedback after, not during

Once the sting fades — an hour later, a day later — sort what you heard into three piles: useful and true, useful but badly delivered, and not about you at all.

Badly delivered truth is still truth. “This is sloppy” is a rude way to say “page four buries the finding” — and the second version is actionable. Strip the tone, keep the data.

The third pile matters too. Some criticism is the other person's weather: their stress, their preferences, their bad day. Not everything aimed at you is about you.

What to do when you still spiral

Sometimes the method works in the room and the replay starts at midnight anyway. That's the old wiring running its highlight reel.

When it happens, interrogate the replay with one question: what am I afraid this criticism proves about me? Usually there's a sentence underneath — “I'm not competent,” “I'm too much,” “They're done with me.” Say it plainly. Vague dread is invincible; a specific sentence can be examined.

Then check the sentence against your actual record, not your feared one. One critical comment against a year of solid work is a data point, not a verdict.

Nobody enjoys criticism. The people who handle it well aren't tougher than you — they just have a procedure that runs faster than their panic. Borrow this one until it's yours.

That Wasn't About Me dedicates full chapters to feedback without the wound: why sensitive people hear evaluation as rejection, and how to stay open without staying raw.

Go deeper with That Wasn't About Me.

Stop taking everything personally.

See the book

Free

Small tools for inner work, in your inbox.

New guides, free printable worksheets and news of new books. No spam, unsubscribe whenever you like.

Your address is kept by ThriveOS, Antara Collective's sister company, and used only for these emails. Privacy policy.

More guides