The Feedback They Almost Didn't Give You

Why the good news rarely comes first, and almost never comes unprompted

There is a habit I picked up somewhere in the middle of my career, small enough that I almost don’t think of it as a habit. At the end of any feedback conversation, once my supervisor has said what they came to say, I ask if there’s anything else. The answer is almost never no.

Most feedback conversations are built around correction, because correction is what feels urgent and actionable to prepare in advance. A manager sitting down to plan what to tell you runs through the list of things that need to change, sequences them, maybe softens the language a little, and walks in with that list ready. Whatever positive observations exist tend to travel separately, if they travel at all: mentioned in passing, tacked on at the start as a warm-up, or quietly dropped when the meeting runs long and the corrective items feel like the part that actually has to get said. You leave with a snapshot that’s technically accurate and still somehow lopsided, because the version of you that got written down is the version that had problems attached to it.

There’s a second layer under that one, and it’s the part I find more interesting: good performance is often invisible by design. Nothing went wrong, so nothing registered as worth mentioning. A deviation from expectation is memorable precisely because it deviates. Meeting the expectation, even meeting it well, just looks like the absence of a problem, and the absence of a problem doesn’t generate a note in anyone’s head unless someone goes looking for it.

Asking is the going-looking. When I ask if there’s anything else, I’m not fishing for compliments (though I won’t pretend it doesn’t feel nice when one shows up). I’m asking because I’ve learned, across enough of these conversations to trust the pattern, that there’s something positive sitting in there that didn’t make the first round, not because it wasn’t true, but because nobody had built it into the plan.

I’ve written before that advice is autobiographical: a story about someone else’s context, offered to you as though it were built for yours. Feedback has a cousin version of that problem. It isn’t a complete account of your performance. It’s an account of whatever was salient enough in your supervisor’s head that week to write down, and salience is not the same thing as significance. The good work you did competently and without drama is real. It just doesn’t announce itself the way a missed deadline does.

The part I actually want to talk about, though, is the ambush. Unprompted feedback, even well-intentioned feedback, has a way of landing on you rather than with you. You sit there absorbing whatever arrives, with no say in its pacing or its scope, bracing for whatever comes next because you don’t yet know how much more there is (a bracing that costs more than people realize if uncertainty is already expensive for your particular nervous system). The moment I ask if there’s anything else, the dynamic changes, even though nothing about the substance has changed. The request came from me. I opened the door. Whatever walks through it now is something I invited rather than something that happened to me, and that single shift in authorship is most of the difference between a review and an ambush.

It costs about thirty seconds. It’s one sentence, asked at the end of a conversation that’s already happening anyway. And more often than not, it turns up something true and kind that was never going to make it into the room on its own.