“To err, is human”, true but it does have a cost, an impact on a business and often results in a disappointed customer.
The greater the monotony of the work activity, the higher the error rate in most situations according to research with a typical level being 4% of transactions.
How many errors will you make today?
Here we are considering an “Action” that is unintentional and consider a mistake rather than any deliberate action intended to cause a problem.
There are four types of “Human Error”, namely:
These are best illustrated with examples.
As temperatures change car tyres need to be inflated by different amounts. For each 10 degrees increase in temperature the tyre pressure will be increase by 2 psi.
In terms of the use of business computer systems, the same types of human error occur but the situations will be much more specific to the company and the computer applications.
What can be done to prevent human errors with such computer applications?
As most people will have experienced, it is possible for valid values to be assigned to the wrong situation, which can result in customers saying “I did not order that!”.
When complex processes are involved one of the recognised best ways to reduce errors is the use of “Check Lists”. These documents act as corporate memory of best practice and provide a person with an extra opportunity to verify that none of the types of Human Error have occurred. For this to be achieved, the Check List has to be thoughtfully completed and not just treated as “tick box” exercise.
When errors have occurred, the resolution of the situation is about attitude and a process to fix. The adoption of a “Blame” culture can lead to attempts to cover-up an error which is never a desirable situation. The best companies look for an “Open Loop” culture and “Continuous Improvement Process”, that can be deployed alongside an “Error Detection” process. Once errors are discovered, actions are followed to mitigate the damage and recover the situation. Once the immediate position is under control, improvement activities need to start. This requires “Root Cause Analysis” to discover where the error occurred and if possible “Why” and “How” it happened. With that information available actions can be consider to reduce or prevent the error occurring in the future. This might be as simple as adding an extra item to a checklist.
A typical emphasis from the adoption of checklists, is the priority for accuracy rather than speed. With a “Get it right first time” mentality.
There are many methodologies (e.g. Six Sigma, Lean, Quality Function Deployment QFD, Soft Systems Methodology SSM, Failure Analysis) available for both problem solving and process improvement. Once a change is identified, it is worth being aware of the law of unintended consequences, so that an the implementation of the change does not cause a bigger issue somewhere else.
What can be done to find errors if they are not reported? Situations where additional goods have been delivered to a customer in error may not be reported by the customer. Finding such errors can be “Like looking for a needle in a haystack”. Auditors who perform various checks on business processes know that any tests they perform on a sample of transactions is unlikely to uncover the odd error, but auditors do try to uncover any systematic error.
Identification of errors can be discovered through data profiling activity which looks for Complete, Correct, Consistent, Reasonable data patterns. It is the use of mathematical techniques to discover “Things which do not fit” alongside other similar data. Once anomalies are identified they can be investigated to see if they represent errors or genuine deviation.
In manufacturing and construction, physical items are created with a level of tolerance in the measurements. This is to recognise that minor variations can occur due to materials, machinery precision, etc., but the outcome can still be “Fit for purpose” if it is within the limits of the range.
When performing tasks on computer applications, the objective has to be zero errors. Given human nature, the costs to achieve that level of result may not be acceptable. The amount of work to catch a small number of errors follows a pattern of diminishing returns for the level of expenditure required as the operation would end up with people checking people checking people, where the second level of review may only be making an improvement of 1% overall. A business may decide that the tolerance level for errors is not zero, but a small percentage of the activity as the cost to prevent the errors is not acceptable.
A lot of academic work has been undertaken on human behaviour in a man-machine system activity and why mistakes occur. The Cognitive Science behind repeating mistakes shows that in attempting to understand where we went wrong, our brains create “mistake pathways,” ruts that we get into when we try not to make another misstep. This is why some people will lose their phone again, and again.
One of the stated benefits of business process automation with software robots to implement robotic process automation (RPA) is the improvement in quality. The reason for this benefit is that although software robots simulate what a human would do on computer applications, when robots perform the activity they do it with 100% consistency. Software robots do not get tired, or distracted, or make human errors, they only know how to perform the logic with which they are configured, no more and no less.
Although software robots will execute processes with 100% accuracy, if they are given “Data with errors”, they will process it the same as good data. One effective use of software robots is to use their capacity to complete repetitive work such as detailed comparisons and cross checking. Such activity is often defined as a background action, over 99% of the time everything will be aligned, but when the discrepancy is found the software robot can highlight it. Such monotonous tasks are ones where humans make more errors but where software robots deliver the required consistency.
Earlier, the concept of checklists was covered in the context of them being used to avoid human errors. When automation is being considered, another approach is to use the software robot to perform the checklist work as this delivers an independent action from the human activity and ensures a consistent application of the checklist criteria.
Human error is part of life, but effective processes and the appropriate use of software robots for automation can reduce the risks arising from human errors.
If you would like to learn more about software robots and their capabilities to reduce errors, please call Ether Solutions. Phone: 0845 643 4410
Subscribe to our LinkedIn Newsletter (New window) : "Business Beyond Automation".
Discover how automation with RPA and AI can unlock business growth, revenue and profits.
