Blog

For years I assumed any tool worth handing to ministry volunteers had to come from a proper engineering team or at least someone who could write and maintain code. That assumption sat in the background of every small idea I had while serving churches. It kept me from starting.

The real cost showed up when a volunteer asked for a simple way to track kids’ ministry attendance that also nudged parents toward at-home follow-up. I told her we would need to wait for the next budget cycle. She never asked again. Two years later the same need still existed and the volunteer had simply built a workaround in a spreadsheet that no one else could use.

This is the foundational misread that causes product teams to treat non-technical owners as end users rather than builders. John Wesley’s three simple rules—do no harm, do good, stay in love with God—offer a sharper lens than most modern product frameworks. They force attention onto whether a new workflow actually preserves the judgment of the person already responsible for the work.

When the Loop Replaces the Volunteer’s Judgment

Most current AI loops promise speed. They let a pastor’s kid open Claude, describe a fitness tracking form for a men’s group, drop the output into Replit, and have a working mobile-friendly page by lunch. The output looks finished. The volunteer who will actually use it never sees how the logic was decided.

That shortcut violates the first of Wesley’s rules. It does harm by removing the exact moment the volunteer would have noticed that the form asked for information she never collects in real life. The harm is small on day one and compounds every time the tool is used without her correction.

I watched this happen with a children’s director who received an auto-generated check-in flow. The flow asked for a child’s grade level before the parent had even signed the waiver. The director caught it only because she still printed every form and read them by hand. If the loop had run one more cycle without her, the error would have shipped.

Wesley’s Rules Applied to Agent Handoffs

The second rule—do good—requires more than a working prototype. It requires that the output measurably helps the person already doing the work. In practice this means the volunteer must be able to change the logic herself within the same day she receives the tool.

Replit’s current agent mode makes this possible if the initial prompt is written as a handoff document rather than a finished spec. The prompt states the exact decision the volunteer still owns, lists the three data points she refuses to collect, and names the person who will review changes before they reach families. The agent then builds only inside those constraints.

Staying in love with God, Wesley’s third rule, translates here into refusing to optimize for metrics the volunteer never chose. An attendance tool that maximizes completion rate at the expense of the volunteer’s actual relational goals fails this test even if the numbers look strong in a dashboard.

Where Ownership Quietly Moves

The quiet transfer happens at the moment the volunteer stops editing the prompt and starts accepting whatever the agent returns. Most teams notice the transfer only after the tool has been in use for months and the original owner no longer feels authorized to change it.

I have seen this shift in two children’s ministry tools built last year. In both cases the volunteer who requested the feature ended up routing every suggested change through the staff member who “owned the AI account.” The tool improved on paper while the real ministry judgment moved one layer further from the people doing the work.

The constraint that actually matters is therefore not technical capability. It is whether the final decision rights remain with the volunteer who will live with the consequences. Any loop that removes those rights fails Wesley’s test regardless of how quickly it ships.

Your Turn: Apply This Today

• Pick one narrow workflow a single volunteer already owns—children’s check-in follow-up, men’s group prayer requests, or nursery volunteer scheduling—and write a one-paragraph handoff document that names the exact decision she still makes.
• Open Claude and paste the handoff document as the system prompt, then ask it to generate only the form fields and one Replit component that matches those constraints.
• Send the generated link to the volunteer with a single instruction: change anything that feels wrong and reply with the new version.
• Watch whether she edits the output herself or asks you to fix it; the first response tells you whether ownership stayed in place.
• If she edits it, commit the change in Replit under her name and archive the old version so the history stays visible to her.
• Repeat the entire loop with one additional workflow before the end of the week so the pattern becomes repeatable without you in the middle.

The Tuesday the Children’s Director’s Inbox Became the Real Product Spec and How Do You Embed Agents Without Quietly Rewriting Ministry Ownership? both trace the same ownership question through different ministry surfaces.

I consult with product leaders in faith-tech and ministry organizations on embedding agents while preserving volunteer ownership and applying judgment frameworks to AI workflows. Let’s talk.

To the director who just turned down the VP title at a faith-tech startup because the role would have you sitting in fundraising decks instead of fixing the volunteer onboarding flow that’s been broken for three years.

You already know the paycheck clears either way. What you’re sorting out now is whether the next move actually matches the work you’re built to do or just adds another line that looks impressive when someone screenshots your profile.

That distinction matters more once the bills are covered. Everything after that point gets scored against internal competence and real flow, not external signals.

The Validation Trap That Hits Directors Hardest

The trap shows up when the title bump is offered before anyone has asked what problem you actually want to own next. You get the new card printed, the LinkedIn update drafted, and then three months later you realize you traded hours inside the product for hours justifying the product to people who never use it.

Most directors I watch reach this point after they’ve already proven they can run a team. The market keeps offering scope because scope is what gets measured in the next comp conversation. Competence inside the actual work stops being the signal once the visible version of your job starts paying better.

At Sermons4Kids we learned the hard way that the metric that kept volunteers coming back was completion rate on a single lesson, not the number of features the director could claim on a roadmap. The same pattern repeats at the career level. The work that actually compounds rarely needs a new title to be visible.

Munger’s Latticework for Deciding What to Accept

Charlie Munger kept a handful of mental models he applied to every major decision instead of chasing surface incentives. Inversion was one: start by asking what would make this choice obviously bad in five years, then work backward. Another was circle of competence: stay inside the problems you can actually see and judge without needing constant external validation.

Applied to a role offer, inversion surfaces the question quickly. Will this position pull you into meetings where you defend metrics you no longer believe move the mission? Will it reward you for claiming credit on work your team already solved while you were traveling for the title? If the answer is yes on either count, the latticework flags it before the ego does.

The circle of competence test is simpler still. Write down the three product problems you have solved well enough that other teams now copy the approach. Then look at the new role and count how many of those problems it still lets you touch directly. When the number drops below two, the role is moving you outside the area where your judgment compounds fastest.

How Dependents Change the Calculation

Once a mortgage and kids enter the picture, the external signals gain real weight again. The paycheck is no longer optional, and the visible title can still open doors that protect the family if the current role ends. Munger’s models don’t ignore that reality; they just force it into the same lattice instead of letting it override everything else.

The adjustment is to treat the title as a temporary hedge rather than the primary score. You still evaluate the work against competence and flow, but you also run the inversion question against the worst-case financial scenario. If the role fails, how many months of runway do you actually need, and does the title itself shorten or lengthen that runway?

Most directors I know discover they can keep the hedge smaller than the market suggests. The last three role conversations I tracked all allowed a narrower scope with the same base comp once the candidate named the exact problems they wanted to keep owning. The title stayed flat, the dependents stayed covered, and the work stayed inside the circle that actually fits.

Your Turn: Apply This Today

• Take the last three role offers or major project assignments you received and list the exact product problems each one would have let you own for more than two hours a week.
• Score each problem against your own competence list: high, medium, or outside the circle. Discard any offer where two or more problems land outside.
• Run Munger’s inversion on the remaining options: write one sentence describing the state you would most regret in three years if you accepted.
• Calculate the actual financial hedge required if the role ended in twelve months, then compare that number to the title premium being offered.
• Identify one current project inside your existing role that still sits inside your competence circle and block four hours next week to make measurable progress on it before any new title conversation.
• Send one note to a peer who has stayed in a narrower scope for the last two years and ask what trade-offs they have actually experienced with dependents in the picture.

The Hiring Surge That Makes Pre-PMF Thinking More Expensive to Skip and The Tuesday the Children’s Director’s Inbox Became the Real Product Spec both track the same pattern at the team level: visible scope expands faster than real ownership unless someone runs the latticework first.

I consult with directors and product leads on role evaluation, competence-based scoping, and keeping dependents covered while refusing title inflation. Let’s talk.

The advice that still circulates in product circles traces back to McKinsey’s repeated “State of AI” surveys: measure what share of any given role can be automated, then budget and staff around that percentage. The framework treats work as a stack of discrete activities that can be sliced, costed, and reassigned without disturbing the surrounding relationships. For teams building tools that land in churches and parachurch ministries, the slice-and-measure approach breaks because ministry work is rarely a set of interchangeable tasks; it is a web of ownership that volunteers accept for free and renew weekly.

When the metric stays at the percentage level, the conversation quickly drifts into questions about model accuracy or token cost. Those numbers look clean on a slide. They hide the actual fracture: some activities can be handed off without anyone noticing the difference, while others quietly transfer responsibility for the person on the other side of the screen. Once that transfer occurs, the original owner stops showing up, and the product team discovers the gap only after usage drops.

This is the foundational misread that causes product teams to ship pilots that look efficient in internal demos and then stall once they reach the actual ministry calendar. The misread treats every hour of work as equivalent. It is not.

Solomon’s judgment supplies the sharper test. Two women claim the same living child. Solomon offers to divide the child so each receives half. The true mother refuses because her stake is not in the fraction but in the whole life of the child. The test does not measure percentage; it reveals whether someone will fight to keep the relationship intact. Applied to AI product work, the same test distinguishes tasks that can be split from ownership that must remain whole.

In volunteer settings the distinction appears quickly. A children’s ministry coordinator can hand a volunteer a pre-written lesson plan generated by a model. The volunteer still owns the moment when a seven-year-old asks an unexpected question during small group. If the tool also generates the follow-up conversation guide and the prayer prompt, the coordinator has begun to transfer ownership of the relationship itself. The volunteer notices the shift within two weeks and stops preparing. Retention falls even though every individual task was completed faster.

The same line appears in pastoral work. Sermon prep contains dozens of tasks—verse lookup, illustration search, slide formatting—that can move to an agent. The ownership that remains is the decision about which text the congregation needs to hear this month and why. When a product asks the pastor to review an entire draft rather than to own the text, the fracture appears. The pastor either rewrites from scratch or begins to treat the output as someone else’s sermon. Either path changes who stands accountable on Sunday.

Once models become cheap enough to run at the edge, distribution patterns shift again. Tools that preserve ownership travel through existing volunteer networks because the volunteer still feels necessary. Tools that quietly absorb ownership require new distribution channels—paid staff, denominational mandates, or direct-to-congregant apps—because the original volunteer network no longer has a role. The cost calculation therefore changes: the cheaper model may require the more expensive distribution strategy.

Why the Percent Question Fails in Volunteer Settings

Volunteer roles are defined by the hours people choose to give, not by job descriptions. When a product team calculates that 65 percent of a volunteer’s checklist can be automated, it assumes the remaining 35 percent will still be performed by the same person. In practice the volunteer experiences the loss of the 65 percent as a reduction in purpose. The remaining slice no longer justifies the drive to the church on a weeknight.

Sermons4Kids data showed this pattern repeatedly. Volunteers who previously spent twenty minutes choosing a craft and ten minutes printing it would accept an auto-generated craft sheet. Once the same system also selected the memory verse and wrote the discussion questions, completion rates fell even though every artifact was still delivered. The volunteer no longer recognized the hour as theirs.

The percent frame also ignores the social contract inside the church. A volunteer accepts the role partly because other volunteers see the effort. When the visible work shrinks, status inside the group shrinks with it. The model has not replaced the task; it has removed the public evidence that the relationship with the children still belongs to the volunteer.

Solomon’s Test Applied to Task Versus Ownership

Map every step of a workflow to one of two categories. A task is complete when the output exists. Ownership is complete only when the person remains responsible for the next human interaction that the output enables. Solomon’s test asks which category a team would fight to keep.

In practice the line appears at the moment of exception handling. A model can generate a small-group question set. It cannot decide, in the moment, whether a particular child’s answer requires a private conversation with a parent. The person who owns that decision must still be present and must still feel authorized to act. Any pilot that removes the need for that person to prepare for the exception also removes the incentive to show up for the exception.

The same line governs data ownership. A children’s director who receives weekly attendance summaries generated by an agent will continue to act on them only if she still owns the follow-up phone call. When the agent also drafts the email to absent families, the director begins to treat the report as background noise. The task moved; the ownership did not survive the move.

Distribution After the Model Gets Cheap

Cheap inference removes the earlier constraint that forced teams to centralize generation inside a single platform. The remaining constraint is who will carry the tool into the room. Tools that leave ownership intact ride existing volunteer and staff relationships. Tools that absorb ownership require paid distribution—regional trainers, licensing deals with denominations, or direct marketing to parents.

The second path carries higher customer-acquisition cost and higher churn once the novelty wears off. The first path scales only as fast as the volunteer network can absorb change, yet it retains the users who already perform the work for free. The choice between these two distribution routes is made at the moment the team decides which ownership transfers it will accept.

Your Turn: Apply This Today

• Pick one current AI pilot and list every discrete step a user performs today; mark each step as either a task or an ownership transfer.
• For every ownership transfer on that list, write the name of the specific person who will still be held responsible when something goes wrong next month.
• Remove or redesign any step where the named person would no longer need to prepare or decide before the next human interaction occurs.
• Run the revised flow with three actual volunteers or staff members and record which steps they still describe as “mine.”
• Compare the revised flow against the original pilot metrics; note any change in completion rate or repeat usage after two weeks.
• Document the ownership line you drew and share it with the next team that proposes a new agent for the same ministry surface.

The posts “How Do You Embed Agents Without Quietly Rewriting Ministry Ownership?” and “The Judgment Step AI Tooling Still Skips in Faith-Tech Pilots” trace the same line through additional ministry surfaces. I consult with product leaders and ministry technology teams on ownership mapping, volunteer retention metrics, and distribution choices after models become cheap. Let’s talk.