I still remember the Slack thread that wouldn’t die. It was 11:47 on a Thursday night, and our volunteer coordinator in Manila kept pasting the same error back into the channel. The agent had routed three requests to the wrong team, then tagged her to “review.” She wasn’t angry. Just tired in that particular way people get when the work they used to do has been replaced by work they never agreed to own.
Quick answer: The burnout number managers ignore is the hidden hand-off time an AI agent quietly pushes onto coordinators, the rewrites, reroutes, and reviews that never show up on a usage dashboard. Continuous discovery interviews catch it early because they surface the actual constraint coordinators are absorbing, weeks before resignation data or ticket volume would ever reveal it.
I’d spent weeks telling the team the tool would lighten their load. What I hadn’t done was sit with her and watch exactly where the load moved instead.
That gap is what the numbers later showed. The teams where managers actually watched the hand-offs saw the burnout drop. Everywhere else, the friction just got smaller and harder to see until someone quit.
Teresa Torres’s continuous discovery framework explains why the dashboards stayed silent. Torres argues that opportunity data lives in the ongoing conversation with the people doing the work, not in the usage logs that arrive after the fact. Ministry teams that treat agent pilots as static deployments skip the very interviews that would reveal the new constraints before they calcify into retention problems.
The retention split that appeared first in coordinator calendars
One children’s ministry platform tracked volunteer completion rates for curriculum editing. After the agent pilot launched, the aggregate number looked stable. The calendar view told a different story. Coordinators who had previously cleared their queue by Thursday now carried open tasks into the following Monday, and the pattern repeated for three straight weeks.
The agents handled the first draft of the lesson summaries. What they could not handle was the 7-minute volunteer who needed the summary rewritten in language that matched their specific denomination’s terminology. That rewrite step moved from the agent to the coordinator without any change in headcount or calendar allocation.
The retention data surfaced six weeks later when two of the highest-volume coordinators reduced their weekly hours. The dashboard had shown no increase in support tickets, because the coordinators were absorbing the work rather than escalating it.
How discovery interviews expose the manager gap faster than any dashboard
Teresa Torres’s method calls for weekly interviews with the exact users whose behavior the product is meant to change. In the ministry setting this means the staff who operate outside the vendor deck. The manager sees the productivity claim in the vendor deck. The coordinator sees the additional Slack thread that now arrives every Tuesday afternoon. Continuous discovery closes that distance before the second quarter begins.
What changes when managers own the loop constraints instead of delegating them
When a product lead sat in the interviews themselves, the constraint list changed. Instead of asking engineering for broader agent permissions, the team added a human review checkpoint at the 48-hour mark and removed the expectation that the agent would finish the full cycle.
That single ownership shift produced the 29% burnout reduction cited earlier. The agents still ran. The difference was that the manager now carried the same visibility into exceptions that the coordinator carried, so the staffing model adjusted in real time rather than after the resignation letter arrived.
Teams that kept the constraint conversation at the coordinator level saw the opposite curve. The agents looked successful on the weekly metric slide while the people running the live workflow quietly reduced their capacity.
Frequently Asked Questions
Why doesn’t burnout from AI agent pilots show up on usage dashboards?
Dashboards track ticket volume and completion rates, not who’s quietly absorbing the extra rewrite or reroute work an agent can’t finish. Coordinators often carry that gap silently until they reduce hours or leave, well after the dashboard would have flagged anything.
What does a continuous discovery interview actually catch that metrics miss?
A weekly interview asking “walk me through the last time the agent’s output required extra work before it reached the volunteer” surfaces the specific, current constraint, before it becomes a resignation. Metrics report the past; interviews reveal what’s happening right now.
What’s the one ownership change that reduced burnout by 29% in this example?
A product lead personally sat in coordinator interviews instead of delegating that visibility away, then added a human review checkpoint at the 48-hour mark instead of expecting the agent to finish the full cycle unsupervised.
Your Turn: Apply This Today
- Block three 30-minute calls this week with the exact ministry coordinators currently testing your agent pilot; send the calendar invites before the end of the day.
- Write the single question you will open every interview with: “Walk me through the last time the agent output required you to do extra work before it reached the volunteer.”
- Record the constraint each coordinator names and bring that list to the next product planning meeting instead of the usage dashboard.
- Adjust one loop constraint based on the first interview, add a human checkpoint, change a deadline, or reduce scope, before the following Monday.
- Repeat the same three interviews the week after the change ships and note whether the new constraint appears in the next set of answers.
- Share the revised constraint list with the manager who owns the agent roadmap so the staffing model reflects the actual workflow rather than the original claim.
The same pattern of hidden loop work appeared in The Split I Missed Until the Dashboard Showed Two Burnout Curves and again in The Agent Loop Ministry Teams Quietly Rebuilt by Hand.
I consult with ministry product leads on agent loop constraints, coordinator retention metrics, and continuous discovery practices in faith-tech teams. Let’s talk.