How to Stop Letting the Wrong Voices Rewrite Your Work

A few years ago, I played a new song for someone I trusted. She listened carefully, asked thoughtful questions, and then told me she thought the bridge was too long and the ending felt unresolved.

I went home and changed the bridge. I rewrote the ending. Then I played the new version for her and she liked it better. Then I played it for myself and I liked it less. The original ending — the one that felt unresolved to her — was doing something intentional. It was supposed to sit with you, uncomfortably, after the song was over. That was the point.

I had taken good feedback from a thoughtful person and used it to make my work worse.

That experience taught me something I've been refining ever since: the problem isn't just learning to take feedback well. It's learning to evaluate it well. And those are completely different skills.

Why All Feedback Feels Equally Urgent

There's something about receiving a critique — especially from someone you respect — that creates a kind of pressure to act on it. Ignoring feedback feels arrogant. It feels like you're not listening, not growing, not being a good collaborator. The cultural narrative around feedback is almost entirely about being open to it, being receptive, being coachable.

What's missing from that narrative is discernment. The ability to receive feedback, sit with it, evaluate it honestly, and then — sometimes — set it aside without that being a failure of humility.

Not all feedback is created equal. But when you're in the moment of receiving it, especially from someone you care about or respect, it can feel like it is. Everything feels equally weighted. Everything feels like something you should probably do something about.

Building a framework for evaluation is how you get out of that trap.

Step One: Who Is This Person Relative to Your Actual Goals?

The first question I ask about any piece of feedback is: does this person understand what I'm trying to do with this specific work?

This isn't about whether they're smart or talented or trustworthy. It's about whether their creative values and aesthetic sensibility are aligned enough with yours that their reaction to your work is meaningful signal.

My friend who didn't like the unresolved ending has impeccable taste. She makes beautiful work. She also fundamentally prefers resolution in music — her own songs always land cleanly. That's not a flaw. It's a preference. And her preference is not my goal.

When I understood that, her feedback didn't become worthless. It became contextualized. She was telling me that the ending didn't work for her. That's useful information. It's just not a mandate.

For feedback to be truly directional — for it to be something you should act on — the person giving it needs to understand and share your creative goals, at least for this piece. Not forever. Not in general. For this.

Step Two: Are They Responding to the Work or to Their Preferences?

This distinction is subtle and important.

Feedback about the work sounds like: The transition here loses me because the tonal shift happens too fast for me to follow emotionally. It's about craft. It's about effect. It identifies something specific that's happening (or not happening) in the work itself.

Feedback about preferences sounds like: I personally don't love this kind of structure. Or: This isn't really my thing. Or, more insidiously, delivered as if it's objective: The structure doesn't work.

The second kind isn't feedback on your work. It's feedback on your taste. And your taste is not a problem to be solved.

The tricky part is that preference-based feedback often gets delivered in the language of craft. People say it doesn't work when they mean it doesn't work for me. Learning to hear that difference — to translate the delivery into what's actually being communicated — is one of the more valuable skills I've developed as an artist.

Step Three: Does It Resonate With Something You Already Suspected?

This one is a gut-check, and it's surprisingly reliable.

When feedback lands on something true, there's usually a recognition in it. Even if it stings, even if it's uncomfortable, you know it when you hear it. Something in you goes yeah, I was afraid of that or I knew that part wasn't quite right.

When feedback is off-base — when it's coming from a misread of your intentions or a mismatch in values — it usually just feels... wrong. Not defensive wrong. Not ego-protection wrong. Just genuinely, quietly, not-true wrong.

That internal response is data. It's not infallible, and it's worth interrogating — sometimes we dismiss true feedback because it's painful. But it's a starting point. It's worth asking: am I resisting this because it threatens my ego, or because it actually doesn't fit what this work is trying to be?

Step Four: What Would Acting on This Cost the Work?

This is the question I've started asking last, after I've evaluated the source and the nature of the feedback and checked it against my own gut.

If I make this change, what does the work lose? Is what it gains worth more than what it loses?

Sometimes the answer is clearly yes. Sometimes the change makes the work more itself — clearer, stronger, more precisely what it was trying to be. That's the feedback worth taking.

Sometimes the change makes the work more palatable to the person giving the feedback, but less true to what you were actually making. That's the feedback worth setting aside.

The Part About Well-Meaning People

I want to say something about the feedback that's hardest to navigate: the kind that comes from people who love you and want your work to succeed.

This feedback is the most dangerous, not because it's bad, but because the relationship creates pressure that can override your judgment. You don't want to seem ungrateful. You don't want to seem like you think you know better. You care what they think, and that caring can cloud the evaluation.

The framework helps here, because it depersonalizes the question. You're not asking should I dismiss what my friend said. You're asking does this feedback meet the criteria for something I should act on. Sometimes the answer is yes. Sometimes it isn't. Neither answer is a verdict on the friendship.

You can hold someone's feedback with gratitude and still not use it. Those are not in conflict.

Building Your Actual Feedback Circle

All of this works better if you're intentional about who you're asking in the first place.

I have different people I go to for different things. Some are great at structural feedback — they can tell me if the architecture of a piece is working. Some are great at emotional resonance — they can tell me if it lands, if it makes them feel the thing I was trying to make them feel. Some are great at the industry layer — they can tell me how something will be received in a specific context.

I try to go to the right person for the right question, rather than asking everyone everything and then drowning in conflicting input.

Feedback is a resource. Use it intentionally, evaluate it carefully, and protect your work from the well-meaning hands that would reshape it into something that was never yours to begin with.