Not every manual task should be automated. Some tasks need clearer ownership or a simpler process first. The best starting point is understanding why the work takes effort—and whether that effort can safely be reduced.
1. Follow the handoffs
Look for places where people copy information between systems, chase missing details, reformat the same material, or wait for an approval. Ask what triggers the work, what information arrives, and what a completed output needs to contain.
A short process map can expose duplicated entry or an unnecessary step. Remove work that does not need to happen before you look for ways to automate it.
2. Separate rules from judgment
Some tasks follow clear rules: routing a request based on a field, checking whether a required attachment exists, or calculating a total. Conventional automation may be enough. AI can be considered when a task involves interpreting text, summarizing material, or preparing a draft.
A mixed workflow often makes sense: software handles fixed rules, AI assists with a bounded language task, and a person reviews exceptions or important decisions. The aim is a dependable process, not using AI everywhere.
3. Compare frequency, effort, and error cost
Estimate how often the task happens and the time it consumes. Then consider how costly an incorrect output would be, how variable the inputs are, and how much review is needed. A frequent task can still be a poor pilot if failures are difficult to detect.
Include setup, maintenance, subscriptions, and human review when comparing options. Saving a few minutes on one step can be outweighed by added work elsewhere.
4. Define a human checkpoint
For administrative work, a person might confirm extracted details before a record is finalized. For customer follow-up, someone should verify names, facts, and commitments before a message is sent. For reporting, figures should be checked against the original source.
Make review responsibility explicit. A vague instruction to “check the AI” is less useful than a short checklist that says what to verify and who signs off.
5. Test the ordinary cases and the awkward ones
Try representative examples alongside incomplete, ambiguous, or unusual inputs. Watch how the workflow behaves when information is missing or a connection is unavailable. Define a fallback so the team can continue working.
Compare the pilot with the starting process. Look at total time, quality, and user experience. Refine the process before extending it to additional tasks or teams.
YOUR PRACTICAL RESOURCE · NO EMAIL REQUIRED
Your automation opportunity worksheet
Compare up to four recurring tasks. Estimate effort, identify risks, and choose one manageable opportunity for closer review.
| Task & owner | Times per week | Minutes per task | Potential value | Error risk | Human review point | Next step |
|---|---|---|---|---|---|---|
Frequency x minutes / 60 gives current weekly effort, not guaranteed savings. Include setup, review, exception handling, and maintenance when comparing options. A high error risk needs closer review even when the potential value is high.
Your entries stay on this page only and are cleared when you leave or reload. Nothing is submitted. The downloadable PDF is a blank copy.
Want a second perspective?
Use this resource independently. When consultations open, you can also bring your notes to a free 30-minute introductory conversation.
Consultation availability ↗General guidance. Apply it in the context of your business and review proposed tools and workflows before using sensitive information or making important decisions.