It’s What You Don’t Know That Can Hurt You
The author Mark Twain was once asked about his many business ventures – most of which had failed. Twain explained how his ventures had failed not...
In this acronym-rich industry of ours there’s still one acronym that I hold above all others because its truth is undeniable: GIGO. For those of you who might not remember this one, it stands for “garbage in, garbage out” – and it describes what we all know too-well: the poorer the quality of the data in our ERP application, the less value we’re going to get out of it.
GIGO has been with us practically since the dawn of the computer software age; and yet, in our excitement over new products, new gadgets, and (most of all) new catch-phrases, GIGO has to a great degree been pushed off to the side. Organizations have been too-accustomed (and too forgiving) in accepting “bad data” in their software applications, and when the economy falters and organizations downsize their staff, the incremental increase in bad data is simply accepted as the cost of doing business with fewer staff to do it.
Don’t you believe it.
Chalking up the increase in bad data to a reduction in staffing is an all-too convenient excuse, and – if anything – staff downsizing should bring the subject of bad data to the forefront of a business and make addressing it a corporate imperative.
But here’s the thing – most organizations think of data quality in terms of data entry; making sure that required fields aren’t left blank, making sure that validated fields have legitimate responses, and seeing to it that date fields contain date values, numeric fields contain numeric values, and so on. Now all of these things do improve the quality of data, but they are not all you can do to improve it.
Consider the following:
The above is just a small sample of the types of “data integrity” conditions that you can watch for in your ERP system; generally speaking, these conditions resolve themselves into the following:
As mentioned earlier, most organizations’ attempts at improving data quality usually begin and end with only the first item above – making sure that required data entry fields are not left blank.
So – do yourself, your staff, and your customers and partners a favor; the next time you go into your ERP application and you see something that makes you want to say “How did that happen?” – don’t just chalk it up as the price of doing business. Implement a data-quality system that continuously checks for (and responds to) that “bad data” that can occur at any time – not just when data is initially entered.
After all, everyone makes mistakes; it’s having to live with them that we can all do without.
The author Mark Twain was once asked about his many business ventures – most of which had failed. Twain explained how his ventures had failed not...
Have you ever had the experience of speaking with someone over the phone so many times that you build up an image of what that person looks like in...
Depending on where you do business and the local privacy laws in your region, you may be required to have evidence of marketing consent from your...