Who This Article Is For
- People expecting major gains simply from adopting AI or RPA
- People busy every day without corresponding results
- People whose improvement efforts miss underlying problems
- Leaders reviewing work design before automation
Learn why automating unnecessary tasks can preserve waste, how to identify work to remove, and how small trials can precede useful AI or RPA adoption.
Improvement aims to reduce unnecessary work and protect time for valuable work.
AI and robotic process automation, or RPA, can help. Automating needless work can also hide waste and add maintenance costs. Ask whether the task needs to exist before making it faster.
Faster processing, less manual labor, and fewer mistakes have value when the underlying work is useful.
Consider:
These accelerate waste. Automation can also make an activity seem justified and harder to stop.
Identify what can disappear alongside what can become faster. A needless activity remains needless after efficiency improvements.
Without that review, you may find:
Routine activities worth questioning include:
Small activities can add up to a substantial burden.
Who benefits? Does it serve customers, decisions, revenue, or quality? Is it only a convention? An inventory reveals activities whose purpose has become unclear.
Why does the report, approval, weekly meeting, or duplicate entry exist? Repeated questions can reveal a method that has become detached from its original purpose.
Who would have a concrete problem? No identifiable impact suggests it might stop. A limited impact may allow an alternative. Unclear reasons deserve further review.
Automation is powerful for work with a clear need, repeated occurrence, and explicit rules: routine aggregation, reminders, conditional entry, and standard administration.
Use it after reviewing and reducing the process.
See RPA mechanisms and suitable activities, including differences from AI and tasks that do not suit automation.
Urgent responses leave little review time. Familiar work feels necessary because it has always existed, someone once requested it, or it is retained just in case.
Set aside time to identify stopping candidates before adding another tool.
Try a narrower change before full removal: make a weekly meeting fortnightly, reduce report frequency, remove one approval stage, or stop entering one field.
If no problem appears, the activity may be removable. If a problem does appear, it clarifies the genuinely necessary part.
SpreadSite is a no-code website builder that lets you create, publish, and update a website from Google Sheets using ready-made templates.
To simplify website publishing around information you already maintain in Google Sheets, give SpreadSite a try!
Build a website with SpreadSite →
Consider reducing work with little purpose so valuable work gets attention.
Before using AI or RPA, ask whether the task is necessary, removable, combinable, or simpler than its present form. This order can change the quality of improvement.
Thank you for reading!
I develop and operate SpreadSite, a service for creating websites from spreadsheets. Please consider it for communicating services and business information with less effort. SpreadSite
A: Yes, for necessary work. Otherwise it may hide waste and increase upkeep.
A: Test a partial pause or lower frequency and observe the consequences.
A: Discuss time spent, actual users, and the expected consequences of stopping, rather than relying on impressions.
A: Removing low-value work creates room for more useful responsibilities. Focus on the quality of the remaining contribution.