The Feedback Problem: Why Most Notes on Your Mix Make It Worse
Everyone tells you to get feedback on your mixes. Nobody tells you that, according to the largest analysis ever conducted on the subject, more than a third of the feedback you receive is actively harming your work.
The number that should change how you ask for notes
In 1996, researchers Avraham Kluger and Angelo DeNisi published what remains the definitive study on feedback. They analyzed 607 effect sizes from 23,663 observations across 131 different studies. Their conclusion: feedback improves performance on average, yes — but the overall effect size is modest, and 38% of feedback interventions actually decrease performance.
Let that sink in. If you ask three people for notes on your track, statistically, at least one of them is giving you feedback that makes the track worse. And you probably can't tell which one.
Feedback is not automatically helpful. It has conditions. When those conditions aren't met, it's destructive — and most people giving you notes don't know the difference.
Which feedback hurts (and which helps)
Kluger and DeNisi didn't just find that some feedback fails. They identified exactly which types fail and why. This is where it gets directly relevant to music:
Praise is nearly useless. The effect size of praise on performance is 0.09 — close to zero. When someone tells you "this sounds great," they might be making you feel good. They are not helping you improve. In fact, compared to not receiving that praise, the difference in your subsequent performance is negligible.
Person-focused criticism makes you worse. When feedback targets you as a person rather than the work — "you're overthinking this," "you don't understand reverb" — the effect size goes negative. It's −0.14. You literally perform worse after receiving this kind of feedback than if you'd received none at all.
Task-focused corrections are what actually work. When feedback is specific, actionable, and directed at the task — "the vocal needs 2dB more at 3kHz" rather than "the vocal sounds wrong" — the effect size is 0.55. This is the gold standard. Even better: when the feedback includes the correct solution, the effect rises further.
Velocity-framed feedback outperforms static feedback. When feedback compares you to your own past performance ("your mixes are getting cleaner — the low end on this one is tighter than last month's") rather than to an external standard, it's significantly more effective.
Why this happens: the attention mechanism
Kluger and DeNisi's central insight was their Feedback Intervention Theory, which proposes that feedback works by directing attention. When feedback directs attention to the task itself — the specific thing you're doing and how to do it better — performance improves. When feedback directs attention to the self — your identity, your ability, your worth — performance declines.
This explains why "this sounds great" fails. It directs attention to your feelings about yourself, not to the track. It's pleasant but inert. And it explains why "you're overthinking the compression" fails: it directs attention to your personal flaw (overthinking), not to the compression setting that needs adjustment.
The most effective feedback keeps attention locked on the work: what's happening in the track, what needs to change, how to change it, and whether it's better than your last attempt.
What this means for your process
If you're an independent artist, you probably get feedback from a few sources: friends, fellow producers, maybe a mentor or a collaborator. Most of them are giving you the wrong kind — not because they're bad people or bad musicians, but because nobody taught them the difference.
Here's what to do about it:
Ask for specific feedback. Don't say "what do you think?" Say "is the low end translating on your system?" or "does the vocal sit right in the chorus?" Narrow the question to the task level. The more specific your ask, the harder it is for the person to default to vague praise or irrelevant criticism.
Filter out praise and person-focused comments. When someone says "this is fire," thank them and mentally discard it. It's noise. When someone says "you always push the high end too much," recognize that as person-focused criticism and treat it skeptically — even if there might be a useful observation buried inside.
Only act on task-specific, corrective notes. The note that says "the kick and bass are fighting at 80Hz — try sidechaining the bass to the kick" is gold. The note that says "the mix feels off" is not actionable. If you can't immediately identify what specific change to make, the feedback is not ready for use.
Limit the number of changes per revision. Even good feedback becomes harmful in volume. Fix one thing. Listen again. Then fix the next. The research on choice overload shows that too many options degrades decision quality — and too many simultaneous changes makes it impossible to tell which one helped.
The implication for collaborators
If you're the one giving feedback — to a collaborator, a client, or a friend — the research gives you a clear protocol: be specific, be corrective, be task-focused, and compare to their own past work. Never say "this sounds great" and leave it there. Never say "you need to work on your mixes." Say "the vocal in the second verse is getting buried — try pulling the guitar back 1.5dB and see if it opens up."
That one sentence will do more for the track than an hour of vague encouragement.