One of the things that we all know as IT professionals is that our industry has a truly appalling failure rate. It has always been there and over recent years I have seen nothing particularly change. Statistics suggest that failure rates are 40% but I suspect that the truth is much higher. Some of these failures will be through projects simply taking too long to deliver the required benefits in a timely manner. I have seen for example Windows 7 projects started as part of a Microsoft TAP program before the OS was released being overtaken by the imminent (6 months) release of Windows 8.
Why is it that these projects take so long? Well a lot of it is down to complexity the products chosen, their configuration and the method of deployment all become highly complex. This is especially so when they are deployed into a preexisting large environment. There is however another possibility, it is us that is over complicating the delivery of these projects.
A few months ago I bought my Son a new mobile phone, he’s a Maths geek who spends a lot of time on the computer. I selected a smart phone that I believed would give him maximum functionality and reduce the number of gadgets that he needed to carry. A few days ago I asked him how one of the programs on it worked and he told me he had no idea he’d never tried it. This surprised me and on further discussion I realised he had tried pretty much none of the advanced functionality of the phone. “It’s like this Dad” he said “I use it for making phone calls and sending texts”.
My knowledge of technology and the potentials of the device lead me to select something considerably beyond what his use of the device required. The people selecting technology for our businesses are also extremely technical and vulnerable to the same conceits. I have seen outsourced projects fail because in house technical staff have mandated architectural elements of the outsourced service. I have also seen selection of simpler products or services overruled by technical opinion, only for the extra facilities obtained to never be used.
I feel this is an indicator that there is still not enough input from the actual end user in the decisions that are made. Even when an end user is involved, the end user tends to pick an IT aware individual from their organisation as their representative and this person has the same tendency to select technology. This is especially likely when you work in an engineering based organisation! The trick is to choose an individual that knows the business purpose inside and out but professes to be bad with computers. Once selected the temptation to sell them the IT options they need must also be avoided, especially if they appear to want less than you feel you should give them.
One last point nowadays I often hear technical staff telling me how Cloud services will never work; that we will always have in house facilities and that cloud is just the latest buzzword. This time it is different though, always in the past making the new technology work has always required the input of the technical people. With Cloud all a business needs to adopt the services is a computer and an Internet connection. Cloud services give the business the chance to choose technology support that is sufficient for them with out added complication from us. If IS departments want to remain relevant they must get better and choosing technology.