Skip to main content

WTF? Why the Failure?


Through the implementation of best practices, one of ITSM's critical success factors is to enhance the business' perception of the IT organization.  By creating a service strategy which helps to define good design, encourage effective transition processes and deliver valuable services through efficient and effective operational management, we work hard at making this goal a reality. Unfortunately, IT is often perceived to be ineffective and inefficient. 
Recently, the government’s inability to deliver a working website for the affordable care act was splashed all over  news with many of my non-IT friends and family asking, how could this happen?  How come IT people never get it right?
I want to respond with “BUT WE DO” and list many of the successes that I have been part of during my career.   But I look at them sheepishly and respond with” I don’t really know”.  As I think about this, I begin to get angry and not just because I’m an American tax payer, but because as an IT professional, I know the kinds of tools that we as an industry have at our disposal to ensure that these kinds of failures should never happen. Given the development of integrated tool sets, best practice frameworks, auditable standards and the focus on continual improvement it is inconceivable that a professional organization could deliver a product of such poor quality? Unfortunately, it happens and more often than we want to admit. 
The thing that is most disturbing for me is that ringing in my ears of “How come you IT people never get it right?”  It seems we have a lot more work in front of us, to enhance the public’s perception of our industry.  Perception is often reality and a successful service management program has to recognize and address internal and external perceptions of IT's ability and performance.   It's not easy but is quite possible when the message is one of learning from past successes and failures as part of your continual improvement.

Comments

Popular posts from this blog

Four Service Characteristics

Recently I came across several articles by researchers and experts that laid out definitions and characteristics of services. ITIL provides us with a definition that can help drive the creation of value-laden services: A means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks. An area that ITIL is not so clear is in terms of service characteristics. Several researchers and experts put forth that services have four basic characteristics (IHIP): Intangibility—Services are the results of actions not things. They have no physical presence and represent a logical set of elements. One way to think of service is “work done for others.”  Heterogeneity—Also known as “variability”; services are unique items because of the mechanisms used to deliver services, which is people. Because the people element adds variability, the service is variable. This holds true, especially for the value proposition—not eve...

What Is A Service Offering?

The ITIL 4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group.   As a service provider, we can’t stop there!   We must know what the contracts of our service offering are and be able to put them into context as required by the customer.     Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include:     Goods, Access to Resources, and Service Actions 1. Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods.   Example of goods that are being provided in the offering – If this is a hotel service then toiletries or chocolates are yours to take with you.   You the consumer own these and they are yours to take with you.      ...

What is the difference between Process Owner, Process Manager and Process Practitioner?

This article was originally published in 2015. With the Introduction of ITIL 4, some of this best practice has changed. See  ITIL 4 and the Evolving Role of Roles . Updated Definitions in ITIL 4: Process Owner: In ITIL 4, the concept of 'processes' has expanded into broader 'practices.' Consequently, the Process Owner is now often referred to as the 'Practice Owner.' This individual is accountable for the overall design, performance, integration, and improvement of a specific practice within the organization. They ensure that the practice achieves its intended outcomes and aligns with the organization's objectives. Process Manager: Now commonly known as the 'Practice Manager' in ITIL 4, this role is responsible for the day-to-day management of the practice. The Practice Manager ensures that activities are carried out as intended, manages resources assigned to the practice, and oversees the practitioners performing the work. Process Practit...