Skip to main content

The State of ITSM: One Company’s Assessment!

Here is an article I thought you might find interesting.  It was first published in itSMF USA's Source EJournal, April 2017.  

The State of ITSM: One Company’s Assessment!
By Keith D. Sutherland and Lawrence J. “Butch” Sheets

Educators and consultants operating in the formal practice of IT service management (ITSM) have largely been doing so since the mid-90s. Even though the best, codified practices of the IT service management framework, ITIL®, is now just over 30 years old, there remains a large number of organizations still in initial adoption of ITIL. 

And of those service providers with longer histories of using ITIL, many still have a significant need to increase maturity, or more fully implement their ITIL practice. The need in these companies for structured education, assessments, and roadmaps still abounds, even while multiple approaches for these practices are available for each. Beyond ITIL (and in many cases, alongside), are the many other evolving and emerging options of frameworks, standards, methodologies, and movements, including IT4IT™, DevOps, lean IT, agile, COBIT 5, simulations, not to mention SDLC, TOGAF®, PMBOK®, PRINCE2 Agile®, CMMI®, ISO/IEC 20000, USMBOK™, Six Sigma and others.

Information technology most would agree, is barely more than fifty years old. Today, mobile, cloud, analytics, IoT, digital, and other technologies dominate the IT landscape. At the same time, a company’s system of record (or legacy) capability could still be based on COBOL programming (and we first saw COBOL in 1973!). IT services emanate from all of these “point” solutions, whether legacy or emerging.

Although the intent of this article is not to understand all of the options for ITSM and IT, governance and the “center of gravity” concept help service providers ensure customers receive services that both provide value and support business outcomes at acceptable costs and risks.

The Need for Governance
Both ITSM and IT will and should continue to undergo transformational change. The real continual challenge for IT service providers lies in how to integrate ITSM and IT to help customers meet business outcomes. Most customers understand the concept of business outcomes or lagging indicators, but there is significant evidence that:
  • Internal customer-facing services are often left undefined. Without quantifying IT effort against business outcomes, it is difficult to express the value that an IT service provider contributes or identify the associated budget needed to support those outcomes.
  • Shadow IT (IT systems built without explicit organizational approval) continues to be pervasive, and it doesn’t matter the industry: internal IT is perceived as operational but not strategic (i.e., as a business partner).
  • Technical debt abounds. There is a trend in lessening investment in the operational aspects (leading to deficiencies in code, documentation, and computing environments), resulting in the overall inefficiency and ineffectiveness of the IT footprint. This lack of investment has resulted in not being able to keep up with the demand for IT services.
The impact of these three trends can be mitigated through stronger governance of ITSM (not to be confused with the governance of IT), value capture and a rolling ITSM roadmap. If the strategy is “beginning with the end in mind,” then a defined, documented, and a published plan needs to be understood and executed with defined roles and activities, trusted dates, and supported actions all of which constitute governance.

Download full article.


Popular posts from this blog

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People:   Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products:   These are the technology managem

What Is A Service Offering?

The ITIL4 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 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 than toiletries or chocolates are yours to take with you.   You the consumer own these and they are yours to take with you.               Note: Goods may not always be provided for every Service

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

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you. Roles and Responsibilities: Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance. Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables.  An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and th