Beware of GIGO
GIGO has been around for as long as I could remember. For those of us who were trained in the field of computer software, we were introduced to it very early on.
The term stands for Garbage In Garbage Out. GIGO principle is still very much applicable today as it was 30 or 40 years ago, perhaps even longer. In simplest terms, GIGO means the information that you get out of your system is as good as the data that you put into it.
Today, with organizations from large to small depend highly on their integrated computer systems to operate their businesses smoothly, the concept is even more relevant.
Many users of Information Systems (IS) especially at the management level, they tend to interact with the output side of the system. The output comes in the form of reports, calculated figures on the screen, or charts and gauges on real-time dashboards etc.
The input side of the system involves even more users from a variety of sources. For example in a typical business operation, the data can come from shipping and receiving, sales reps on the road, production team on the shop floor or inventory control folks in the warehouse. Each has different set of focus and priorities as well as training background and skill sets. And they all constantly interact with the system and feeding data into it.
GIGO is at the heart of every transaction.
To mitigate the effect of GIGO, a well designed system will take this into consideration and validate data entries made by human operators and from other sources such as automatic data collection devices and sensors.
The information that you get out of your system is as good as the data that you put into it.
But hardware and software error checking and data validation components can only go so far.
The most critical component of all is constant, up-to-date communications and training for all users and designers of the system in terms of expectations for the output side as well as on the input side.
Many of us have seen how a simple change to the system, however small, without proper communications between all involved can lead to minor frustrations or even disastrous outcomes. Without proper notifications often time old assumptions are made and erroneous data (garbage) begin to propagate throughout the system.
Many of our users over the years may recognize some of the steps that we have taken to prevent GIGO from taking place such as checking the post date to make sure that it is within valid accounting periods or as simple as selecting options from a list. There are many ways and tools available to help this process and we will talk more about them in future newsletters.
Despite all the checking and validations, it is still the responsibility of all users that interact with the system to be aware of GIGO and take appropriate actions at all levels, in all areas, and all the time to ensure the system's output fulfills expectations.
Enough about GIGO. Dumpsters diving anyone?
Until next time.
Best Regards,
Tuan Vo
Compex Software