Studio Workflow Reviews: Common Mistakes and How to Avoid Them

The commonest mistake in a workflow review is to open with a list of equipment. People want to know whether the vision mixer is old enough to blame or whether the router needs replacing. Kit matters, but a studio loses time in the gaps between jobs far more often than inside any one machine. A review that begins with the equipment list tends to confirm what the team already suspects and misses what nobody thinks to mention.

A better start is to follow one ordinary production from the first call of the morning to the last cable coiled away. Note who waits for whom, which messages go by radio and which by shouting across the room, and where a person stops to ask what happens next. Those pauses are where the minutes go, and they rarely appear on any inventory.

• Follow one real production from call time to wrap
• Write down every wait, however short
• List the questions people ask each other during the day

Many teams arrange a review for a day when nothing much is happening, because it feels polite not to get in the way. The trouble is that a quiet studio hides almost every problem worth finding. Cues are relaxed, nobody is rushing a rundown change, and the awkward workarounds that crews use under pressure never come out.

Choose a day with a real programme, a rehearsal with a full crew, or a live event with its usual last-minute changes. The reviewer should sit in the control room and watch quietly rather than ask for a demonstration. People behave differently when they are showing you how something works, and the habits you need to see are the ones they no longer notice themselves.

Every studio has a problem everyone talks about: the intercom that crackles, the tally that lags, the monitor wall that is awkward to read. These get attention because they are annoying, and fixing them feels productive. Meanwhile a slower loss goes unnoticed, such as a graphics handover that always takes three attempts, or a lip-sync check that is skipped because nobody owns it.

When we write up a review we try to rank findings by the time or quality they cost over a month, not by how irritating they are. A small delay repeated at every programme can outweigh a dramatic fault that happens twice a year. Ask the crew which job they dread, then ask which one they have simply stopped thinking about.

• Rank findings by cost over a month, not by annoyance
• Ask which tasks have no clear owner

A review done only with managers and engineering leads produces a tidy report that the floor does not recognise. Camera operators, floor managers and audio assistants see the workflow from places the control room cannot, and they often know exactly why a step is done in a strange order. Skipping them also makes the later recommendations harder to adopt, because people are asked to change a routine nobody consulted them about.

Spend a few minutes with each role, ideally away from the desk and without a supervisor listening. Ask what they would change first and what they would never touch. The answers are usually practical and specific, and they tend to point at the same two or three issues that the observation alone had only hinted at.

A long document full of findings can be as unhelpful as no document at all. If a report lists forty observations with equal weight, the team will read the first page, agree with it and return to the old routine. Vague advice such as improve communication in the gallery also gives nobody a task they can start on Monday.

We prefer a short list of changes, each with a named step, a rough effort and a reason. Some are free, such as a revised cue sheet or a change to the order of checks. Others need a purchase or a day of rewiring, and those should be clearly marked as separate decisions. A report should help a producer choose what to do next, not simply prove that the review took place.

• Keep the first list short and ordered by effect
• Mark clearly which changes cost nothing
• Give each change one person to own it

Workflows drift. A new presenter arrives, a graphics package is updated, a second studio opens, and the procedure that worked in spring no longer fits by the end of autumn. Teams sometimes treat a review as a repair job: once done, it is filed away and the improvements slowly fade as old habits return.

A lighter check every few months, using the same production and the same notes, shows whether the changes stuck and where new friction has appeared. It does not need an outside reviewer each time. Someone on the crew can time the same three handovers and compare them with the earlier figures. Small, regular attention keeps a workflow honest far better than a large effort every few years.