Blog

The goal loop I built ignored Sunday validation, and that omission hid the real failure for months. I spent months building a goal loop for a children’s ministry curriculum tool that measured success by how cleanly a volunteer completed the lesson prep workflow inside the app. The loop closed when the PDF downloaded and the checklist hit 100 percent. I treated that as the finish line because the data looked strong and the retention curves held steady in the first weeks.

What I missed was that the real test happened after the download. The loop never checked whether the printed materials made it to the classroom table or whether the 7-minute volunteer could adapt the content on Sunday morning without a second device. The cost showed up in quiet churn: teams kept the account active but stopped using the new features because the Sunday handoff kept failing in ways the metrics never surfaced.

This is the foundational misread that causes product teams to optimize agent loops for task closure instead of mission outcome. Teresa Torres’s continuous discovery framework exposes the flaw directly. Her method insists that teams interview users in the context of the actual work, not after the digital step is done, so the success criteria stay tied to the observable result the user needs.

The Loop That Shipped Clean but Never Reached the Volunteer Desk

The discipline of validating against real outcomes echoes Nielsen Norman Group guidance: a clean internal result means nothing until it is tested where the work actually happens.

The curriculum tool’s agent watched for three signals: content selected, notes added, and file exported. Once those three steps occurred inside the same session, the loop scored the interaction as successful and moved the user into a “completed” cohort. We celebrated the numbers because they looked better than the old manual process.

Yet the exported file often sat in an email inbox or downloads folder until the volunteer had five minutes on Saturday night. At that point the layout no longer matched what the classroom needed, and the agent had already marked the job finished. The loop had no way to register that the materials never made it to the table.

Continuous discovery would have caught this earlier. Torres’s practice of weekly interviews in the actual work environment forces the team to watch the printout travel from screen to printer to classroom. Without that observation, the success criteria stayed inside the app.

How Continuous Discovery Forces Sunday Validation into the Criteria

Torres teaches that opportunity solution trees must be updated against real customer moments, not against internal task definitions. Applied to ministry agents, that means every goal loop needs an explicit Sunday handoff node. The node records whether the volunteer opened the printed page at the right time and could find the next activity without searching.

In practice this changes the data collected. Instead of only tracking export completion, the loop now logs whether the volunteer marked the lesson “used” on Sunday morning and whether any adaptation notes were added afterward. Those two signals sit downstream of the digital steps and become the real stopping condition.

The shift also changes what the agent is allowed to optimize. It can no longer declare victory on a clean PDF. It must wait for evidence that the content survived the handoff and served the actual teaching moment. That requirement surfaces new questions about print layout, timing reminders, and simple fallback instructions that the original loop never considered.

Why Timer Loops Hid the Missing Sunday Validation for Months

Many agent loops default to time-based success because elapsed time is easy to measure. Our loop rewarded any prep session finished inside forty-eight hours of the scheduled class. The timer created the appearance of reliability even when the materials arrived too late for meaningful review.

The hidden cost was delayed feedback. Volunteers who struggled on Sunday rarely reported the problem inside the app, so the timer kept scoring the prior week as successful. Months passed before usage data showed that the high completion rate was not translating into repeat classroom use.

Continuous discovery interrupts this pattern by requiring teams to watch the outcome moment repeatedly. When the interview or observation happens at the Sunday table, the timer loses its authority. The loop must now track the observable sign that the handoff succeeded, which a simple elapsed-time rule cannot provide.

Your Turn: Apply This Today

• Pick one existing agent loop in your current product and add a single Sunday handoff signal that only fires when the volunteer confirms the materials reached the classroom table.
• Schedule two 15-minute calls this week with volunteers who used the tool last Sunday and ask them to show you exactly what they had in their hands at 9:45 a.m.
• Rewrite the loop’s success definition so it requires both the digital completion and the Sunday confirmation before the agent records the interaction as done.
• Remove any time-based reward that currently closes the loop and replace it with the observable handoff event.
• Test the revised loop on three active ministry accounts and log whether the new signal changes which users are counted as successful.
• Share the before-and-after success rates with your team in a single paragraph that names the exact Sunday moment being measured.

The Workflow Handoff Where Models Finally Earned Their Keep and The Question Every Agent Mandate Still Leaves Unanswered both explore what happens when outcome criteria stay anchored to the final human moment rather than the digital step.

I consult with ministry product teams on agent goal loops and Sunday outcome criteria. Let’s talk.

The print step handoff is where the 8x claim quietly breaks down. Teams tracking AI model deployment in content pipelines report an average 8x lift in output volume within the first sixty days. The number shows up in dashboards that count generated outlines, rewritten sections, and draft emails. What the dashboards omit is the unchanged Saturday-night print-and-fold step that still consumes the same volunteer hours it did before any model was installed.

The obvious reading treats the 8x figure as proof that the models scaled the entire workflow. The opposite reading is the accurate one. The measured gains stop at the digital handoff. Everything after that handoff continues to run on the same physical constraints that existed in 2019.

Where the 8x number was actually captured

Analysis from McKinsey on AI adoption shows productivity gains concentrate upstream, leaving the final handoff steps untouched unless they are designed in.

The 8x claim surfaces most often inside the content-creation layer. A team ships a prompt chain that turns sermon notes into children’s ministry scripts, small-group questions, and social posts in one pass. The internal metric tallies those artifacts and divides by the hours the prompt engineer spent. The result looks dramatic because the old baseline counted every manual rewrite.

That baseline never included the next step: exporting the final PDF, loading the copier, and collating sets for volunteers who arrive thirty minutes before the first service. Those tasks remain outside the model loop by design. The 8x number therefore records only the portion of work that already lived inside a computer.

When the same teams later audit total cycle time from idea to printed sheet in a volunteer’s hand, the multiplier drops below 2x. The compression happened entirely upstream of the printer tray.

The print step handoff that stayed outside the model loop

Ministry resource sites have long optimized for the seven-minute volunteer. The person who prints the lesson at home or at the church office still needs a single-sided, correctly collated packet that fits in a folder without extra staples. Models that generate beautiful digital layouts rarely touch the printer driver settings or the paper-size defaults that break that packet.

One children’s curriculum platform tracked volunteer completion rates for three years. The rate held steady at 71 percent even after the organization introduced an AI-assisted script generator. The only variable that moved the needle was the addition of a one-click “print packet exactly as last week” button that bypassed the new digital workflow entirely.

The print step functions as an unmeasured dependency. Because it sits after the model output, teams can celebrate velocity gains while the actual delivery bottleneck stays fixed. The metric hides in plain sight because it lives on a physical machine rather than in the SaaS dashboard.

Latticework that connects engineering output to the print step handoff

Charlie Munger described a latticework of mental models as the habit of pulling ideas from multiple disciplines to see where they intersect. In this case the relevant models are queueing theory from operations research and the doctrine of total depravity from theology. Both insist that friction does not disappear just because one segment of the chain improves.

Queueing theory shows that the slowest station determines throughput. If the print-and-collate station still requires the same labor minutes, upstream acceleration simply creates a larger backlog in front of that station. The model output piles up as unprinted PDFs.

Total depravity supplies the corresponding human observation: people default to the path of least resistance. When the new digital pipeline adds even one extra click or file-format conversion, the volunteer reverts to the old printed master that has worked for years. The latticework therefore predicts that isolated model gains will be absorbed rather than multiplied unless the physical handoff itself is instrumented.

Teams that applied both models together began logging the timestamp when the final PDF reached the copier and when the last packet left the building. Those two timestamps revealed that the 8x digital gain translated into a 1.3x end-to-end gain. The difference was not a failure of the model; it was the predictable result of measuring only the segment the model touched.

Your Turn: Apply This Today

• Add a single timestamp field in your workflow tool that records when the final approved file is sent to the printer or copier queue.
• Run a seven-day audit on one recurring resource: note the exact minute the print job starts and the minute the last collated set is placed in the volunteer bin.
• Compare that elapsed time against the digital generation time you already track; surface the ratio in the same dashboard that currently shows the 8x claim.
• Identify the one volunteer who performs the print-and-fold step and ask them to log any extra clicks or reformatting required by the new AI output.
• Set a target to reduce the print-to-bin interval by fifteen percent this month without changing the digital generation speed.
• Share the updated ratio with the engineering team in the next sprint review so the next model improvement is scoped against the physical constraint rather than the digital one.

The Workflow Handoff Where Models Finally Earned Their Keep and The 10/10 Rule That Still Gets Skipped for the Novel Agent both trace similar gaps between model output and actual delivery.

I consult with product leaders shipping AI workflows for ministry teams on measuring end-to-end handoffs and volunteer completion rates. Let’s talk.

The One-Word Relief the Volunteer Actually Buys

Continuous discovery work, as Teresa Torres describes it, starts by naming the outcome a user actually buys—not the task the system completes.

If you just inherited the agent mandate, start here. Most ministry agents still optimize for task completion. The volunteer who prints curriculum at 9:15 p.m. on Saturday does not buy task completion. She buys relief from the low-grade dread that she might stand in front of eight-year-olds unprepared.

That relief has one word: ready. When the agent returns the lesson plan, the craft list, and the three backup activities already formatted for the printer, the word she feels is ready. Everything else is noise.

You see the difference in the usage data from tools like Sermons4Kids. Completion rates jump when the final artifact lands in a single printable packet. They flatline when the agent asks her to choose between three versions or reformat anything herself. The word ready explains why.

How an Inherited Agent Mandate Changes Every Routing Decision

Once ready is fixed, the model no longer needs to demonstrate creativity. It needs to demonstrate absence of friction. That single constraint kills most of the clever multi-step agent loops that look impressive in demos.

Routing now favors the shortest path that produces a print-ready file over the path that gathers extra context. If the volunteer has already told the system her age group and room size in a previous week, the agent should not ask again. Ready means no new questions on Sunday morning.

The same word also dictates what the agent must refuse. It must refuse to generate extra options, extra illustrations, or extra discussion questions. Those extras feel like generosity until the volunteer is standing at the copier with six minutes left. Ready removes them by design.

The Prioritization Rule for an Inherited Agent Mandate

Any roadmap item that lengthens the time between request and printed artifact loses priority. Any item that reduces that time gains it, even if it looks less intelligent.

Apply the rule to the three agent features still sitting in your backlog. The one that adds voice input for last-minute changes stays only if it still produces the same printable packet in under four minutes. The one that lets the volunteer edit the lesson in a browser tab gets cut, because editing breaks the feeling of ready.

The rule also surfaces the real metric. Track the percentage of weeks where the volunteer downloads and prints without opening any other screen. That number tells you whether the core offering is landing, not model accuracy scores.

Your Turn: Owning the Inherited Agent Mandate Today

• Open the current agent spec and write the single word that describes the volunteer’s relief; keep it to one word only.
• Take the top three open roadmap items and score each one against whether it shortens or lengthens the path to that relief.
• Delete or defer the item that adds any new screen, choice, or confirmation step before the printable output appears.
• Find the last three weeks of volunteer usage data and count how many sessions ended with a single download and print action.
• Write the new acceptance criteria for the next agent build using only that one-word relief as the success condition.
• Share the revised one-page spec with the two engineers who will actually implement the routing changes this sprint.

The Single Feeling Most Ministry Tools Still Refuse to Name and The Question Every Agent Mandate Still Leaves Unanswered both trace the same pattern back to the moment the core offering gets named or skipped.

I consult with product leaders on naming one-word core offerings for agentic ministry tools, routing decisions that protect volunteer time, and prioritization rules that survive handoff to volunteer users. Let’s talk.