Opinion: Christians need a better measure of progress than speed

September 22: a Lutheran synod asks for a pause

A September 22, 2026 pastoral letter from the Florida-Bahamas Synod says its council adopted a resolution asking the Evangelical Lutheran Church in America to join other Christian traditions in advocating a pause in developing increasingly powerful AI until suitable safeguards exist. The letter connects this request to human agency, creation and human worth. It also announces learning opportunities and listening sessions. This documents a synod’s request; it does not establish that the whole ELCA adopted it, that development has paused, or that a specific regulatory mechanism exists. Original letter, signed by Bishop Suárez: Source: fbsynod.com

Christian analysis: this gives the discussion of speed a concrete institutional expression. But a pause needs more definition before it can be evaluated as policy: which systems, which activities, what conditions for resuming, and who judges compliance? Those are our questions, not provisions claimed for the resolution. Sabbath can help Christians question relentless production, but it does not by itself select the best regulatory design. A congregation could support the moral concern while asking for clearer implementation.

The listening sessions matter because discernment should include people affected by a decision, not only those confident enough to speak first. A useful church conversation would invite both people benefiting from AI and people bearing its costs, then distinguish their experiences from predictions about future systems. This update does not claim a representative survey of Lutheran opinion.

What is the saved hour for?

A church administrator finishes a routine task an hour earlier with AI assistance. What happens to that hour? It could become time to welcome a visitor, prepare carefully for a meeting, or leave work at a reasonable time. It could also become the starting point for a higher output target. The technology alone does not decide which outcome follows. The institution does.

This is the question Christian discussions of acceleration should bring into focus. Speed has moral significance through the goods it serves and the pressures it creates. A faster process can reduce needless burdens. It can also make existing demands harder to question. Calling either outcome “innovation” does not explain which people benefit or what kind of life the change supports.

Our argument is that Sabbath offers a serious challenge to institutions adopting AI: human beings should not have to justify every moment by its contribution to production. That conviction is compatible with useful technology. It requires leaders to decide what efficiency is for before treating greater output as an automatic good.

What the industry argument contributes

The June 29, 2026 a16z episode featuring Marc Andreessen and Navin Girishankar presents an optimistic account of AI's potential contribution to expertise, productivity and economic development. Its published description identifies institutional and infrastructure barriers as part of the discussion. That is an attributable perspective from an investment firm's platform, not an independent finding that every proposed deployment will improve life. Source: Source: a16z.com

It would be unfair to reduce this argument to a desire for speed at any cost. Easier access to useful expertise and less burdensome work are intelligible human goods. Christians can welcome those possibilities while asking how an institution will recognize success and how affected people can challenge a harmful implementation.

This essay does not estimate AI's net effect on employment or productivity. It examines the purpose of time saved within organizations, especially churches and faith-based institutions. Those practical decisions can be assessed without pretending that a single theological argument settles a disputed economic prediction.

Christian perspective: rest belongs to more than the powerful

Deuteronomy 5:12–15 places Sabbath within Israel's covenant life and memory of liberation from slavery. The command includes dependents, workers and others within the household's sphere of responsibility. Rest is not reserved for the person with the authority to assign work. The passage can be read here: Deuteronomy 5 (NIV)

Christians differ over the day, form and continuing obligation of Sabbath observance. This essay does not collapse those differences into one rule. Its ethical application is narrower: an institution should question arrangements in which those with power enjoy relief while others absorb unending demands. Remembering liberation challenges a measure of human worth based entirely on production.

Applied to AI, that principle directs attention to who experiences the promised efficiency. An executive's faster access to a report may require additional checking by an overstretched employee. A minister's easier preparation may leave an assistant correcting generated material. Those are hypothetical possibilities to investigate, not findings about a particular church. The point is to count the work that moves, as well as the work that disappears.

Efficiency can be an act of service

There is no special virtue in making people repeat avoidable clerical labor. A tool that simplifies an accessible schedule, helps locate a document or supports a carefully reviewed translation may free people for work they value. A Christian argument against making productivity ultimate should not romanticize exhaustion or refuse improvements simply because they arrive through technology.

The important distinction is between removing a burden and concealing it. If a new workflow saves time for one person but creates an unpaid checking task for another, its benefits need a more honest description. If a faster process makes a service inaccessible to people who cannot use the interface, the organization should include that loss in its evaluation.

A church could therefore begin with a small, well-defined task and a human purpose: reducing repetitive administration so volunteers can finish on time. It would then check whether volunteers actually experience that change. The test is more informative than counting how many documents the software can produce in a demonstration.

The objection from urgent need

Some work cannot wait. A congregation preparing help after a local emergency may reasonably prioritize speed. A school facing a shortage of staff may need relief immediately. An abstract demand to slow everything down would be insensitive to the people waiting for assistance.

Sabbath-informed judgment should distinguish urgency from an institution's habit of treating every request as urgent. A temporary response to an exceptional need is different from building permanent availability into everyone's role. A team can move quickly while deciding who is on duty, who can rest, what information must be checked, and when the emergency arrangement ends.

The relevant question is not whether a rapid action is automatically wrong. It is whether the institution can describe the need proportionately and accept limits when the need passes. An organization that cannot stop has surrendered an important form of judgment, even if its tools make that condition appear efficient.

What a church should measure

Before introducing an efficiency tool, record the task's existing demands and the improvement sought. Include the time required to check outputs and correct mistakes. Ask staff and volunteers whether the change helps them carry out their responsibilities rather than simply asking whether they like the technology.

Then identify a use for any genuine saving. Perhaps a team will reduce evening administration, improve preparation or increase personal contact. The purpose should be specific enough that people can later say whether it happened. Otherwise an efficiency promise can keep expanding without ever becoming a benefit anyone experiences.

These measures should be proportionate. A small congregation does not need a complicated dashboard to discuss whether a new process helped. A short written account, a few practical examples and honest feedback may be enough. The important feature is that affected people can disagree with the official success story without being treated as obstacles to progress.

A shared boundary is stronger than private willpower

It is easy to tell individuals to use technology wisely while surrounding them with expectations that reward constant availability. A staff member may find it difficult to disconnect if leaders routinely request instant revisions. A volunteer may feel that declining another task displays insufficient commitment when the software supposedly makes everything easy.

Institutional boundaries make a different statement. Leaders can define response expectations, maintain an alternative for people who do not use the tool, and resist turning every saving into an additional obligation. These are editorial recommendations for discussion, not a universal employment policy. Their value lies in aligning the organization's behavior with its stated concern for people.

A practical exercise is to follow one task through a typical week. Identify who starts it, who checks it, who receives it, and who has to repair an error. Then ask whether the new system lets those people stop. That final question often reveals more about the purpose of acceleration than a claim about output volume.

The Christian contribution is not a reflexive rejection of speed. It is an insistence that time, work and rest belong within a larger account of human dignity and worship. When an institution knows the good it seeks, it can welcome an improvement without making every technological possibility into a new demand.