{"id":6461,"date":"2016-06-28T19:55:03","date_gmt":"2016-06-28T19:55:03","guid":{"rendered":"https:\/\/multiacademstg.wpengine.com\/20000academy\/?p=6461"},"modified":"2025-04-04T10:11:16","modified_gmt":"2025-04-04T10:11:16","slug":"how-itil-can-help-reduce-the-gap-between-customers-and-the-it-department","status":"publish","type":"post","link":"https:\/\/advisera.com\/20000academy\/blog\/2016\/06\/28\/how-itil-can-help-reduce-the-gap-between-customers-and-the-it-department\/","title":{"rendered":"How ITIL can help reduce the gap between customers and the IT department"},"content":{"rendered":"<p>I have witnessed a situation where an IT department designed and implemented a service that they find useful and functional. And, no one else. The result was that resources were spent, service was implemented, but no one ever use it. The point is that the service was not something the customer needed, meaning \u2013 the service did not create any value in the customers\u2019 eyes. I\u2019m pretty sure that each of you will find similar examples.<\/p>\n<p>These days, people working in IT are pretty self-confident, particularly if they are in the same company for many years. And, they think that knowing the business or customers gives them the right to know who needs which service and why it is good for them. I would say \u2013 stop before you begin with the creation of such services or process changes. It\u2019s not IT who sets the pace \u2013 it\u2019s the customer. But, what do they care about? What\u2019s important for them? Let\u2019s see the customers\u2019 view and learn the\u00a0<a href=\"https:\/\/advisera.com\/20000academy\/what-is-itil\/\" target=\"_blank\" rel=\"noopener noreferrer\">ITIL<\/a>\u00a0approach to reducing the gap between customers and the IT department, i.e., IT service provider.<\/p>\n<h2><strong>Value<\/strong><\/h2>\n<p>The fact is that it\u2019s the <a href=\"https:\/\/advisera.com\/20000academy\/iso-20000-documentation-toolkit\/?rel=relationship-and-agreement-processes&#038;doc=customer-agreement-portfolio\" target=\"_blank\" rel=\"noopener\">customer<\/a>\u00a0who decides what is valuable or not (i.e. what creates value) to them. Not the IT. Maybe this statement sounds simple. But, my experience shows that, quite often, people in IT comment various situations like \u201cHow they (users) don\u2019t understand this\u2019\u201d, \u201cHow come they don\u2019t like this functionality?\u201d, \u201cIf they would use this application, their life would be much easier.\u201d\u2026 Honestly, from time to time I have also high expectations from my customers. I see the world with my eyes and not with the customers\u2019 one. And, that\u2019s wrong. To understand this thesis, let\u2019s consider the definition of value \u2013 \u201cThe benefits delivered in proportion to the resources put into acquiring them.\u201d From customers point of view &#8211; resources they put to acquire a service(s) are usually money they pay for the service(s). But, more important is \u2013 benefit they get. Since customer is paying for the service(s), they will decide whether the benefits gained are worth it.<\/p>\n<p>To get a better understanding, imagine you booked your vacation, you just arrived at the hotel, and you start gaining impressions. \u00a0Well, there could be the best-designed catalogue of that destination or sales person who is highly professional in selling tourist arrangements, but it\u2019s you and your impressions who will decide whether you like the hotel, destination, offerings\u2026 It\u2019s the same with IT customers and the services they use.<\/p>\n<p>Read the article\u00a0<a href=\"https:\/\/advisera.com\/20000academy\/blog\/2014\/11\/11\/itil-strategy-framing-the-value-of-services-part-i\/\">ITIL strategy \u2013 Framing the value of services (part I)<\/a>\u00a0to learn more about value.<br \/>\n<div id=\"middle-banner\" class=\"banner-shortcode\"><\/div><script>loadMiddleBanner();<\/script><br \/>\n<div id=\"side-banner-trigger\" class=\"banner-shortcode\"><\/div><\/p>\n<h2><strong>Utility<\/strong><\/h2>\n<p>Utility, or functionality, is what the service does. The point is that your customers need your services to do something. And, they are the only ones who know what exactly they need to do \u2013 that\u2019s their expectations towards the IT service(s). To gain a mutual understanding (of what creates value to the customer), you should talk to them and describe the functionality as detailed as possible. And, first of all \u2013 listen to what they are saying. Don\u2019t try to record the customer\u2019s description in a way to support your view of the functionality. It\u2019s the customer\u2019s view that is important.<\/p>\n<p>Utility should answer the question: \u201cWhat does the service need to do?\u201d Functionality of the service is just one half of the value description. Another one is the description of the customer\u2019s requirements, or warranty.<\/p>\n<p>Read the article <a href=\"https:\/\/advisera.com\/20000academy\/knowledgebase\/service-level-requirement-slr-origin-sla-content\/\" target=\"_blank\" rel=\"noopener noreferrer\">Service Level Requirement (SLR) as origin of the SLA content<\/a>\u00a0to learn more about service level requirements.<\/p>\n<h2><strong>Warranty<\/strong><\/h2>\n<p>Warranty describes how well the service is working. Namely, you can have the best service in the world (from a functionality point of view), but if it doesn\u2019t deliver at the level the customer needs \u2013 it\u2019s useless. And, again, it\u2019s the customer who knows what kind of service he wants to get. Here we talk about design of the service and the parameters that describe it. These parameters are security, service continuity, availability, and capacity.<\/p>\n<p>All those parameters need to be defined unambiguously and (if possible) in measurable units. In such way, you will avoid future misunderstandings. Parameters that describe warranty are usually a good foundation for the\u00a0<a href=\"https:\/\/advisera.com\/20000academy\/iso-20000-documentation-toolkit\/?rel=relationship-and-agreement-processes&#038;doc=service-level-agreement-sla-\" target=\"_blank\" rel=\"noopener\">Service Level Agreement (SLA)<\/a>. Warranty answers the question: \u201cHow is the service delivered?\u201d However, ITIL recommends that warranty should not be seen separately from utility, meaning design of the service has to have a tight connection with functionality. I know, it\u2019s logical, but also many times omitted.<\/p>\n<p>Read the article\u00a0<a href=\"https:\/\/advisera.com\/20000academy\/blog\/2015\/01\/27\/itil-service-level-agreements-designing-frameworks\/\">ITIL \u2013 Service Level Agreements: Designing frameworks<\/a>\u00a0to learn more about SLA.<\/p>\n<h2><strong>ITIL as an enabler<\/strong><\/h2>\n<p>The value that the customer expects can be achieved only when the service meets customer expectations (in the form of utility and warranty). But, there is one pitfall in this statement. What often happens is that customers are concerned about functionality and forget about characteristics of the service, i.e., warranty, until the service enters the live environment. You, as an IT service provider, should have established the IT Service Management (ITSM) structure (using ITIL will enable you to do that) and taken care about all warranty parameters right at the beginning of the service establishment. You gain because of the satisfied customer, and the customer gains because they will get value to the full extent and they will get a feeling of having professionals \u201con the other side\u201d (meaning \u2013 you).<\/p>\n<p>Let\u2019s resume \u2013 a service has value when it enables someone to do exactly what he needs to do. ITIL puts high importance on understanding the\u00a0<a href=\"https:\/\/advisera.com\/20000academy\/iso-20000-documentation-toolkit\/?rel=relationship-and-agreement-processes&#038;doc=service-level-requirements\" target=\"_blank\" rel=\"noopener\">customer\u2019s requirements<\/a>\u00a0and demand for functionality. During the whole service lifecycle these parameters are the cornerstone of all further activities. For example, ITIL recommends not continuing with IT service implementation until all parameters that describe the service are known and agreed with the customer. And, that\u2019s logical. Mistakes made later in the service lifecycle (e.g., just before going live) can be quite expensive, and I\u2019m sure no one wants that.<\/p>\n<p><em>To implement ISO 20000 easily and efficiently, use our<\/em> <a href=\"https:\/\/advisera.com\/20000academy\/iso-20000-documentation-toolkit\/\" target=\"_blank\" rel=\"noopener\">ISO 20000 Documentation Toolkit<\/a> <em>that provides step-by-step guidance for full ISO 20000 compliance.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"<p>I have witnessed a situation where an IT department designed and implemented a service that they find useful and functional. And, no one else. The result was that resources were spent, service was implemented, but no one ever use it. The point is that the service was not something the customer needed, meaning \u2013 the &#8230;<\/p>\n","protected":false},"author":32,"featured_media":17365,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[404,344,204,141,433,434,435],"class_list":["post-6461","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog","tag-customer","tag-itil","tag-service","tag-sla","tag-utility","tag-value","tag-warranty"],"acf":[],"_links":{"self":[{"href":"https:\/\/advisera.com\/20000academy\/wp-json\/wp\/v2\/posts\/6461","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/advisera.com\/20000academy\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/advisera.com\/20000academy\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/advisera.com\/20000academy\/wp-json\/wp\/v2\/users\/32"}],"replies":[{"embeddable":true,"href":"https:\/\/advisera.com\/20000academy\/wp-json\/wp\/v2\/comments?post=6461"}],"version-history":[{"count":3,"href":"https:\/\/advisera.com\/20000academy\/wp-json\/wp\/v2\/posts\/6461\/revisions"}],"predecessor-version":[{"id":18231,"href":"https:\/\/advisera.com\/20000academy\/wp-json\/wp\/v2\/posts\/6461\/revisions\/18231"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/advisera.com\/20000academy\/wp-json\/wp\/v2\/media\/17365"}],"wp:attachment":[{"href":"https:\/\/advisera.com\/20000academy\/wp-json\/wp\/v2\/media?parent=6461"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/advisera.com\/20000academy\/wp-json\/wp\/v2\/categories?post=6461"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/advisera.com\/20000academy\/wp-json\/wp\/v2\/tags?post=6461"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}