Download the authoritative guide: Cloud Computing 2018: Using the Cloud to Transform Your BusinessI was buying some clothes at a major department store the other day and was struck by the extra effort the clerk was putting in -- simply because of a lack of standards. And if it was causing a problem in this store, imagine what it would do in your IT department.
The problem arose from those anti-theft ink tags that are attached to some clothes to dissuade shoplifters. If they're not removed with the proper tool at the store, they often burst and plash ink all over the clothing.
What was gumming up the works was the fact that the tags weren't attached to all the clothes, and when they were, they weren't always attached in the same place. My bet is that it took the sales clerk at least five times longer to check, fold and bag my clothes simply because of the lack of standards regarding these tags and what they're attached to.
It was the perfect example of the inefficiencies caused by a lack of standards.
What I knew for sure was that the store was dealing with wasted productivity, and the potential for customers to become frustrated with the added delays in the checkout line.
All of this was happening because of a lack of standards (or multiple standards), poor training, and the wrong message coming down from the top.
Standards and Training
With standardization comes many efficiencies.
Simple standards make employee training simpler because there is only one ''way'' to do something. People can develop and share best practices because they are all working from a common context.
Better yet, in IT, there are best practices that are developed and shared by various bodies. For example, the British Government's Office of Government Commerce maintains the Information Technology Infrastructure Library (ITIL), which is a treasure trove of best practices for IT.
Now, simply having standards is not enough.
Without adequate training so all practitioners can understand what needs to be done, deviations will occur. It is far too easy to create a list of standards and policies that are never used because no one knows they exist or they aren't taught how to apply them.
Another problem area relates to senior management -- their actions and the way they communicate. Both aspects can impact workers' adherence to standards dramatically. For example, management may say that the ink tags are important, but if they do not allocate enough resources to getting all the clothing tagged, then employees will see that the standards really don't matter.
Actions, or inactions, can make or break the best of standards.
Lastly, multiple standards can be problematic as can multiple scenarios of when to apply a given criteria. For example, if process A, B or C can be performed with different outcomes, then people downstream of that process can be left wondering when one standard is applied, compared to another.
In terms of people following a given process, the more selection criteria they must remember concerning when to follow the process, the greater the likelihood that they will fail to follow the process correctly. If we think of it in terms of a simple function, the probability of an error increases exponentially as the number of decision makers and potential choices increases.
What About IT?
Right now, many organizations are rushing to implement standard policies and procedures for regulatory compliance. In their rush, they must factor in the impact of standardization on a formerly variable organization, as well as training, complexity and communication from upper management.
Organizations, regardless of their function, must consider human factors in their process design or risk errors, inefficiencies and failed audits -- all arising from their attempts to adopt, if not outright force into place, standard policies and procedures. All too often, we overemphasize technology at the expense of people and appropriate process.
In this day and age, we can no longer do that as we risk far more than an overlooked ink tag soiling our new purchases.