Why "Resistant to Feedback" Is Often a Misread

There was a young man, about 25, who sat across from me a few years ago. He had been let go from an architectural firm where he had worked for three years. Efficient on the technical side, by all accounts. A strong hire on paper. But somewhere in year two, something started to break down, and by the time anyone named it, his manager had already made the decision.

When I asked him what happened, he didn't talk about the termination right away. He talked about a workflow.

There was a specific process the team used, one he had been trained on from day one. He saw a better way. Not a radical overhaul, just a cleaner approach that would have saved time. He raised it once. He raised it again. He asked questions in team meetings, tested the edges in a few one-on-one conversations. And every time, the response was either a redirect or silence. Nobody said yes. Nobody said no. Nobody acknowledged that he had said anything at all. So he kept working the way he had been taught, grew quietly frustrated, and eventually stopped bringing ideas forward altogether. His manager interpreted the silence as disengagement. Put it in a file. Called it resistant to feedback. And eventually handed him his walking papers.

Here is what struck me about that conversation. He was not resistant to feedback. He had never been given any.

That is not a small distinction.

We are living through a moment where the entire architecture of how feedback works has been rebuilt, and most organizations are still operating on the old blueprints. Not out of bad intent, but out of habit. The annual performance review was designed for a different era, one where the relationship between a worker and an institution was built on a kind of deferred trust. You showed up, you did the work, and once a year someone told you how you were doing. That model made sense when the nature of the work itself was compliance-oriented, when people were hired to follow systems rather than improve them, and when loyalty was measured in tenure rather than contribution.

But the world that shaped this 25-year-old is not that world. He grew up inside systems that gave him feedback in real time. Gaming platforms tracked his progress and adjusted difficulty as he learned. Social platforms showed him immediately whether his thinking resonated with others. Academic tools told him not just whether an answer was right but where his reasoning broke down. The feedback loop was constant, specific, and calibrated to his growth. He never had to wait a year to find out how he was doing. He was never asked to operate blind.

So when he stepped into a workplace that offered nothing until it had already decided he was a problem, it did not feel like professional culture to him. It felt like a system that had decided not to see him.

This is the part that gets labeled as sensitivity, and I want to sit with that for a moment because I think we are reaching for the wrong word. When a younger leader or a younger professional pushes back at feedback delivered with a sharp tone or a controlling edge, we tend to name that as a character issue. Too sensitive. Needs too much reassurance. Can't take criticism. But what we are often actually watching is a safety response. The nervous system doing exactly what it was designed to do.

Feedback is never neutral. It never has been. It carries the memory of every time a person was evaluated and found lacking, every time a question was dismissed, every time a tone told them the conversation was already over before it started. For people who have spent their early lives in environments where feedback was interactive and growth-oriented, landing in a space where it arrives as judgment rather than dialogue doesn't just feel discouraging. It feels threatening. And when something feels threatening, the brain does not optimize for openness and reflection. It defends.

When we label that defense as resistance, we are looking at the symptom and calling it the disease.

The sensitivity to control and tone that shows up in younger professionals is not a generation-specific flaw. It is a signal. It is telling you something about whether the conditions for real feedback have actually been created. An authoritarian delivery style, regardless of how accurate the content, will land in the nervous system as a threat before it ever reaches the rational mind. The message gets lost. The relationship sustains damage.

And the person across from you walks away not more coachable, but less.

The man I spoke with was not broken. He was a person who had tried to contribute, had never been met in that attempt, and had eventually learned to go quiet. His manager read the quiet as proof of the problem. But the quiet was the result of a system that never built the conditions for honest conversation.

Resistance, more often than not, is not an attitude. It is a signal. It tells you that somewhere along the way, the psychological safety required for real feedback to land never got built. 

It tells you that the person across from you carries, the way all of us do, a memory of what feedback has historically cost. And it tells you that before you can expect someone to receive hard truths with openness, they need to have experienced the smaller moments that build the foundation for that: the question acknowledged, the idea taken seriously, the concern met with curiosity instead of correction.

The young man I spoke with would have stayed. He wanted to grow. He wanted to contribute. He wanted to be seen making something better. None of that required a radical shift in organizational culture. It required someone to say, "That's an interesting question.

Let me come back to you on it." It required a feedback loop that did not wait until the damage was already done.

He did not fail his organization. His organization failed the conversation.