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

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 policies (r…

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service".
I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize:
SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle.
ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with the needs …

Incidents when a Defect is Involved

Question: We currently track defects in a separate system than our ticket management system. With that said, my question is does anyone have suggestions and/or best practices on how to handle incidents when a defect is involved? Should the incident be closed since the defect is being worked on in another defect tracking system if it is noted in the incident ticket? I am considering creating an incident statuses of 'closed-unresolved' so the incident can still be reported on in our ticket management system but know it is being worked on/tracked in the defect system. With defects, it is possible that we may never work on them because they are very low priority and the impact is low to the user. However, in some cases a defect is being worked on. Should we create a problem ticket instead?
Thanks, René W.

Answer: René. In ITIL, the activity you are describing is handled by the Problem Management process. ITIL does not use the term “defect” but it does use the term “known error” to…