IT and the culture of blame

When IT projects go wrong - and it's safe to assume that for every one that gets publicity, there are five which get covered up - the knee-jerk reaction is to blame the vendor.

"They missed their deadline" "their technology doesn't work" "their products failed to live up to the hype".

All are familiar cries heard emanating from desperate IT departments.

But while the vendors should indeed take responsibility for their part in these cock-ups, they should not be used as scapegoats for the failings of inhouse IT staff and processes.

"The missed their deadline." That's caused by poor project management, perhaps.

"Their technology doesn't work." That's a result of a less than rigorous tender process, perhaps.

"Their products failed to live up to the hype." For every bit of sales spiel, there's someone listening to it - and believing it.

The implications of this go way beyond one project falling flat on its face. How can IT ever be taken seriously by business managers if they point the finger of blame at third parties as soon as things go off the rails?

It's time to stop shirking responsibility for failure, and being more open about it. It comes as a shock when someone as respected as Dr Richard Sykes, the outgoing chief information officer of ICI, says that users are just as culpable as vendors when it comes to eulogising technology (see http://www.silicon.com/a32173 )

It shouldn't be a shock. IT should stand up and be counted. That takes a bold IT manager - but ultimately, it will go a long way in gaining the respect of business executives.