The PM Who Inherited the Agent Schedule

You’re the product manager who opened your inbox in March and found yourself responsible for an agent schedule that now books, cancels, and reschedules volunteer shifts at a denomination whose regions you have never seen in person. The previous owner left for a startup, the handoff doc is three bullet points, and the agents have already started changing assignments based on rules nobody documented.

This is the foundational misread that causes product teams to treat agent execution as a prompt problem instead of a state-change problem. Teresa Torres’s continuous discovery insists on ongoing contact with users and evidence before every decision. When agents own the loops, that contact must move from the initial request to the exact moments the system alters ministry reality.

Map the handoff points where agents fork ministry state

In the children’s ministry tool I helped shape, the real boundary was never the lesson request. It was the moment the system marked a volunteer as confirmed and removed them from the open list. Agents now do that step without a human seeing the calendar conflict that only surfaces on Sunday morning.

The fork happens at three places: when an agent accepts a last-minute swap, when it drops a recurring commitment, and when it notifies the small-group leader instead of the volunteer coordinator. Each fork changes the shared record that later humans treat as truth. Torres’s method would require sitting with the actual coordinator while the agent proposes the change, watching which field they check first and which notification they ignore.

Without that map, teams keep adding guardrails to the prompt. The guardrails never reach the record that actually drives attendance reporting and background-check reminders.

Build discovery into the rollback surface, not the prompt

Continuous discovery loses its power when the only place to test an assumption is before the agent runs. The useful test happens after the change exists. In one region, an agent moved twenty volunteers from a midweek program to a weekend event based on attendance trends. The rollback required three separate systems to be edited by hand because no one had built an undo path that preserved the original notification chain.

Discovery therefore belongs on the rollback surface. That means every agent action must leave a reversible record that the coordinator can inspect in under thirty seconds. The question becomes: what evidence would make this coordinator choose to revert rather than repair? You learn that by watching the revert happen, not by asking about preferences in a workshop.

Measure coordination debt the way you once measured velocity

Velocity once tracked story points closed per sprint. Coordination debt tracks the number of manual corrections required after an agent schedule runs for one week. In the volunteer system, that number started at four corrections per hundred assignments and climbed to thirty-eight once agents began handling recurring conflicts without human review.

The debt shows up as duplicate background-check requests, leaders receiving two different volunteer names for the same slot, and printed rosters that no longer match the app. Torres would treat each correction as a signal that the current permission boundary is wrong. The team that measures debt this way stops optimizing for agent speed and starts optimizing for the speed of human repair.

Your Turn: Apply This Today

• Pick the single live agent workflow that books or reassigns people this week and list every state change it can make without human approval.
• Instrument one rollback action so the coordinator sees the before-and-after record in the same screen they already use for manual edits.
• Run the agent for seven days, then count every manual correction required and write the exact reason given for each one.
• Choose one handoff point from your list and add a required human confirmation only when that specific field changes.
• Meet with the person who performs the most corrections and watch them fix one live example without offering any suggestions.
• Update the permission boundary so the agent cannot touch recurring assignments longer than four weeks without an explicit approval step.

The post “The PM Role That Broke When Agents Took the Wheel” shows what happens when those boundaries stay undefined. “The Verification Layer No One Budgeted For” walks through the cost of discovering the need for reversibility only after the first schedule collision.

I consult with product leaders running agent workflows in ministry tools on permission boundaries, rollback design, and coordination debt tracking. Let’s talk.