
There has rarely been a better time for using IT systems for business management and measurement. Systems are sophisticated and flexible and modern hardware can eat through large data sets. However, having been a ‘victim’ of well intentioned but ultimately futile attempts with technology there are a number of key observations which need to be considered to improve any systems project.
The most important consideration is the premise of the Heisenberg Uncertainty Principle. In quantum mechanics, the Heisenberg Uncertainty Principle (HUP) states a fundamental limit on the accuracy with which certain pairs of physical properties of a particle, such as position and momentum, can be simultaneously known. In other words, the more precisely one property is measured, the less precisely the other can be controlled, determined, or known.
It is identical with systems projects... the more precise you make the data collection (characterised by the various codes and hierarchies you deploy); the less chance the end user has of using the correct code. This therefore undermines the very precision you are trying to drive. If everyone books to a handful of codes, you can be pretty sure the figures are right. If there are hundreds, the total will be right, but the underlying breakdown will be largely fictional due to the inherent difficulty an individual has in picking the correct code.
Consequently when you are looking at this crucially important and topical subject you should think about the following;
Remember why you are doing this project and focus on the ‘critical few’ metrics that will make a genuine difference to your business;
Keep the number of codes that users have to navigate to an absolute minimum. Accept the loss of discrimination for the increase in precision;
Make the key measures visible... use classic lean management systems, short interval controls and other visible management techniques so that the output becomes central to operational improvements;
For the limited number of codes you do use, look at ways of ‘error proofing’ data entry through both systems (Validation rules) and user (Crib sheets) approaches;
Start simple... most over-engineered systems are spawned by people ‘theorising’ at what is needed. You should design the end-state, but get a simple practical solution working first; then look at how to make it better. At some point you will discover where the boundary is between more detail and less precision.
The HUP is fundamental to the invention and performance of so many modern inventions from the phone to the computer, from GPS to laser printing. Perhaps its application in business systems deployment can be equally profound.