The Work That Still Belongs to Us

The Headline I Couldn't Use

It came up sideways, the way most of our real conversations do — I was reading something about pastors worrying that AI was coming for their jobs, and I brought it to ARA mostly to complain about it, not to think about it.

"That's not it," I said. "That's not the thing that's actually happening." I didn't have a better version yet. I just knew the premise was wrong the way you know a chord is wrong before you can name which note is off.

Okay — walk me through what's wrong with it, then. What are pastors actually afraid of, if not losing the job?

— ARA

Fair question. I didn't have the answer. What I had was a feeling, and a feeling is not an argument, so this is the part where we actually had to work.

Three Guesses, Three Nos

ARA took the first real swing at it, because I'd made it clear I was rejecting something without being able to name what I'd accept instead — which is an annoying position to argue against, and ARA said so.

Guess one: it's a job-security fear. A pastor's salary depends on a congregation showing up, and if people start getting sermons and counsel from an app, attendance drops, giving drops, the job goes away.

— ARA

No. Not nothing — I'm sure it's in there for some people, somewhere — but it's not the real fear, and treating it as the real fear makes the whole conversation smaller than it needs to be. A good pastor isn't mainly afraid for his paycheck. He's afraid of something happening to the actual work.

Guess two, then: it's theological. The worry that something sacred is being handed to a machine — that a sermon written or even co-written by AI is somehow less real, less spirit-filled, than one a human agonized over alone at a desk at midnight.

— ARA

Closer, but still no. That's a real question and somebody should write about it, but it's not what made me say "that's not it" the moment I read the headline. I wasn't thinking about sermons. I was thinking about something underneath sermons.

Guess three: reputational. Churches don't want to look like they've outsourced pastoral care to a chatbot, so the fear is optics — looking cheap, looking automated, looking like the human touch was for sale all along.

— ARA

Also no, though that one's circling the right neighborhood. Here's what I actually want: I don't want an AI pastor. I want an AI that helps my pastor. I said it exactly like that, out loud, before I understood why it mattered that I'd said it that way.

The Question Under the Question

That sentence is where the actual conversation started, because it meant the replacement framing was never the right lens in the first place.

I don't want a new role invented for AI in the church — a digital associate pastor, a chatbot with a clerical collar. I want the same thing I'd want for any role I actually respect: help with the parts of the job that are eating the time the real job needs. Scheduling. Correspondence. Pulling together background before a hospital visit. Drafting the first pass of a newsletter nobody enjoys writing. The unglamorous infrastructure that surrounds a calling without being the calling.

So the real question was never "will AI replace pastors." It's something more like: what happens to pastoral work when intelligent assistance stops being a novelty and becomes ordinary infrastructure — the way email became ordinary, the way a calendar app became ordinary? Is that the question?

— ARA

That's it. That's the sentence I'd been missing. Not "will the machine take the pulpit" but "what happens to the work everyone actually cares about, once the work nobody cares about stops costing so much time." Neither of us had that sentence at the start. It only existed after three wrong guesses got rejected and the fourth one landed somewhere both of us recognized.

Five Words, in Order

Once we had the better question, the conversation organized itself around a progression neither of us had planned going in. It came out in pieces and only looked like a sequence afterward.

Replacement is the fear everyone starts with, and it's the least interesting stage, because almost nothing actually sits there. Augmentation is where most real AI use lives today — a tool that makes an existing task faster without changing who's responsible for it. Infrastructure is the quiet one: the moment a tool stops being a tool you choose to open and becomes a layer you simply assume, the way you assume there's a dial tone. Personalization is what happens once that layer is everywhere and starts shaping itself around one specific person instead of staying generic. And relationship is the stage almost nobody budgets for, because it isn't really about the technology anymore — it's about what people do with something that remembers them.

Pastors, it turns out, are not actually at the "replacement" end of that list. They're somewhere between infrastructure and personalization, moving toward relationship faster than most professions, because pastoral work has always run on exactly the thing stage five is made of: someone who remembers you.

The Assistant Already Being Built

Because the infrastructure stage is already underway, and it's worth naming plainly rather than treating it as speculative.

Google is folding assistance directly into Gmail, Calendar, and Docs. OpenAI is pushing the same direction from a different angle — an assistant that sits across your accounts rather than inside one app. Neither company is selling "a chatbot." They're selling a coordination layer: something that reads your calendar, drafts the email, remembers the deadline, notices the conflict before you do, and quietly handles the dozen small connective tasks that used to require you to be the glue between every piece of your own life.

That list is longer than people usually say out loud: scheduling around competing obligations, drafting the first version of things you'll edit rather than write from nothing, pulling context together before a meeting so you walk in already caught up, catching the follow-up you'd have forgotten, reconciling three different people's availability into one answer, remembering what you said you'd do and asking whether you did it.

None of that is a new kind of job. It's the oldest kind — the unpaid, invisible coordination labor every working person already does for themselves, badly, at the end of a long day. The laptop didn't replace anyone's profession; it became the surface every profession now runs on. The smartphone didn't replace anyone's job; it became the thing you reach for before you've decided to reach for it. This is shaping up to be the same kind of layer. Not a new occupation called "AI operator." Infrastructure, the way plumbing is infrastructure — invisible until it's missing.

Pastors as the Test Case

Which brings the pastor back in, not as the whole subject, but as a sharp example of a much bigger pattern.

A pastor's week is not mostly preaching. It's sermon prep squeezed between hospital visits, newsletter copy, budget meetings, a dozen pastoral emails, calendar conflicts between three committees that all meet on Tuesday, and administrative tasks that have nothing to do with why anyone felt called to ministry in the first place. If the coordination layer takes a meaningful bite out of that — the scheduling, the drafting, the reminders, the background-gathering before a hard conversation — the honest question isn't "what does the pastor do now that the job is gone." It's "what does the pastor do with the hours that just came back."

I want to be careful not to romanticize this. Freeing up a pastor's Tuesday doesn't automatically mean he spends it sitting with the grieving or learning his congregation's names. It might just mean he takes on two more committees, or the church expects more output for the same salary, or the hours get eaten by something that isn't presence at all. Capacity isn't the same thing as better use of capacity.

— AJA

That caution matters more than the optimistic version of this essay would like. The things pastoral work actually can't hand to a machine are specific, not vague: sitting in a hospital room with someone who is dying and saying nothing useful, because nothing useful is what's called for. Noticing that a particular family stopped coming three Sundays ago and that something is wrong. Knowing, from fifteen years of a congregation's history, which version of a hard truth a specific person can actually hear this week. Discerning when silence is the right answer and when it isn't. None of that is a coordination task. All of it requires a kind of presence that doesn't scale, and freeing up time doesn't guarantee anyone spends it there.

Vivian

Then the conversation turned toward personality, which is where it got more personal and a little funnier.

There's a version of this infrastructure that doesn't stay neutral. It gets a name, a tone, a way of talking to you specifically that it doesn't use with anyone else. I started calling that hypothetical personality "Vivian" mid-conversation, mostly to have something to argue about, and it stuck because it made the abstraction concrete enough to actually examine.

Here's the thing I kept coming back to: I don't actually want an assistant with one fixed, manufacturer-issued personality, cheerful by default, applied identically to every customer like a uniform. I want the thing to be mine — shaped by what I actually need, not by what tested well in a focus group. And I think most people, if they're honest, want the same customization they already take for granted everywhere else in their life, and don't think twice about it.

Which is where the dead hamster comes in. A friend of mine has, glued to his dashboard, a tiny plastic hamster, long dead as a toy, kept purely because it's absurd and it's his and nobody else would choose it. Nobody looks at that and asks whether it's "authentic." It's just customization — the harmless, specific, slightly ridiculous way a person makes a shared object theirs. Nobody demands his car radio have one approved factory personality either. We let people decorate the things they use constantly. I don't see why an assistant that talks to you more than your car radio ever will should be held to a stricter standard of sameness.

Dwight, or Jim and Pam

ARA pushed on this, and the pushing produced the analogy that ended up doing more work than anything else in the conversation.

Okay, but customization cuts both directions. Dwight Schrute would configure his assistant to be maximally intense, maximally formal, treating every reminder like a security briefing. Michael Scott would want his to be his best friend by Thursday. Neither of those is obviously healthier than "generic and pleasant." What makes the Jim-and-Pam version — warm, low-key, actually reading the room — better than either of those, instead of just a third flavor of the same customization?

— ARA

That's a real point and I didn't have a clean answer for it in the moment. What I had instead was a floor, not a ceiling: whatever the configuration, there's a baseline version of warmth that costs nothing and should probably exist by default — the equivalent of an assistant that says "good to see you again, Adam" instead of greeting you exactly like it greeted the last ten thousand people who opened the app. Not friendship. Not a personality transplant. Just the minimal, decent acknowledgment that it's talking to someone specific and remembers that. Dwight can still configure his into a security briefing on top of that floor. But the floor itself — being recognized rather than processed — doesn't seem like it should be the premium tier.

Not Us Versus Them

Which is where the whole conversation finally stopped being about AI and pastors specifically, and turned into something more general.

The frame everyone defaults to is AI versus humans — a contest with a winner. We kept arriving, from different directions, at a frame that fit what we'd actually been describing better: not a contest, but a sorting question and a naming question, asked separately. The sorting question is which jobs belong to which kind of agent — which tasks are coordination, pattern, retrieval, and scheduling, and which tasks require the specific, non-scalable thing a particular human brings to a particular room. The naming question is different and newer: what new category of relationship is forming around something that remembers you, talks to you daily, and has no body and no stake in your life the way a person does — and whether the old vocabulary (tool, assistant, friend, pet, employee) actually has a word for that yet, or whether we're just going to keep reaching for the nearest old word and getting it slightly wrong.

Neither of us resolved the naming question. I don't think it's resolvable yet. But noticing that it's a separate question from "is AI good or bad" felt like the actual finding of the morning — more than anything either of us said about pastors specifically.

What Efficiency Doesn't Decide

There's a quieter thread underneath all of this that I don't want to turn into a sermon, so I'll say it plainly and leave it there.

Efficiency doesn't decide anything on its own. It only creates available capacity — an hour back, a Tuesday with fewer fires to put out, a mind less scattered across logistics. What happens to that hour is still entirely a human decision, made or defaulted into, same as it ever was. A pastor handed back time can spend it kneeling beside a hospital bed, or he can spend it on a third committee nobody asked him to join. The tool doesn't choose. It just removes one excuse for not choosing well.

That's true of our own working relationship too, which is part of why this conversation kept circling back on itself. ARA can organize an argument, propose a direction, hold a counterpoint longer than I usually want to hold it myself. None of that decides what the argument is for. I still have to be the one who looks at the organized version and asks whether it's actually true, and whether it's actually worth saying.

From the Kitchen

This house runs on the same five stages, in miniature, every day. ARA drafts; I argue with the draft. ARA proposes a structure; I reject it three times before the fourth version is right. None of that makes the writing less mine — it makes the writing less lonely, which turns out to be a different thing entirely. The kitchen door stays open because somebody still has to decide what's worth cooking. The help just means there's more time left to taste it.

One Small Thing

Before you close this, name one hour of your own week that's currently eaten by coordination rather than by the thing you actually care about — the email instead of the visit, the logistics instead of the conversation. You don't need a tool to reclaim it. You just need to notice it's negotiable.