They're students, parents, and people who said yes on a Sunday. The gear shouldn't be the thing standing between them and serving well. So we build the surface they actually touch - and hide everything else.They're students, parents, and whoever said yes. Every system we build gets a surface shaped to the person operating it - one job per screen, one object per hand - and the complexity stays in the platform, not on their glass.
The youth booth is a dim room and a teenager who has fifteen minutes of training. So the control surface is a game controller - and every button fires the exact same command the broadcast switcher fires.
Every action on the pad can be individually switched off. So you don't hand a fifteen-year-old a scaled-down toy and hope - you hand them a real surface where the dangerous buttons simply do not exist. Turn them on as they grow into it.
The layout lives in a config, not in code, so re-mapping the booth for a new volunteer takes a minute and no deploy. And because the pad fires the same commands as the main switcher, nothing about the youth service is a lesser, parallel rig - it's the same system, with a friendlier handle.
Not one dashboard that shows everything to everyone. Each volunteer gets a screen built for their job - and every screen moves together the instant a cue fires. What's now, what's next, what's coming.
A watcher reads the multiview a few times a second and tells each operator, on the phone already in their hand, whether their shot is in focus, not sure, or not in focus - and whether they're on air. It's the question every camera volunteer has been unable to answer until they saw the recording on Monday.
Tools that watch volunteers can turn into tools that grade volunteers. These are the lines we hold, and they're built into the software - not the policy.
We take on a small number of churches at a time, and build this with you - not ship you a login.