Lecture 10-2: A Planning Cycle, and What Secular Frameworks Can and Cannot Do

Proverbs 16:9 (World English Bible)

The three moving parts of a planning cycle

A planning cycle, stripped to its administrative bones, has three parts. First, goals: specific, time-bound statements of what the congregation intends to accomplish, derived from the vision statement discussed in Lecture 10-1 rather than invented independently of it — a goal that does not trace back to the stated vision is either evidence the vision was incomplete or evidence the goal does not actually belong in this cycle. Second, resource allocation: money, staff time, volunteer hours, and facility use committed against those goals in the budget and the calendar, because a goal without allocated resources is a wish, not a plan (Chapter 6 covers the budgeting side of this in detail). Third, a review point: a specific, calendared moment — not "sometime later" — at which leadership asks plainly whether the goal was met, partially met, or missed, and why. A cycle missing any of the three degrades into something else: goals without resources become slogans, resources without goals become last year's budget copied forward, and a cycle without review becomes a plan nobody is ever accountable to.

A named framework: SWOT analysis

SWOT analysis — an assessment of an organization's internal Strengths and Weaknesses alongside external Opportunities and Threats — is probably the most widely used planning tool in existence, secular or religious, precisely because it is simple enough to run in an afternoon and concrete enough to produce something usable. A congregation might identify, as strengths, a strong volunteer base in children's ministry and a debt-free building; as weaknesses, an aging membership and no functioning young-adult ministry; as opportunities, a new housing development within walking distance of the building; and as threats, a declining number of families with children in the surrounding area generally. Laid side by side, these four categories can surface a goal that would not have been obvious from any one category alone — for instance, that the new housing development (an opportunity) is exactly the population that could offset the aging-membership weakness, if a specific outreach goal is set and resourced toward it.

The tool's real limitation is not that it produces bad answers but that it produces only as good an answer as the honesty of the people filling it in. A SWOT exercise run by a leadership team unwilling to name real weaknesses (because naming a weakness can feel like criticizing whoever is currently responsible for it) produces a document that flatters rather than informs. This is not a defect unique to churches — the same failure occurs in any organization with strong interpersonal loyalty among its leaders — but it is worth naming because a congregation's culture of loyalty and grace, rightly prized in most contexts, can specifically undermine the honesty a SWOT analysis requires to be worth the time spent on it.

A church-specific alternative: Kennon Callahan's twelve keys

Kennon Callahan's widely used framework, first published as Twelve Keys to an Effective Church, differs from SWOT in an important structural way: it was built from the outset for congregations rather than adapted afterward from general business use. Callahan's twelve keys span both what he calls relational characteristics (a specific, concrete missional objective; effective pastoral and lay visitation; corporate, dynamic worship; significant relational groups; strong leadership resources; streamlined structure and solid, participatory decision-making) and functional characteristics (adequate parking, accessibility, and adequate space and facilities, among others). What is distinctive is not any single key but the framework's starting assumption: that a congregation's effectiveness is a property of specific, nameable congregational practices and characteristics, evaluated against what actually works across many congregations Callahan studied, rather than a property inferred from a generic business-planning template applied to a church because no church-specific one was at hand.

The practical difference this makes: a congregation using Callahan's framework does not first ask "what would a well-run business do here?" and then adapt the answer. It asks a question already shaped for congregational life — for instance, whether the church has "a specific, concrete missional objective" the congregation could actually state, rather than a generic mission statement of the kind critiqued in Lecture 10-1. This does not make Callahan's framework theologically neutral or beyond critique — a framework built from observing which congregational characteristics correlate with growth or vitality is still, at bottom, an empirical and largely sociological tool, not a theological one, and a congregation should not treat "this key correlates with effectiveness in Callahan's data" as equivalent to "this key is what Scripture actually requires of a healthy church." But it starts closer to the actual subject than a framework built for any voluntary organization whatsoever and retrofitted afterward.

What transfers, and what does not

This is a point where readers will not agree, and the disagreement runs deeper than a simple "use some of it, not all of it" compromise, because thoughtful practitioners actually differ on where the line falls. One position, represented by administratively minded evangelical writers such as Aubrey Malphurs, holds that a rigorous planning process — closely resembling secular strategic management in its discipline and tools, distinguished from a secular process chiefly by being saturated with prayer and Scripture at every stage rather than by using fundamentally different tools — is not merely permissible but a form of stewardship a congregation owes its mission; on this view, resisting disciplined planning in the name of "trusting God" can itself be a failure to steward the resources and opportunities God has actually given. A different position, associated with theologians and practitioners skeptical of importing corporate management culture into the church (a concern with real representatives across both mainline and evangelical traditions, and echoed in different terms by writers wary of measuring congregational faithfulness by metrics borrowed from institutions with fundamentally different purposes), holds that strategic-planning language imports assumptions a church should resist even when the specific tools seem harmless — assumptions that an organization's future is primarily a function of correct technique, that faithfulness and effectiveness are the same thing, and that a congregation is fundamentally a voluntary association optimizing toward a goal it authored for itself, when in fact its goals were given to it and its outcomes were never fully its own to produce (compare Lecture 1-4's treatment of the same tension with Peter Drucker specifically, and its administrative rather than existential form).

This lecture does not resolve that disagreement, because it is not a disagreement about facts a lecture could settle; it is a disagreement about how much administrative discipline a congregation can adopt before the discipline starts quietly reshaping what the congregation thinks it is for. What can be said without taking a side in that larger dispute is narrower and more useful: whatever framework a congregation uses, and whatever position its leadership holds on how much of it to adopt, Proverbs 16:9 sets a limit no framework should be allowed to erase. "A man's heart plans his course, but Yahweh directs his steps" does not counsel against planning — the verse assumes planning happens and does not condemn it. It counsels against a planning process that forgets whose steps are actually being directed. A SWOT analysis or a twelve-keys assessment produces a proposal, stated with appropriate confidence and pursued with real diligence; it does not produce a guarantee, and a leadership team that presents its plan to a congregation as though the plan itself secures the outcome has claimed something the tool cannot deliver and Scripture will not underwrite.