When Feedback Skips The Most Important Question
Soft Signal Episode 008.
The Soft Signal episode for this post is about finding people whose feedback can be useful at all. This post is about what to do once you have them.
Someone listens to your track and tells you it needs more changes. More variation. More movement. Maybe they're right. Or maybe you spent three weeks building a deliberately homogenous soundscape, and what they're describing as a problem is the whole point.
They don't know that. And often, they don't ask.
That's where a lot of feedback gets stuck. Not because the person giving it has bad ears or bad intentions, but because feedback usually arrives as a statement about the artifact, with no question about the intent behind it.
What feedback usually is
When someone tells you a track needs something, they're describing the distance between what they heard and what they expected to hear. That's useful information about them. It's not necessarily useful information about your track.
"This needs more energy in the second half." Did you want energy in the second half? "Nothing really happens." Was something supposed to? "This feels unfinished." Was it?
These aren't rhetorical questions. Sometimes the answer is no, that wasn't intentional, and the feedback is exactly right. But the feedback doesn't know which situation it's in.
The thing that's hard
Finding the intent underneath the artifact is the difficult part of listening to someone else's music. It requires setting aside what you would have done and trying to understand what the producer was attempting. That's a different mode than most people are in when they listen, especially casually, especially once.
That's the structural limit of outside feedback. It can describe what it heard. It can describe what it expected. It can't see what was being attempted.
Which puts most of the responsibility on the producer.
The producer's part
A producer who can articulate what they were going for, even roughly, gives the person giving feedback something to aim at. "I was trying to build a texture that doesn't resolve" changes what useful feedback looks like. Without that, the listener is guessing.
This is also why pre-loading a track with disclaimers tends to backfire. "It's rough, the mix isn't done, ignore the drums" sounds like humility but it's actually shaping the feedback before the listener has heard anything. The listener now has a frame for what to notice and what to excuse, and the response gets organized around that frame rather than the track.
Stating intent is different from apologizing for what isn't there. Intent is what you were trying to do. Apology is what you're worried they'll say. The first gives the listener something useful. The second gives them a script.
What useful feedback looks like
It starts with a question. What were you going for here? Is this where you wanted it to be, or are you still working on it? Was this choice intentional?
That single move changes the conversation. Now the feedback is about whether the track is doing what it's supposed to do, rather than whether it matches what the listener assumed it should do. Those are very different problems with very different answers.
The part that goes both ways
Producers can be too close to their own work to hear what it's doing. A fresh pair of ears can sometimes describe the intent of a track more clearly than the person who made it, which is one of the genuinely useful things outside listening can do.
But that only works if intent is part of the conversation. Feedback that skips straight to "this needs something" misses the chance. The more interesting question is what the track is trying to do. Then whether it's doing it.
The other half of this — finding the listeners in the first place — is in the Soft Signal episode.