Skills
Learning to be reviewed is a separate skill from doing the work
How you respond to criticism of your output is watched more closely than the output itself, and most of the damage happens in the first thirty seconds.
By Yash Agarwal3 min read
Two things are being assessed
When work you produced is picked apart in a review — a document marked up, a piece of code commented on, a plan questioned in a meeting — two separate evaluations are happening. One is of the work. The other is of you, based on how you handle the first, and the second is more consequential because it predicts what you will be like to work with on everything that follows.
Most people know this abstractly and still respond badly, because criticism of something you made lands as criticism of your competence, and the defensive reaction is faster than the reasoned one. That gap of a few seconds is where the damage occurs, and it is a mechanical problem with a mechanical fix.
Separating yourself from the artefact
The habit that makes this manageable is treating the work as an object that now exists independently of you. A document with problems is a document with problems. Someone finding them is doing what they were asked to do, and their finding them earlier is strictly better than a user or a client finding them later.
This is easier said than felt, and it gets easier with volume. People who have had a great deal of work reviewed develop a genuine indifference to it, which reads as confidence and is closer to calibration: they have learned that most criticism is about the artefact and very little of it is about them. Seeking out review deliberately, on lower-stakes work, is the fastest way to acquire that.
What to do in the moment
Ask questions before offering explanations. "What would you have done instead?" and "is this a must-fix or a preference?" are both useful and both signal engagement rather than resistance. The second one in particular is worth asking, because reviewers frequently mix binding corrections with personal taste and do not always distinguish them.
Explaining why you did something is legitimate, and the ordering is what matters. Explanation offered first is a defence. The same explanation offered after you have understood the objection is context, and it is often welcomed, because the reviewer may not have known about the constraint you were working under.
Do not agree with everything either. Accepting criticism you think is wrong, purely to end the conversation, is read as passivity and produces worse work. Disagreeing once, with a reason, and then accepting the decision if you are overruled is a much stronger position than either arguing indefinitely or capitulating immediately.
The signals people read
Reviewers notice a small number of things. Whether the same correction comes back a second time, which is the strongest negative signal available and is really a signal about whether you incorporate or merely comply. Whether the work arriving for review has got cleaner over months. Whether you ask about the reasoning behind a correction or just apply it.
That last one is worth dwelling on. Applying a fix without understanding it means you will make the same class of mistake in a different form next week. Asking what the principle is converts a single correction into a rule, which is the entire mechanism by which review makes people better rather than merely making the document better.
When the review is the problem
Not all review is good. Some is delivered carelessly, some is a display of seniority, and some is genuinely hostile in ways that have nothing to do with the work. Reviewers vary enormously in skill and almost none of them have been trained in it, which is worth remembering before concluding that harsh feedback is accurate feedback.
The practical response is to separate content from delivery. Extract whatever is technically correct, discard the tone, and if the tone is persistent and personal, treat that as a management issue rather than a work issue. It is also fair to ask for feedback in a form you can use: "could you tell me which of these are blocking?" is a reasonable request and often improves the reviewer’s behaviour without anyone having to name the problem.
And if you are somewhere that gives no review at all, understand that this is a cost even though it feels comfortable. Working for years without anyone examining your output closely produces confident habits that nobody has ever checked, and that gap tends to become visible at exactly the wrong moment.
Common questions
How do I stop taking feedback personally?
Mostly through volume and through deliberately lowering the stakes, by sharing drafts early and often rather than presenting finished work. Early drafts are expected to have problems, so criticism of them carries less weight, and the habit gradually decouples your sense of competence from any single artefact.
Should I push back on feedback from someone senior?
Once, with a reason, and then accept the decision unless something is actually going to break. Senior people generally respect a considered disagreement and lose patience with repetition, and the ability to say "I still think X, but I will do it your way" is more useful than either silence or persistence.
What if I keep getting the same feedback?
Treat it as the most important thing on your list, because a repeated point is what will be cited in any formal conversation later. Ask explicitly what would count as fixed and how you would both know, since vague corrections are hard to close out and can follow you for years.
Contributing editor, After the First Job
Yash writes the explanatory pieces on first months, managing up, money at work and would rather show the working than assert the conclusion.
