Field notes · NOV 2026 · 1 min
Agents break on the cases nobody wrote down
Why we start every engagement by mapping the exceptions, not the happy path.
Every operations team has a process document. It describes how an order, an invoice or a request is supposed to move. It is usually accurate for most of the volume, and almost useless for the part that takes most of the time.
The time goes into the exceptions: the customer who emails a PDF instead of using the portal, the supplier whose part numbers never match, the approval that needs a phone call because the threshold changed last quarter. Nobody wrote these down, because the people who handle them carry them in their heads.
The happy path is the easy part
An agent that only knows the documented process will look great in a demo and stall in week one. It meets its first real exception, has no idea what to do, and a person has to step in. Do that a few dozen times a day and the team decides the agent is more work than it saves.
So we start the other way around. In the first weeks we sit with the people doing the work and collect the exceptions as they arrive: what triggered them, who decided, what they looked at, and what they did next. That list, not the process document, is the real specification.
Sort before you automate
Once the exceptions are visible, the work sorts itself into three lanes. Routine work an agent can take end to end. Work that needs a check, where the agent prepares everything and a person signs off. And true exceptions, where the agent stops, asks, and learns from the answer.
Getting that sorting right matters more than any model choice. It decides where approvals sit, what the agent is allowed to touch, and how quickly the share of routine work grows. It is also where your team's know-how goes into the system, and it stays yours.