Skip to main content

ISO 20K Can Be a Starting Point, Not a Destination

Since it's adoption, there has been a slow, but steady growth in the number of organizations that are seeking, or have achieved, ISO/IEC 20000 (ISO 20K) certification. For the most part, interest in the standard is being driven by RFP requirements or perceived competitive advantage. The certificate is seen as an "award" that an organization receives for achieving best practice ITSM. While ITIL is being actively adopted, many organizations are overlooking ISO 20K because they do not perceive any value in the certification.

I recently realized that we are looking at ISO/IEC 20000 in the wrong way. The standard has so much more to offer than just a certificate. It actually provides a starting place for an ITSM journey, not only the
destination.


ISO/IEC 20000 defines the "minimum critical activities" required to deliver high quality, aligned services. Once these activities are understood, an organization can assess which activities they already execute well and which may need implementation or improvement.

Here are some other benefits of ISO/IEC 20000:

  • It is succinct and easy to understand ("you shall record all incidents")

  • It applies to every internal or external IT organization regardless of size or industry

  • It distinguishes critical ITSM activities (in Part 1) from recommended activities (in Part 2)

  • It logically groups processes (Resolution, Service Delivery, Control, Relationship, Release) so you can build related processes together

  • It includes a Quality Management System with requirements for Management Responsibility, Training/Awareness/Competency, Documentation and Plan-Do-Check-Act

  • It is founded on continual improvement

  • It is objective and measurable and can help diffuse political or cultural challenges

There is no requirement that you adopt ITIL in order to implement ITSM according to ISO 20K. ITIL does offer a wealth of good knowledge that conforms to the standard. However, you can also cherry-pick guidance from other frameworks such as MOF or Cobit. Microsoft recently released a free Using MOF for ISO/IEC 20000 whitepaper. You can also meet the standard's requirements through successful, conformant, internal practices.

Whether you are at the beginning, underway or mature in IT Service Management, I would highly recommend learning more about the standard. It is available as a formal standard, digested ISO/IEC 20000 pocket guide or in several ISO/IEC 20000 books.

EXIN has also created a qualification scheme for ISO/IEC 20000 training and certification. You can explore the scheme at www.takeanotherlook.it. At the very least, I would recommend the ISO/IEC 20000 Foundation course for key staff involved in your ITSM implementation.

Striving for ISO/IEC 20000 certification is a management decision; using the standard as a tool for successful ITSM is just good management.

Comments

Jayne Groll said…
Ed Williams wrote an interesting blog that elaborates on this topic even further. Check it out at http://itsmadviser.com/portal/index.php?option=com_wrapper&view=wrapper&Itemid=4
Reading this post I completely agree with the topic.I mean that's true it is just the begining....
ITIL Version 3

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