Look for repeated friction
Start with tasks that recur and require people to transfer information, chase updates or apply a consistent set of rules. Speak with the people doing the work to understand exceptions as well as the normal path.
Assess readiness
Automation depends on usable inputs and clear rules. Determine whether the required information is accessible, whether decisions are repeatable and who is responsible for resolving exceptions. Some processes need simplification before automation.
Define a measurable outcome
Agree on the outcome you want to assess, such as fewer manual handoffs or clearer visibility into pending requests. Establish a baseline using your own information, then review the result after deployment. Avoid promising a result before understanding the process.