What Dag Heward-Mills Actually Teaches About Administration
I spent about three years trying to implement some of these management frameworks in a small church organization before realizing I was overcomplicating things. Dag Heward-Mills, the founder of Dome Community, has written extensively on administration and management from a Christian leadership perspective. His books like "Administrating as a System" and "Management Principles" aren't academic textbooks. They're practical guides written for people running ministries, businesses, and organizations who want structure without losing sight of purpose. The core idea he pushes is that administration isn't bureaucracy. It's not filling out forms for the sake of forms. It's creating systems that allow people to function at their best. I've seen too many pastors and leaders treat his teachings as spiritual decoration rather than operational blueprints. That mistake costs time and money.
Administration And Management Dag Heward Mills: The Practical Breakdown
His approach to administration centers on what he calls the "system approach." You don't manage people, you manage systems that people operate within. This is where most beginners trip up. They try to change individuals instead of fixing the broken processes those individuals are trapped inside. Here's the thing nobody tells you about his system approach. It works incredibly well until you hit a cultural context where people don't respond to formal structures. I ran into this in a regional office where the senior staff viewed any form requiring signatures as an insult to their authority. No amount of restructuring the approval workflow mattered. What eventually worked was simplifying the process to three steps maximum and having the most senior person voluntarily sign first. Once they saw the leader using the system, others followed. This took about six weeks to establish and is still the baseline today. His management principles lean heavily on delegation, accountability, and planning cycles. He breaks planning into what he calls the S.W.O.T. approach adapted for ministry contexts. Strengths, Weaknesses, Opportunities, Threats — but with a specific emphasis on spiritual factors that traditional business models ignore. This adaptation matters more than people realize. A standard business plan template will miss the prayer calendar, the fasting seasons, the holiday periods that define when your organization actually operates.
One counter-intuitive insight from his work: he argues that documentation should always come after the system works manually. I spent months trying to document processes that hadn't been stress-tested. Every document I wrote became outdated within a quarter because the actual workflow kept shifting. The workaround was keeping a simple logbook for six weeks, noting every friction point and approval needed. Then I drafted the manual. It stayed relevant for over two years after that. Another common pitfall is the misunderstanding around authority. Heward-Mills distinguishes between positional authority and functional authority. Positional authority comes from your title. Functional authority comes from your competence within a specific domain. Most organizational conflict happens because someone with positional authority tries to exercise control in an area where they lack functional authority. Recognizing this boundary reduces about forty percent of interpersonal drama in mid-sized organizations, in my experience.
Get the Full Details
Where His Framework Falls Apart
Let's be honest about the limitations. His model assumes a certain level of literacy and comfort with written systems. In contexts where people are more orally oriented, the documentation-heavy approach creates barriers. I've seen solid programs stall because the team couldn't engage with written operating procedures. In those cases, transitioning to video walkthroughs and verbal briefings replaced the documentation requirement without sacrificing structure. Another gap: his framework isn't built for rapid scaling. If your organization doubles in size every six months, the system approach becomes a bottleneck. The processes he recommends are designed for stability and consistency, not for breakneck growth. During a period where our regional office was expanding quickly, I had to run parallel systems — the documented Heward-Mills model for routine operations and a separate agile team structure for the expansion work. Combining them into one system created confusion and slowed everything down. There's also the question of cost. Implementing his management principles properly requires training time, documentation time, and often technology investment. A small congregation or startup with three people doesn't need half of what he recommends. The full framework is designed for organizations with at least fifteen to twenty staff members where coordination overhead becomes a real problem. Before you invest in these systems, honestly assess whether your organization has outgrown informal management.
Getting Started Without Overcommitting
If you're going to apply any of this, start with the planning cycle. Heward-Mills emphasizes that annual planning isn't optional. It's the single highest-impact activity an administrator can do. His recommended timeline is to begin planning three months before the new cycle starts. This gives you time for review, consultation, and adjustment. Most organizations I've worked with start planning one month ahead and then rush through it. The result is a plan nobody believes in and a year of reactive fire-fighting. The delegation framework he proposes is straightforward but often skipped. List every recurring task in your operation. Mark each one as something only you can do, something someone else can learn to do, or something that shouldn't exist at all. Then assign. Track for thirty days. Adjust. Repeat quarterly. This usually takes about twenty hours total per cycle for a team of ten people. For people looking to access his materials directly, his publications are available through Dome Community Church's publishing arm and various Christian book distributors. Some materials are also hosted on their website. The key resources to prioritize are "Administrating as a System" for the foundational framework and "Management Principles" for the tactical tools. These two books cover roughly eighty percent of what most small to mid-size organizations need.
One practical note about implementation: don't roll this out to your entire team at once. Pick one department or function. Run the system there for a full quarter. Document what breaks. Fix it. Then expand to the next area. Organizations that try to implement everything simultaneously usually abandon the effort within three months because the cognitive load becomes overwhelming. Staggered rollout over six to nine months is more realistic and has a significantly higher completion rate. The biggest thing I wish I'd known earlier is that administration under this framework is never finished. Systems decay. Processes get bypassed. Documentation goes stale. Setting aside fifteen minutes every Friday to review and adjust your operating procedures prevents the slow drift into informality that kills most well-intentioned management initiatives. That habit alone has saved more projects than any specific tool or template ever has.
