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.