The extended-context-window playbook that swept product teams in 2024 promised that feeding agents hundreds of thousands of tokens of prior conversation would remove continuity breaks in multi-step workflows. Ministry teams adopted the same logic for volunteer scheduling agents and curriculum distribution bots. They loaded every policy update, past email thread, and volunteer preference into the prompt and expected the agent to carry the thread forward without dropping details.
That approach breaks in practice because ministry handoffs rarely stay inside a single digital thread. The coordinator who receives the agent’s output still prints a one-page summary, walks it to the children’s area, and hands it to a volunteer who has never opened the app. The extra tokens never reach that second person. The framework treats the agent as the sole carrier of state when the actual state lives in printed sheets, shared Google Drives that volunteers ignore, and verbal confirmations at the door.
This is the foundational misread that causes product teams to overinvest in prompt length while the real constraint sits outside the model. Larger windows improve recall inside the chat but leave the physical transfer points untouched. The agent generates a perfect schedule. The coordinator still rewrites it on paper because the permission log lives in a separate system that the agent cannot update.
Teresa Torres’s continuous discovery process offers the corrective lens. Torres insists teams run weekly interviews with the people who actually touch the output, not just the users who request the feature. In ministry agent work that means sitting with the coordinator who prints the sheet, not just the pastor who approved the budget. The method surfaces the exact moment the digital state stops traveling with the task.
The coordinator who printed the policy sheet anyway
One children’s ministry coordinator in a mid-size church received a clean agent-generated volunteer roster on Monday. The agent had pulled attendance history, skill tags, and room assignments from the last six months. She opened the message, read it, then printed a condensed version that fit on half a page. She carried that half-page to the supply closet and taped it to the door.
The printed version omitted the agent’s notes on background check expiration dates. Those notes sat in the full context window but never made it onto the paper. Two volunteers showed up the next Saturday without current checks. The coordinator later said she printed because the volunteers expected a physical list they could cross off with a pen. The extra tokens in the agent’s window did not change that expectation.
The same pattern appears when agents generate curriculum outlines. The outline arrives with linked resources and timing suggestions. The volunteer still writes the three main points on an index card before class because the tablet is charging in another room. Continuous discovery would have caught this behavior in the first interview round rather than after launch.
How fixed context still collides with permission logs
Permission systems in most churches remain split between the planning software and a paper sign-off sheet kept in the church office. An agent can hold the full history of who is cleared to drive the van, but it cannot write to the clipboard that the insurance company requires. When a last-minute substitute appears, the coordinator checks the clipboard, not the agent.
Teams that tried to solve this by expanding the context window simply moved the collision earlier. The agent now refuses to output a name until it confirms the log entry, yet the log entry only happens after a human signs the paper. The loop stalls. Torres’s method would require the product team to observe the clipboard step in real time rather than assume the digital record is authoritative.
The collision repeats in budget approvals. The agent can track line items inside its window, but the treasurer still needs a printed requisition form with two signatures before releasing funds. Adding more context about past budgets does not remove the signature requirement. The constraint lives in the physical gate, not the token count.
The discovery loop that actually surfaces the real constraint
Torres recommends a weekly cadence of customer interviews focused on recent decisions, not hypothetical preferences. For ministry agents this means asking the coordinator to walk through the last handoff that happened that week. The question is not “Would you use an agent?” but “Show me the paper you used yesterday.”
One team ran three consecutive weeks of these interviews and found the same pattern: every successful schedule change involved a verbal confirmation at the Wednesday staff meeting. The agent output arrived after that meeting, so it was already stale. The discovery loop revealed that the real redesign target was not the context length but the timing of when the agent ran relative to the in-person meeting.
Another loop exposed that volunteers only trusted outputs they could annotate. They wanted margins for handwritten notes. The agent produced clean PDFs with no white space. Adjusting the output format took one afternoon once the interview data arrived. The context window size never came up as the blocker.
Your Turn: Apply This Today
- Pick one ministry workflow that currently uses an agent for scheduling or resource distribution and list every physical object that leaves a person’s hand during that workflow this week.
- Schedule two 20-minute interviews with the actual coordinator or volunteer who receives the agent’s output and ask them to show the paper or screen they used the last time the task ran.
- Map the exact timestamp when the agent’s output becomes irrelevant because a permission log or verbal confirmation happens outside the system.
- Reduce the agent’s context by half and test whether the output still fails at the same physical handoff point you observed in the interviews.
- Change the run time of the agent so it executes immediately after the weekly in-person meeting rather than before it, then measure whether the printed sheet still appears.
- Document the single permission gate or annotation step that the agent cannot touch and bring that item to the next product review instead of another token budget request.
The Context Window That Only Closed When a Real Coordinator Sat Down and The Permission Gate That Kept the Agent From Running the Schedule both trace the same pattern of digital state stopping at physical boundaries.
I consult with ministry product leaders on agent handoff redesign, continuous discovery interviews, and permission log integration. Let’s talk.