Letter to the PM Who Just Inherited the Agent Mandate

Dear PM who just inherited the agent mandate at a denomination you still can’t name without checking the org chart, You opened the first planning doc and the words “autonomous agents” and “workflow automation” sat there like they belonged. The team expects you to turn that mandate into something that ships before Q4. You know the real users are volunteers who already give up their only free hour on Sunday, but the spec keeps drifting toward model capabilities instead of what actually leaves their shoulders. This is the same pattern that turns every new AI initiative into another dashboard nobody opens after month two. The foundational misread is treating the agent as a set of capabilities rather than a single, named emotional relief the user feels the moment the task disappears. Shreyas Doshi’s discipline of naming the one-word core offering forces that clarity before any routing logic gets written. When you lock the word first, every later decision stops floating.

The One-Word Relief the Volunteer Actually Buys

Continuous discovery work, as Teresa Torres describes it, starts by naming the outcome a user actually buys—not the task the system completes.

If you just inherited the agent mandate, start here. Most ministry agents still optimize for task completion. The volunteer who prints curriculum at 9:15 p.m. on Saturday does not buy task completion. She buys relief from the low-grade dread that she might stand in front of eight-year-olds unprepared.

That relief has one word: ready. When the agent returns the lesson plan, the craft list, and the three backup activities already formatted for the printer, the word she feels is ready. Everything else is noise.

You see the difference in the usage data from tools like Sermons4Kids. Completion rates jump when the final artifact lands in a single printable packet. They flatline when the agent asks her to choose between three versions or reformat anything herself. The word ready explains why.

How an Inherited Agent Mandate Changes Every Routing Decision

Once ready is fixed, the model no longer needs to demonstrate creativity. It needs to demonstrate absence of friction. That single constraint kills most of the clever multi-step agent loops that look impressive in demos.

Routing now favors the shortest path that produces a print-ready file over the path that gathers extra context. If the volunteer has already told the system her age group and room size in a previous week, the agent should not ask again. Ready means no new questions on Sunday morning.

The same word also dictates what the agent must refuse. It must refuse to generate extra options, extra illustrations, or extra discussion questions. Those extras feel like generosity until the volunteer is standing at the copier with six minutes left. Ready removes them by design.

The Prioritization Rule for an Inherited Agent Mandate

Any roadmap item that lengthens the time between request and printed artifact loses priority. Any item that reduces that time gains it, even if it looks less intelligent.

Apply the rule to the three agent features still sitting in your backlog. The one that adds voice input for last-minute changes stays only if it still produces the same printable packet in under four minutes. The one that lets the volunteer edit the lesson in a browser tab gets cut, because editing breaks the feeling of ready.

The rule also surfaces the real metric. Track the percentage of weeks where the volunteer downloads and prints without opening any other screen. That number tells you whether the core offering is landing, not model accuracy scores.

Your Turn: Owning the Inherited Agent Mandate Today

• Open the current agent spec and write the single word that describes the volunteer’s relief; keep it to one word only.
• Take the top three open roadmap items and score each one against whether it shortens or lengthens the path to that relief.
• Delete or defer the item that adds any new screen, choice, or confirmation step before the printable output appears.
• Find the last three weeks of volunteer usage data and count how many sessions ended with a single download and print action.
• Write the new acceptance criteria for the next agent build using only that one-word relief as the success condition.
• Share the revised one-page spec with the two engineers who will actually implement the routing changes this sprint.

The Single Feeling Most Ministry Tools Still Refuse to Name and The Question Every Agent Mandate Still Leaves Unanswered both trace the same pattern back to the moment the core offering gets named or skipped.

I consult with product leaders on naming one-word core offerings for agentic ministry tools, routing decisions that protect volunteer time, and prioritization rules that survive handoff to volunteer users. Let’s talk.