We need a Bank IT Stress Test, and we need it now

This summer will be remembered for a number of things: the London 2012 Olympics surely. A Brit winning the Tour de France, if you're so inclined. And the first time widespread banking IT outages gained national prominence. And just like climate change scientists will tell you there will be more rain and more often, I'm here to tell you that there will be more banking IT outages and more often.

Why? I hear you ask. Glad you did. Let me try and explain. The average bank's IT can best be seen as a series of what can charitably be described as sheds built on quicksand. These sheds were made from available materials; which means that some of the sheds are built using 1960's technology. Some of the sheds (the later sheds) were made from prefab standardised components. And some of the sheds are built using cutting edge not-yet-proven technology. (Let's call those the marketing sheds). And of course, there is an intricate system of hallways, doorways and trapdoors, to connect all the sheds in an infinite number of ways. This way, whenever a door or hallway is blocked, there is a possibility of getting to another shed, you just don't know how.

 So how did this come about, and what are we going to do about it? 


 The reason this all happened is pretty simple: no management attention. Early on, "automation" was a logical follow-up to using calculators and tabulating machines. They merely sped up an existing process. By the time it became clear that IT is a disruptive force, the sheds were firmly sinking in the quicksand. Anyone with any ambition as a manager within a large bank quickly realised this and decided to run for the marketing or the investment side of the bank.

 What are we going to do about it? The first step towards any solution is admitting you have a problem. Even in the light of overwhelming evidence to the contrary, most boards of banks still feel IT is a non-core activity. The only thing the board seems interested in is IT cost, which should be lower.