Before I Arrive:
We review your audio systems, PA deployment, and reference mixes. We discuss your biggest frustrations and prepare a plan for your room and team.
Day 1: Systems & Programming
Morning: Walk through your current setup with your engineer - listening and observation.
Afternoon: We start rebuilding systems together. Your engineer speaks into programming decisions.
Evening: Core Team Dinner.
Day 2: Training
Morning: 1:1 skills development with your engineer.
Afternoon: Volunteer equipping.
Evening: Rehearsal, Worship Night, or other Team Building event.
After I Leave:
14-day and 30-day check-ins to make sure changes stick.
Skills Accelerator (3-6 Months)
Right for you if:
What happens over 3-6 months:
Mentorship Track (6-12 Months)
Right for you if:
What happens over 6-12 months:
How This Works
Real growth starts with truth—and truth is received best when it comes from the right messenger.
Engineers are often confident, opinionated, and highly self-directed. That's not a flaw—it's part of the role. But it also means growth stalls when feedback feels theoretical, outdated, or disconnected from real experience.
My approach is built around three principles.
1. Discernment before development.
Part of my responsibility is discerning timing: whether an engineer is in a place where coaching will actually produce momentum. Growth requires openness, curiosity, and a willingness to engage—not perfection, just readiness.
The result: You invest at the right time, and we focus effort where real growth is possible.
Once readiness is clear, the next question is: will they actually receive the coaching?
2. Kind truth grounded in experience.
My coaching comes from working at the highest levels. I've led teams across multiple campuses at a church of 30,000 weekly attendees. I've launched television programs and online church experiences. I currently mix in arenas and broadcast events where the pressure to deliver is constant.
This matters because engineers don't receive abstract advice well—they respect perspectives earned in the trenches.
The result: Defensiveness drops, curiosity returns, and growth can actually begin.
And once they're open to feedback, the final question is: are we developing the right things?
3. Identity before technique.
Audio education is widely available. What's rare is helping an engineer understand who they are as a mixer at their current stage—and how that aligns with what your church actually needs.
I help them reconcile:
The result: Engineers mix with confidence, restraint, and consistency—serving your church without misplaced ego.
Midweek coaching delivers better results. On Sundays, your engineer is in execution mode—focused on getting through the service, not learning. We can't stop, pivot, or refine in real-time.
Midweek, during rehearsals, we can:
The result: Better decisions, stronger confidence, and fewer Sunday surprises.
There's a personal reason too: After years as the person who was never home on weekends, I committed to being at my own church on Sundays with my family when I'm not touring. That boundary limits my capacity—but it ensures I show up fully invested in the ones I take on.
For longer engagements (Skills Accelerator or Mentorship Tracks), I'm on-site for at least one Sunday when it meaningfully serves the team—to align expectations, observe your weekend experience, and anchor long-term development.
We use cookies to analyze website traffic and optimize your website experience. By accepting our use of cookies, your data will be aggregated with all other user data.