DOCTOR AUDIO / TALK / AUDIO DIRECTION
Why So Many Games Sound the Same
Why sonic identity gets diluted when direction arrives late, and how producers can define, implement and review audio as part of gameplay.
Audio direction · Production ownership · GC Latam 2026 · 10 min read
Take the audio of your game and swap it for the audio of another game in the same genre. Would anyone notice? A game can have distinctive mechanics and art direction yet rely on audio cues whose timing, palette and gameplay role are indistinguishable from genre conventions.
The production problem starts when audio's gameplay role is defined only after mechanics, UI states and content workflows are already fixed. At that point, changing a cue can also mean changing its trigger, priority or mix behavior. A recognizable sonic identity needs design ownership before asset production accelerates.
This article is a written adaptation of Victor Hime's talk at gamescom latam 2026 in São Paulo, Brazil.
We start by defining five decisions: sonic identity, references, gameplay behavior, decision ownership and implementation. The three-question audit tests whether those decisions survive in the brief, the engine integration and the team's approval process.
TL;DR
- 01Audio identity is a production decision. Interchangeable audio often follows late direction, disconnected gameplay requirements and unclear ownership. The fix starts with decisions, not a bigger sound library.
- 02Give sound direction an owner. Give one lead authority to resolve conflicts between gameplay feedback, sonic style, integration and the build review as features change.
- 03Define five decisions before production. Define identity, curate references, connect sound to gameplay, name a reviewer and decide implementation boundaries. Write them down and test them in builds.
- 04Audit three production foundations. Check the direction brief, the integration contract and the person accountable for approvals. Then verify each answer against the current build.
Why so many games sound the same
Sonic identity is established through repeatable choices about timbre, feedback hierarchy, state transitions and mix priorities. Individual assets can be excellent while the game still lacks an audible language.
The question
Take the audio of your game and swap it for the audio of another game in the same genre. Would anyone notice?
This is not a question about technical quality. It is not asking whether the sounds are well recorded or the music is good. It is asking whether the game has a sound of its own: something that, with your eyes closed, tells you which game this is and not another.
A familiar pickup, interface cue or reload can communicate a game's identity without relying on the screen. That is the useful test: do the sounds have consistent character and meaning, or are they merely competent genre defaults?
When audio feels interchangeable, we examine who established its purpose, its sonic rules and its implementation boundaries before questioning the talent behind individual assets.
Why it happens
When Flutu joins a project and starts asking about audio, the answers tend to follow a pattern. "We will sort out audio later, once the game is further along." "We hired a freelancer to make the sounds." "I found some tracks on a free library, I think they work."
These are ordinary scheduling and sourcing decisions. Problems emerge when nobody connects them to sound direction, playback rules and in-game review.
Audio treated as an isolated deliverableAudio arrives after features are specified, without an owner or review criteria. Playback rules and creative decisions are then made in isolation.
Decisions without a shared sonic briefWithout agreed references or evaluation criteria, choices tend to follow immediate deadlines and available assets rather than the needs of gameplay.
A generic starting pointFree libraries, asset stores and ready-made packs used as the main strategy rather than as tools. Without deliberate selection, processing and contextual implementation, familiar library assets tend to retain a familiar identity.
No discussion of how audio strengthens the player experienceThe team has not defined which music states should respond to gameplay, which cues must communicate information and how voice supports narrative. Retrofitting these decisions later can require new event logic.
The gameplay relationship is especially costly to postpone. Clarifying it late can require changing event triggers, game-state parameters, mixing priorities and interface feedback.
The problem is not the audio
The recurring production gap is clear audio ownership: someone who can resolve aesthetic and technical decisions across the project.
A team can produce excellent individual assets and still lack a coherent in-game result. Someone needs authority to resolve conflicts between sound direction, gameplay priorities, integration and what the player actually hears.
This is the premise for everything that follows. For an independent perspective on production ownership, see Rob Bridgett on the audio director role. The method specifies who approves each decision, which gameplay behavior it serves and how the team evaluates it in a playable build.
What a project loses without audio leadership
Cohesion with gameplaySounds made by different people at different moments with no common direction. Each piece is fine in isolation; the whole does not hold together.
Identity and narrativeWithout a sonic identity the game could be any other in its genre. The chance to make something the player carries after closing the game is gone.
Production costWhen audio direction and integration are deferred, teams risk late rework: reimplementation, re-recording, last-minute fixes before launch or a pitch event. This is the loss producers feel most directly.
OpportunityRecognizable sound can contribute to a game's public identity. That potential matters, but gameplay readability and consistent in-game behavior remain the first review criteria.
Direction before production
Establish the aesthetic and technical direction, document the five foundational answers and build a production flow that makes those decisions actionable.
Before any sound, there is a choice
Before producing a sound, decide what the player needs to recognize, how urgently they need to hear it and what the rest of the mix should do around that information.
Record the intended behavior, audible references and responsible reviewer. A brief tied to gameplay states survives staff changes and implementation handoffs better than aesthetic adjectives alone.
Step zero: five questions
Our starting point is five decisions that constrain sound creation and implementation. Each answer should guide a concrete choice in a real gameplay sequence, not sit unused in a slide deck.
| Question | What a good answer looks like | What it unlocks |
|---|---|---|
| 1. How should this game sound? What is its sonic identity? | Three descriptors are a starting point, each tied to an audible reference and an intentional contrast. "Tense, organic, primitive." "Bright, colorful, retro." | A filter for every decision that follows |
| 2. What are the references? | A curated list of games, films, albums and artists, not a generic mood board | A compass the audio team can use |
| 3. How do sound and music relate to gameplay? | Where audio is interactive, where music reacts to player state, where sound carries information the interface no longer needs to, how audio fits the HUD priority and the user experience | Audio designed as a system rather than a layer |
| 4. Who owns quality? | A named decision-maker who can review in-game behavior and resolve audio, design and engineering conflicts | Clear ownership and an escalation path |
| 5. What is the technical implementation? | Middleware (FMOD, Wwise or native engine audio), event ownership, naming, game-state contracts, asset delivery and in-engine QA | A pipeline that scales without rework |
These answers form the first version of an audio direction document. Its value is whether a sound designer and programmer can apply the same decisions to a playable feature.
To audit the technical implementation behind those decisions, read Before We Touch a Sound.
How the flow should run
The sequence has four stages. A frequent production risk is starting at asset creation before the earlier decisions are ready.
Direction and documentation establish the decisions that production must implement. Early representative cues should still be prototyped in-engine so the team can challenge assumptions before scaling asset creation.
Sound direction is defined, the five questions are answered, and someone with technical and aesthetic authority is in place.
References, scope and technical decisions, all recorded.
Now it starts, with clarity and a shared direction.
Audio QA, iteration, adjustments based on context rather than guesswork.
When asset production begins without an approval owner or acceptance criteria, production absorbs unresolved design decisions. A sound may be approved in isolation yet fail when competing with dialogue, UI feedback or a state transition.
Learn to diagnose: three questions about your project
Use these questions as a production health check, not a pass/fail score. An answer only helps if the team can demonstrate it in the current build. Missing answers show where decisions can drift.
01 · Do you have audio documentation?
Curated references, written sound direction, genre benchmarking.
Curated references. Not a random playlist. An intentional selection of games, films and music that defines the project's sonic territory.
Written sound direction. Words that describe how the game should sound and what the player should feel while playing without looking at the screen.
Genre benchmarking. An analysis of how similar games treat audio: what is being done, what has not been explored, where there is room to differentiate.
An initial two-page document can establish direction for a small team. Expand it where feature complexity, platforms or delivery dependencies demand more detail, and update it when decisions change.
In practice Flutu produces this as an audio vision board: a visual and descriptive map any team member can open and understand. It holds films, games, analyses of sound design, music and gameplay context. Shared references make reviews easier to repeat: the team can point to a cue's intended purpose and a playable example instead of exchanging vague adjectives.
Output: a two-page direction document or vision board the whole team can open.
02 · Do you have a technical definition?
Naming, middleware and handoff, loudness and mix structure.
This is the integration contract: event naming, trigger ownership, parameters, bus hierarchy, loudness targets, handoff responsibilities and the tests that confirm the system behaves as designed.
| Area | The question to answer |
|---|---|
| Naming and file structure | Is there a convention the whole team follows? If a freelancer delivers a file tomorrow, will it be named like the file delivered six months ago? |
| Middleware and implementation pipeline | How does audio enter the game: FMOD, Wwise, native? Who implements, who tests, how is the handoff between audio and engine done? |
| Volume management and mix | Is there a loudness standard for the project? How do dialogue, music, ambience and SFX coexist without fighting each other? |
Without shared naming, trigger ownership and gain conventions, each added feature increases the risk of duplicate events, inconsistent routing and avoidable rework. On large projects this shows up at the end as hundreds of audio files named in different ways, implemented by different people, at levels that do not talk to each other.
The documentation that supports this on Flutu projects includes volume structures by SFX category, voice over scripts, and session control sheets with recording specifications. Audio works with a very high asset count and with cross-disciplinary relationships across design, narrative, programming and production. Shared documentation keeps this information accessible across disciplines. Useful documentation supports consistent revisions, handoffs and repeatable audio QA.
Output: naming convention, middleware and handoff, loudness standard, all written down.
03 · Who is responsible for the audio project?
Technically, aesthetically and in production, from start to launch.
This is the most important of the three. The question is not who was hired to make the sounds. It is who has ownership, who guarantees quality, who decides.
Experience matters here. Not everyone can carry this responsibility. It requires technical depth, aesthetic sensitivity and experience with the game development cycle. Knowing how to record well is not the same as knowing how to direct an audio project.
Real ownership runs from start to launch. A person or team follows the project, revisits decisions, adapts when the game changes direction, and keeps the sound experience aligned with what was defined at the beginning. At every milestone, every new build, every mechanic change that affects audio, someone is looking at it.
A junior can own a bounded feature with support. Project-wide direction needs someone experienced at resolving aesthetic, technical and scheduling trade-offs.
Output: one named person or team with authority to say yes or no, from now to launch.
What a project gains when it is done right
Autonomy and cooperationThe audio team works independently. Guidelines are documented and the vision is clear, so the producer is not needed for every decision.
Aesthetic cohesionThe game has audio with its own identity. Sounds that talk to each other, music that reinforces gameplay, sound design that complements the art direction.
ResilienceWhen the team changes, a new member joins or a freelancer is replaced, documentation carries continuity. The aesthetic does not depend on one person.
PredictabilityThe reason behind each decision is known. If part of the audio needs refactoring, it is clear where, when and why that decision was made.
Defined ownership and review criteria help producers assess in-game results and keep revisions tied to gameplay, rather than approving isolated sound files.
How we validate audio direction in production
Audio direction becomes actionable when an intended player response maps to a cue, a game state, an implementation owner and an in-build acceptance check. The review needs to distinguish a sound-design issue from a trigger, routing or prioritization issue.
- Direction ownership
- A named lead owns the acceptance criteria for critical cues and resolves trade-offs between gameplay readability, sonic character and production constraints.
- Working artifacts
- A direction brief, integration conventions and review notes connect audio decisions to implementation.
- Sonic differentiation
- Compare critical cues in context, including crowded mixes and repeated gameplay. A reference palette only matters when its rules are audible in the build.
- Milestone reviews
- Review sound in playable builds, assign changes to an owner and retest when mechanics or game-state contracts change.
| Decision area | What to inspect | Review focus | Validation step | Failure risk |
|---|---|---|---|---|
| Direction and ownership | Is the audio lead named before systems and asset production are locked? | Direction ownership | Review the approval path and verify a core cue against the direction brief | Late or contradictory approvals |
| Source palette and differentiation | Do references specify a palette, a counterexample and the role of each core cue? | Sonic differentiation | Compare key feedback cues against gameplay needs and genre references | Distinctive sound never reaches the playable build |
| Technical implementation consistency | Are event names, parameters, buses, handoffs and loudness rules documented? | Direction ownership | Run a representative state transition and inspect event routing and mix balance | Late reimplementation and inconsistent levels |
| A usable audio direction brief | Does the brief connect identity, references, gameplay, ownership and integration? | Working artifacts | Review a representative mechanic against the five decisions | The brief exists but does not guide changes |
| Build review and change control | Are review notes tied to current builds, assigned owners and acceptance criteria? | Milestone reviews | Verify that gameplay changes trigger an audio review and clear action items | Feedback lost between disciplines |
Keeping audio direction actionable
Experienced direction belongs early in the schedule
The audio lead needs access to gameplay and engine decisions before event contracts become expensive to change. Small teams can assign this role part-time, provided review gates, escalation and integration ownership are explicit.
Documentation needs upkeep
A short direction brief is enough to start, but it must be versioned with gameplay changes. An outdated document can be worse than a missing one when teams treat obsolete mix or event rules as current.
The method needs to fit the game
Use vision boards, mix structures and session sheets where they support real decisions. A combat-heavy game and a narrative puzzle need different event taxonomies, priority rules and validation gates.
Applying this to your project
A sequence for a producer or audio lead on a live project. The steps are in order: each one depends on the previous.
01 · Run the three-question diagnostic
Which of the three stalls?
Documentation, technical definition, ownership. Write down which of the three stalls.
02 · Answer the five step-zero questions before the next audio delivery
What is the direction?
Three words for identity, a curated reference list, the gameplay relationship, the owner, the implementation.
03 · Put the answers in a document outside one person's head
Where does the decision live?
Two pages is enough to start.
04 · Name the owner
Who says yes or no?
One person or team with authority to say yes or no to audio deliveries, from now to launch.
05 · Fix the technical definition before volume rises
Will this scale?
Naming convention, middleware, handoff, loudness standard.
06 · Review at every milestone
Is the direction still true?
Direction document, build, and any mechanic change that touches audio.
Technical knowledgeSomeone who understands FMOD and Wwise and also game feel, feedback loops and narrative identity. The bridge between aesthetics and the engine.
PlanningAn audio schedule integrated with the game schedule, defined milestones, documentation from pre-production. A process that scales.
LeadershipSomeone with ownership who defends the direction and guarantees quality through to ship. A production partner, not a file supplier.
When a game's sound feels interchangeable, our first question is not which library was used. We ask who decided what the player should hear, how the game should respond and how that intent would be checked in a build.
Questions We Can Answer
Why does Flutu publish technical whitepapers?
Much of Flutu's production work is confidential. Doctor Audio focuses on practical audio decisions and engineering approaches that can be discussed without disclosing client materials.
These papers explain how we organize audio direction, design integration boundaries and evaluate results in playable game systems.
The point is to make our decision-making legible: why we choose a method, what it costs and how the team knows whether it works.
Is there anything wrong with using free libraries or asset stores?
No. They are tools, and useful ones. The problem is when they become the main strategy. Without deliberate selection, processing and contextual implementation, familiar library assets tend to retain a familiar identity. Used under a defined sound direction, library material can be selected, layered and processed into something specific to the game.
How long does the audio direction document need to be?
Two pages can be sufficient for an initial audio direction brief. Include references, gameplay behavior, ownership and implementation decisions, then expand it as project complexity demands and validate it in builds.
Can a junior sound designer take the ownership role?
A junior designer can take responsibility for clearly bounded features with review. Direction across the entire game requires authority and enough experience to resolve conflicts between sound, game design, engineering and the production schedule.