Look for repeatable friction

A good candidate has a clear trigger, well-understood inputs, a narrow output, and a person who owns the result. Preparing a weekly account summary is easier to evaluate than asking an agent to “run sales.”

Make exceptions visible

Write down the normal path and the common ways it fails. Decide what happens when data is missing, sources disagree, or an action needs permission. The exception path is part of the workflow.

Measure before and after

Record the time required, the error rate, and the team’s confidence before introducing automation. Use comparable tasks during the pilot. Faster work that creates more rework may not be better work.

Keep the next step reversible

Begin with draft outputs and recommendations. Once quality is demonstrated, expand permissions deliberately. Retain logs and a human owner who can pause the system.

All field notes