Skip to main content

Experience Level Agreements (XLAs) – Tick Tock!

It is a new day! The world of IT has changed from solely provisioning technology and services to actually being integral in the fulfillment of all business operations. It is time for staff and leaders to learn, get certified, evolve and most importantly to move forward with XLAs. As the climate of business operation changes it makes sense (or should make sense) that the way we measure and fulfill the provisioning of services must evolve to meet new challenges. This does not mean that SLAs are gone and XLAs are taking over. They can co-exist!

Traditional Service Level Agreements (SLAs) are sometimes rigid and can be restrictive in a world where the ability to shift and change with dynamic business needs are prevalent. Many of you can relate to those organizations that are meeting and exceeding SLAs only to find Customer Satisfaction (C-Sat) Scores are tanking. Internally the staff celebrate while the organization loses market share!

There is still a place for SLAs in the world and they remain an important element for the delivery of IT services. For digital environments, the evident need for Experience Level Agreements (XLAs) is obvious as we strive to focus on what, who and how the patterns of business/user experience are shifting. We have moved beyond needing to ensure the minimum level of service is maintained and delivered. As service and business providers we must be able to change when the business environment and consumer require it.

XLAs require a shift in thinking. Instead of thinking about tech and systems and only how they support, the perspective shifts. Honor the past, leverage from existing measurement models but know that in order to truly generate value we must keep that outside-in viewpoint. XLAs allow us to do that. As we shift the way we think and shift the focus to the consumer we must also shift the way we measure. Service provisioning requires that XLAs measure both hard and soft data to determine how satisfied customers and employees are with IT services. It’s a critical factor and it does not stop there. We need to be on top of things in order to monitor how those patterns are shifting so that we progress at the same rate as the demand for dynamic change evolves.

Research shows that companies are willing to pay more for better service. The industry expects the ability to leverage innovative and new technology. Internally, staff expect the ability to leverage cutting-edge cloud services that enable them to meet the day-to-day end-user business and customer experience. With a shift in thinking and a shift in measuring, XLAs will allow us to move from viewing targets with customers as penalties. We move into a more collaborative culture where we co-exist and co-create with our business partners. By deploying XLAs with closed-loop feedback cycles, data about how employees interact with IT services and how they feel when they encounter specific issues drives ongoing improvement to boost overall satisfaction.

Experience Level Agreements – Tick Tock, Tick Tock. The time is now, take action!!

To learn more, visit us on the web, check out this webinar, or consider registering for the ITSM Academy Essence of eXperience (XLA) Certification course.



Comments

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 then 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 Offe

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 the