STARTING WITH AI · 2 MIN READ
Your church staff does not need to be excited about AI
Build a useful conversation around actual work rather than pressure to adopt a new tool.
Curiosity is not a requirement
Some people enjoy trying new tools. Others would rather finish the work they already know how to do. A team can contain both without anyone being resistant or reckless.
Leading an AI conversation well means making room for those differences. Enthusiasm about the technology is not a measure of commitment to the mission.
Ask about the work
A person who is uninterested in AI may have a very clear description of the administrative task that consumes their week. That is a better starting point than a demonstration of everything a tool can generate.
The problem gives the conversation a purpose. Would a prepared first draft help? Would organizing approved information remove a repetitive step? Would the review cost outweigh the benefit?
Let concerns improve the experiment
Questions about privacy, tone, accuracy, and relationships can make a proposed workflow stronger. They help you spot where the plan needs clearer limits. Dismissing those questions as fear can damage trust before the tool has done any work.
A limited experiment gives the team something concrete to assess together. People can evaluate the result without signing up for a sweeping claim about the future.
Let the relief speak for itself
If a workflow makes an ordinary task easier and the person remains in control, interest may follow. If it does not, the team should be free to say so.
A colleague who never gets excited about AI may still appreciate finishing the weekly announcement a little earlier. That is enough.
Topics: church AI adoption · church staff leadership · AI for ministry teams