What a gallery review changed for one regional programme team

Marcus produces a weekly magazine programme for a regional broadcaster, and he got in touch with us in the first weeks of autumn. His complaint was not about picture or sound. The programme looked fine on air. The trouble was that every episode reached the playout team later than planned, and nobody on his side could say exactly where the hours went.

He described a gallery that had grown by habit over several years. A monitor wall was added here, an extra talkback panel there, and the team had stopped noticing how awkward it had become. When I read his notes, I could see he was describing a workflow problem rather than an equipment problem, which is exactly what our review is meant for.

Marcus asked for the review on a Tuesday, and we agreed a visit for the following recording day so we could watch the real routine rather than a rehearsal.

I spent the day in the gallery without touching anything. The director sat at one end of a long desk, the vision mixer at the other, and the graphics operator had her back to the main monitor wall. Every cue had to be called twice because the room was too wide for a quiet instruction to carry.

Behind the gallery, a runner collected cards from the cameras after each block and carried them to a laptop in a different room. Nobody had designed that step. It had simply appeared, and it cost the team around forty minutes after every recording, mostly spent waiting for one person to be free.

I noted the layout, the cable routes, the order of tasks after the last take, and who was waiting on whom. By the end of the afternoon the pattern was clear enough to write down.

• Cues repeated because of the distance between desks
• Graphics operator without a clear view of the programme monitor
• Camera cards moved by hand between rooms
• No agreed naming for files leaving the gallery

The product of a review is a document, not a sales pitch. Marcus received a plain list of changes, ordered by how much time each would save and how little it would cost to do. Some items needed no spending at all, only a different seating plan and a short briefing for the crew.

The first recommendation was to bring the director, vision mixer and graphics operator into a tighter group facing one shared monitor row. The second was to record to a network drive that the edit team could reach directly, which removed the runner and the laptop from the chain. The third was a simple file naming rule, written on one page and pinned beside the desk.

We were careful about what we left out. The list named no new equipment where a change of habit would do the job, and it said plainly which items we could not judge without seeing the broadcaster's own playout requirements.

Marcus did not want to stop production, so the changes went in over three recording weeks. The seating plan came first because it cost nothing and could be tested at once. Within one session the repeated cues dropped away, and the director told him the room felt smaller in a good way.

The network drive took longer. His engineer needed to confirm the bandwidth and agree access rules with the broadcaster's technical department, and I was clear that this part was theirs to decide, not mine. We supplied a short note describing what the gallery needed from the drive, and they worked out the rest between themselves.

The naming rule was the last piece. It sounds trivial, but several of the late deliveries had turned out to be files that existed and could not be found. A clear name made them findable.

A few weeks later Marcus rang to say that episodes were now reaching playout on the day of recording instead of the morning after. He was careful not to overstate it. Some weeks still ran late, usually when a guest overran, but the delay now had a visible cause instead of a vague one.

What he valued most, he said, was having the observations on paper. When he spoke to his own management about the network drive, he could point to a specific step in the chain and its measured cost in time, rather than a general feeling that things were slow.

I should add that I am a lighting designer by trade, and the lighting in his gallery was not part of the review. I joined the visit because the room's monitor glare was affecting the graphics operator, and that went into the list as a small, separate item.

Marcus's situation is common. A gallery grows by small additions, each one sensible alone, until the whole no longer matches how the team actually works. The remedy is rarely a big purchase. It is usually a careful look at who waits for whom, and a willingness to change the order of tasks.

If you are considering a review, the most useful preparation is to know where your own delays seem to occur, even roughly, and to let us watch a genuine recording day. A staged session hides the very habits that cause trouble.

The review ends with a written list you can act on yourself, hand to a colleague, or ask us to help with. What you do with it is up to you.