DOCTOR AUDIO / TALK / AUDIO DIRECTION
Why So Many Games Sound the Same
Why so many games sound the same despite strong mechanics and art direction, where the problem actually starts, and a three-question diagnostic producers can run on their own project today.
Take the audio of your game and swap it for the audio of another game in the same genre. Would anyone notice? Many games with interesting mechanics and resolved art direction ship with sound that could belong to any other project in their category.
This publication is adapted from a talk given at GC Latam 2026 for producers, game directors and project leads. It argues that the cause is structural, not a lack of talent, and that it appears well before the first sound is recorded.
It names the four causes, the five questions Flutu answers before touching a sound, and a three-question diagnostic a producer can run on a live project. Limits sit next to each claim, and a sequence at the end shows how another team can apply it.
TL;DR
- The problem is structural, not talent. Generic audio comes from audio treated as a late deliverable with no owner, no document and no direction. It is decided before the first sound is recorded.
- Leadership, not sound, is the missing piece. Excellent sound designers working without someone holding technical and aesthetic authority produce parts that are fine alone and fragmented together.
- Five questions before any sound. Identity in three words, curated references, the gameplay relationship, who owns quality, and the technical implementation. Two pages is enough.
- A three-question diagnostic. Do you have audio documentation? Do you have a technical definition? Who owns the audio project? Whichever one stalls is where to focus.
Why so many games sound the same
The difference between a recognizable sonic identity and interchangeable audio begins in production decisions, not simply in the quality of individual sounds.
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.
Many games today have interesting mechanics, strong visuals and a resolved art direction. With eyes closed, the sound could belong to any other project in the genre. The contrast is easy to test: play a coin pickup, an item chime or a weapon reload from a well-known title without showing the screen, and most of a room will name the game.
That gap is not a coincidence, and it is not a lack of talent. It is structural. It happens well before the first sound is recorded.
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."
None of this signals bad intent. It signals a way of thinking, and it breaks down into four causes.
Audio treated as an isolated deliverableIt enters when someone remembers it is needed. No owner, no process, no direction. Decisions are made late and in isolation.
Decisions made without aesthetic depthThe producer was not trained to make sound direction choices, so decides on intuition, pressure, speed and leftover budget. Direction defaults to whatever is available.
A generic starting pointFree libraries, asset stores and ready-made packs used as the main strategy rather than as tools. A starting point shared with a thousand other studios produces a shared result.
No discussion of how audio strengthens the player experienceNobody asks how music reacts to the player, how sound carries information the UI no longer needs to, how voice builds narrative. These questions arrive late, when changing the answer is expensive.
The fourth cause is the most critical. The questions it names rarely appear in the early stage of a project, and when they do appear, the cost of answering them has already risen.
The problem is not the audio
The problem is leadership, or the lack of it.
A project can have excellent audio professionals working on it. If nobody with technical and aesthetic authority is guiding decisions from start to finish, the result will be fragmented. Each part may be well made on its own. Together, they do not hold.
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 is not about better sounds. It is about who decides, when, and where that decision is written down.
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 costUnplanned audio produces rework at the end: reimplementation, re-recording, last-minute fixes before launch or a pitch event. This is the loss producers feel most directly.
OpportunityGames with a memorable sound get recorded, recommended and talked about. Audio becomes part of organic marketing. Without it, that channel never opens.
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 any sound is recorded, a choice exists. An aesthetic choice, a technical choice, a direction choice.
That choice needs to be documented. It needs to live somewhere outside one person's head. When it lives only in someone's head, it disappears when that person leaves the project, when the project changes phase, or when a new team member joins.
Step zero: five questions
When Flutu enters a project, the first thing we do is not record a sound. It is to answer five questions. Answered honestly, they set the path for the entire audio project.
| Question | What a good answer looks like | What it unlocks |
|---|---|---|
| 1. How should this game sound? What is its sonic identity? | Three words are enough. "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? | The person or team that says yes or no to an audio delivery, with full project view and decision authority | A single point of accountability |
| 5. What is the technical implementation? | Middleware (FMOD, Wwise, native engine audio), file naming, folder structure, the delivery pipeline between the audio studio and the engine team | A pipeline that scales without rework |
When these five questions are answered, the project has the base of an audio direction document. Call it a creative bible, an audio brief, an audio guideline. The name does not matter. What matters is that a shared direction exists.
This step is described in more detail in the Doctor Audio publication Before We Touch a Sound.
How the flow should run
The ideal sequence has four stages. Most projects skip the first two.
Illustrative diagram. The two highlighted stages are the ones usually skipped.
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.
Most projects start at stage three. Straight into production, with no leadership, no document and no defined direction. The result is the one described above: no cohesion, rework, extra cost at the end.
Learn to diagnose: three questions about your project
Three questions, about your project, now. If you can answer all three, the project is in good shape. If one of them stalls, that is where to focus.
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.
This documentation does not need fifty pages. A well-made two-page document can define the whole game from a sound perspective. It does not need to be long. It needs to exist.
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. When the whole team looks at the same thing, decisions get faster, feedback gets more precise, and aesthetic alignment stops being subjective.
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 about structure: how the audio project is organized operationally.
| 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? |
A pipeline without definition is guaranteed 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. Producers easily get lost in the amount of information that needs to be recorded. Documentation is not bureaucracy. It is what lets the project scale without turning into chaos.
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. Not a freelancer who delivers files and disappears, but a person or team that 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 well-intentioned junior does not replace a professional with direction experience. The difference is not technical. It is maturity of decision.
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.
When the process is structured, the working experience changes too. The producer does not chase deliveries. The audio team knows what is being asked and why.
What the evidence establishes
This paper is a method drawn from practice. The table says, for each claim, what kind of support it has and where it stops.
- Observed pattern
- Something seen repeatedly across projects by the author. Real, but not counted.
- Implemented method
- A practice Flutu runs on real projects, with working documents behind it.
- Design argument
- A structural explanation that follows from how production works, not from a measurement.
- Qualitative feedback
- What clients said about working with the process. Not published with names here.
| Claim | Supporting evidence | Category | What it establishes | Limit |
|---|---|---|---|---|
| Audio is routinely treated as a late, ownerless deliverable | Recurring answers heard by the author when joining projects | Observed pattern | A pattern across the author's projects | Anecdotal; not a survey |
| Generic sourcing as main strategy produces generic results | Shared starting points produce shared outcomes | Design argument | A structural explanation | No comparative test |
| Unplanned audio produces rework at the end | Author's experience on large projects with inconsistent naming, implementation and levels | Observed pattern | An observed failure mode | No cost figures |
| Five questions give a project a usable audio direction base | Flutu's onboarding practice; audio vision boards and pre-production documents on real projects | Implemented method | A method with artifacts behind it | Effect on outcomes not measured |
| Structured audio leadership improves the producer's working experience | Client feedback citing clear communication, organized pipeline and on-schedule delivery | Qualitative feedback | How past clients described the process | Not published with names; no measurement |
Trade-offs and limits
It costs a senior person early
The method depends on someone with direction experience being involved from pre-production. That is a cost most projects defer, and the method does not work with a junior in that seat.
Documentation needs upkeep
A two-page direction document is cheap to write and easy to abandon. It only protects the project if it is revisited at milestones and when the game changes direction.
It does not replace craft
Direction and documentation make good sound design cohesive. They do not make weak sound design good.
It is a practice, not a product
The vision board, the volume structures and the session sheets are working documents. There is no template that fits every project.
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.
Why do so many games sound the same? Because nobody made a sound direction decision. Because audio was treated as a delivery, not a system. Because nobody owned the result.
Questions We Can Answer
Why does Flutu publish technical whitepapers?
Around 99% of our projects are covered by strict non-disclosure agreements. That limits how much we can share through named case studies, project footage or internal production material.
Whitepapers give us a way to document how we have helped AA and AAA teams develop working methods, implementation standards and validation workflows, while respecting those confidentiality commitments. We focus on the methods, technical reasoning and evidence we can share without exposing protected project details.
This gives prospective partners a clearer basis for technical evaluation and due diligence: how we investigate systems, structure production work and check results. Each paper distinguishes what was implemented, what was observed and what remains unverified.
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. A starting point shared with a thousand other studios produces a shared result. 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 define the whole game from a sound perspective: three words of identity, a curated reference list, how audio relates to gameplay, who owns quality, and the implementation. It does not need to be long. It needs to exist, and it needs to be revisited when the game changes.
Can a junior sound designer take the ownership role?
A well-intentioned junior does not replace a professional with direction experience. The difference is not technical skill but maturity of decision: knowing how to record well is not the same as knowing how to direct an audio project across a full development cycle. The ownership seat needs technical depth, aesthetic sensitivity and experience with how games are actually built.