You leave for a weekend and get a text Saturday morning. A student can't find the cables. Another doesn't know which settings to use. A third is asking about the call time, even though you sent it on Tuesday.

You answer all of them because there's nowhere else to look.

That's not a student problem. That's a system problem.

Watch Week 3 of the Striv Summer Series

What "Student-Led" Actually Means

Student-led doesn't mean students doing tasks when you tell them to.

It means students who own their roles. Who know what "ready" looks like before you walk in the room. Who can train the next student without calling you.

That's a different thing entirely. And most programs never get there, not because the students aren't capable, but because the system wasn't built to get them there.

Why I Care About This

When I left my high school program for college, I took all the knowledge with me.

Every workflow, every setting, every system I'd built as a student in our broadcast program. None of it was documented. None of it was transferable. And when my teacher needed to figure out how to run the setup the next fall, she called me.

I didn't mean to hoard it. I just never built anything that outlasted me.

That's the moment I knew I didn't want that to happen to anyone else's program.

Five Areas Where Programs Break

The Week 3 session went long because this topic is deep. Here are the five areas we covered.

Recruiting and onboarding. Attitude over skill, every time. A student who cares and can't do anything yet is fixable. A skilled student who doesn't care will drag your program down. Onboarding sets the expectation from day one. If you skip it, you pay for it all year.

Role assignment. There's a difference between a student who completes a task and a student who owns a role. One waits to be told what to do. The other figures it out. Getting students to role ownership requires them to understand the why behind what they're doing, not just the what.

SOPs and documentation. Standard operating procedures aren't for the student who already knows how to do it. They're for the next student. Write them that way. And build in a 90-day review, because a document that reflects last year's setup trains students to do it wrong.

Scheduling and conflict. No-shows happen. Drama happens. The calendar system that survives this has a parent-facing layer and a student leader who catches problems before they reach you. If you're the one noticing when someone didn't show, you're still the system.

Recognition and ownership. Students who feel seen stay. Students who feel like cogs don't. Recognition isn't just praise. It's building a culture where students understand their role matters to the show, to the team, and to the audience.

The One Idea Under All Five

A teacher-run program breaks the moment the teacher isn't there.

That's the thing. Every one of those five areas is just a different angle on the same problem. If students don't own the process, you're the process. And that doesn't scale, doesn't survive turnover, and doesn't build the kind of program that outlasts you.

Your Challenge

Pick one task you currently own.

Hand it to a student before the fall. Tell them what done looks like, give them the resources to figure it out, then get out of the way.