The Ambition I Treated as Optional Until Agents Arrived

I used to treat ambition as something that would surface on its own once the tooling got out of the way. In the early days of rolling out agent prototypes for curriculum routing and volunteer scheduling, I kept my focus on the interfaces and the handoff logic. I figured the people around the system would naturally step into bigger questions once the repetitive work shrank. That assumption cost us six months of flat output and two key volunteers who quietly disengaged because the work no longer asked anything hard of them.

The real price showed up in the numbers we actually tracked. Completion rates stayed high, but the rate at which new ideas for ministry outcomes reached the backlog dropped by half. People stopped proposing changes to how the agents should decide what counted as a finished lesson plan or a successful follow-up sequence. They treated the agents as finished tools rather than shared instruments that still needed direction.

This is the foundational misread that causes product teams to hand execution to agents while accidentally shrinking the scope of everyone else. John Wesley’s first rule—do no harm—offers a sharper lens than most modern frameworks for agent design. Wesley meant the rule as a daily discipline, not a slogan. Applied to product work, it asks whether every handoff preserves or reduces the capacity of the people who remain in the loop.

Wesley’s rule of doing no harm applied to agent handoffs

When an agent takes over generating initial sermon outlines or children’s ministry activity sheets, the handoff decision is not neutral. If the prompt and acceptance criteria are written only by the product manager, the volunteer or staff member downstream loses the chance to define what “good enough” actually means for their context. Over time that loss registers as reduced ownership even if the output quality holds steady.

I watched this happen on a volunteer routing project at Sermons4Kids. The agent suggested assignments based on past completion data, and the handoff looked clean in the dashboard. Two months later the volunteer coordinators stopped suggesting adjustments to the rules. They assumed the system already knew what mattered. The harm was not in the suggestions themselves but in the quiet removal of their judgment from the definition of success.

Wesley’s rule forces a different question at the point of handoff: does this transfer of execution also transfer the authority to revise the criteria? If the answer is no, the design is doing harm to the ambition already present in the team.

Raising ambition inside volunteer and staff teams that now steer agents

Most ministry teams already contain people who think in outcomes rather than tasks. The shift to agents does not create that capacity; it surfaces whether the product work protects it or crowds it out. When a staff member can now edit the agent’s rules for what counts as a completed follow-up sequence, their attention moves from filling the queue to shaping what the queue should serve.

One children’s ministry director I worked with began requiring every agent-generated lesson plan to carry a short note on the single outcome the volunteer would measure in the room. The note took thirty seconds to write but forced the director to decide what mattered before the agent ran. Within three weeks her team was proposing new outcome categories the original prompts had never included.

The pattern holds across both volunteer and paid teams. Ambition grows when the product surface makes the steering decision visible and cheap to change. It shrinks when the same surface treats the agent’s defaults as settled.

The weekly practice that keeps ambition from collapsing into ticket triage

The practical discipline is a standing thirty-minute review that separates execution review from ambition review. In the first ten minutes the team looks only at what the agents completed. In the next twenty they examine one steering decision that was made or deferred the previous week and ask what would change if that decision moved one level higher in the organization.

The review stays small on purpose. It never expands into backlog grooming or metric dashboards. Its sole output is a single revised rule or outcome definition that one person will carry into the next cycle. Over time the practice keeps the team from treating agent output as the main product and their own judgment as optional commentary.

I have seen this rhythm surface decisions that would otherwise stay buried inside prompt engineering tickets. A volunteer coordinator recently used the slot to question whether the agent should optimize for lesson completion or for the number of children who asked a follow-up question after the lesson. The change moved from a minor prompt tweak to a measurable shift in how the team defined retention.

Your Turn: Apply This Today

• Pick one agent workflow you own and schedule a twenty-minute conversation this week with the person who currently only approves its output; give them the explicit task of rewriting the success rule before the next run.
• In your next 1:1, replace one execution assignment with a steering question: ask the team member to name the single outcome the agent should optimize for on their behalf and write it into the prompt themselves.
• Block thirty minutes on Friday to run the ambition review described above with one volunteer or staff member who already uses an agent you built.
• Take the most recent agent handoff you designed and surface the current success criteria to the end user in plain language so they can edit it before the next cycle.
• Identify one person whose role has shrunk to ticket triage since agents arrived and hand them authority to change one rule that affects at least three future runs.
• Document the change they make and bring it to the next weekly review so the team sees that steering decisions now belong to them, not only to the product manager.

The same pattern appears in The PM Who Inherited the Agent Schedule and The PM Role That Still Needs Human Judgment After Agents Ship. Both posts trace what happens when teams treat execution relief as the end of the work rather than the start of a new set of steering questions.

I consult with ministry product leaders on agent handoff design, weekly practices that protect team ambition, and the product decisions that keep execution relief from shrinking scope. Let’s talk.