Look for repeated friction
Good candidates often involve repeated copying, routine status checks, consistent reminders, or preparing the same information in the same format. Describe the task in plain language before naming a tool. Identify how often it occurs and what staff must do each time.
Choose a workflow with clear boundaries
A first project should have an identifiable trigger and a finish line. “Improve operations” is too broad. “When an inquiry arrives, record it and assign the next action” is a workflow that can be discussed, tested, and improved.
Evaluate more than the time saved
- Frequency: how often does the work actually happen?
- Consistency: are the steps stable, or does every case require different judgment?
- Impact: what happens when the task is late or missed?
- Access: can the necessary systems be connected appropriately?
- Risk: can errors be detected and corrected before they create a serious consequence?
- Ownership: who will maintain the process?
Keep a person responsible for exceptions
Not everything should run unattended. Customer complaints, unusual payment situations, sensitive records, and business commitments may need review. The purpose of automation is not to remove accountability; it is to make routine work clearer and exceptions easier to handle.
Define success before building
Record a baseline where practical: manual steps per case, time spent, missing follow-ups, or status visibility. Select a measure that matches the workflow and can actually be observed. A tool being connected is not the same as the business problem being solved.
Start with a focused scope
Map the current process, choose one improvement, agree what is out of scope, test the important paths, and document the handoff. If the work is useful, expand from evidence rather than from a long list of possible features. Use our planning checklist or discuss a scoped automation project.