Main Menu
Home / IT Governance / Legacy Support / Why You Can’t Ignore ITSM

Why You Can’t Ignore ITSM

ITSM is a necessity that no one would refute. Most are familiar with and utilize in some manner ITIL, PRINCE2, and/or CoBIT frameworks. These methods are time tested and improve IT structures. However, there are those who believe these frameworks to be too constraining and that blind adherence of them is not always beneficial. ITSM can often distract from the original commissioning of IT departments; IT should aid in the benefit of achieving their company’s goals.

Below are some excerpts to think about:

All models are wrong

Brian Clark, CIO of Melbourne-based university, RMIT, is happy to be quoted as saying that he “doesn’t give a stuff” about frameworks such as ITIL. He does, however, quantify that by saying when he started at RMIT, the organisation was plagued by regular and ongoing SAP outages that were happening as a result of badly managed internal processes.

“One of my favourite quotes is from mathematician George Box who said; ‘All models are wrong but some are useful’”, Clark said. “When it comes to ITSM models, I think people get too caught up in the idea of process, frameworks and ideology.

Early success, vital ammunition

“On the upside, from our established benchmark we were then able to demonstrate the improvements we were making. Those operational performance metrics are now allowing us to have the type of conversations we should be having about systems availability, which has a direct business-impact.

“Indeed, increasingly that conversation is coming back to me from the senior executives at the University. They now understand the opportunity for IT service management to support and drive core business objectives.”

Clark believes that the foundation of an IT leader’s role is to manage existing systems and applications really well before you can look at investing.

About Ryan Malinoski

Ryan Malinoski was a staff writer and technical assistant for CAI’s Accelerating IT Success. He joined the team in 2013.

Check Also

COBOL Is Still Around Because Nothing Better Has Replaced It

When COBOL was made in 1959, no one could have dreamed that it would outlive …

Leave a Reply

Your email address will not be published. Required fields are marked *

Sorry, but this content
is for our subscribers only!

But subscribing to ACCELERATING IT SUCCESS is FREE and only one click away!
Join more than 40,000 IT Professionals and get the best IT management articles to your mailbox with Accelerating IT Success!

Unsubscribe at any time