Taking Feedback Without Defending Yourself

Taking Feedback Without Defending Yourself

Brand Vantage Academy | Talent Development & Workforce Solutions

A reviewer leaves a single line on a junior developer’s pull request: “This works, but I wouldn’t have done it this way.”

There is no explanation attached, no suggestion, and no obvious next step. The junior spends the next twenty minutes writing a reply defending the approach, deletes it, writes a shorter one, and eventually sends three paragraphs explaining why the design was reasonable.

The reviewer, who had meant something quite specific and had simply been in a hurry, reads the paragraphs as an argument. He approves the change anyway and, over the following months, gradually stops leaving comments on that person’s work.

Nobody was unprofessional. A junior lost access to the most valuable thing available to someone in their first two years, which is a senior person willing to spend attention on their output.

Graduates are unprepared for this because the feedback they have received for fifteen years arrived in one shape: a mark, at the end, from an authority whose judgement was final and whose reasoning was not up for discussion. Workplace feedback is the opposite of all four of those properties. It is continuous, mid-process, delivered by peers as often as seniors, and frequently negotiable.

The Delivery and the Signal Are Two Different Things

Most workplace feedback is badly delivered. It is given between two other tasks, by someone who is not trained to give it, in whatever words occurred to them at that moment.

“This isn’t what I asked for.” “Did you even test this?” “Can you redo the second half?”

The instinct is to respond to the tone. The skill is to extract the content and discard the packaging, because the packaging usually reflects the sender’s day rather than an assessment of you.

Two questions separate them. What is the specific thing this person wants to be different? And is that thing reasonable, independent of how it was said?

You will find that harshly delivered feedback is often correct, and that gently delivered feedback is sometimes wrong. Delivery quality carries almost no information about signal quality, which is precisely why reacting to delivery is such an expensive habit.

The people who improve fastest are not the ones who receive the best feedback. They are the ones who lose the least of it to their own reaction.

Vague Feedback Is Incomplete, Not Empty

“Make it more polished.” “This needs more depth.” “It’s not quite there.”

Juniors treat these as unhelpful and move on frustrated. They are unhelpful, but they are not empty — the specificity exists in the other person’s head and has simply not been transferred.

Four questions reliably retrieve it, and none of them read as pushback.

• “Can you point me at the part that isn’t working, rather than the whole thing?”
• “Is there an example of this done well that I could look at?”
• “If I only change one thing before tomorrow, which should it be?”
• “What would you have expected to see here?”

The last of these is the most productive question in the workplace and the least used. It converts an evaluation into a description, and descriptions can be acted on.

Ask these in the moment. Feedback retrieved a week later has usually lost the detail that made it useful.

The First Three Seconds Decide the Rest

Defensiveness rarely appears as an argument. It appears as a reflex, and it appears immediately.

“Yes, but the requirement changed.” “I did test it, the environment was down.” “That’s how the previous version worked.”

Every one of these may be factually true. All of them close the conversation, because each one tells the speaker that the next thirty seconds will be spent on adjudication rather than improvement.

The alternative is not agreement. It is deferral. “Let me look at that properly and come back to you” costs nothing, commits to nothing, and preserves both the relationship and your right to disagree later, once you have checked.

Context matters and is worth supplying — but afterwards, as information, and only if it changes what should happen next. Explaining that the requirement changed is useful if the fix depends on it. It is defensive if it exists only to distribute blame.

When You Genuinely Disagree

Some feedback is wrong. Reviewers misread code, managers misremember what they asked for, stakeholders judge a draft against a brief they never communicated.

Disagreeing is allowed and, done properly, improves how you are seen. The form that works has three parts: confirm you have understood, state your reasoning rather than your conclusion, and name what would change your mind.

Compare the two versions.

Weak: “I don’t agree, the current approach is fine.”

Stronger: “So the concern is that this will not hold if the file size grows. I chose it because the input is capped upstream at ten megabytes — but if that cap is likely to be removed, you’re right and I should change it. Is it?”

The second version is not softer. It is more precise, and it makes the disagreement about a testable fact rather than about whose judgement is better.

If you make that case and the decision stands, implement it properly. Reopening a settled point is remembered far longer than being wrong once.

Why Some People Stop Receiving Feedback

Feedback is discretionary. Nobody is required to spend twenty minutes explaining what a junior could do better, and the amount you receive is a direct function of how it went last time.

This creates a quiet divergence within a joining cohort. Those who visibly act on comments accumulate mentors. Those who argue, go silent, or absorb the comment and change nothing find that after a few months people simply start fixing things themselves rather than telling them.

The second group often interprets the silence as approval. It is the opposite, and it is the most dangerous position an early-career professional can be in — improving slowly while believing there is nothing to improve.

The remedy is to make your action visible. When you change something because of a comment, say so in a single line: “Restructured this the way you suggested last week.” It takes four seconds and it tells the other person their attention was not wasted.

Turning a Repeated Comment Into a Pattern

One comment is an instance. The same comment from two different people is a pattern, and patterns are what appraisals are made of.

Keep a plain running list of feedback received — date, who, what. Not for sentiment, for detection. After three months, read it in one sitting.

You will usually find two or three themes that never announced themselves individually: work delivered without checking edge cases, updates that arrive later than people need them, drafts that answer a slightly different question from the one asked.

Those themes are the actual development plan. They are more accurate than any self-assessment, because they are drawn from observation rather than intention.

The hardest part of feedback is not hearing it. It is staying in the position where people are still willing to give it to you.

Key Takeaways

• Separate what is being asked for from how it was said, and respond only to the first.
• Use “What would you have expected to see here?” to convert vague evaluation into an actionable description.
• Replace the immediate justification with “Let me look at that and come back to you” — deferral preserves both the relationship and your right to disagree.
• When you disagree, state your reasoning and name the fact that would change your mind, then commit to the outcome.
• Keep a dated log of feedback received and review it quarterly to find the two or three patterns nobody stated directly.

Placement Connection

Interviewers probe this deliberately, usually with a question about a time your work was criticized. What they are listening for is whether you can describe the criticism accurately, which most candidates cannot — defensive candidates retell the story as a misunderstanding, and the retelling reveals the habit. Preparing an honest instance where you received a correction, asked a clarifying question and changed something specific gives an interviewer evidence of coachability, which is weighted heavily for freshers precisely because technical depth is expected to be low at entry.

Brand Vantage Academy

Coachability is trainable, and it is best trained where the stakes are lower than a live appraisal. Brand Vantage Academy runs practical, industry-aligned training that puts learners through repeated review and correction cycles, alongside placement assistance — learn more at brandvantageacademy.com.

Suggested Internal Links

Anchor Text	Destination	Relevance
how collaboration is judged once you are employed	Blog 95 — How Collaboration Is Actually Judged Once You Are Employed	Feedback response is one of the behaviors managers observe and record
what confirmation after probation actually requires	Blog 52 — Why Probation Exists, and What “Confirmed” Actually Requires	The first formal point at which accumulated feedback is applied to you
why continuous learning is now structural	Blog 14 — The Skills Half-Life Problem: Why Learning Never Stops Now	Feedback is the mechanism through which on-the-job learning actually happens
communication habits that decide how you are read	Blog 12 — Communication Skills: Why Technically Strong Candidates Get Rejected	The same reflexes that create defensiveness surface in interviews
Professional Development Programs	Academy page — Career Development Programs	For structured early-career development beyond technical training

---