www.itbusinessedge.com

Login Register

www.itbusinessedge.com

 

www.developer.com

Login Register

www.developer.com

 

www.developer.com

Login Register

www.developer.com

 

www.itbusinessedge.com

Login Register

www.itbusinessedge.com

 
Internet.com logo
IT Professionals
Communications

Database

Enterprise Applications

Hardware

IT Management

IT News

Mobile

Networking

Security

Server

Small Business

Storage

ITManagement
CIO Update

Datamation

Earthweb

Enterprise IT Planet

Intranet Journal

IT Career Planet

IT Channel Planet

ITSM Watch

Project Manager Planet

Developers
Architect

Java / OS

Microsoft Technology

Web Development

Sign in Sign in

http://www.itsmwatch.com/itil/article.php/3863596/How-to-Measure-ITIL-Service-Utility-and-Warranty.htm
Back to Article

By Hank Marquis
Feb 8, 2010

The ITIL v3 definition of quality is "the ability of a product, service, or process to provide the intended value." The ITIL Service Strategy book describes utility and warranty as forming the basis of value for IT service consumers. Simply put, according to ITIL, get utility and warranty right, and you are providing the intended value, which means you have a high quality service with satisfied customers.

We can see that from an ITIL perspective, service quality consists of two components: utility (fitness for purpose) and warranty (fitness for use.) But how, exactly, do you measure fitness for use or purpose? Is it even possible to develop a score, a value, for a service based on utility and warranty?

What Your Customers Say

The short answer is yes, you can measure utility and warranty; and yes, you can create a number that represents the combined quality (utility + warranty) "score" of a service.

First, the ITIL definitions and explanations of both are a matter of record. ITIL states, "Utility is perceived by the customer from the attributes of the service that have a positive effect on the performance of tasks associated with desired outcomes." The ITIL glossary adds that utility is "[f]unctionality offered by a product or service to meet a particular need. Utility is often summarized as 'what it does'."

ITIL describes warranty as "[a] promise or guarantee that a product or service will meet its agreed requirements" and as "derived from the positive effect of being available when needed, in sufficient capacity, and dependably in terms of continuity and security."

Second, note how the explanation of utility refers to "attributes" and, in the case of warranty, to availability, capacity, continuity and security. Also, note how the explanation of warranty mentions effects. Utility and warranty seem to be placeholders for one or more other concepts related to service delivery. In other words, there is no test per-se for utility or warranty. Instead, it appears that satisfying multiple factors across several dimensions is the key achieving service quality from an ITIL utility and warranty perspective.

Third, the revelation in understanding how to measure utility and warranty reside in the discussion of utility―"Utility is perceived by the customer from the attributes of the service." We already discussed "attributes", but do note the words "perceived by the customer." It seems then that the definition of a quality service can only arise from the perceptions of its customers, and further, the customer makes this determination based on examining multiple attributes of service delivery. This means that to measure service quality (utility and warranty) one must exit the data center, and discover consumer perception―actually solicit customer expectations and perceptions. Service quality is what your customers say it is. So, it seems that you cannot measure IT service quality from inside the data center, at least not according to ITIL v3.

Inside the Data Center

This point is lost however, since so few actually know how to measure consumer perceptions. Luckily, measuring customer perception of satisfaction across multiple dimensions to determine quality is not a new idea. Albeit not well know to IT managers, the de facto continual service quality improvement methodology SERVQUAL is over 20 years old. Its less diagnostic cousin SERVPERF is approaching it's 15th birthday. Even the ITIL v3 Continual Service Improvement (CSI) book includes a model derived from the more mature SERVQUAL. These models all revolve around the primary concepts of customer perception and expectation. These methodologies provide precisely the guidance we need to do measure and take action on ITIL v3 utility and warranty.

SERVQUAL and SERVPERF both operate on the idea that any service has just five (5) dimensions, some of which the definition of utility calls just "attributes of the service" and others called out by name. SERVQUAL is not an IT specific domain and did not arise from an e-services point of view. SERVQUAL is a comprehensive quality measurement and improvement system. Its five dimensions have titles, and each title has detailed explanations, examples, causes, symptoms and solutions. These five dimensions are Reliability, Responsiveness, Assurance, Empathy and Tangibles. These terms probably need some explanation:

  • Reliability is the "Ability to perform the promised service dependably and accurately." In other words, what it does or fitness for purpose―from an ITIL perspective: its utility. A reliable service as measured by SERVQUAL is one that provides the required functionality.
  • Responsiveness is the "Willingness to help customers and provide prompt service." Providing prompt service pertains to the concepts of capacity, performance and latency making the dimension of Responsiveness an attribute of warranty.
  • Assurance is the "Knowledge and courtesy of employees and their ability to inspire trust and confidence." Inspiring trust and confidence during interactions with consumers spans continuity and security, and thus, is part of warranty.
  • Empathy is the "Caring, individualized attention the firm provides its customers." It includes listening in a caring fashion, making an effort to understand, and making consumer needs their top priority. Empathy can arise from offering convenient business hours or being available for support or service when needed, and so on―another component of warranty.
  •  Tangibles describe the "Appearance of physical facilities, equipment, personnel, and communication materials"―think the usability of documentation, interfaces, handsets, keyboards, monitors, etc. All of which fit neatly under the "how its delivered" concepts of warranty.

The SERVQUAL Reliability dimension appears to equate very well to ITIL utility and answers the "does it do what it needs to do" question that encapsulates utility. The other four SERVQUAL dimensions (Responsiveness, Tangibles, Assurance and Empathy) pertain mostly to warranty – "how it does it." Therefore, using SERVQUAL (or it's cousin SERVPERF) you can measure the five dimensions of a service, and discover the services' utility and warranty.

Given that ITIL CSI very clearly references SERVQUAL, and the importance of the concepts of utility and warranty to service strategy, it only makes sense for service managers to extend the concepts of service quality outside of the data center and adopt customer perception and expectation as valid IT metrics of service quality. From one point of view, anything less is not only failing to measure service quality, but also more predictive than actual, and certainly not diagnostic and actionable.

The ITIL v3 definition of quality is "the ability of a product, service, or process to provide the intended value." The ITIL Service Strategy book describes utility and warranty as forming the basis of value for IT service consumers. Simply put, according to ITIL, get utility and warranty right, and you are providing the intended value, which means you have a high quality service with satisfied customers.

We can see that from an ITIL perspective, service quality consists of two components: utility (fitness for purpose) and warranty (fitness for use.) But how, exactly, do you measure fitness for use or purpose? Is it even possible to develop a score, a value, for a service based on utility and warranty?

What Your Customers Say

The short answer is yes, you can measure utility and warranty; and yes, you can create a number that represents the combined quality (utility + warranty) "score" of a service.

First, the ITIL definitions and explanations of both are a matter of record. ITIL states, "Utility is perceived by the customer from the attributes of the service that have a positive effect on the performance of tasks associated with desired outcomes." The ITIL glossary adds that utility is "[f]unctionality offered by a product or service to meet a particular need. Utility is often summarized as 'what it does'."

ITIL describes warranty as "[a] promise or guarantee that a product or service will meet its agreed requirements" and as "derived from the positive effect of being available when needed, in sufficient capacity, and dependably in terms of continuity and security."

Second, note how the explanation of utility refers to "attributes" and, in the case of warranty, to availability, capacity, continuity and security. Also, note how the explanation of warranty mentions effects. Utility and warranty seem to be placeholders for one or more other concepts related to service delivery. In other words, there is no test per-se for utility or warranty. Instead, it appears that satisfying multiple factors across several dimensions is the key achieving service quality from an ITIL utility and warranty perspective.

Third, the revelation in understanding how to measure utility and warranty reside in the discussion of utility―"Utility is perceived by the customer from the attributes of the service." We already discussed "attributes", but do note the words "perceived by the customer." It seems then that the definition of a quality service can only arise from the perceptions of its customers, and further, the customer makes this determination based on examining multiple attributes of service delivery. This means that to measure service quality (utility and warranty) one must exit the data center, and discover consumer perception―actually solicit customer expectations and perceptions. Service quality is what your customers say it is. So, it seems that you cannot measure IT service quality from inside the data center, at least not according to ITIL v3.

Inside the Data Center

This point is lost however, since so few actually know how to measure consumer perceptions. Luckily, measuring customer perception of satisfaction across multiple dimensions to determine quality is not a new idea. Albeit not well know to IT managers, the de facto continual service quality improvement methodology SERVQUAL is over 20 years old. Its less diagnostic cousin SERVPERF is approaching it's 15th birthday. Even the ITIL v3 Continual Service Improvement (CSI) book includes a model derived from the more mature SERVQUAL. These models all revolve around the primary concepts of customer perception and expectation. These methodologies provide precisely the guidance we need to do measure and take action on ITIL v3 utility and warranty.

SERVQUAL and SERVPERF both operate on the idea that any service has just five (5) dimensions, some of which the definition of utility calls just "attributes of the service" and others called out by name. SERVQUAL is not an IT specific domain and did not arise from an e-services point of view. SERVQUAL is a comprehensive quality measurement and improvement system. Its five dimensions have titles, and each title has detailed explanations, examples, causes, symptoms and solutions. These five dimensions are Reliability, Responsiveness, Assurance, Empathy and Tangibles. These terms probably need some explanation:

  • Reliability is the "Ability to perform the promised service dependably and accurately." In other words, what it does or fitness for purpose―from an ITIL perspective: its utility. A reliable service as measured by SERVQUAL is one that provides the required functionality.
  • Responsiveness is the "Willingness to help customers and provide prompt service." Providing prompt service pertains to the concepts of capacity, performance and latency making the dimension of Responsiveness an attribute of warranty.
  • Assurance is the "Knowledge and courtesy of employees and their ability to inspire trust and confidence." Inspiring trust and confidence during interactions with consumers spans continuity and security, and thus, is part of warranty.
  • Empathy is the "Caring, individualized attention the firm provides its customers." It includes listening in a caring fashion, making an effort to understand, and making consumer needs their top priority. Empathy can arise from offering convenient business hours or being available for support or service when needed, and so on―another component of warranty.
  •  Tangibles describe the "Appearance of physical facilities, equipment, personnel, and communication materials"―think the usability of documentation, interfaces, handsets, keyboards, monitors, etc. All of which fit neatly under the "how its delivered" concepts of warranty.

The SERVQUAL Reliability dimension appears to equate very well to ITIL utility and answers the "does it do what it needs to do" question that encapsulates utility. The other four SERVQUAL dimensions (Responsiveness, Tangibles, Assurance and Empathy) pertain mostly to warranty – "how it does it." Therefore, using SERVQUAL (or it's cousin SERVPERF) you can measure the five dimensions of a service, and discover the services' utility and warranty.

Given that ITIL CSI very clearly references SERVQUAL, and the importance of the concepts of utility and warranty to service strategy, it only makes sense for service managers to extend the concepts of service quality outside of the data center and adopt customer perception and expectation as valid IT metrics of service quality. From one point of view, anything less is not only failing to measure service quality, but also more predictive than actual, and certainly not diagnostic and actionable.


The ITIL v3 definition of quality is "the ability of a product, service, or process to provide the intended value." The ITIL Service Strategy book describes utility and warranty as forming the basis of value for IT service consumers. Simply put, according to ITIL, get utility and warranty right, and you are providing the intended value, which means you have a high quality service with satisfied customers.

We can see that from an ITIL perspective, service quality consists of two components: utility (fitness for purpose) and warranty (fitness for use.) But how, exactly, do you measure fitness for use or purpose? Is it even possible to develop a score, a value, for a service based on utility and warranty?

What Your Customers Say

The short answer is yes, you can measure utility and warranty; and yes, you can create a number that represents the combined quality (utility + warranty) "score" of a service.

First, the ITIL definitions and explanations of both are a matter of record. ITIL states, "Utility is perceived by the customer from the attributes of the service that have a positive effect on the performance of tasks associated with desired outcomes." The ITIL glossary adds that utility is "[f]unctionality offered by a product or service to meet a particular need. Utility is often summarized as 'what it does'."

ITIL describes warranty as "[a] promise or guarantee that a product or service will meet its agreed requirements" and as "derived from the positive effect of being available when needed, in sufficient capacity, and dependably in terms of continuity and security."

Second, note how the explanation of utility refers to "attributes" and, in the case of warranty, to availability, capacity, continuity and security. Also, note how the explanation of warranty mentions effects. Utility and warranty seem to be placeholders for one or more other concepts related to service delivery. In other words, there is no test per-se for utility or warranty. Instead, it appears that satisfying multiple factors across several dimensions is the key achieving service quality from an ITIL utility and warranty perspective.

Third, the revelation in understanding how to measure utility and warranty reside in the discussion of utility―"Utility is perceived by the customer from the attributes of the service." We already discussed "attributes", but do note the words "perceived by the customer." It seems then that the definition of a quality service can only arise from the perceptions of its customers, and further, the customer makes this determination based on examining multiple attributes of service delivery. This means that to measure service quality (utility and warranty) one must exit the data center, and discover consumer perception―actually solicit customer expectations and perceptions. Service quality is what your customers say it is. So, it seems that you cannot measure IT service quality from inside the data center, at least not according to ITIL v3.

Inside the Data Center

This point is lost however, since so few actually know how to measure consumer perceptions. Luckily, measuring customer perception of satisfaction across multiple dimensions to determine quality is not a new idea. Albeit not well know to IT managers, the de facto continual service quality improvement methodology SERVQUAL is over 20 years old. Its less diagnostic cousin SERVPERF is approaching it's 15th birthday. Even the ITIL v3 Continual Service Improvement (CSI) book includes a model derived from the more mature SERVQUAL. These models all revolve around the primary concepts of customer perception and expectation. These methodologies provide precisely the guidance we need to do measure and take action on ITIL v3 utility and warranty.

SERVQUAL and SERVPERF both operate on the idea that any service has just five (5) dimensions, some of which the definition of utility calls just "attributes of the service" and others called out by name. SERVQUAL is not an IT specific domain and did not arise from an e-services point of view. SERVQUAL is a comprehensive quality measurement and improvement system. Its five dimensions have titles, and each title has detailed explanations, examples, causes, symptoms and solutions. These five dimensions are Reliability, Responsiveness, Assurance, Empathy and Tangibles. These terms probably need some explanation:

  • Reliability is the "Ability to perform the promised service dependably and accurately." In other words, what it does or fitness for purpose―from an ITIL perspective: its utility. A reliable service as measured by SERVQUAL is one that provides the required functionality.
  • Responsiveness is the "Willingness to help customers and provide prompt service." Providing prompt service pertains to the concepts of capacity, performance and latency making the dimension of Responsiveness an attribute of warranty.
  • Assurance is the "Knowledge and courtesy of employees and their ability to inspire trust and confidence." Inspiring trust and confidence during interactions with consumers spans continuity and security, and thus, is part of warranty.
  • Empathy is the "Caring, individualized attention the firm provides its customers." It includes listening in a caring fashion, making an effort to understand, and making consumer needs their top priority. Empathy can arise from offering convenient business hours or being available for support or service when needed, and so on―another component of warranty.
  •  Tangibles describe the "Appearance of physical facilities, equipment, personnel, and communication materials"―think the usability of documentation, interfaces, handsets, keyboards, monitors, etc. All of which fit neatly under the "how its delivered" concepts of warranty.

The SERVQUAL Reliability dimension appears to equate very well to ITIL utility and answers the "does it do what it needs to do" question that encapsulates utility. The other four SERVQUAL dimensions (Responsiveness, Tangibles, Assurance and Empathy) pertain mostly to warranty – "how it does it." Therefore, using SERVQUAL (or it's cousin SERVPERF) you can measure the five dimensions of a service, and discover the services' utility and warranty.

Given that ITIL CSI very clearly references SERVQUAL, and the importance of the concepts of utility and warranty to service strategy, it only makes sense for service managers to extend the concepts of service quality outside of the data center and adopt customer perception and expectation as valid IT metrics of service quality. From one point of view, anything less is not only failing to measure service quality, but also more predictive than actual, and certainly not diagnostic and actionable.


Doing the Math

After measuring customer perception using SERVQUAL, you can also combine raw scores into a value (not the value or worth of the service, but rather a numeric representation of the services' utility and warranty.) For example, consider a utility score of 71% (based on Reliability perception scores) and a composite score of 65% (based on the average of the other dimensions). The average of these two values is 68%; a quantitative representation of qualitative consumer perception of service utility and warranty.

Using SERVQUAL, you have an understandable quality metric based on business engagement. It is not a technical operational metric like those found in so many SLAs, nor is it an assumption of expected quality. This value represents ITIL utility and warranty, and thus true service quality.

Since SERVQUAL also provides a minimum and maximum observation set, you can determine areas of possible advantage and differentiation, as well as perhaps cost controls. The expectation components of SERVQUAL create a "box" or sorts. Upper and lower boundaries of expectations indicate "how much" utility and warranty the customer wants. The perception components of SERVQUAL indicate "how well" the service meets utility and warranty requirements. Taken together, this approach to service measurement is both business aligned and actionable. [Note: The main difference between SERVQUAL and SERVPERF is this diagnostic ability. SERVPERF only collects current performance perception, it does not collect or determine upper and lower boundaries for service quality as does SERVQUAL.]

Consider a SERVQUAL score of 100% of expectations to mean the service meets minimum quality requirements, then a score:

  • Higher than 100% is either "over doing it" (e.g., perhaps wasting money) or possibly represents an advantage to the provider and its customers. Determine which it is and take action accordingly.
  • Less than 100% means something in the utility or warranty are off. Unlike non-diagnostic "inside out" technical measurements (or even "outside-in" SERVPERF), the "outside-in" nature of measuring utility and warranty using SERVQUAL is inherently diagnostic so you know exactly what must improve, and to what degree. As a bonus, the previous measurements are baselines and useful for showing progress.

You can even use these utility and warranty dimensional importance observations to modify components if you want. Part of SERVQUAL is a collection of weighting for the dimensions. This technique develops a custom model of importance by dimension for your customers. Normally this simply means asking the customer to allocate 100 points across the five dimensions, assigning points to each dimension based on how important it is to that customer. For example, if customers say that Assurance was very important, you could boost it by multiplying it with an importance weighting factor. This would have the effect of increasing (or decreasing) warranty level.

Contemplate using utility and warranty as the means to implement ITIL, or drive business/IT integration and alignment. Think about replacing a complex and technical SLA with an easy to understand Service Quality index or score. Consider the ramifications of providing clear, transparent guidance to the IT organization.

Hank Marquis is practice leader for Business Service Management at Global Knowledge. Reach Hank at hank.marquis@globalknowledge.com.


 

Sitemap | Contact Us
Terms of Service | Licensing & Permissions | Privacy Policy
About the Developer.com Network | Advertise
Terms of Service | Licensing & Permissions | Privacy Policy
About the IT Business Edge Network | Advertise
Acceptable Use Policy
Terms of Service | Licensing & Permissions | Privacy Policy
About the Developer.com Network | Advertise
Acceptable Use Policy
Terms of Service | Licensing & Permissions | Privacy Policy
About the IT Business Edge Network | Advertise