Blog

I was pouring the second cup when the screenshot landed. Same red bars on energy and recovery, posted by three people who don’t know each other. One of them had added just eight words: “Can’t do another AI cycle like the last one.” That was the morning AI cycle burnout stopped being a survey statistic and became a name I recognized.

I stared at it longer than I meant to. Those numbers used to feel like someone else’s quarterly review. That morning they looked like the week I came home from the field and couldn’t answer simple questions without checking Slack first.

The gap between what we ship and what it costs us is no longer theoretical, and AI cycle burnout is the receipt.

How AI cycle burnout hides in discovery loops that never reach the volunteer desk

The three product managers had run internal demos and leadership reviews. None had watched a children’s ministry volunteer print a lesson at 9:40 p.m. on a Wednesday while a toddler pulled at her sleeve. That scene never entered the backlog.

Continuous discovery requires the weekly touch with the person who will live with the output. When the loop stops at the product team’s own Slack, the AI mandate gets framed as “we need to stay competitive.” The volunteer’s real constraint—seven minutes between dinner and bedtime—never surfaces.

One of the managers later described shipping an AI sermon-outline generator. The tool produced clean copy. It also required the volunteer to copy, paste, and reformat into the existing print template the church already used. That step added four minutes. No one caught it because the discovery conversations happened inside the building, not at the kitchen counter.

Happiness Tied to Visible Ownership, Not Headcount

Smaller teams report steadier scores on the same survey. The difference is not size. It is whether a single person can still trace a shipped feature back to a specific user conversation that week. That traceability is what keeps AI cycle burnout from spreading across a team.

Larger faith-tech groups often measure happiness through engagement metrics on internal tools or attendance at all-hands meetings. Those numbers stay abstract. They do not register when an AI feature quietly removes the last point of direct ministry judgment from a volunteer’s workflow.

Torres’s method forces the ownership question into the open each week. The product manager must ask, “Who will decide what stays and what gets edited?” If the answer drifts toward an automated system, the team sees the ownership shift before the burnout scores move.

The Survey Number That Hid a Specific Workflow

The shared screenshot showed identical red bars, yet the three managers described three different daily frictions. One spent extra hours cleaning AI-generated curriculum that referenced resources their denomination no longer used. Another fielded support tickets from pastors who could not find the output inside their existing church management system. The third simply could not locate any quiet hour to run the required weekly user calls.

The aggregate burnout score collapsed those distinct workflows into one color. Continuous discovery keeps the workflows separate. Each conversation returns a concrete next step tied to one person’s actual desk or kitchen table. The number stops being the only signal.

Your Turn: Apply This Today

• Pick the AI initiative currently sitting in your backlog and schedule a five-minute call this week with the exact ministry owner who would use the output.
• During that call ask only one question: “Walk me through the last time you prepared this material and what you did with the extra four minutes.”
• Write down the answer verbatim and bring the single sentence to your next team stand-up without adding interpretation.
• If the sentence reveals a step the AI would remove or alter, add that constraint to the acceptance criteria before any further build work begins.
• Repeat the same five-minute call with one different ministry owner each remaining weekday this week.
• Track whether any of the six answers change the scope or priority of the original AI mandate.

Two recent posts explore the same territory from different angles: The Tuesday the Children’s Director’s Inbox Became the Real Product Spec and How Do You Embed Agents Without Quietly Rewriting Ministry Ownership??

I consult with product leaders at faith-tech organizations on running continuous discovery loops and protecting visible ownership when AI features are added. Let’s talk.

I remember the exact Tuesday it flipped. I was three hours into a backlog review, staring at an AI summary that had flattened six stakeholder threads into four neat priorities, none of which matched what the teams actually needed. My job had become deciding which machine output to bless with my signature. That signature moment is where mid-career PM burnout quietly begins.

The survey caught the same pattern across 2,400 PMs. Mid-career folks—five to nine years in—hit weekly mid-career PM burnout at 71 percent, well above the newer and the grizzled. The difference wasn’t hours worked. It was that every hour now ran through an extra layer that rewarded speed and volume while quietly draining the judgment that used to make the work feel like ours.

Adding more agents only widened the gap. The tools cleared noise but left the real weight untouched.

What the sentiment numbers reveal about mid-career PM burnout and role design

The survey did not ask about workload in the abstract. It asked what portion of a typical week still required a PM to exercise judgment that could not be delegated to an agent or a junior teammate. Mid-career respondents who answered “less than six hours” showed the highest burnout scores. Those who protected at least nine hours of non-delegable judgment time reported burnout rates closer to the late-career cohort. Mid-career PM burnout is a scoping problem, not a willpower one.

The difference is not individual resilience. It is how the role was scoped. When a product organization measures success by tickets closed and experiments shipped, the natural response is to route every repeatable decision through automation. What remains for the PM is a steady stream of edge cases that arrive without context and must be resolved before the next planning cycle. Nine years into a career, that stream becomes a career.

The same survey showed that teams using volunteer-completion rate or ministry-leader time-to-value as the north-star metric kept mid-career burnout twelve points lower. Those teams had already removed the assumption that every decision must scale through software. The PM’s remaining hours were therefore spent on the small set of choices that actually changed whether a children’s ministry volunteer finished the lesson in seven minutes or abandoned it.

Applying Wesley’s Rules to How We Allocate PM Time

John Wesley framed Christian practice with three rules that map directly onto product work: do no harm, do good, and stay in love with the work itself. Most AI adoption conversations skip the first rule. Adding an agent that drafts user stories or summarizes feedback looks neutral until you measure what it removes from the PM’s week. When the removed activity was the only remaining place where the PM observed a real ministry leader struggling, the net effect is harm to the product’s fitness for purpose.

The second rule—do good—requires choosing the good that cannot be automated. In ministry tooling this often means sitting with the exact moment a volunteer prints a resource, notices the missing graphic, and decides whether to fix it or give up. That moment is not captured by usage analytics. It only appears when someone with authority has protected time to watch it happen.

The third rule is the one most often ignored in capacity arguments. Staying in love with the work requires repeated contact with outcomes that feel worth the cost. When AI tooling compresses every observable loop into a dashboard, the mid-career PM loses the direct encounters that used to replenish judgment. Burnout is the predictable result of a calendar that no longer contains those encounters.

One Mechanism for Protecting Judgment Capacity

One team I watched replaced their weekly AI experiment review with a standing two-hour block called “live observation.” The PM and two designers sat with three ministry leaders while those leaders completed their actual tasks using the current version of the product. No recordings, no summarization agents, no follow-up tickets generated in the room. The only output was a single paragraph written by the PM describing one concrete change in user behavior they had witnessed.

After eight weeks the team had shipped fewer experiments but had raised their volunteer completion rate by nine points. Mid-career burnout scores inside the team dropped measurably. The mechanism worked because it forced the calendar to contain non-delegable judgment time and made that time visible to the rest of the organization.

The same practice scales to any ministry tool where the real user is not the purchaser. The cost is one protected block per week. The return is a role that still contains the encounters capable of sustaining judgment over a twenty-year career.

Your Turn: Apply This Today

• Export your calendar for the past seven days and highlight every block longer than thirty minutes that involved an AI experiment, prompt iteration, or agent output review.
• Mark every block that contained direct observation of a ministry leader completing a real task without your tooling in the room.
• Calculate the ratio of AI-experiment time to direct-observation time and write the single number at the top of a blank page.
• Block two contiguous hours next week labeled “live observation” with at least two actual users of whatever product you ship.
• During that block, write one paragraph describing a behavior change you witnessed; do not open a ticket or generate a prompt from it.
• At the end of the week, compare the new ratio to the previous one and note whether any AI experiment time was removed to protect the observation block.
• Repeat the audit the following Monday and decide whether the ratio itself becomes a standing metric for your role.

The same tension between measured output and protected judgment appears in the 1997 lesson AI product teams keep missing and in the hiring surge that makes pre-PMF thinking more expensive to skip. Both posts trace how role design choices compound over time.

I consult with mid-career product leaders in ministry tools on calendar audits, role redesign, and protecting judgment capacity under AI pressure. Let’s talk.