glamoxyn

The call from Marcus

Marcus produces a weekly regional magazine programme and rang us in the quiet part of late autumn, when the schedule eases and a team can afford to look at itself. His message was short. Transmission nights were running late, the crew was tired, and nobody could say exactly where the minutes went. Rehearsals seemed fine, the equipment was reliable, yet the gallery kept ending the evening in a scramble.

He was not asking for new kit or a redesigned studio. He wanted someone from outside to watch the whole chain, from the first rehearsal to the moment the programme left the building, and write down what they saw. That is the plain description of our Workflow Consulting, and it suited him well. I agreed to spend two production weeks with his crew before saying anything at all.

I mention this because the brief matters. A review that begins with a solution tends to find evidence for it. We began with a question and a notebook instead.

Watching rehearsal to transmission

I sat at the back of the gallery for the first rehearsal and wrote down times rather than opinions. When did the running order arrive, when did the graphics team receive it, when did the director first hear the audio check, and how long did each handover take. It is unglamorous work, and the crew was a little wary at first, as people reasonably are when someone watches them work.

By the second day they had stopped noticing me. That is when the real pattern showed. Decisions were being made twice: once in rehearsal, and again on transmission night, because the notes from rehearsal lived in three places. A producer's pad, a message thread and the director's memory did not always agree.

None of this was anyone's fault. It was simply how the production had grown, one sensible shortcut at a time, until the shortcuts formed a chain with a weak link in the middle.

  • Running order changes noted on paper, in messages and verbally
  • Audio check held after camera line-up, not alongside it
  • Graphics received the final order late in the afternoon

What the written review said

After the second week I wrote the review as a plain document the whole crew could read in one sitting. It described what I observed in the order it happened, named the three points where time was lost, and gave each a specific recommendation with a reason. I avoided jargon on purpose, because a document the runner cannot follow is a document the gallery will not use.

The main finding was modest: one agreed place for the running order, locked at a stated time, with changes after that time passing through a single person. The second was to run the audio check in parallel with camera line-up. The third was a short written handover sheet between the studio floor and the gallery.

Marcus read it twice and asked a fair question: which of these costs money. The honest answer was almost none. The changes were about sequence and agreement, not equipment.

Putting the changes to work

We did not ask the crew to change everything at once. Marcus chose to begin with the single running order, because it removed the most arguments. For the next two programmes I returned to watch, mostly saying nothing, and noted whether the handover sheet was being filled in or quietly ignored.

It was filled in, and then improved by the floor manager, who added a line for tally checks that I had not thought of. That is the best outcome a review can have: the crew takes the document and makes it theirs. Our recommendations were a starting point, and the people who work the gallery every week knew better than I did which details deserved a box on the sheet.

Callum from the lighting side of the crew, a colleague of the floor manager rather than of ours, also asked to attach his cue notes to the same sheet, and the gallery agreed.

What stayed difficult

Not everything resolved. Late changes from the presenter's side still arrived now and then, and no sheet can stop a guest cancelling an hour before air. The review did not claim otherwise. What it gave the team was a clear route for those moments, so that a late change reached one person rather than five.

There was also a cost in attention. For the first few weeks the crew had to remember a routine that felt unnecessary, and a couple of people said so. Marcus held to it, and the habit settled. I would rather tell a client that a change feels fussy before it feels natural than promise it will be effortless from the first night.

A review also has limits. I looked at one programme in one season, and a crew with a different rhythm would need a different reading of its own chain.

  • Late guest changes remain a manageable nuisance
  • New routines feel fussy for the first few weeks

Why the small answer was the right one

When I look back at the case, what stays with me is how ordinary the answer was. No new desk, no rebuilt gallery, just agreement about where information lives and when it stops changing. Many production problems are of this kind, and they are easy to miss from the inside because everyone is busy keeping the programme on air.

An outside reader can see the pattern because they are not part of it. That is the whole value of the exercise, and it is also why we put the findings in writing: a spoken summary fades by the next rehearsal, while a page can be pinned to the gallery wall and argued with.

Marcus still has his copy, now marked up in three colours of pen, which I take as a good sign.

A workflow review rarely produces a single dramatic fix. In Marcus's case it produced a calmer gallery by settling where the running order lives, running two checks side by side and writing a handover down. If your transmission nights feel longer than the programme deserves, a careful look at the chain, from rehearsal to the final feed, is often the cheapest place to begin.