SHARE
Follow this article on Twitter Facebook LinkedIn Bookmark and Share
Home >> Integrating IT

Delivering IT services without ‘grandma’s quilt’

Delivering IT services without ‘grandma’s quilt’

By:  Kathleen Lau  On: 18 Aug 2010 For: ComputerWorld Canada Creator

An ITIL V3 chief architect lists what organizations should do when sourcing new tools to support their IT service management strategies, and the things they should definitely avoid

It’s never easy choosing the best tools to support your organization's IT service management (ITSM) strategy. The same aches and pains are met by most IT departments during the decision-making process, not the least of which is making the mistake of sticking with an existing tool simply because it’s comfy.

ITIL V3 chief architect Sharon Taylor calls this common error “grandma’s quilt” when organizations make the fateful decision to continue using a product because they’ve got so used to the functionality.

“We tend to find comfort in things that are familiar to us and often tools that we’ve used for a very long time give us a sense of comfort,” said Taylor during a recent Webcast about how not to choose tools for your ISTM strategy.

Organizations later “realize these older tools are often full of holes,” added Taylor.

Another reason for wanting to stick to familiar tools is a reluctance to throw away the investment made in legacy systems over the years. Taylor calls this “innovation past its time” when the tools are no longer serving their purpose yet they don’t get replaced.Nominate someone you work with for a ComputerWorld Canada IT Leadership Award

And neither is it a good idea to salvage legacy systems by customizing them to force them to fit current business needs because that just costs more over time, said Taylor.

Here are some tips organizations can follow to acquiring tools for their ITSM strategies, according to Taylor:

1.Identify successful processes in the business and create “outcome statements” that will help define the delivery model for acquiring ITSM tools. For instance, an outcome statement would be: We need to trend incident patterns by using a common classification system.

2.Ask the business for their desired quality of IT service because often they have a much better view of quality of service than IT people do. “There are strategic implications in the tools we select and the functionality that they have,” said Taylor.

3.Differentiate between mandatory and desirable functionality by walking through established processes and identifying a list of tool functions that can support different steps. Also, identify points of integration that additional tool functionality can help.

4.Build a requirements list of functions and classify by priority. Also, classify them by processes to ensure that all areas are covered by the tools. But don’t forget about performance of the tools, said Taylor, because a tool bursting with functionality is useless if it doesn’t perform to your standards. “You have to consider both,” she said.


Sign up for our Newsletters
Tags: ITIL, itsm, IT service












Print |  Views: 3942   |   Rating:offoffoffoffoff  (0 votes)
Rate this article on a scale of
1 to 5 stars,5 being the best.




Kathleen Lau Kathleen Lau was a senior writer with ITWorldCanada.com and ComputerWorld Canada from December 2006 to August 2011.In her role as senior writer, she covered broadly technology news and issues r... more

Comments (0)

No Comments!
Name: (required) eMail: (optional)

Your email address will not appear online and will be used only if the editor wishes to contact you personally for additional comments.