Ministry by Design stands on its own. You don't need to read a business book or adopt a corporate framework to use it. But three bodies of thought have shaped how we think about the challenges churches face when they try to move from reactive to intentional. Understanding the root principles behind each one will make you more effective at implementing Ministry by Design, whether you adopt these frameworks formally or not.
Your church may already have its own way of handling organizational structure, planning rhythms, and growth management. That's fine. The point isn't to prescribe a specific business system. It's to surface the underlying principles so you can recognize where your current approach is strong and where it might have gaps that will undermine your ministry design work.
Michael Gerber's The E-Myth Revisited identified the pattern we explore in The Missing Role: most organizations are led by visionaries, staffed by doers, and almost entirely missing the systems-builder. Gerber called these three roles the Entrepreneur, the Technician, and the Manager. His central argument is that without the Manager, organizations hit a ceiling they can't break through, no matter how talented or committed the team is.
Why it matters for Ministry by Design: Ministry by Design is fundamentally a Manager's framework. It asks churches to define systems, document standards, and sequence priorities. That work requires Manager capacity on staff. The E-Myth helps leaders see why that capacity isn't optional and why it needs real authority, not just a title.
The deeper principle: your church may not have a process problem. It may have a resource problem. And it may not be that you don't have enough resources, but that you don't have the right blend.
Gino Wickman built the Entrepreneurial Operating System (EOS) directly on Gerber's foundation. Where Gerber diagnosed the problem, Wickman built the prescription: a complete operating system covering vision, people, data, issues, process, and traction.
The most distinctive feature of EOS is the Visionary/Integrator pairing at the top of the organization. This is Gerber's Entrepreneur/Manager distinction made into a structural requirement. Wickman is emphatic that these two roles are co-equal. The Integrator isn't support staff. They're the counterweight that keeps the organization from spinning on vision without ever landing.
Why it matters for Ministry by Design: EOS answers "how do we run this organization?" Ministry by Design answers "what should this organization be building?" A church running EOS without Ministry by Design has a great engine with no blueprint. A church running Ministry by Design without EOS (or something like it) has a great blueprint with no engine to drive implementation.
The deeper principle: even if your church never formally adopts EOS, the underlying concepts matter. Does your leadership team have a consistent meeting rhythm? Are your quarterly priorities clearly defined and tracked? Does every major function have a single owner? If not, your ministry design work is at risk of stalling. For a deeper look at how EOS works and connects to Ministry by Design, see EOS: What It Is and Why It Matters.
Reid Hoffman's Blitzscaling provides the necessary counterbalance to the E-Myth and EOS arguments. His Marines/Army/Police metaphor (explored in The Missing Role) warns that over-systematizing is just as dangerous as under-systematizing. When the Managers take over completely, process becomes the point. Innovation dies. The very thing that made the church alive gets suffocated.
Why it matters for Ministry by Design: The Application Framework is built with this tension in mind. It doesn't ask churches to systematize everything at once. It asks them to address the lowest broken system first and build from there. That sequencing protects churches from the over-systematization trap while still driving toward health and intentionality. For a practical look at how the right blend of roles shifts as a church grows, see The Role Blend.
From the E-Myth: know your team's composition. Make sure the Manager role exists and has authority. Without it, your ministry systems will be designed and never maintained.
From EOS: build an execution rhythm. Have clear priorities, consistent accountability, and someone who owns the integration of it all. Without it, your ministry systems will be maintained for a season and then quietly abandoned.
From Blitzscaling: resist the urge to over-systematize. Build structure to serve people, not to control them. Without that restraint, your ministry systems will become bureaucracy, and your best people will leave.
Ministry by Design provides the blueprint. These principles help you build a foundation strong enough to support it.