Before you automate it,
understand the work.
The best first project is useful, bounded, and testable. Use these eight questions to assess a workflow with the people who do it every day.
This checklist is a planning aid, not a technical or security assessment. A high score does not guarantee a workflow is suitable for AI.
Estimate the time tied up in the task.
Frequency × average handling time gives you a baseline, not a savings forecast. If a team processes 80 requests a week at 10 minutes each, about 13 hours a week goes into that task. An automation still needs review, maintenance, and exception handling.
Write a one-paragraph workflow brief.
“When [trigger] happens, [person] takes [inputs] from [systems] and produces [output]. It happens [volume] times a week. The slowest step is [step]. Before anything consequential happens, [reviewer] approves it.”
Choose the right kind of solution.
Use ordinary rules and integrations where the logic is stable. Consider AI where unstructured information needs to be interpreted, summarized, classified, or drafted. Many useful workflows combine both.
Your selections stay in this page and are not saved or submitted.