Map the exceptions
Repeated steps are a useful starting point for automation. First understand the exceptions: missing information, conflicting records, unexpected inputs and decisions requiring judgement. Identify the owner of each exception and the information they need.
Make decisions explainable
A workflow should leave a clear record of what happened. Show the relevant inputs, the action taken and the reason it was selected where the system can provide one. Give the responsible person a practical way to review, correct or stop an action.
Improve from real use
Start with a bounded process and check the result against the current workflow. Review failures and recurring exceptions before expanding the scope. Track measures that matter to the team, such as manual steps avoided or unresolved items awaiting review.