Last night’s homework was simple. Read an online article, list in your notebook 5 words you need to learn the meaning of and make sentences with each. Simples!
Fifteen minutes passed before I decided to check on the wailing and crying. What was wrong? Dictonary.com does not have the word “anjacent”!! And neither does the hardcopy Oxford dictionary! What to do?!
That was a classic example of how important it is to record information correctly. A lot of time and energy was wasted with a definite dead-end. Unfortunately this is not limited to children but can be found in businesses where information is erroneously collected.
People’s names can be the trickiest because without a standard we can record both the official name and a nickname of someone in different parts of an information system. This is a recipe for frustration and time wasting. How do we translate that Bob = Rob = Robert?
A different name can create problems in obvious systems such as the contacts directory and email but it can also prove to be problematic in granting access control to IT systems. It might be possible for Bob and Rob to be working on two different projects with associated access rights while it is only one person.
This lowers the level of accountability and can waste time correcting the initial mistaken identity. There should be a policy stating how the company supports initiatives to maintain data integrity. It will advise staff to consistently identify themselves.
There are technologies to help with this. Applications can insist on formats for input, use of ID numbers help, directory services such as Active Directory and OpenLADP, all which must be supported by strong managerial vision.