I once spent six months rewriting a perfectly good product strategy because a senior leader told me, in a fifteen-minute hallway conversation, that it lacked ambition. The strategy was working. Customers were buying. The team was shipping. By month four, the rewrite had killed momentum, frustrated three engineers into quitting, and produced a document that no one outside the leadership team ever read. The leader who gave the feedback never followed up. He had moved on to other concerns by month two.
That experience changed how I receive feedback. Not all feedback is useful, not all critics are equally credible, and the cost of acting on bad feedback is often invisible at the moment of the conversation. Mature professionals filter inputs aggressively. The skill is not about ego protection or stubbornness. It's about recognizing which signals deserve action and which deserve a polite nod.
The Three Common Failure Modes
Most bad feedback fits one of three patterns. The first is feedback from someone who has never done the job you're doing. A board member who has never built software telling you the product needs to be more elegant. A peer in marketing telling you how engineering should prioritize. A retired executive telling you how to manage a team in a market they last worked in fifteen years ago. Sometimes these inputs are useful as outside perspective. Often they're projections of the speaker's own experience onto a context where it doesn't apply.
The second pattern is feedback that is technically correct but practically irrelevant. Yes, the deck could be tighter. Yes, the email could have been more concise. Yes, the onboarding flow has rough edges. None of these are wrong. None of them are the leverage point. Acting on every accurate-but-low-priority piece of feedback fragments attention and produces a portfolio of small improvements while the actual problem goes unaddressed.
The Third Pattern Is the Hardest
The third pattern is feedback that reflects the speaker's own anxiety more than your actual situation. A boss whose budget is being cut tells you to be more aggressive. A peer who is uncertain about their own role tells you that you're not visible enough internally. A friend who is unhappy in their career tells you that your career path has limits. The feedback may even contain useful kernels, but the framing is shaped by the speaker's pressures, not yours.
This pattern is hardest because the speaker is often well-intentioned and the relationship matters. The instinct is to take their input seriously. Sometimes that's correct. Often it isn't. The test is whether the same person, in a different emotional state, would give the same feedback. If they wouldn't, the feedback is about them, not you, and your job is to listen, thank them, and continue with your own assessment.
How to Tell Good Feedback from Noise
Good feedback usually comes from people with relevant experience, given on a specific timeline, with a concrete proposal attached. "Your Q3 plan undersells the platform investment, and here's why" is good feedback. "I think you should be more strategic" is noise. The first is actionable, falsifiable, and proposes a path forward. The second is a Rorschach test that means whatever the speaker wants it to mean.
Good feedback also tends to repeat across sources. If three different people, working in different parts of the organization, all tell you the same thing within a quarter, the signal is strong even if any one source is questionable. If one person tells you something five times and no one else has mentioned it, that's a single voice rather than a pattern. Treat single voices as input. Treat repeated patterns as data.
The Cost of Listening Too Much
Senior professionals who built their careers on accepting feedback often hit a ceiling when they fail to develop a counter-skill: the ability to dismiss feedback that doesn't apply. The receptive mode that worked at the entry level becomes a liability at the leadership level, where the volume of input grows faster than the ability to act on it.
Every piece of feedback you accept costs something. It costs attention, which is finite. It costs trust with the team, who watch you change direction in response to each new input. It costs momentum, because every redirect resets the clock. The internal scoreboard most professionals carry, where accepting feedback signals humility, breaks down at scale. At a certain career stage, the right move is often to acknowledge feedback and not act on it.
What to Do With Feedback You're Ignoring
Pretending you didn't hear feedback you've decided to ignore is the wrong move. The speaker remembers, follows up, and notices the silence. The right move is explicit acknowledgment without commitment. "I heard you, I've thought about it, here's why I'm taking a different path" is the polite, professional version of saying no. Most reasonable people accept this. The ones who don't are usually the same people whose feedback you correctly identified as noise.
Document the feedback you're ignoring and your reasoning. Six months later, you'll either have evidence that your judgment was right, evidence that you were wrong and should rethink, or evidence that the situation has changed enough that the original feedback now applies. The documentation costs nothing and protects against the natural human tendency to forget that you ignored something on purpose.
When Bad Feedback Comes from Your Boss
This is the hardest case. Direct refusal is rarely viable in most professional contexts, and bosses often have information you don't. The move is usually to accept the framing of the feedback while quietly preserving your judgment about the underlying work. Reframe the conversation around shared goals, propose alternatives that address the boss's stated concern through different means, and execute on what you actually believe is right while reporting progress in the language the boss is using.
This sounds cynical and isn't. The honest version is that bosses are often pattern-matching to past experiences, and their suggested action may not be the right one for your situation, but their underlying concern usually is valid. If your boss says the project lacks visibility, they're probably right that visibility matters. They may be wrong about how to create it. Address the concern, not necessarily the prescription.
One Counter-Point
The risk in any framework like this is that it becomes a license to dismiss feedback that's actually accurate but inconvenient. The professionals who get the most stuck are the ones who have built sophisticated frameworks for explaining why the latest piece of difficult feedback doesn't apply to them. If you find yourself rejecting nearly everything, the problem is probably you, not the feedback. The framework is a filter, not a fortress. Use it to focus, not to insulate.
The Recommendation
Build a short list, mental or written, of the five to seven people whose feedback you take seriously without question. These should be people who have done the job, who know the context, and who have a track record of being right about you. For everyone else, run the filter: relevant experience, specific timeline, concrete proposal, repeated pattern, not driven by the speaker's own anxiety. If feedback fails three or more of those tests, acknowledge it, document your reasoning, and move on. The career cost of ignoring bad feedback is far smaller than the career cost of reorganizing your work around the loudest voices in the room.