What Written Procedures Changed for One Regional Studio Crew

Ellis is a floor manager at a regional television studio. When he first contacted us in the early part of this year, his problem was not a lack of skill. His crews were experienced, and most of them had worked together for years. The trouble was that three different crews rotated through the same gallery, and each had its own habits for the same morning programme.

One crew powered up the vision mixer before checking talkback. Another patched the audio desk from memory and left no record of what had changed. A third kept a handwritten sheet in a drawer that nobody else had seen. Nothing was wrong on any single day, but handovers between crews took far longer than they should, and small mistakes kept returning in slightly different forms.

Ellis asked whether we could write down how the studio should be run, so that it no longer depended on who happened to be on shift.

I spent the first two days in the studio and wrote no procedures at all. I sat in the gallery and on the floor, watched three full rehearsals and two live transmissions, and noted where people paused, asked a colleague, or reached for a phone. Those pauses showed where the real gaps were.

Most of what I found was ordinary. A camera head cable that had to be reseated every few weeks, but only a couple of people knew why. A monitoring preset that one operator reset by hand each morning. A lighting cue that was safe only if the previous cue had completed first.

I wrote these down as plain observations and read them back to the crews before turning any of them into steps. Ellis said this was the part that built trust, because nobody felt the documents were being imposed from outside.

• Pauses and questions point to missing steps
• Workarounds usually hide an undocumented fault
• Crews accept procedures they have helped shape

The documents we produced were short. Each covered one task, such as bringing the gallery up, handing over between crews, or recovering from a lost talkback line. A procedure fitted on a single sheet where possible, with numbered steps, one action per step, and the expected result written beside it so an operator could confirm the step had worked.

We avoided long explanations of theory. Where a reason mattered, it appeared as a single line beneath the step, because people follow a rule more reliably when they know what it prevents. Anything that varied between shows was marked clearly, so the stable parts stayed stable.

Ellis had the sheets laminated and fixed at each position in the gallery. He told me later that the best sign was a crew member quietly correcting a colleague by pointing at a step number instead of arguing about preference.

• One task per sheet, one action per step
• Expected result written beside each step
• Variable items marked so fixed ones stay fixed

Paper alone would not have held. We ran three short sessions, one for each crew, in the gallery itself with the equipment powered and the procedures in hand. Nobody sat through a presentation. Each crew ran a simulated morning from first power-up to handover, following the sheets exactly, while the others watched and noted where the sheets did not match reality.

Those sessions found several errors in my own drafts. A step was out of order, a label on the desk did not match the name I had used, and one recovery routine assumed a spare cable that was not where I expected. We corrected the documents the same afternoon and ran the section again.

By the end, the three crews had practised the same routine on the same equipment, and each had seen the others make the same small slips, which removed much of the old defensiveness.

Ellis kept in touch through the autumn, and the changes he described were modest and believable. Handovers became quicker because the outgoing crew filled in a short end-of-shift note against the same headings every time. Faults were reported in the same words, so the engineer on call understood the problem before arriving.

He also said the sheets were revised twice by the crews themselves, which pleased me more than anything. A procedure that nobody edits has usually stopped being read. We had agreed from the start that one person would own the documents and that every change would carry a short note of what was altered and why.

Not everything was solved. One crew still resisted the checklist for powering down, and Ellis has chosen to raise it gently rather than insist.

• Shorter handovers using one shared note format
• Faults described in the same words by every crew
• Revisions made by the crews, tracked by one owner

The case taught me, again, that documentation is mostly a listening exercise. The skill lies in noticing what experienced people no longer say aloud, then putting it on paper in a form they respect. A neat manual written without that observation tends to sit unopened on a shelf.

Training matters for the same reason. A sheet read once by one person changes little, while a crew that has rehearsed the routine together carries it into the next show without prompting. We now plan documentation and sessions as one piece of work, not two.

If you are considering something similar, start with the handover, since it is where inconsistency costs the most and where improvement is easiest to see.