Menu
Menu
Australian bank to keep IT frontline in country

Australian bank to keep IT frontline in country

ANZ Bank is giving the market-driven fashion of offshoring IT and support center services a firm reality check, with a senior executive revealing his organization intends to keep customer-facing services in Australia.

ANZ Bank is giving the market-driven fashion of offshoring IT and support center services a firm reality check, with a senior executive revealing his organization intends to keep customer-facing services in Australia. Addressing the Information Technology Services Management Forum (ITSMF) in Brisbane Tuesday, John Young, ANZ senior manager for technology production risk, said his bank will keep both its customer support and internal level one IT support at home because of a commitment to quality of service for both customers and staff.

"ANZ will not outsource its customer contact [services]... ANZ will not outsource its [IT] service desk," Young said, noting that a commitment to excellence in customer service remained a key differentiator for his bank.

Explaining how ANZ has adopted ITIL (Information Technology Infrastructure Library) to better manage IT costs and investments, Young said there are plenty of savings to reap from IT if proven management methodologies such as incident and problem analysis are formalized and applied.

At ANZ, this has included setting up an ITIL-based, centralized system to notify, monitor, locate and resolve IT problems and incidents, backed by causal and systemic analysis. Describing the ITIL project as "a healthy self-interest that is relevant", Young said so far the system has reduced IT incidents from 25,000 to 15,000 a month, or 20 percent.

Describing the ITIL repository as a powerful tool, "because it gives us single reports", Young also warned IT managers to take a good hard look at the way they tracked IT problem and incident resolution, because losing focus on IT performance was both easy and a costly trap to fall into.

He said this included cutting down on low severity and automatically-generated event notifications which find their way into systems reporting -- and shutting down inconsistent, self-spawned incident databases.

"Someone had a few [Microsoft] Access skills. [They] built something...institutionalized it...and left. Then someone else came along and had a play -- and infuriated lots of people in the process. There are a lot of very highly paid techies who spend a lot of time cutting and pasting into Excel. To the disgust of certain consultants, we banned the term 'known error'."

Another strategy Young has employed is turning the IT mirror back on line-of-business managers so that non-IT staff can accept responsibility for the impact, including expenditure, their decisions have on infrastructure.

"We made a decision to record [risk-based] decisions [such as] where a database is not backed up because it is too expensive. That's an accepted risk and that's recorded," Young said.

"We needed to understand the relationship between change and incident creation. It's a numbers game." -- Computerworld Australia

Join the CIO New Zealand group on LinkedIn. The group is open to CIOs, IT Directors, COOs, CTOs and senior IT managers.

Join the newsletter!

Error: Please check your email address.
Show Comments

Market Place