Choosing help to run a complex programme without a hitch

A complex programme isn't just about hiring hands on the day—it's about hiring someone who understands the *exact* shape of your event before anything goes wrong. The person running your AV and production needs to see what you're trying to do, not just execute a checklist.

The split between candidates widens fastest when you stop asking "Can you do it?" and start asking "How would you run *this*?" That's where most hiring decisions go sideways.

The person who reads your programme, not just your brief

What matters first is whether they take time to understand your sequence. If you have a live speaker followed by a filmed segment, then a Q&A with audience interaction, then a product reveal on multiple screens—a good technical lead thinks through the *transitions*, not just the individual components.

Ask them to walk you through how they'd handle the handoff from live to video. Watch whether they ask about your speakers' comfort level with tech, whether they know what happens if the internet drops during your stream, and whether they've already thought about backup power for your critical elements. Someone who digs into these details before quoting hasn't just run events; they've run events that mattered.

Another layer: do they ask *why* you've structured it that way? Sometimes they'll spot a bottleneck in your plan that would cause a 90-second dead space or a rushed crew change. That instinct to question and improve is the difference between someone reactive and someone protective.

Experience matters, but not in the way most people measure it. "I've run 50 events" means less than "I've run three events with this exact problem, and here's how I solved it each time." Ask specifically about complexity they've handled—not just the number of screens or cameras, but the *coordination challenge*. A fashion show with split-second cue timing is different from a conference with multiple breakout rooms. Different from a hybrid event where half your audience is remote. Make sure they've solved *your* type of complexity, not just accumulated years.

One practical filter: do they have a documented tech rider or setup protocol? Not a templated one—one they've evolved through their own projects. That tells you they learn from every run.

What they'll do when your plan meets reality

The technical crew member you want is the one who's already run through the failure scenarios in their head. When you ask "What happens if [X] goes down?" they should have a framework, not a shrug.

Specific: ask them how they'd handle a speaker arriving late and needing to skip their video intro, or a presentation file that arrives corrupted 20 minutes before the session. The quality of their improvisation thinking predicts their usefulness far more than perfect execution of a perfect plan.

Check whether they've worked with your venue before, or a similar one. Venues vary wildly in power supply, network reliability, rigging points, and how much the house team can help or hinder. If they know your space, they've already solved half the unknowns. If not, push them to visit and build a site-specific plan.

During your conversations, listen for how they talk about other crew members and stakeholders. Do they mention coordinating with your event organiser, liaising with the venue, or checking in with your speakers beforehand? Or do they frame the day as them running the tech while everyone else stays out of the way? The first person is a force multiplier; the second is a single point of failure.

Finally, chemistry matters in a way people often skip. You'll be coordinating under pressure. A crew lead who's clear on the radio, who explains decisions without jargon when you ask, and who treats your event like their own is worth the conversation. Spend 15 minutes on a call; you'll feel the difference.

When you're ready to compare candidates with verified credentials and past client reviews, Strove's technical support specialists can help you find someone who's already demonstrated this kind of rigour.