The Melody & The Machine

Part 1: AI, Jazz and Christian responsibility

This is part one of a two-part reflection. Part two will look more closely at how AI can shape sermons, reports, minutes, and church governance.


In some classic jazz, the tune appears briefly.

A melody is stated. A few bars, perhaps. Enough for you to know where you are. Then the musicians begin to explore. The saxophone wanders. The piano answers. The drums push and tease. The bass holds the room together like a quietly competent church treasurer.

To someone listening casually, it may sound as if the music has wandered away from the tune altogether. But good improvisation is not randomness. It depends on formation, discipline, memory, listening, judgement, and trust. The musicians can only play freely because they know the melody.

That is not a bad way to think about Christian reflection in an age of artificial intelligence.

Much of the Bible works like this too. Scripture introduces themes and returns to them again and again: creation, covenant, exile, wisdom, temple, Spirit, kingdom, new creation. The theme is not simply repeated. It is deepened, stretched, fulfilled, and sometimes turned inside out until we see more clearly what God has been doing all along.

Christian thinking about AI needs that same discipline. We should not chase every shiny new tool as if salvation arrived in a software update. Nor should we retreat into fear whenever the machines start playing unfamiliar notes. We need to keep returning to the melody.

Here is one way to state it:

AI may assist human work, but it must not displace human responsibility.

That is the tune. Everything else is a variation.

The question beneath the question

Most church conversations about AI begin with immediate usefulness.

Can it write the newsletter?
Can it summarise the minutes?
Can it help with the roster?
Can it draft a sermon?
Can it make the annual report sound less like a cry for help wrapped in photocopy paper?

These are real questions. Many churches are running on thin capacity, tired volunteers, and office systems held together by goodwill, prayer, and one person who knows where the password book lives. If AI can reduce drudgery, that matters.

But usefulness is not the deepest question.

The deeper question is this: what kind of people, churches, institutions, and societies are being formed by our use of AI?

That question is slower. It is less glamorous. It does not fit neatly into a product demo. But it is the question the church must learn to ask.

A tool can save time and still train us to be careless. A system can produce polished words and still weaken truthfulness. A chatbot can sound pastoral while knowing nothing of the person receiving the message. A board paper can be summarised neatly while the actual responsibility for discernment remains with the humans around the table.

Efficiency is useful. It is not the highest Christian virtue.

A hundred-year technology

Gina Raimondo, former Governor of Rhode Island and former United States Secretary of Commerce, recently described AI as a “100-year technology” requiring a “100-year response.” Her concern was that a country might win the AI race economically while hollowing itself out socially.

That warning belongs to a particular American policy debate, but the phrase travels well.

If AI is a 100-year technology, the church cannot respond with a 100-day content strategy.

We do not need only tips and tricks. We need formation. We need governance. We need theological imagination. We need care for the vulnerable. We need practices that help communities ask not only “Can we do this?” but “Should we do this?”, “Who might be harmed?”, “Who is responsible?”, and “What kind of witness does this give?”

The church does not need to “win” at AI. It needs to remain recognisably Christian while using it.

That means we should be neither dazzled nor dismissive. AI is not magic. It is not a demon in the server cupboard. It is a powerful set of technologies, built by people, trained on human material, shaped by commercial incentives, and increasingly woven into everyday systems.

Some of this opens into serious ethical and moral argument. Churches, denominations, and agencies will need to work through those questions in time. But we should not wait for the trumpet to sound — or for the committee report to emerge blinking into daylight — before taking personal responsibility. Every user still has choices to make: what we put into these tools, what we accept from them, what we pass on, what we check, and what we sign our name to.

At the most basic level, AI is still a human tool: made by people, used by people, and answerable through people.

Poor use will produce poor results. Sometimes worse than poor. Confident nonsense, fabricated details, privacy breaches, lazy decisions, and pastoral tone-deafness are not imaginary risks. They are the ordinary failure modes of tools used without enough understanding.

Good use, however, can genuinely help. AI can assist with drafting, searching, summarising, planning, translating, brainstorming, and reducing administrative grind. Used carefully, it may give small organisations access to support they could never otherwise afford.

The Christian question is not simply whether AI is good or bad. The better question is whether we are using it wisely, truthfully, and accountably.

Coming in Part 2:

When the Melody Drifts: AI, Sermons, Governance, and Responsibility will look at two places where AI-shaped words can quietly reshape church life: proclamation and governance.


Peter Lane is Principal Consultant at System Design & Communication Services and has over 30 years of experience with Technology systems.    We invite your questions, suggestions and ideas for articles.   These can be submitted either through the editor or by email to dct@dct.org.nz We also operate a website focused on building a community of people interested in improving how we use technology in churches, located at dct.org.nz 

Church + AI: We Want Your Story

We’re building something.

It’s called Church + AI — a guide to using artificial intelligence in faith-based and small-scale contexts.

Not a thinkpiece. Not a hype-fest. Not another ethics lecture (unless your story needs one).

Just something practical. Something grounded. Something that reflects what’s actually happening out there — from the Sunday service to the spreadsheet.

That’s where you come in.

If you’ve used AI in your ministry, community group, or small-but-mighty organisation — we want your story.

What worked?
What didn’t?
What surprised you?
What made you want to throw your laptop out the vestry window?

Stories can be about:

  • Preaching, liturgy or study
  • Rosters, planning or communications
  • Websites, media, or outreach
  • Anything else you tried, whether it succeeded or not

And yes — you don’t have to be a church to contribute.
If your organisation shares the same scale, constraints, or values — we’re listening.

Tell us your tale:

👉 dct.org.nz/church-ai

We’re not looking for polish. Just honesty.
(And maybe a little humour. We know what ministry life is like.)

AI, Automation and the Admin We Can’t Avoid

(aka: Why ChatGPT Can’t Replace the Parish Secretary — Yet)

I recently helped someone use AI to draft a pastoral care roster.

It confidently produced a six-week schedule — nicely formatted, evenly distributed, and even colour-coded.  A small miracle, except for one problem: it assigned duties to three people who’d moved away, one who’d passed away, and one who had, in no uncertain terms, declared themselves done with morning tea forever — and said so loudly enough that even the flower roster flinched.

That’s the problem with clever automation: it’s fast, it’s convincing… and it doesn’t actually know your people.


🤖 “Yes, and here are three ways to make your bad idea better.”

We like the idea that technology will take boring tasks off our plate. And to be fair, it often can. But AI doesn’t say, “Are you sure that’s wise?” If anything, it says, “Yes — and here are three ways to make your bad idea even shinier!”

I’ve had this same tool write notices, suggest announcements, and summarise minutes from meetings I wasn’t in.  Which, as it turns out, is still slightly better than most people manage after actually attending.  But it also generates hymns that rhyme “Holy Ghost” with “vegemite toast,” and thinks the Lay Preachers’ Network meets monthly in Rotorua, led by someone called Cheryl.  So we’re not quite ready to hand over the mailing list.


🧠 What AI can do well

There’s real potential in using AI as a support tool. It’s excellent at:

  • Summarising minutes (though more on that in a moment)
  • Rewording notices in plain English
  • Writing templated blurbs for events
  • Suggesting topics or structures for sermons, emails, or posters
  • Helping roster-wranglers match names to roles (if you feed it a correct list!)

Used well, it’s like having a patient, mildly robotic intern who never sleeps and doesn’t complain about your formatting choices.


✋ What AI can’t do (yet)

It can’t remember who swapped with who last Easter. It doesn’t know that Margaret never says yes until Dawn does.  It doesn’t see the half-raised eyebrow in a committee meeting that actually means “not now.”

AI can’t exercise discretion. It doesn’t sense relational dynamics or know when to tread carefully.  It doesn’t even blink when your most pastoral person gets assigned to prune the hedge.

And no matter how confidently it generates a suggestion, it still doesn’t know anything.  It just guesses what would look plausible based on the internet and a frankly suspicious number of LinkedIn posts.


🙃 “The minute secretary is redundant now, apparently.”

This might sound like a punchline, but it’s something I actually heard recently — from a real, human minute secretary, no less.  AI tools like Otter.ai and Fathom are now quietly turning up in Zoom meetings, transcribing conversations with eerie fluency and very little oversight.

Some IT teams are reportedly having quiet panic attacks about this trend — not least because many of these tools store data offshore, with no real guarantees about privacy or data retention.  “Free” transcription comes with hidden costs, and they’re not always paid in dollars.

Let’s be honest: we didn’t all sign up for this.  But the tools are here — and some are genuinely helpful.


⚖️ Use it? Sure. But don’t give it keys to the vestry.

I’m not anti-AI.  In fact, I’ve seen it do great things — like help someone draft a sermon outline when they were under time pressure and stuck for a start.  (Philip Garside wrote about his own experience with AI sermons: AI-assisted sermon.)

But the golden rule is this: treat it like a tool, not a secretary.  Please and thank you are optional — but double-checking is not.

If it saves you time, excellent.  If it gives you ideas, fantastic.  But it won’t notice who’s tired.  It won’t ring someone who missed the meeting and quietly ask if they’re okay.  And it certainly won’t follow up when you forget to.


📬 Got AI stories from your church?

At d|c|t (the Diaconate of Church Technologists), we’re collecting stories — both the successes and the “well, it seemed like a good idea at the time…” moments.  If you’ve experimented with AI tools in your church (for admin, worship, planning, or pure curiosity), we’d love to hear from you.  Your examples will help shape a practical, grounded Church + AI resource we’ll be releasing later this year. You can contact us through dct.org.nz/church-ai.  We’re here to help churches navigate the digital world with a bit of wisdom, a bit of humour, and only as much automation as necessary.

Peter Lane is Principal Consultant at System Design & Communication Services and has over 30 years of experience with Technology systems.  We invite your questions, suggestions and ideas for articles.  These can be submitted either through the editor or by email to dct@dct.org.nz.  We also operate a website focused on building a community of people interested in improving how we use technology in churches, located at dct.org.nz.