Skip to main content

Our disjointed human world

Yes, there is a customer out there and you need to take into consideration his view. But don't discount that view at the expense of a technology view. The reverse is also true where an exclusive view is taken from the technology, discounting the human component. What is required is a balance. It is not as easy as asking the customer or business what they want and blindly executing on that objective. Invariably, the technology will fail and even if it doesn't the second pitfall is that the goalposts will change.
Client's and customer's perceive new processes even if they are more effective and provide added value in a negative fashion. That is because of the underlying lesson in the "Monkey banana experiment." Read about it here.
Humans, like monkeys, do things like they use to do it (and for that reason only.) Habit is the biggest comfort zone and change is automatically resisted. No amount of propaganda about a better way changes the view. To illustrate my point, I'll provide a few examples:
  1. Some countries drive on the left hand side of the road and others on the right hand side of the road. Why not all agree to the same side of the road?
  2. Some countries have imperial measurements still in existence while others are purely metric. The name says it all, "imperial!" It should have died with Queen Victoria but it stays around because of habit.
  3. Banning the import of Cuban cigars? Why?
  4. The English language. There is British English and American English and each has separate dictionaries. Who cares how you spell colour/color or centre/center?
  5. Ditto keyboards!
  6. Video and DVD formats?
  7. Pence and cents?
  8. Electrical connectors and 115V vs 220V?
and so on...

The only reason the above disparities exist is human habit where once someone has become use to something they will not change. In IT a new process is ridiculed and resisted, not because it doesn't add value or isn't effective and efficient, but because it wasn't done like that yesterday.

I don't really have a solution to this problem. Do you?

Comments

Popular posts from this blog

Why Madge Networks, the token-ring company, went titsup

There I was shooting the breeze with an old mate. The conversation turned to why Madge Networks which I wrote about here went titsup. My analysis is that Madge Networks had a solution and decided to go out and find a problem. They deferred to more incorrect strategic technology choices. The truth of the matter is that when something goes titsup, its not because of one reason only, but a myriad of them all contributing to the negative consequence. There are the immediate or visual ones, which are underpinned by intermediate ones and finally after digging right down, there are the root causes. There is never a singular root cause for anything but I'll present my opinion and encourage everyone else to chip in. All of them together are more likely the reason the company went titsup. As far as technology brainfarts go there is no better example than Kodak . They invented the digital camera that killed them. However, they were so focused on milking people in their leg

Flawed "ITIL aligned"​ Incident Management

Many "ITIL aligned" service desk tools have flawed incident management. The reason is that incidents are logged with a time association and some related fields to type in some gobbledygook. The expanded incident life cycle is not enforced and as a result trending and problem management is not possible. Here is a fictitious log of an incident at PFS, a financial services company, which uses CGTSD, an “ITIL-aligned” service desk tool. Here is the log of an incident record from this system: Monday, 12 August: 09:03am (Bob, the service desk guy): Alice (customer in retail banking) phoned in. Logged an issue. Unable to assist over the phone (there goes our FCR), will escalate to second line. 09:04am (Bob, the service desk guy): Escalate the incident to Charles in second line support. 09:05am (Charles, technical support): Open incident. 09:05am (Charles, technical support): Delayed incident by 1 day. Tuesday, 13 August: 10:11am (Charles, technical support): Phoned Alice.

A checklist for troubleshooting network problems (22 things to catch)

  Assumptions! What is really wrong? Is it the network that is being blamed for something else? Fully describe and detail the issue . The mere act of writing it down, often clarifies matters. Kick the tyres and do a visual inspection. With Smartphones being readily available, take pictures. I once went to a factory where there was a problem. Upon inspection, the network equipment was covered in pigeon pooh! The chassis had rusted and the PCB boards were being affected by the stuff. No wonder there was a problem. In another example, which involved radio links. It is difficult with radio links to remotely troubleshoot alignment errors. (I can recall when a heavy storm blew some radio links out of alignment. Until we climbed onto the roof we never realised how strong the wind really was that day!) Cabling. Is the cable actually plugged in? Is it plugged into the correct location. Wear and tear on cabling can also not b