How to Prepare Your Team for a Studio Workflow Review

A workflow review is most useful when it starts with a plain question. Before anyone visits, write down the one or two problems you actually feel: a changeover that always overruns, rehearsals that start late, retakes caused by the same fault, or a gallery that depends on one person who knows where everything is. A review without a question tends to produce a long list of small observations, and a short list of real causes is more use to a crew. Keep the question about time and quality, not about equipment. Kit is often blamed for problems that come from handovers, unclear cues or settings nobody has written down. If you can describe the symptom in a sentence, the reviewer can look for its source across the whole chain.

Ask the people who work in the studio each week to contribute a line or two. Floor staff, vision mixers, sound operators and runners see different failures, and they rarely get to say so in one place. Collect these remarks before the visit and keep them anonymous if that helps people be candid. You will usually find that three or four themes are mentioned by several people independently, and those themes deserve the most attention on the day.

• Name one or two symptoms, not a wish list
• Describe the cost in minutes lost or shots repeated
• Gather short remarks from floor, gallery and sound
• Note anything that has already been tried

Bring together whatever the crew genuinely relies on, not what the filing cabinet says should exist. That might be a laminated line-up sheet, a shared running order, a patch list pinned beside the desk, or a page of handwritten notes kept by the longest-serving engineer. Include the unofficial material. The gap between the official procedure and the one people follow is often where time disappears, and the reviewer needs to see both to understand it. If a document is out of date, leave it as it is rather than tidying it beforehand. A corrected version hides the very thing the review is meant to find. Date the copies you hand over if you can, and note who last changed them. A clear picture of how information moves between people, and how stale it becomes, tells us more than a polished set of manuals ever could.

Add a simple floor plan and a signal flow sketch, even a rough one drawn on paper. They do not need to be accurate to the centimetre. What matters is showing where cameras, talkback, audio feeds and the control room sit in relation to one another, and which connections are permanent and which are patched in for each show. Rough sketches also reveal disagreements, when two people draw the same route differently, and those disagreements are worth discussing.

• Running orders and line-up sheets in current use
• Patch lists, talkback assignments and channel plans
• Handwritten notes and pinned reminders
• A rough floor plan and signal flow sketch

The temptation before a review is to put on a perfect production. Resist it. A reviewer who watches a rehearsed, carefully managed session will see a team performing, not working. Schedule the visit on an ordinary production day, with the usual pressures, the usual late changes and the usual people. If a guest always arrives ten minutes behind, let them. If the autocue always needs a restart, let it restart. These small recurring events are the evidence. Tell the crew in advance that nobody is being assessed. The review looks at the process, and the process belongs to everyone who contributes to it. People who feel watched tend to skip steps they normally take or add steps they normally skip, and both distort the result. A short briefing at the start, explaining that the aim is to find where time and quality leak out, usually settles the room within the first hour.

Allow the reviewer to sit in different places. Time at the back of the gallery, on the studio floor and beside the sound desk shows how a single cue travels and where it gets lost or repeated. Ask them to note how long each handover takes, not just whether it happens. A handover that works but costs ninety seconds every time becomes a large number across a week of shows, and it is rarely visible from a single seat.

• Choose a typical production day
• Brief the crew that the process is under review, not them
• Let the reviewer move between floor, gallery and audio
• Keep the usual delays and late changes in place

Once the visit is complete, a good report is short enough to be read by the whole crew and specific enough to act on. It should describe what was observed, say where time or quality was lost, and rank the findings by how much they cost. Anything that cannot be tied to something seen on the day belongs in a separate note of questions, not in the findings. A report that mixes evidence with opinion is harder to trust and easier to argue with. Expect the report to include small items alongside the large ones. A mislabelled fader or an ambiguous cue word costs little to fix and builds goodwill. Larger findings, such as a layout that forces people to cross each other's paths, take longer and need budget. Seeing both together helps a team choose where to start without committing to a full overhaul, which is rarely what the evidence calls for.

Read the draft together with the crew before it is finalised. People often spot a misunderstanding, a detail that has since changed or a cause the reviewer could not see from outside. Correcting these at this stage makes the final version more accurate and more likely to be used. A report that the team recognises as a fair description of their work is far more likely to lead to changes than one that arrives as a verdict.

• Findings tied to something observed on the day
• Ranked by the time or quality they cost
• Quick fixes separated from larger changes
• Draft read through with the crew first

The most reliable way to act on a review is to change one thing at a time and watch what happens. Pick a finding with a clear measure, such as the time a changeover takes, and alter a single step. Run it for a handful of productions and compare. If the result is better, keep it and write it down. If not, return to the old way without fuss. Small trials are cheap, and they give the crew a say in what stays. Avoid changing the order of work, the layout and the equipment in one go. When several things move together, nobody can tell which change helped and which caused a new problem. Autumn is a sensible time to begin, because the schedule often settles after the summer break and there is room to try things before the busy weeks near the year's end.

Record every adopted change in the documents people actually use, and remove the old version so it cannot creep back. Many improvements fade within a few months because the paperwork still describes the previous routine and newcomers learn from it. A single page that says how a step is done now, kept beside the desk, does more to hold a gain than any amount of reminder.

• Change one step and measure it over several shows
• Keep the trial small and reversible
• Update the working documents straight away
• Remove outdated copies from the gallery and floor