Good Article - 2 key mindsets that have assisted in creating this scenario.
This article pretty much sums it up. There are however 2 other issues that were touched on but which I have drawn my own conclusions over the years.
1 - Pretty much all organisation consider IT as only a cost centre (as opposed to a profit centre). They therefore continually press for reduction in operating costs. The lack of real intelligence is startling as there seems to be little appreciation of the fact that without IT the organisation will cease to be. In the RBS case it would be very interesting to see the figures provided for the cost savings of the IT restructure and how that stacks up against the financial impact of this one incident (I'm sure there are others that have costs the organisation but have not been so widely publicised)
2 - The change management regeime at RBS has (for many, many years) been driven with the wrong philosphy. It is run like a police state. They use it to create fear and to enable isolation of staff at fault. The change management process SHOULD be a service for the IT function (as well as other business areas) to facilitate change. I should assist in ensuring change is implemented in the correct manner , with the correct considerations and as efficiently as possible. As intimated in the article, the process is so complex @ RBS that the staff involved in change spend so much time on the administration that (given difficulties with obtaining change windows and the volume of change that is required to keep the operation running), that administration takes away focus from the technical detail. Again as the article indicates each time there is a change related technical incident , the WHOLE of the IT business endures increased process/admin, in most cases complete lock down. Which again creates backlog of mandatory change (either technical to remain on supported versions, or regulatory to ensure tha bank is allowed to operate). The whole situation creates inevitable failure and only does more so as time goes on and a multiplier effect takes hold.
Both of the above can be explained by the management style at the bank, where it's extremely rare for management to be challanged by their direct reports once you get past the front line technical staff.