Start with a repeatable process
Look for work that happens frequently, follows clear rules and starts with information your team can identify. Invoice checks, document intake and routine data handoffs are common candidates.
Write down the current steps, the exceptions and how much time the process takes. That baseline makes it possible to tell whether a pilot is helping.
Keep people in control of uncertain cases
A good first release does not need to automate every decision. Set confidence thresholds, send exceptions to the right person and keep a record of what the system did.
Begin with a small, representative sample. Check the results with the people who do the work before expanding to more cases.
Measure the outcome, not the novelty
Agree on a measure such as handling time, error rate or time to resolve an exception. Compare the pilot with the baseline and use the findings to decide whether to continue.