Tuesday 26 June 2012

Who is accountable for application sprawl?

In my last post I mentioned application sprawl. In many organisation, like self replicating nano-bots, the list of applications that enables the business to function increases uncontrollably. The IT organisation tries to bring some order to this chaos with limited success.

We try demand management techniques, which may be designed to help people to stop and think but are largely seen as barriers to change,dampeners on the springs of agility. We enforce standards, erect governing bodies and create IS Strategies (aligned with business strategies, of course). Despite all this effort there are still the exceptions justified by "my case is special"; and let's not open the can of worms that is self-built solutions - those excel spreadsheets, access databases and (heaven forbid) the unauthorised use of free services on the web.

This is application sprawl, and it exists to some degree or another in every organisation large enough to have an IT department (and probably many that don't as well).

Who is accountability for this sprawl? In the end it is the holder of the purse strings who fail to understand the implications of their decisions, the leaders who create the culture that nurtures this behaviour and the watchmen who understand what is happening and fail in their task to open the eyes of others. In my experience ongoing, open discussion, developing a mutual understanding (often teasing these out through interrogation) of the motivations, showing pragmatism not dogmatism and playing the long game (not winning every battle) is the most effective approach.

In the end, this is not a tug-of-war between IS and "The Business"; this is about recognising an issue that affects the bottom line of the organisation and working together to resolve it.

No comments: