- The business is rarely satisfied with IT service levels, yet there is no clear definition of what is acceptable.
- Dissatisfaction with service levels is often based on perception. Your uptime might be four 9s, but the business only remembers the outages.
- IT is left trying to hit a moving target with a limited budget and no agreement on where services levels need to improve.
Our Advice
Critical Insight
- Business leaders have service level expectations regardless of whether there is a formal agreement. The SLA process enables IT to manage those expectations.
- Track current service levels and report them in plain language (e.g. hours and minutes of downtime, not “how many 9s” which then need to be translated) to gain a clearer mutual understanding of current versus desired service levels.
- Use past incidents to provide context (how much that hour of downtime actually impacted the business) in addition to a business impact analysis to define appropriate target service levels based on actual business need.
Impact and Result
Create an effective internal SLA by following a structured process to report current service levels and set realistic expectations with the business. This includes:
- Defining the current achievable service level by establishing a metrics tracking and monitoring process.
- Determining appropriate (not ideal) business needs.
- Creating an SLA that clarifies expectations to reduce IT-business friction.
Search Code: 76572
Last Revised: October 26, 2015