AI engineering job postings grew 63 percent between 2024 and 2025 according to the most widely cited labor-market trackers. The obvious reading is that organizations are finally building the technical muscle needed to ship reliable systems. That reading is backwards. The same period produced a measurable drop in experienced product and ministry roles inside faith-tech teams, precisely the people who once turned model outputs into usable tools for volunteers and pastors.
The hiring surge measures demand for narrow technical skills. It does not measure whether those skills are being applied inside organizations that still need someone to define success in human, not benchmark, terms. When the two groups stop overlapping, the product ships but the weekly workflow breaks.
This is the foundational misread that causes product teams to treat AI staffing as a pure capacity problem. They add engineers and assume the mission translation layer will take care of itself. It does not. The gap appears first in places where the work is already unpaid and time-constrained.
What the surge measures versus what faith-tech actually tracks
Public dashboards count filled requisitions and salary bands. They do not count the number of people who previously sat between an AI feature and its end user. In one curriculum platform serving children’s ministry volunteers, an automated lesson-outline generator was added without redefining anyone’s weekly checklist. Within six weeks the volunteer completion rate fell from 71 percent to 48 percent because the outlines still required manual adaptation that no one’s job description now included.
Faith-tech teams have always measured retention by whether a volunteer finishes the task, not whether the model produced an artifact. The hiring data never captures that distinction. It only records that an AI engineer was added to the org chart.
Charlie Munger’s latticework insists that a single mental model is never enough. Technical performance and ministry outcome are two separate models. When teams optimize only the first, the second degrades without showing up in any engineering KPI.
Role erosion that appears first in volunteer no-shows
Volunteer no-shows are an early signal because volunteers have the least formal power to push back. When an AI feature removes a coordination step that once belonged to a part-time ministry coordinator, that coordinator’s remaining work becomes harder to justify to their own supervisor. They stop recruiting new volunteers. The system still reports high model accuracy while the actual supply of prepared lessons drops.
The pattern repeats across teams that adopted agent-style tools for sermon research or small-group curriculum. The engineer who built the agent rarely sees the downstream effect on the person whose Friday afternoon used to include a 20-minute review pass. That review pass disappears from the job description before anyone notices it was load-bearing.
The latticework missing when teams track only model performance
Munger’s approach requires at least two additional models: one for role boundaries and one for feedback latency. Most faith-tech AI rollouts operate with a single model. They watch precision and recall, then declare success. They do not track whether the person whose scope just shrank still has a reason to stay in the room when the next feature is scoped.
Without the second and third models, product leaders keep adding engineering headcount while the people who once connected technical output to lived ministry constraints quietly exit. The organization ends up with stronger models and weaker translation capacity at the exact moment the models need more translation, not less.
Your Turn: Apply This Today
- Pick one AI feature that launched in the last 90 days and list the three people whose weekly task list changed because of it.
- For each person, write the exact task that used to exist and whether it still appears in any current job description or volunteer expectation.
- Schedule a 30-minute conversation with the person whose task disappeared and ask what they now skip on weeks when time is short.
- Adjust the feature’s output format or handoff step so the remaining human task takes no more than seven minutes for that specific role.
- Re-measure the original success metric (volunteer completion, pastor review time, coordinator retention) four weeks after the adjustment.
- Document the change and the metric shift in the next product roadmap review so the latticework is visible to the next team that ships an agent.
Capacity Constraints Are Crippling AI in Faith-Tech and AI Is Redefining Team Roles in Faith-Tech both trace the same pattern from different angles.
I consult with faith-tech product leaders on AI feature rollout and role clarity. Let’s talk.