Sound Guidance: The Art of Creative Feedback

In the fast-paced world of game development, the difference between good sound design and great sound design often comes down to the quality of feedback exchanged between team members.

After years of supervising sound designers, I’ve learned that how we communicate about creative work can either unlock extraordinary potential or inadvertently stifle innovation and enthusiasm

After years of supervising sound designers, I’ve learned that how we communicate about creative work can either unlock extraordinary potential or inadvertently stifle innovation and enthusiasm.
After trials, errors, and countless feedback sessions, I’ve developed approaches that consistently yield better results. Here are nine practical techniques that can transform how you give feedback to your team, and ultimately elevate everyone’s work:

 

Start with Context, Not Criticism

Before diving into specifics, I always take a moment to understand the landscape. It’s tempting to jump right in with immediate reactions—that explosion sounds too thin, that footstep sequence lacks weight—but a quick check-in makes all the difference.

“What were you aiming for with this piece?”

“Which elements do you feel are working, and which aren’t?”

“How does this specific game mechanic work?”

“What kind of feedback would be most helpful right now?”

These questions do more than clarify expectations; they transform the conversation from a one-sided critique into a collaborative exploration. They signal respect for the designer’s creative vision and acknowledge that they might already be aware of certain issues.

 

Match Your Method to the Maker

I’ve learned (sometimes the hard way) that feedback isn’t one-size-fits-all. Some of my team members thrive on immediate, face-to-face discussions where they can ask questions and see my reactions. Others prefer written notes they can process privately before responding.

Understanding each team member’s preferred communication style isn’t just about making feedback more palatable—it’s about making it more effective.

 

Describe Effects, Not Techniques

Perhaps the most transformative shift in my feedback approach has been moving from prescriptive instructions to descriptive guidance. Instead of saying, “Apply a high-pass filter at 150 Hz and add a low shelf with -12dB at 3 kHz,” I’ll say something like, “The underwater sequence still feels too full—can we make it feel more muffled and distant?”

Perhaps the most transformative shift in my feedback approach has been moving from prescriptive instructions to descriptive guidance

This approach accomplishes two critical things: it preserves the creative agency of the sound designer, and it keeps the focus on the emotional impact rather than technical minutiae.
It invites the designer to draw on their expertise to solve the problem, often yielding solutions more innovative than what I might have prescribed.

That said, experience level matters here. With junior sound designers who are still building their technical toolkit, I make a point to add: “If you’re not sure how to achieve this effect, I’m happy to walk you through some specific techniques.” This creates a safe space for learning without assuming everyone has the same technical foundation. I’ve found that explicitly offering technical guidance—without forcing it—helps junior team members grow while still giving them room to experiment and develop their own creative problem-solving skills.

Practice Brevity and Focus

When I first started giving feedback, I’d try to address everything at once. I quickly learned that overwhelming someone with a laundry list of tweaks often results in none of them being addressed effectively.

When I first started giving feedback, I’d try to address everything at once. I quickly learned that overwhelming someone with a laundry list of tweaks often results in none of them being addressed effectively

Now I prioritize ruthlessly. If a piece needs substantial work, I focus on the 2-3 most critical issues that will have the greatest impact. When those are resolved, we can address more nuanced concerns in the next iteration.

Just as in sound design itself—where knowing what to leave out is as important as what to include—effective feedback requires thoughtful curation.

 

Separate the Work from the Person

“This ambience feels disconnected from the emotional arc of the scene” hits differently than “You’re not understanding the emotional requirements here.”

By focusing critique on the work rather than the person who created it, we create psychological safety that encourages risk-taking and experimentation. This isn’t just about being nice—it’s about creating an environment where innovation can flourish without fear of personal judgment.

 

Make Every Conversation Two-Way

Some of the most valuable insights emerge when feedback becomes a dialogue rather than a monologue. I regularly ask questions like:

“What were the challenges you encountered with this design?”

“What alternatives did you try before landing on this approach?”

“How do you feel about trying a different direction here?”

These questions often reveal constraints or considerations I wasn’t aware of, leading to more informed decisions and better outcomes.

Close the Loop

Feedback shouldn’t disappear into the void. Following up on previous conversations—”I love how you addressed the timing issues we discussed last week”—reinforces a culture of continuous improvement and shows that you’re invested in the designer’s growth, not just the immediate deliverable.

 

Beware the Feedback Sandwich

Early in my career, I followed the “praise-criticism-praise” formula. I’ve since learned that transparent, straightforward communication builds more trust than formulaic approaches.

When designers sense you’re softening criticism with obligatory compliments, it can undermine the authenticity of both your praise and your critique

When designers sense you’re softening criticism with obligatory compliments, it can undermine the authenticity of both your praise and your critique.
Instead, I try to be genuine in acknowledging strengths while being clear and direct about what needs improvement.

 

Consider the Timeline

Feedback that arrives too late in a development or deliverable cycle can be more frustrating than helpful. “This would have been perfect if we’d gone in a completely different direction” isn’t useful feedback when milestones are looming. Being mindful of production constraints and the realistic scope for changes is part of giving responsible feedback.

 

In Conclusion: Feedback as Creative Fuel

At its best, feedback isn’t just about fixing problems—it’s about igniting possibilities. When delivered thoughtfully, it can be the catalyst that transforms good sound design into something memorable and emotionally resonant.

The goal isn’t perfection in a single iteration, but rather creating a collaborative environment where each conversation brings us closer to something extraordinary. In game development, where player experience is shaped by countless small decisions, this approach to feedback doesn’t just make for better sound—it makes for better games.

What feedback approaches have worked best in your creative teams? I’d love to hear your thoughts and experiences in the comments below.

---