Corrective feedback has an obvious starting point: something went wrong, and the conversation is about fixing it. Feedback for someone who's already excellent doesn't have that starting point, which is exactly why it gets skipped so often. When there's no problem to point to, the path of least resistance is just more praise - and praise alone, however deserved, doesn't help someone grow.
Why this feedback gets avoided
A few reasons, usually operating together: there's a real fear of demotivating someone who's already delivering, a sense that critiquing strong work risks seeming ungrateful or nitpicky, and - honestly - it's simply harder to construct. Corrective feedback writes itself once the problem is named. Developmental feedback for someone already strong requires actually noticing something subtle enough that the person hasn't spotted it themselves.
The cost of skipping it is real, even if it's invisible day to day: high performers who only ever hear "great job" eventually plateau, or leave for somewhere that offers them a clearer growth path, or - worse - develop a blind spot that eventually does become a real problem, at a point where it's much harder to name gently.
What actually useful feedback looks like here
Look for an overused strength, not a weakness. The most common real growth edge for a strong performer isn't a skill gap - it's a strength applied past the point where it's still helping. Someone whose thoroughness makes their individual work excellent may be the same person whose thoroughness is quietly slowing down a team that needs faster iteration. Naming that specifically - "this exact strength, applied here, is now working against you" - lands very differently than generic critique.
Connect it to something they're already trying to get. Most high performers have a real ambition - more scope, more influence, a promotion, a harder problem to work on. Framing feedback as "here's what's between you and that" turns it from an evaluation into genuinely useful information they have their own reason to act on.
Be specific about the moment, not the person. "In the client meeting, you cut off two people mid-sentence when they were raising concerns" is usable. "You can come across as not listening" is a trait judgment with nothing to actually act on.
Ask what they already suspect. High performers are often more self-aware about their own edges than managers assume - asking "what do you think is actually between you and [the thing they want]?" frequently surfaces the exact issue a manager was hesitant to raise, and hearing it from them first makes the rest of the conversation collaborative rather than corrective.
Don't manufacture a problem that isn't real. If someone's performance genuinely doesn't have a meaningful growth edge worth raising right now, saying so honestly - and finding a different, real topic (career direction, what's next, what they want more of) - beats inventing a critique just to have something to say.
The version worth avoiding
The failure mode isn't giving too little feedback to strong performers - though that's common - it's giving feedback that's technically present but practically empty: vague enough that nothing changes, or so hedged with praise that the actual point gets lost. A high performer who leaves a feedback conversation unsure what, if anything, they were actually told to work on has effectively had no feedback conversation at all.
This kind of feedback tends to get squeezed out by status updates in a regular one-on-one - MBA Lab's Compassionate Accountability Planner includes a prompt built specifically to stop the overdue development conversation from quietly getting skipped again.