McKinsey’s AI transformation framework tells leaders to set the mandate at the top, define the use cases from strategy documents, then cascade requirements downward through implementation teams. The model assumes the center holds enough context to name what good looks like before any local team touches the tool. That assumption collapses the moment the workflow crosses a competence boundary into the hands of volunteer coordinators who decide in seven-minute windows between service and lunch duty.
The framework measures success by adoption dashboards and model accuracy scores. It never asks whether the person who actually assigns rooms and prints name tags can still exercise judgment when the agent suggests a different curriculum track. The result is a shipped feature that meets the mandate and breaks the loop that keeps real ministry work moving.
This is the foundational misread that causes product teams to ship agents that look complete in demos and stall in practice. The gap is not technical. It is a competence boundary problem.
Charlie Munger described a circle of competence as the small set of decisions where a person knows the variables well enough to see second-order effects. Outside that circle, even smart people produce confident errors. Ministry tools cross that boundary the moment an AI agent starts suggesting how a volunteer should adapt a lesson for a child who just lost a parent. The coordinator sees the child’s face and the empty chair. The model sees patterns across anonymized sessions. Munger’s point was that you stay inside the circle or you bring in someone who lives there. Most AI mandates do neither.
How the Mandate Reached the Volunteer Coordinator
The requirement landed in an all-hands note: every new curriculum product must include an AI-assisted personalization layer by Q3. The product team translated the mandate into a clean spec. The agent would read the lesson text, the child’s age and attendance history, then output a suggested adaptation plus a printable note for the volunteer.
The volunteer coordinator first saw the feature the week before VBS training. She opened the new screen, read the suggested rewrite for the story of David and Goliath, and realized the model had removed every reference to violence without asking whether the church’s teaching team wanted that choice made for them. She spent twenty minutes rewriting the note by hand so it still matched what the lead pastor had approved six months earlier.
No one on the central team had seen that rewrite cycle because the success metric stopped at “agent output accepted.” The coordinator’s actual work of preserving local teaching intent never appeared in the dashboard.
The Competence Boundary the Model Crossed Without Noticing
The agent operated on content patterns and user metadata. It had no signal for whether a suggested change would require the volunteer to find new craft supplies at 8:45 on a Wednesday night. That decision sits inside the coordinator’s circle. She knows which families can bring extra glue sticks and which weeks the church van is already booked.
When the model suggested swapping the craft for a tablet-based reflection activity, it crossed the boundary. The coordinator could see the downstream cost in real time: two extra parent volunteers needed, one device cart that was already reserved for the youth group, and a training burden she would carry alone. The agent could not see any of it because those variables live only in her weekly rhythm.
Munger would have called this operating outside the circle with no compensating process. The mandate treated the model as competent across the full decision surface. The local team experienced the model as confidently wrong on the details that actually determined whether the session happened.
Rebuilding Decision Rights at the Competence Boundary
After the first month of quiet workarounds, the team added a single gate. Any agent suggestion that touched supply lists, room assignments, or approved teaching emphasis required an explicit “local override” click before the note could be printed. The override did not require explanation in the system, only acknowledgment that a human with weekly context had seen it.
They also moved the default output from a full rewritten lesson to a short margin note that the coordinator could accept, edit, or ignore in under sixty seconds. The model still generated the note, but the decision rights stayed with the person who would stand in the room.
Usage recovered once coordinators could treat the agent as a suggestion layer rather than a replacement for their own judgment. Retention among volunteer leads rose because the tool no longer created invisible extra work that only they could see.
Your Turn: Apply This Today
- Pick the single recurring decision your current AI feature makes on behalf of a local ministry user and write down the exact variables that person sees weekly that the model cannot access.
- Shadow one volunteer coordinator for a full planning cycle this week and note every judgment call that happens after the agent output appears on screen.
- Change the default output of one agent flow from a completed artifact to a one-sentence margin suggestion that requires an explicit local accept step.
- Remove any success metric that counts “agent output accepted” without also tracking whether the local user still completed their weekly task in the same amount of time.
- Map the three decisions that must stay inside the local circle and add a visible override control for each before the next release.
- Run a thirty-minute review with the actual end user of the last agent suggestion that crossed a competence boundary and log what the model missed.
The same pattern shows up in how teams handle inherited agent mandates and in the months spent routing every spec through the largest model before testing it against real weekly rhythms. Both posts trace the cost of assuming central competence where local judgment loops still do the work.
I consult with product leaders building tools for ministry volunteers and church staff on AI workflow boundaries and local decision rights. Let’s talk.