Every few years a new technology shows up promising to fix whatever a church or school has been quietly struggling with. Right now it’s artificial intelligence. A few years ago it was the all-in-one church management platform. Before that, the learning management system, the redesigned website, the parent app that was finally going to make communication painless. Each one helped at the margins. Each one also left the deeper problem about where it started. 

That pattern is worth paying attention to, because it tells you something the sales pitch never will. A tool can only carry work that someone has already thought through. It can speed up a clear process and make a muddled one faster and more confusing. It cannot supply judgment a leadership team hasn’t formed, and it cannot remember things the institution never bothered to write down. 

So when a church or a Christian school starts asking “what should we use,” it has usually skipped a few questions that come first. Not because those earlier questions are more spiritual or more sophisticated, but because the answers to them are what any tool actually runs on. 

There are six of these questions, and they build on each other. The order matters more than the list. 

1. Foundational Clarity: Do We Know Who We Are and What God Has Called Us to Do? 

Start with the obvious one that almost nobody finishes: do we actually know what we are and what we’re for?

I don’t mean the mission statement on the website. Most churches and schools have one of those, and most of them are fine, and most of them are doing very little work day to day. Clarity is the larger thing underneath the statement — the convictions, the doctrine, the philosophy of ministry or education, the sense of what is non-negotiable and what is merely current. It’s the difference between an institution that can explain why it does what it does and one that mostly knows that it does it. 

A church needs to be clear, in a way it can say out loud, about the gospel, the authority of Scripture, what membership means, what discipleship looks like in practice, who shepherds whom, and what it will not hand off to anyone or anything. A school needs the same kind of clarity about its view of the world, what a formed graduate looks like, how it partners with parents instead of merely informing them, and what it believes Christian education is even supposed to accomplish that a good secular school couldn’t. 

When that clarity is thin, the symptoms are predictable. Programs accumulate without anyone able to say how they fit. Curriculum gets adopted because it was on sale at the conference. A school adds an honors track or a church adds a midweek service, and three years later no one can quite reconstruct why, only that removing it would upset someone. Activity keeps rising. It just stops adding up to anything. 

The cure is rarely doing more. It’s usually understanding, more honestly than is comfortable, what you’re already responsible for. What do we believe? What are we here to protect? What kind of people are we trying to help form? What would still matter if the culture around us shifted hard? An institution that can answer those questions can evaluate a new opportunity in about five minutes. It can say yes with some conviction and no without a guilty conscience. An institution that can’t will treat every shiny option as a referendum on its own identity, because in a sense it is. 

This is the layer everything else sits on. It’s also the one that gets skipped most often, because it produces no deliverable. There’s nothing to install and nothing to announce. There’s only the slow, unglamorous work of a leadership team getting honest about what it actually believes and writing it down where the next leadership team can find it. 

2. Institutional Knowledge: Are We Preserving the Wisdom God Has Already Given?

Which brings up the second thing, and it’s the one I’d guess most institutions underestimate by the widest margin: you already know far more than you’ve kept. 

Think about everything a church has learned in twenty years. How to fold in a new family. Which benevolence requests tend to be genuine and which follow a familiar script. What works in the nursery and what burns volunteers out by March. How a particular kind of conflict tends to unfold and what defused it last time. A school carries the same kind of accumulated sense — how to handle the parent who emails at eleven at night, which accreditation evidence the visiting team actually wants, what a struggling reader in third grade needs before anyone reaches for a label. 

Now ask where any of that lives. 

Some of it is written down, in handbooks and minutes nobody reopens. A great deal more lives in one person’s head. The longtime administrator who just knows how things are done. The volunteer who’s run a ministry so quietly for fifteen years that the church has frankly forgotten it requires running at all. The pastor whose counseling wisdom exists entirely in his memory and his prayer life and nowhere else. 

That arrangement works beautifully right up until it doesn’t. The adminis‐ trator retires. The pastor takes a call elsewhere. The volunteer’s health gives out. And the institution discovers it has lost not just a pair of hands but a decade of judgment, and that the people now responsible are starting over with a confidence they have no right to. 

Scripture is unusually insistent on this point, and it’s striking how operational the insistence is. Israel is told, over and over, to remember; to rehearse what God did, to teach it to children who weren’t there, to build reminders into the calendar precisely because people forget. Paul tells Timothy to take what he received and entrust it to faithful people who can teach others in turn. The assumption running underneath is that wis‐ dom is fragile and gets lost on purpose unless someone deliberately hands it down. 

Preserving what an institution has learned isn’t an administrative nicety, then. It’s a way of refusing to make every new generation of leaders rediscover from scratch things that were paid for in real mistakes. The goal isn’t a bigger archive. It’s continuity, so the next set of leaders inherits something instead of starting from zero with the breezy confidence of people who assume the story began when they walked in. Though an inheritance nobody can find, read, or make sense of is barely an inheritance at all. 

3. Shared Communication: Can Our Convictions and Knowledge Travel Clearly Through the Whole Community?

And that’s the catch with communication, the third item on the list and the one leaders tend to file under housekeeping: it’s what decides whether anything you’ve clarified or carefully preserved ever lands on the people it was meant for. Most places treat it as the step that comes after the real work. The decision gets made, and then someone writes the announcement. The policy gets finalized, and then the note goes home. 

But communication isn’t the loading dock where finished decisions get shipped out. It’s one of the main ways an institution’s identity actually travels — the medium through which trust, expectations, and conviction either reach people or quietly fail to. 

Here’s the test. A church can have a genuinely thoughtful philosophy of discipleship, worked out over years. But if the ministry leaders each describe it a little differently, and parents have never heard it in plain language, and a new volunteer couldn’t repeat it to save his life, then the philosophy isn’t shaping the church much. It’s shaping the leadership meeting. A school can hold a serious vision for forming students under Christ and still have that vision trapped in the language of the administration, intact and admirable and almost entirely internal. 

What fills the gap, when communication is thin, is assumption, and people assume the worst at no extra charge. Parents decide the school doesn’t care. Members decide leadership is hiding something. Volunteers conclude they’re on their own, which, functionally, they are. Almost none of this is malice. It’s just what human beings do with silence. 

Clear communication mostly works by lowering the number of things people have to guess about. And it covers far more ground than the bul‐ letin: handbooks, onboarding, the parent packet, the volunteer training, the language leaders reach for when someone asks a hard question in the parking lot. 

None of this requires sounding like a corporation, and it shouldn’t. The goal is to be truthful, warm, and plain, and to make wisdom easy to get at instead of burying it under language built mainly to sound impressive. Words get this much attention because people do. But saying a thing clearly, even saying it well, is not the same as the thing actually getting done, and the distance between those two is where most good intentions quietly go to die. 

4. Faithful Workflow: Does the Work Move Responsibly Through People and Processes?

That distance has a name, more or less. It’s the fourth job, the one nobody actually calls a job. Every church and school already runs on workflows whether or not anyone has ever said the word out loud, and the only real question is whether they’ve been thought about or are just limping along on habit and goodwill. 

A workflow is nothing fancier than the path a piece of work takes from “this needs to happen” to “this happened and somebody knows it did.” How does a first-time visitor actually get followed up with, not in theory, but in fact? How does a prayer request turn into pastoral care rather than evaporating after the service? How does a child-safety concern get raised, routed, and resolved? How does a struggling student get help before the failing grade, not after? How does a board’s decision become something that’s true on a Tuesday? 

When those paths are undefined, the work doesn’t stop. It just relocates into people’s heads, which is a terrible place to store it. Staff become bottlenecks because they’re the only ones who know the sequence. Two volunteers do the same task and a third assumes someone else has it. Follow-up depends on whoever happens to remember, and memory under load is not reliable. Families experience all of this as inconsistency, and they’re not wrong to. 

Acts 6 is the unglamorous proof text here, and it’s better than its reputa‐ tion. A real problem surfaces — some widows are being overlooked in the daily distribution. The apostles don’t spiritualize the complaint or scold anyone for caring about logistics. They build structure so the need gets met and the ministry of the Word can continue. The structure served the ministry. That’s the entire point. Good process is not the enemy of spiritu‐ al work; bad process is, because it quietly consumes the people doing the spiritual work. 

Which is the line worth keeping: bad systems exhaust good people. Be‐ fore you decide a recurring frustration is a character problem, ask wheth‐ er faithful people are simply trying to work inside a process nobody ever clarified. Usually they are. And only once that process exists — once the path is actually drawn on paper — does it make any sense to go looking for something to carry it. 

5. Supporting Tools: Are Our Systems and Platforms Serving the Work Rather Than Shaping It?

Notice how far down the list that lands. A tool is the thing you reach for to carry a process, which is exactly why it shows up this late — and why reaching for it first is the single most common mistake in the building. By tools I mean the ordinary ones: the church management system, the SIS, the website, the giving platform, the file storage, the dozen apps that have quietly piled up over the years. 

These genuinely help. A good tool reduces repeated effort, keeps informa‐ tion from walking out the door, and makes coordination less dependent on any one person’s attention. None of that is in dispute. 

But notice that everything a tool can do well presupposes the four layers underneath it. It can support a clear process and only multiply a confused one. And most institutions I’ve seen don’t actually have a tool shortage. They have the opposite problem: one system for giving, another for at‐ tendance, a third for communication, a fourth for documents, a fifth that someone set up in 2019 and no longer fully understands. The grades are over here, the curriculum is over there, the accreditation evidence is in a shared drive whose folder logic died with the last administrator. Adding a sixth tool to that environment doesn’t reduce confusion. It charges a subscription for more of it. 

So the useful question was never “what’s the newest platform” or “which one has the most features.” It’s narrower and more boring: what tool best serves the work we’ve actually defined, with the least friction and the clearest sense of who owns it? A tool that answers that earns its place. A tool that creates new busywork, hides information, or pulls attention off people and onto its own dashboards is a net loss no matter how good the demo looked. 

Tools make excellent servants. They make ruinous masters, and they’re always quietly applying for the promotion. 

6. AI-Native Maturity: Can We Use and Shape AI Without Surrendering Wisdom?

The sixth layer is AI-native maturity.

This is different from ordinary technology use. Churches and Christian schools already use many digital tools: calendars, spreadsheets, church management systems, school information systems, websites, livestream tools, curriculum platforms, file storage, and communication apps. Most of these tools store, send, organize, or display information.

AI does something more active. It can generate language, summarize material, suggest plans, draft communication, classify problems, answer questions, assist research, and even help create small custom tools. That makes it useful. It also makes it dangerous when it is not bounded.

The first step of AI-native maturity is learning to use powerful agentic tools well. This includes tools like ChatGPT, Claude, Gemini, sermon-support tools, AI features in Bible software, school-focused AI tools, church-focused platforms, and other systems that can assist with writing, planning, teaching, administration, and follow-through. These tools can help. A pastor may use AI to organize non-confidential notes, draft discussion questions, or refine a communication piece. A school administrator may use it to organize policy material, prepare parent communication, or structure accreditation evidence. A teacher may use it to create review activities or think through ways to explain a difficult concept. But these tools must be governed.

Churches and Christian schools should define what AI may be used for, what requires review, what should be prohibited, and what information must never be entered into AI systems. They must decide who checks accuracy, theology, tone, context, privacy, and appropriateness. Without those boundaries, AI can quietly lead a church or school in the wrong direction. It can produce confident errors. It can flatten pastoral care into generic language. It can weaken teacher judgment. It can make communication faster while making it less personal, less careful, and less trustworthy.

The second step of AI-native maturity is learning to create small custom tools that fit the actual work of the ministry or school.

For years, churches and schools have had to adapt their work to whatever software already existed. A church bought a management system and shaped its processes around that system. A school bought a learning platform and adjusted its work to match the platform. Ministries filled the gaps with spreadsheets, forms, emails, and workarounds. AI changes what may be possible.

A ministry leader who cannot code may still be able to describe a workflow clearly. A teacher may be able to explain the parent-support tool she needs. A principal may be able to describe how accreditation evidence should be collected. A pastor may be able to explain how meeting follow-up, ministry planning, or care tracking should work.

That means churches and schools can begin asking a better question: not merely, “Which available tool is closest to what we need?” but, “What tool would actually fit the work God has given us?” This does not mean every church or school should become a software company. Custom tools still require security, testing, privacy, oversight, and maintenance. But it does mean the distance between ministry knowledge and practical implementation is shrinking.

A church may be able to create a focused tool for volunteer onboarding, room setup, ministry planning, pastoral follow-up, resource requests, or institutional memory. A school may be able to create one for parent communication, faculty development, accreditation readiness, student support, curriculum mapping, or board reporting. The goal is not novelty. The goal is fit.

AI-native maturity means churches and Christian schools learn both how to use powerful AI tools responsibly and how to shape small tools around their actual calling. They do not force ministry and education to fit technology unnecessarily. They make technology serve the work.

But this must happen in the right order. Clarity still comes first. Knowledge still matters. Communication still carries trust. Workflow still needs to be understood. Ordinary tools still need to be chosen carefully. Only then should AI be used or custom tools be built. AI may help churches and schools do more. Used wisely, it may help them do more of the right things, in better ways, with greater clarity and care. But it must never replace the people God has called to shepherd, teach, lead, disciple, govern, parent, serve, and love.
 

The Order Is the Argument 

The future these institutions are walking into is genuinely complicated. Families are stretched thinner. Attention is more fractured. The administrative demands keep climbing, and the technology keeps arriving faster than anyone can sensibly evaluate it. But none of that has touched the things that were true before any of it. The church still belongs to Christ. Christian education still answers to God’s Word. Children still need to be formed and not merely informed.  Parents still need a partner rather than a vendor. The people doing this work still need wisdom that no amount of processing power can manufacture for them. 

So the order holds, and the order is really the whole argument. Clarity before activity. Memory before reinvention. Communication before the vacuum fills itself with rumor. Workflow before everyone burns out carrying it in their heads. Tools after all of that, and AI after a community has grown up enough to handle it. The tools will keep changing; they always have. The work underneath them won’t. An institution that knows who it is, holds onto what it has learned, says things plainly, moves work through clear paths, picks its tools with some discipline, and uses AI like an adult will be in far better shape for whatever comes next. 

Not because any of that machinery made it faithful. Machinery can’t. But because faithful people will have done the harder, earlier work of making sure every tool serves the thing it was supposed to serve, and never the other way around.