The CEO Who Read the Same Feedback Twice and Did Nothing Both Times

The 360 review landed in his inbox on a Thursday, same as it had the year before. He scrolled to the qualitative comments first, the way he always did, and found a sentence he recognized almost word for word. "He asks for input and then makes the decision he had already planned to make regardless of what anyone says."

He had read nearly the same sentence the previous year. He remembered reading it, remembered feeling defensive, remembered deciding it reflected one or two specific disagreements rather than a pattern, and remembered doing nothing further about it.

This year, five different reviewers had said some version of the same thing, up from two the year before. The pattern had not just persisted. It had spread.

Why the first reading changed nothing

The first time, he had read the feedback as a claim about a few specific incidents he could individually explain. He remembered the meetings the comments were likely referring to and had a private justification ready for each one. The feedback had felt, to him, refutable, and something that feels refutable rarely gets acted on, because acting on it would concede a point he had not actually accepted.

What he had not done, either time, was ask a direct report to describe a specific recent instance in detail and simply listen to the answer without offering a justification back. Feedback delivered anonymously and in aggregate is easy to argue with in your own head. Feedback delivered by one person, in the room, describing one specific meeting, is much harder to wave away, because there is a real person's real memory sitting across from you rather than an abstract summary.

How much is one unresolved conflict really costing your company?

What made the second reading different

What actually broke the pattern was not the second 360 report itself. It was a conversation his COO initiated a week after it landed, where she named a specific recent meeting and told him plainly what she had watched happen in it. "Two weeks ago you asked the room for input on the vendor decision. You had already signed the contract. Three people spent forty minutes giving you input on a decision that was already made."

He could not explain that one away. It was too specific, too recent, and attached to someone he trusted enough to believe was not exaggerating. Hearing his COO name it directly did something the aggregated survey comment never could. It moved the feedback from an abstract pattern he could rationalize into a single concrete moment he had to sit with.

This is the mechanism behind why direct, named feedback tends to land where anonymous aggregate feedback does not. The nervous system registers a specific person's specific memory in a way it never registers a statistic. The move sits in the same family as affect labeling, applied to the leader instead of a peer. A specific instance, described by a specific person, activates a different kind of attention than a statistic does. It cannot be filed away as noise, because it is not noise. It is a memory someone else is holding up next to your own.

Doug Noll's new book Empathy Leadership: The Powerful Skill That Drives Winning Results lays out why one direct, specific account changes a leader faster than any aggregated survey ever will. See it here.

What he did with the vendor decision itself

He reopened the vendor conversation the same week, not to reverse the decision but to tell the room honestly that he had already made it before asking for input, and to apologize for wasting their time on a discussion he had treated as theater. It was an uncomfortable meeting. It was also the first time in two years anyone on that team had heard him admit the pattern out loud instead of defending it.

His next 360, run eleven months later, dropped the comment to a single reviewer, down from five. He still does not enjoy hearing it. He no longer has a justification ready before the sentence finishes.

‍