The first time you have to tell someone who reports to you that something in their work isn’t landing, the instinct is to soften it until it barely registers, or to save it for the annual review where it arrives as a surprise. Neither one is actually kind. Feedback from a manager carries a weight that feedback from a peer doesn’t, and avoiding that weight doesn’t make the gap in someone’s work go away — it just delays when they find out about it, usually at a worse moment.

Why withholding feedback isn’t neutral

A manager who avoids giving feedback until it’s unavoidable isn’t protecting the relationship — they’re making a unilateral decision that the other person doesn’t get to correct course until the stakes are higher. Someone who finds out in a performance review that something has been a problem for months can reasonably ask why nobody said anything sooner, and it’s a fair question. The discomfort of a small, early, specific conversation is real, but it’s smaller than the discomfort of a pattern that’s had months to compound, and smaller still than the trust cost of a review that contains no surprises because there weren’t any good ones either.

Separate the observation from the story you’re telling about it

The useful version of feedback describes what happened and what it affected, not a conclusion about the person’s character or effort. Naming the specific section a submission didn’t address is specific, checkable, and gives the person something to act on; telling them they aren’t reading carefully enough is a judgment about them, not a description of what’s in front of you, and it invites defense instead of correction. It’s the same gap that separates a useful comment from an unhelpful one in reviewing a colleague’s draft: the comment points at the document, not at the author.

Make it a habit, not an event

Feedback that only happens at scheduled checkpoints puts all the weight on a single conversation and makes every instance of it feel significant, which pushes both sides toward avoidance. A short, specific comment close to when something happened — in either direction — costs less for the manager to deliver and less for the report to hear than the same observation held for a formal moment. That habit is also what makes a performance review genuinely uneventful for the people reporting to you: nothing in it should be new, because the smaller version of it already happened in real time.

Where this goes wrong

Saving everything for the performance review

By the time a pattern reaches a formal review, it’s had months to compound and the person has had no chance to correct it earlier.

Describing the person instead of the work

Judgments about character or effort invite defensiveness; specific, checkable observations about what happened don’t.

Giving positive feedback too generically to be useful

Praise that doesn’t name the specific decision that worked doesn’t tell anyone what to repeat.

The job isn’t to make feedback painless — it’s to make it small, specific, and frequent enough that nothing in a formal review is a surprise. That’s a harder habit to build than avoiding the conversation, and it’s the one that actually serves the person doing the work.

Sources & further reading

  1. Regulatory Academy — How to Review a Colleague’s Regulatory Draft regulatoryacademy.com
  2. Regulatory Academy — Your First Regulatory Affairs Performance Review regulatoryacademy.com
  3. Regulatory Academy — Moving From Individual Contributor to Manager regulatoryacademy.com

This essay is provided for general educational purposes and reflects the regulatory landscape as of its publication date. It is not legal, regulatory, or career advice.