Giving and Receiving Feedback on Music

Why Feedback Is a Skill

Giving and receiving feedback on music is a learned skill, not a natural talent. Most producers either give vague, unhelpful feedback (“sounds good!”) or overly harsh criticism that discourages more than it helps. And most producers receive feedback poorly — either dismissing it defensively or accepting all of it uncritically.

Good feedback accelerates growth. Bad feedback stalls it. Learning to do both well is one of the most undervalued skills in music production.

Giving Feedback

The Sandwich Problem

You’ve probably heard the “feedback sandwich” advice: say something positive, give the critique, say something positive. The problem is everyone knows this trick, and it makes the positive comments feel insincere. Instead, just be honest and specific.

Be Specific, Not Vague

The most important rule of good feedback is specificity:

Vague: “The mix sounds off.”
Specific: “The kick and bass are competing around 80-100Hz. Try cutting 3dB from the bass around 90Hz or sidechaining it from the kick.”
Vague: “The arrangement is boring.”
Specific: “The 8-bar section from 1:20 to 1:50 doesn’t introduce any new elements. Consider adding a rhythmic variation or a new layer halfway through to maintain interest.”

Specific feedback is actionable. Vague feedback just creates confusion.

Reference Timestamps

When discussing specific sections, always reference timestamps or bar numbers. “The part at 2:15” is immediately locatable. “That one section in the middle” isn’t.

If you’re providing written feedback, a format like this works well:

0:00-0:30 - Intro is solid, good energy right from the start
0:45 - The snare feels buried under the pad. Try pulling the pad back 2-3dB
1:15-1:45 - This section drags. Could you cut it to 8 bars instead of 16?
2:00 - Love the vocal chop here, great moment
2:30-end - The outro fades too quickly. Give it another 4 bars to breathe

Separate Mix Feedback from Composition Feedback

These are two different conversations:

Composition feedback: “The chord progression in the verse is unexpected — it keeps me engaged” or “The melody in the chorus doesn’t feel resolved.”
Mix feedback: “The reverb on the vocal is too wet for this style” or “The stereo width is great but the centre feels thin.”

Make it clear which type of feedback you’re giving. A composer doesn’t need mix notes on a rough demo, and a mixing engineer doesn’t need arrangement opinions on a track that’s already arranged.

Respect the Vision

Before critiquing, understand what the producer is going for. A sparse, minimal track isn’t “empty” — it might be intentionally restrained. An abrasive sound design choice might be exactly what the genre calls for.

Ask “what are you going for with this track?” before offering opinions. Your feedback should help them achieve their vision, not redirect the track toward your taste.

Use “I” Statements

Instead of: “The bass is wrong.”
Try: “The bass feels heavy to me — have you tried it an octave up in the verse?”
Instead of: “This arrangement doesn’t work.”
Try: “I lost interest during the bridge. I think it needs a stronger rhythmic element to pull me through.”

“I” statements frame feedback as perception rather than objective truth. This makes it easier to receive and discuss.

Offer Solutions, Not Just Problems

Identifying problems is step one. Suggesting potential solutions makes feedback vastly more useful:

Problem only: “The drop doesn’t hit hard enough.”
Problem + solution: “The drop doesn’t hit as hard as it could. Try adding a 1-beat silence right before it, and bring the kick in with some parallel compression to add punch.”

You’re not demanding they use your solution — you’re demonstrating that the problem is solvable and giving them a starting point.

Receiving Feedback

Listen Without Defending

When someone critiques your music, your first instinct is to explain why you made every choice: “Well, the reason the bass is like that is because…” Stop. Just listen. Write down the feedback. Thank them. Process it later.

Defending in the moment shuts down the conversation. The person giving feedback feels like their input isn’t wanted, and you miss potentially valuable insights.

Give Yourself a Cooling-Off Period

If feedback stings (and it will sometimes), don’t act on it immediately. Wait at least a day, then re-read or re-listen to the feedback with fresh ears. You’ll often find that what felt harsh in the moment was actually accurate and useful.

Ask Clarifying Questions

If feedback is vague, ask for specifics:

“When you say the mix sounds muddy, which frequency range are you hearing that in?”
“You mentioned the arrangement drags — is that the whole track or a specific section?”
“Can you point me to a reference track that has the energy level you think this should hit?”

Good feedback-givers appreciate being asked to elaborate. It shows you’re taking their input seriously.

Look for Patterns

A single person’s opinion is data, not truth. Multiple people’s opinions are a trend. If three different listeners say the intro is too long, it’s probably too long. If one person says the synth sound is annoying and two others love it, it’s a taste difference, not a problem.

Collect feedback from multiple sources before making significant changes.

Know What to Ignore

Not all feedback deserves action:

Taste differences: “I don’t like this genre” isn’t useful feedback. Neither is “I would have used a different synth.”
Feedback outside the request: If you asked for mix feedback and someone rewrites your melody, that’s overstepping.
Feedback from the wrong audience: A dubstep producer’s opinions on your ambient track may not be relevant.
Contradictory advice: When two trusted sources directly contradict each other, go with your gut. They cancel each other out.

Track and Review Feedback Over Time

Keep notes on feedback you’ve received across multiple tracks. Over time, patterns emerge:

If multiple people across different tracks mention muddy low-end, that’s a mixing skill to develop.
If arrangement pacing comes up repeatedly, spend time studying song structures you admire.
If your sound design consistently gets compliments, lean into that strength.

Use a simple notes system, or track it alongside your projects in Mixvisor.

Creating a Feedback Culture

If you produce within a community or group:

Set Ground Rules

Feedback must be specific and constructive
No “this sucks” without explanation
The producer can specify what feedback they want (“mix only” or “arrangement focus”)
Respect time — if someone shares a 5-minute track, spend at least 5 minutes listening before responding

Reciprocate

The best way to get good feedback is to give it consistently. If someone takes 20 minutes to give you detailed notes, invest the same effort in their work. Reciprocity builds trust and raises the quality of feedback everyone receives.

Many producers never share works-in-progress because they’re afraid of judgment. Normalise sharing rough, unfinished work. The earlier feedback comes, the more useful it is.

Next Steps

Feedback skills are essential for effective collaboration. Read the full Music Production Collaboration guide for the complete framework.