The Rule of 100 and 1,000 and automation
I originally coined the rule of 100 and 1,000 in relationship to data conversion (here and here). I extended that rule to ongoing data management here.
The rule of 100 and 1,000 can also be applied to automation. Simply put, if you're managing fewer than 100 records for some process (e.g., accepting 50 submissions for an awards program), it's probably not going to be worth the effort to automate most of that process. But if you're receiving over a thousand submissions, you're definitely going to want to automate the process as much as possible.
In fact, for automation, I might adjust the rule to 100 and 500, especially if there are multiple steps in the process (e.g., submission, review, multiple communications with applicants, etc.).
It often doesn't make sense (in terms of time and money) to automate a process that can be managed manually. And definitely don't automate for the sake of automation.
The rule of 100 and 500 might help you decide whether or not to automate a process.
![]()
Wes's Wednesday Wisdom Archives
Two tips for data conversion
Two Tips for Data Conversion I’ve written a lot about data conversion over the years […]
Who should “own” the database?
Who should “own” the database? One of the most common questions I get from my […]
What makes you weird?
What makes you weird? When I work with clients on selecting a new association management system, one […]
Why “AMS Consortiums” Don’t Work
Why “AMS Consortiums” Don’t Work About once a year I will get a call from […]
Your vendor will disappoint you
Your vendor will disappoint you I follow politics as a hobby. A past publisher from […]
Learn how to lose
Learn how to lose “Winning is great, sure, but if you are really going to […]
Ownership is Required
Ownership is required When asked for the most common reason AMS implementations fail, I typically respond […]
It’s all relative…
It’s all relative… Over the course of my 22 years of consulting, I’ve consulted with […]
Eliminate to optimize
Eliminate to optimize So much of data management is habit (both good and bad) which is […]
For data governance, ask “Why?”
For data governance, ask “Why?” Recently I’ve had the opportunity to work on several data […]
