Home > Articles > Information Technology

📄 Contents

  1. Management Reference Guide
  2. Table of Contents
  3. Introduction
  4. Strategic Management
  5. Establishing Goals, Objectives, and Strategies
  6. Aligning IT Goals with Corporate Business Goals
  7. Utilizing Effective Planning Techniques
  8. Developing Worthwhile Mission Statements
  9. Developing Worthwhile Vision Statements
  10. Instituting Practical Corporate Values
  11. Budgeting Considerations in an IT Environment
  12. Introduction to Conducting an Effective SWOT Analysis
  13. IT Governance and Disaster Recovery, Part One
  14. IT Governance and Disaster Recovery, Part Two
  15. Customer Management
  16. Identifying Key External Customers
  17. Identifying Key Internal Customers
  18. Negotiating with Customers and Suppliers—Part 1: An Introduction
  19. Negotiating With Customers and Suppliers—Part 2: Reaching Agreement
  20. Negotiating and Managing Realistic Customer Expectations
  21. Service Management
  22. Identifying Key Services for Business Users
  23. Service-Level Agreements That Really Work
  24. How IT Evolved into a Service Organization
  25. FAQs About Systems Management (SM)
  26. FAQs About Availability (AV)
  27. FAQs About Performance and Tuning (PT)
  28. FAQs About Service Desk (SD)
  29. FAQs About Change Management (CM)
  30. FAQs About Configuration Management (CF)
  31. FAQs About Capacity Planning (CP)
  32. FAQs About Network Management
  33. FAQs About Storage Management (SM)
  34. FAQs About Production Acceptance (PA)
  35. FAQs About Release Management (RM)
  36. FAQs About Disaster Recovery (DR)
  37. FAQs About Business Continuity (BC)
  38. FAQs About Security (SE)
  39. FAQs About Service Level Management (SL)
  40. FAQs About Financial Management (FN)
  41. FAQs About Problem Management (PM)
  42. FAQs About Facilities Management (FM)
  43. Process Management
  44. Developing Robust Processes
  45. Establishing Mutually Beneficial Process Metrics
  46. Change Management—Part 1
  47. Change Management—Part 2
  48. Change Management—Part 3
  49. Audit Reconnaissance: Releasing Resources Through the IT Audit
  50. Problem Management
  51. Problem Management–Part 2: Process Design
  52. Problem Management–Part 3: Process Implementation
  53. Business Continuity Emergency Communications Plan
  54. Capacity Planning – Part One: Why It is Seldom Done Well
  55. Capacity Planning – Part Two: Developing a Capacity Planning Process
  56. Capacity Planning — Part Three: Benefits and Helpful Tips
  57. Capacity Planning – Part Four: Hidden Upgrade Costs and
  58. Improving Business Process Management, Part 1
  59. Improving Business Process Management, Part 2
  60. 20 Major Elements of Facilities Management
  61. Major Physical Exposures Common to a Data Center
  62. Evaluating the Physical Environment
  63. Nightmare Incidents with Disaster Recovery Plans
  64. Developing a Robust Configuration Management Process
  65. Developing a Robust Configuration Management Process – Part Two
  66. Automating a Robust Infrastructure Process
  67. Improving High Availability — Part One: Definitions and Terms
  68. Improving High Availability — Part Two: Definitions and Terms
  69. Improving High Availability — Part Three: The Seven R's of High Availability
  70. Improving High Availability — Part Four: Assessing an Availability Process
  71. Methods for Brainstorming and Prioritizing Requirements
  72. Introduction to Disk Storage Management — Part One
  73. Storage Management—Part Two: Performance
  74. Storage Management—Part Three: Reliability
  75. Storage Management—Part Four: Recoverability
  76. Twelve Traits of World-Class Infrastructures — Part One
  77. Twelve Traits of World-Class Infrastructures — Part Two
  78. Meeting Today's Cooling Challenges of Data Centers
  79. Strategic Security, Part One: Assessment
  80. Strategic Security, Part Two: Development
  81. Strategic Security, Part Three: Implementation
  82. Strategic Security, Part Four: ITIL Implications
  83. Production Acceptance Part One – Definition and Benefits
  84. Production Acceptance Part Two – Initial Steps
  85. Production Acceptance Part Three – Middle Steps
  86. Production Acceptance Part Four – Ongoing Steps
  87. Case Study: Planning a Service Desk Part One – Objectives
  88. Case Study: Planning a Service Desk Part Two – SWOT
  89. Case Study: Implementing an ITIL Service Desk – Part One
  90. Case Study: Implementing a Service Desk Part Two – Tool Selection
  91. Ethics, Scandals and Legislation
  92. Outsourcing in Response to Legislation
  93. Supplier Management
  94. Identifying Key External Suppliers
  95. Identifying Key Internal Suppliers
  96. Integrating the Four Key Elements of Good Customer Service
  97. Enhancing the Customer/Supplier Matrix
  98. Voice Over IP, Part One — What VoIP Is, and Is Not
  99. Voice Over IP, Part Two — Benefits, Cost Savings and Features of VoIP
  100. Application Management
  101. Production Acceptance
  102. Distinguishing New Applications from New Versions of Existing Applications
  103. Assessing a Production Acceptance Process
  104. Effective Use of a Software Development Life Cycle
  105. The Role of Project Management in SDLC— Part 2
  106. Communication in Project Management – Part One: Barriers to Effective Communication
  107. Communication in Project Management – Part Two: Examples of Effective Communication
  108. Safeguarding Personal Information in the Workplace: A Case Study
  109. Combating the Year-end Budget Blitz—Part 1: Building a Manageable Schedule
  110. Combating the Year-end Budget Blitz—Part 2: Tracking and Reporting Availability
  111. References
  112. Developing an ITIL Feasibility Analysis
  113. Organization and Personnel Management
  114. Optimizing IT Organizational Structures
  115. Factors That Influence Restructuring Decisions
  116. Alternative Locations for the Help Desk
  117. Alternative Locations for Database Administration
  118. Alternative Locations for Network Operations
  119. Alternative Locations for Web Design
  120. Alternative Locations for Risk Management
  121. Alternative Locations for Systems Management
  122. Practical Tips To Retaining Key Personnel
  123. Benefits and Drawbacks of Using IT Consultants and Contractors
  124. Deciding Between the Use of Contractors versus Consultants
  125. Managing Employee Skill Sets and Skill Levels
  126. Assessing Skill Levels of Current Onboard Staff
  127. Recruiting Infrastructure Staff from the Outside
  128. Selecting the Most Qualified Candidate
  129. 7 Tips for Managing the Use of Mobile Devices
  130. Useful Websites for IT Managers
  131. References
  132. Automating Robust Processes
  133. Evaluating Process Documentation — Part One: Quality and Value
  134. Evaluating Process Documentation — Part Two: Benefits and Use of a Quality-Value Matrix
  135. When Should You Integrate or Segregate Service Desks?
  136. Five Instructive Ideas for Interviewing
  137. Eight Surefire Tips to Use When Being Interviewed
  138. 12 Helpful Hints To Make Meetings More Productive
  139. Eight Uncommon Tips To Improve Your Writing
  140. Ten Helpful Tips To Improve Fire Drills
  141. Sorting Out Today’s Various Training Options
  142. Business Ethics and Corporate Scandals – Part 1
  143. Business Ethics and Corporate Scandals – Part 2
  144. 12 Tips for More Effective Emails
  145. Management Communication: Back to the Basics, Part One
  146. Management Communication: Back to the Basics, Part Two
  147. Management Communication: Back to the Basics, Part Three
  148. Asset Management
  149. Managing Hardware Inventories
  150. Introduction to Hardware Inventories
  151. Processes To Manage Hardware Inventories
  152. Use of a Hardware Inventory Database
  153. References
  154. Managing Software Inventories
  155. Business Continuity Management
  156. Ten Lessons Learned from Real-Life Disasters
  157. Ten Lessons Learned From Real-Life Disasters, Part 2
  158. Differences Between Disaster Recovery and Business Continuity , Part 1
  159. Differences Between Disaster Recovery and Business Continuity , Part 2
  160. 15 Common Terms and Definitions of Business Continuity
  161. The Federal Government’s Role in Disaster Recovery
  162. The 12 Common Mistakes That Cause BIAs To Fail—Part 1
  163. The 12 Common Mistakes That Cause BIAs To Fail—Part 2
  164. The 12 Common Mistakes That Cause BIAs To Fail—Part 3
  165. The 12 Common Mistakes That Cause BIAs To Fail—Part 4
  166. Conducting an Effective Table Top Exercise (TTE) — Part 1
  167. Conducting an Effective Table Top Exercise (TTE) — Part 2
  168. Conducting an Effective Table Top Exercise (TTE) — Part 3
  169. Conducting an Effective Table Top Exercise (TTE) — Part 4
  170. The 13 Cardinal Steps for Implementing a Business Continuity Program — Part One
  171. The 13 Cardinal Steps for Implementing a Business Continuity Program — Part Two
  172. The 13 Cardinal Steps for Implementing a Business Continuity Program — Part Three
  173. The 13 Cardinal Steps for Implementing a Business Continuity Program — Part Four
  174. The Information Technology Infrastructure Library (ITIL)
  175. The Origins of ITIL
  176. The Foundation of ITIL: Service Management
  177. Five Reasons for Revising ITIL
  178. The Relationship of Service Delivery and Service Support to All of ITIL
  179. Ten Common Myths About Implementing ITIL, Part One
  180. Ten Common Myths About Implementing ITIL, Part Two
  181. Characteristics of ITIL Version 3
  182. Ten Benefits of itSMF and its IIL Pocket Guide
  183. Translating the Goals of the ITIL Service Delivery Processes
  184. Translating the Goals of the ITIL Service Support Processes
  185. Elements of ITIL Least Understood, Part One: Service Delivery Processes
  186. Case Study: Recovery Reactions to a Renegade Rodent
  187. Elements of ITIL Least Understood, Part Two: Service Support
  188. Case Studies
  189. Case Study — Preparing for Hurricane Charley
  190. Case Study — The Linux Decision
  191. Case Study — Production Acceptance at an Aerospace Firm
  192. Case Study — Production Acceptance at a Defense Contractor
  193. Case Study — Evaluating Mainframe Processes
  194. Case Study — Evaluating Recovery Sites, Part One: Quantitative Comparisons/Natural Disasters
  195. Case Study — Evaluating Recovery Sites, Part Two: Quantitative Comparisons/Man-made Disasters
  196. Case Study — Evaluating Recovery Sites, Part Three: Qualitative Comparisons
  197. Case Study — Evaluating Recovery Sites, Part Four: Take-Aways
  198. Disaster Recovery Test Case Study Part One: Planning
  199. Disaster Recovery Test Case Study Part Two: Planning and Walk-Through
  200. Disaster Recovery Test Case Study Part Three: Execution
  201. Disaster Recovery Test Case Study Part Four: Follow-Up
  202. Assessing the Robustness of a Vendor’s Data Center, Part One: Qualitative Measures
  203. Assessing the Robustness of a Vendor’s Data Center, Part Two: Quantitative Measures
  204. Case Study: Lessons Learned from a World-Wide Disaster Recovery Exercise, Part One: What Did the Team Do Well
  205. (d) Case Study: Lessons Learned from a World-Wide Disaster Recovery Exercise, Part Two

When the 39 industry experts from business, government and academia began developing the first version of ITIL in Great Britain during the mid 1980s, they quickly realized that IT service management was the common link on which the numerous best practices of IT infrastructure management was based. Service management in general focuses the quality of products and services on the reasonable expectations of customers. When applied to an IT environment, service management focuses the quality of its IT services on the reasonable business expectations of its customers and end-users. In ITIL terminology, end-users are defined as the day-to-day users of IT services while customers are defined as the managers of these end users.

IT Service Management (ITSM) bridges the gap between the business goals of a company and the technology used to accomplish those goals. It sets up formalized and regular communications channels to allow requirements, requests and difficulties to be expressed and dealt with. This serves the very important function of ensuring IT aims are correctly aligned to the business.

This notion of IT service management was not always prevalent within IT. In fact, as the IT industry passed through its infancy and adolescent stages, there was little or no emphasis on service management. How, then, did IT environments evolve from being totally technical entities into world-class service-oriented organizations? The next section answers that question.

How IT Evolved into Service-Oriented Organizations

Most IT organizations began as offshoots of their company's accounting departments. As companies grew and their accounting systems became more complex, their dependency on the technology of computers also grew. The emphasis of IT in the 1970s was mostly on continually providing machines and systems that were bigger, faster, and cheaper. During this era, technological advances in IT flourished. Two factors led to very little emphasis on customer service.

First, in the 1970s the IT industry was still in its infancy. Organizations were struggling just to stay abreast of all the rapidly changing technologies, let alone focus on good customer service. Second, within most companies the IT department was the only game in town, so to speak. Departments that were becoming more and more dependent on computers—finance, engineering, and administration, for example— were pretty much at the mercy of their internal IT suppliers, regardless of how much or how little customer service was provided.

By the 1980s, the role of IT and customer service began changing. IT was becoming a strategic competitive advantage for many corporations. A few industries such as banking and airlines had long before discovered how the quality of IT services could affect revenue, profits, and public image. As online applications started replacing many of the manual legacy systems, more and more workers became exposed to the power and the frustration of computers. Demand for high availability, quick response, and clear and simple answers to operational questions gave rise to user groups, help desks, service level agreements, and eventually customer service representatives, all within the confines of a corporate structure.

Good customer service was now becoming an integral part of any well-managed IT department. By the time the decade of the 1990s rolled around, most users were reasonably computer literate; PCs and the Internet were common fixtures in the office and at home; the concept of customer service transitioned from being hoped for to being expected. Demands for excellent customer service grew to such a degree in the 1990s that the lack of it often led to demotions, terminations, and outsourcing.

Whether IT professionals were prepared for it or not, IT had evolved from a purely accounting and technical environment into a totally service-oriented one. Companies hiring IT professionals now often use traits such as empathy, helpfulness, patience, resourcefulness, and being team-oriented as requirements for the job. The extent to which these traits are in evidence frequently determines an individual's, or an organization's, success in IT today.

Other Factors Driving IT Service Management

Several other factors help drive the IT industry to become more service-oriented, and the truly successful organizations understand and respond to these factors.

Competition: We see IT everywhere these days and it affects all our lives. If your IT service delivery lets you down, you will lose customers. In high volume, real-time industries such as online travel or banking, you may lose them immediately. Providing a framework for successful Customer retention is one of the prime deliverables of ITSM.

Increased dependency on IT: Most organizations could not function as a business without acceptable levels of IT service availability and reliability.

Higher visibility of service failures: If things do go wrong, the impact on the business is more likely to be noticed quickly.

More exacting customer demands: A general increase in computer literacy, particularly amongst customers, has led to a higher expectation of what is required from IT services, and a reduction in their level of tolerance of faults and failures in the IT services.

Increased complexity of the IT infrastructure: IT services are delivered by a complex mix of hardware, software, networks and people. It is essential that all these components are managed effectively and efficiently as poor performance of any one component can seriously affect the quality of the overall IT service.

Services and Service Management

ITIL is a service management framework, so let's talk about what services are. A service is what is perceived by the customer as a service. The important point here is that if you have defined your services without including your customers in the process you have no assurance you are providing what is really needed. It is important that the services are defined in conjunction with customers.

Service management is a total organizational approach that makes quality of service, as perceived by the customer, the number one driving force of the operation of the business. In the context of IT, service management is ensuring the provision of the highest quality of IT services required by the customer to accomplish business goals.

IT service management is driven by the following three objectives:

  • To ensure that the organization's business needs are underpinned by high quality, cost effective, value-adding IT Services
  • To improve the quality of IT service provision
  • To reduce the long term cost of service provision

IT operations exist to develop, deliver, support and maintain services which support one or more business operations. They are not 'in business' for IT reasons alone. Wherever applicable these services should enhance as well as underpin business operations. Service management is also a philosophy or mindset that encompasses: enacting a service culture, recasting individuals, teams, and organizations as IT service providers, and enacting processes that underpin the creation and delivery of services that meet changing business needs and expectations, conceptualizing and running IT as a business, as opposed to an overhead function.

Service management is about managing the client service experience and infrastructure, where a service is set of related functions IT provides that are seen by the Customer as a coherent, self-contained entity, and infrastructure is everything that underpins service delivery, including people, processes, and technology. This means Service management requires a focus on the relationships with customers that include sometimes difficult conversations about what is needed to consistently deliver on service commitments

Summary

Service management is 'service-centric' as opposed to 'client-centric' or 'technology centric'. Being service-centric means systematically managing both client expectations and perceptions, and the technology infrastructure required to consistently deliver on those expectations. As the ITIL framework started taking shape, the overriding emphasis on service management became very evident. As we explore the different ITIL processes in upcoming sections, we will see how being 'service centric' manifests itself, and why it is so valuable.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.