The Missing Role makes the case that most churches are heavy on Entrepreneurs (visionaries) and Technicians (doers) but almost entirely missing the Manager (systems-builder). This page takes that observation a step further: the right blend of those three roles isn't fixed. It shifts as a church grows, and getting the timing wrong in either direction causes real damage.
The church is mostly Marines. The founder is running on vision, relationships, and adrenaline. Staff (if any) are generalists doing whatever needs doing. Systems are informal, held together by the founder's personal memory and relational bandwidth.
Ideal blend: 70-80% Entrepreneur/Technician energy, 20-30% Manager. At this stage, the "Manager" might not even be a separate person. It might be one staff member who naturally thinks in systems, or even the founder wearing that hat for a few hours a week. The danger here isn't lack of systems. It's premature systems. Over-systematizing a church plant kills the very energy that makes it grow. You're taking the beach. Move fast.
Ministry by Design application: Light touch. Focus on getting the First Contact and Connection systems roughly defined so people don't fall through the cracks. Don't worry about operational standards yet. Just make sure someone is tracking guests and someone is following up.
This is where most churches stall, and it's almost always a Manager problem. The founder has hit the ceiling of personal capacity. They can no longer hold every relationship, remember every guest, and drive every initiative through sheer will. The church needs systems to carry what the pastor used to carry personally.
But here's the pattern: the founder hires more Technicians (another worship leader, a youth pastor, a groups director) and more Entrepreneurs (a creative director, a campus pastor with big vision). The staff gets bigger but the gap stays the same. Lots of energy, lots of ideas, no systems, no follow-through, no accountability.
Ideal blend: This is where the ratio needs to shift significantly. The church needs at least one dedicated Manager-wired leader, ideally in an executive pastor or operations director role with real authority. Think 50-60% Technician, 20-25% Manager, 15-20% Entrepreneur. The Technician percentage stays high because the ministry work always needs doing. But the Manager capacity needs to be real, funded, and empowered.
Ministry by Design application: Full engagement. This is the phase where the framework has the most impact. Define your Ministry Systems. Start building Operational Standards. Use the Application Framework to sequence what to fix first. The church is big enough to need systems and small enough that implementing them is still manageable.
The critical hire: The person in the Manager seat at this stage needs to be a true systems thinker, not an admin assistant with a bigger title. They need the authority to hold department leads accountable to the systems, push back on the senior pastor's impulse to launch five new things, and say "we're not adding anything until the current systems are healthy." That's an uncomfortable hire for most Entrepreneur-wired pastors, which is exactly why it's the right one.
The church now has multiple layers of leadership. Department leads, campus pastors, volunteer team leaders. The founder is further removed from day-to-day operations. Systems aren't optional anymore; they're the only way information flows and quality stays consistent across a larger organization.
Ideal blend: The Manager function should now be distributed, not just sitting in one person. Every department lead needs some Manager wiring. The central operations/executive team should be heavily Manager-oriented. Think 50% Technician, 30% Manager, 20% Entrepreneur across the whole staff. The Entrepreneur energy concentrates at the top (senior pastor, executive team) while the Manager capacity spreads throughout.
Ministry by Design application: The Operational Standards become critical. When you have 50 group leaders, 20 first-impressions volunteers, and three campuses, consistency depends on shared definitions, clear data practices, and documented processes. The Application Framework helps leadership stay focused on which system needs attention rather than chasing whatever feels urgent this week.
This is where the Blitzscaling caution kicks in. The church has systems. It has process. It has organizational structure. The risk now is becoming a police state, where process exists for its own sake and innovation gets suffocated.
Ideal blend: The organization needs to consciously protect Entrepreneur and Technician energy at this stage. It's easy for a large church to become so Manager-heavy that it loses its ability to take risks, experiment, and respond to the Spirit. The healthiest large churches find ways to create "Marine" spaces within the larger "Army" structure: innovation teams, new ministry incubators, rapid-prototype initiatives that operate with less process overhead.