Working With a Theatre Sound Designer

Some of the most useful feedback I've had on a sound design pitch came from a production team working on a script-driven piece, built around performed text with very little else on stage. Their concern wasn't cost, or whether sound design was a legitimate discipline. It was more specific: they were worried that sound would get in the way of the script — that it would pull focus from the words the production was built entirely around.

That's not a misconception to correct. It's a reasonable instinct, and for that kind of production, a legitimate risk if the sound design is handled badly. Sound can compete with dialogue for attention. It happens when a designer works in isolation from what the production actually prioritises, guessing at what matters instead of being told. The failure in that scenario isn't sound design itself — it's sound design without a clear brief about what it isn't allowed to compete with.

Which is really the argument for this whole article. Whether sound design serves a production or undermines it has less to do with talent and more to do with how the working relationship between director and designer is set up. Get that right, and a text-driven production ends up with sound design that protects the primacy of the script rather than threatening it. Get it wrong — bring a designer in late, hand them a finished show, and hope for the best — and the risk that team was right to flag becomes a lot more likely.

Why this collaboration needs deliberate management

Most creative departments in theatre sit either clearly upstream or clearly downstream of the text. A set designer's decisions are largely fixed before rehearsals begin. A lighting designer typically works from a mostly settled show. Sound sits awkwardly across both positions: it needs the same lead time as an upstream department, because building a sonic world and testing reinforcement takes time, but many of its decisions can only be finalised once blocking, pacing and the director's read on key moments have settled — which happens well into rehearsal, if not later.

That in-between position is exactly why the relationship needs managing rather than assuming it. Left to default timing, sound design tends to slide toward the end of the process, arriving once everything else is fixed. At that point the designer is reacting to a finished show rather than shaping it — which is precisely the scenario that produces sound design detached from the production's actual priorities.

When to bring a designer in

Early involvement doesn't mean a designer needs to sit in on every rehearsal from day one. It means being in the room, or at least in conversation, while the director's read on the text and its emotional shape is still forming — before decisions calcify to the point where sound can only illustrate them rather than inform them.

Practically, that means involvement from early rehearsals or production meetings, not tech week. Leaving it later doesn't just compress the schedule. It removes the opportunity to agree the kind of boundary that team wanted for their script-driven production — an explicit understanding that dialogue takes precedence, established early enough to shape every subsequent decision, rather than negotiated defensively once a sound cue has already been flagged as intrusive in a run-through.

What a designer needs from a director

The single most useful thing a director can give a sound designer isn't a list of tasks — it's a clear account of what the production is actually prioritising, and what it explicitly isn't. For a text-forward piece, that might be as direct as: dialogue is never to be obscured, and any sound that risks pulling focus from a speech needs a strong justification to survive.

Beyond that priority-setting, a useful brief typically covers:

• The tone and world of the production — realistic, stylised, minimal, or something in between.
• Key emotional beats — the moments the director considers pivotal, where sound is more likely to be asked to do real work.
• Non-negotiables versus open ground — what must never happen (a phone ringing a beat too early, dialogue being masked) versus where the designer has genuine creative licence.
• Existing reference points, if any — though these are a starting conversation, not a brief to imitate.

None of this needs to be formal or written. What it needs is to happen early enough that the designer is working from the production's priorities rather than inferring them from a finished run-through.

What to ask before you commit

Because so much of this depends on process rather than talent alone, it's worth evaluating a designer on process before signing off on the collaboration — particularly for a production where getting the balance with text wrong would be costly. A few questions do more work than a portfolio review:

• How do you handle a note that a sound choice is pulling focus? The answer worth hearing is something like a quick, unresisting adjustment, not a defence of the original idea. Designers who treat every note as a negotiation are harder to work with under tech-week pressure.
• How do you approach a production where dialogue has to take priority over everything else? This tests whether they've actually worked on text-forward pieces or are assuming every show wants a fuller sonic treatment by default.
• What do you need from me, and by when? A designer without a clear answer to this either hasn't thought about the collaboration structure or is used to working in isolation — both worth knowing before rehearsals start, not during them.

None of these questions require technical knowledge to ask or evaluate. They test working style, which is the thing most likely to determine whether the collaboration goes well.

Where creative authority sits

The clean version of this is straightforward: the director holds final authority over the story being told; the designer holds authority over how sound achieves whatever the director has asked for. In practice, friction rarely comes from a genuine artistic disagreement between those two positions. It comes from vague direction — a note like "make this bit feel more atmospheric" that hasn't specified what the atmosphere needs to protect.

A brief, invented example: a designer proposes a low ambient bed under a monologue, intended to add tension. The director cuts it in the run-through, not because the idea was wrong, but because it was drawing attention to itself at a moment where the production needed the audience's attention entirely on the actor's face. Read as conflict, that looks like the designer's judgement being overruled. Read accurately, it's a brief that was never quite specific enough about where the line sat — resolved quickly, because the relationship allowed for a note and a fix rather than a defence of the original choice. The same disagreement arriving for the first time in tech week, with no working relationship to fall back on, tends to take longer to resolve and costs more goodwill on both sides.

Sound and lighting

The pillar article on this site notes that lighting and sound shape the audience's sense of time and place simultaneously, and that a mismatch between the two tends to feel unfinished even when neither department has done anything wrong in isolation. The collaboration mechanics behind that point are simple in principle: sound and lighting designers benefit from knowing what the other is doing at the same production meetings, rather than each working from the script independently and reconciling differences only once both are in the room together. On smaller productions without a formal system for this, the director is often the one holding that connection — worth being deliberate about rather than assuming it happens by osmosis.

In practice, the dependency shows up most clearly at transitions — the moment discussed in the pillar article's worked example, where a scene change relies on lighting and sound landing together. If the two designers haven't compared notes, the common failure is a lighting cue that completes half a second before or after the sound does, which reads to an audience as a rough edit even when both elements are individually well designed. Fixing that in tech week is a matter of minutes once someone notices it; the value of earlier coordination is that fewer of these small mismatches make it to tech week in the first place, leaving more of that limited time for problems that actually need it.

What this looks like in tech week

By tech week, the working relationship should already be established — this isn't where it starts. What changes is the mode of communication: notes become faster and more specific, tied to what's just been seen rather than what's anticipated. A director who has been in dialogue with the designer throughout rehearsals can give a note like "that transition is too long against the blackout" and expect it to be understood immediately, because the designer already knows the production's priorities. A director meeting the designer's choices for the first time in tech week is giving the same note without that shared context, which is slower to resolve and more likely to produce exactly the kind of friction the relationship, done earlier, would have avoided. The scheduling mechanics of tech week — what happens when, and in what order — are covered separately; what matters here is that the quality of communication in that week is set by everything that happened before it.

Where this leaves a text-driven production

None of this requires sound design to be minimal, and minimal isn't automatically safer — an underused sound design can also fail a production, just less visibly. What it requires is that "does this serve the text or compete with it" is a standing question the designer is answering with the director, throughout, rather than a concern raised once and then left to hope for the best. Productions built entirely around performed text are not a case where sound design doesn't belong. They're a case where the brief needs to be unusually clear about what sound is there to protect.

If you're weighing up how sound design would sit against a particular production — especially one where the text is doing most of the work — that's worth talking through early. Get in touch before the schedule and expectations are set around an assumption that turns out not to fit.