Score by frequency and friction
Tasks that happen often and consistently frustrate staff are usually better automation candidates than infrequent, complex edge cases. Frequency compounds the value of even a modest time saving.
Weigh implementation complexity honestly
A task might be high-frequency but require deep integration across several legacy systems. Weigh the engineering effort against the expected benefit before committing.
Sequence for early wins
Sequencing automation projects so early wins are visible builds organizational confidence and budget support for larger initiatives later.