SHIFTING YOUR SERVICE MANAGEMENT STRATEGY

No matter how strong your service strategy is, it was most likely put to the test during 2020 as your service teams were challenged with providing customer support during the novel coronavirus (COVID-19) crisis.

Any crisis, including this pandemic, can severely impact businesses and customers alike. Whether you fell into the group who planned ahead or scrambled to develop a contingency plan, it's important to keep in mind that a crisis may pose different challenges every day, so you’ll need to continuously assess and adapt your strategic plan.

Read on to discover the four most important things to assess and adjust in your service management strategy during a crisis. A good place to start is to consider the big picture - ask yourself: How is my service strategy going to be impacted? What components of my strategy must change, and how do I prioritize these changes?

Now, take a step back and review your current strategy before making adjustments. Here are the challenges that may possibly arise, what will be impacted most and what to focus on first.

1. REVIEW YOUR CONTRACTS

The most important question to ask when reviewing your service strategy in a crisis is: What’s the contractual impact going to be during (and immediately following) this situation?

As a service provider, your service level agreements (SLAs) to customers, regardless if they are internal or external to your organization, are likely to be impacted. Now is the time to evaluate your most important contracts to ensure you can meet your obligations, and if not, re-prioritize them and address what may need to change and include business stakeholders where necessary. If your service level agreements are internal, then try to determine what the impact might be if there is a fundamental change in the way your entire business operates. With all of your internal staff working remotely, what is the impact on your ability to deliver service within your internal SLA’s?

For example, your service teams may experience an overload of requests from panicked customers that lead to higher volumes of work, which means that your team’s target close time for a particular type of non-urgent request may get lower priority and thus, an uncommon increase in resolution turnaround time.

If this is the case, you’ll need to determine whether you have provisions in place in your contracts for SLA changes. If you do, you may need to implement them for the remainder of the crisis to mitigate disruption to your service as much as possible and reset customer expectations. If you don’t have provisions in place, you’ll need to figure out what SLAs can and can’t change and address how to deal with SLA adjustments as soon as you can.

The key to making any adjustments to your contractual obligations is ensuring you communicate them to the right people, so that they know why and how your business services are changing.

2. CONSIDER THE TECHNICAL IMPACT

The next important piece of your service strategy to review is the technical impact a crisis will have on your organization. Is it “business as usual” for you? This is doubtful. Even if your business continues to thrive, how you continue to do so will shift.

Now you’ll need to ask yourself and your department the following: If required, is your staff capable of working remotely, and are your networks ready for a higher volume of remote workers? Do you have collaboration and communication tools in place to support people across the organization effectively, especially if they need to work remotely?

The situation may require the need to acquire, provision and support new hardware and software if your staff needs to work from home. You must also think about whether your company is required to provide better working environments for your staff (not everyone will have access to a comfortable office chair and desk) and if your workers are insured. It’s crucial to consider what parts of the business need altered supplies and processes and what the protocol will be for implementing and monitoring these changes.

Ultimately, the technical impact will result in financial implications. How much will the changes in processes and tools cost your company, and what budget shifts need to be made for those changes to happen? Keep this at the forefront of your strategy as you navigate each day of the crisis.

Are you breaching any contractual obligations like HIPPA by allowing staff to work remotely? Does it introduce data security risks? Are others not in your organization going to overhear/see things they should not? These are all important considerations to keep in mind as you review and implement your service strategy.

3. DON'T FORGET THE HUMAN EXPERIENCE

Because service management is about serving people, you’ll also need to determine what the human impact is going to be, not just for your customers, but also for your employees.

It’s time to take a close look at your service team structure. Is it still applicable if your service teams need to work remotely in case of a building shutdown? There may be essential and non-essential employees within your organization, so some employees may still be required to come into the office. How do you plan to support each group of individuals?

Working remotely can also be isolating, so consider how your organization plans to keep teams in communication with one another (both for business brainstorms and for social interaction) to keep morale high.

Keep in mind that everyone—customers, employees and leadership included—will likely experience some stress and anxiety both at work and personally during the situation. To minimize confusion and fear, be as responsive and upfront as possible in your communications regarding the new status quo. If your employees and customers have clarity into what is occurring and how you as a leader are dealing with it, the less concerned and more cooperative they will be.

4. VERIFY THE STATUS OF YOUR VENDORS

Now it’s time to assess your vendors. After all, how they modify their strategies might affect yours. With that in mind, have you assessed how prepared your vendors are for daily shifts in crisis management? If they’re not ready, how does your company need to respond?

First, evaluate your company’s most critical applications that your organization needs in order to stay operational and reach out to those vendors. If your vendors can no longer meet your business needs, consider an alternative vendor that may have solutions geared toward your altered requirements or certain product and supplies in stock that your current vendor doesn’t.

Before choosing this route, inquire how easy it is to switch vendors during and after the crisis to make sure the switch is worth your effort, time and money.

CONCLUSION

When it comes to providing service and having service management strategies in place, the primary goal of providing excellent service doesn’t change, even during a crisis. And while having a strategic plan in place is crucial to your department—and your company’s—success, it’s important to be flexible enough to alter your strategic plans to maintain business procedures and prevent widespread concern among your teams and customers should an unexpected situation arise.

• Contractual Obligations
• Technical Impact
• Impact on Humans
• Status of Vendors

By prioritizing these four pieces first, you’ll be as prepared as possible for a crisis and be able to monitor and adjust your company goals and plans accordingly.

WHAT ARE OPERATIONAL LEVEL AGREEMENTS?

In order to provide excellent customer service, you need to meet your service level agreements (SLAs): the agreements you have with your customers about the level of service you’ll provide. But how do you make sure you’re doing that? And if you’re not doing it, how do you understand why? The first step is making sure you hit your internal goals: your operational level agreements (OLAs).

Whereas SLAs are focused on the customer, OLAs are in place to describe the level of service your internal teams can expect from each other. These might include relationships between your front line service desk and the teams who support them: network support, operations management, application management, desktop engineers, etc..

They can–and should!–be used as a key metric in service management because they allow teams to understand where bottlenecks are, and why they’re not hitting those all-important SLAs. OLAs should also be transparent so that everyone knows what their own targets are, and the impact it has on the rest of the business.

However, sometimes service teams bite off more they can chew when attempting to measure SLAs and ultimately fail to meet them. Instead of setting goals for the sake of having them, start small by clarifying or setting up OLAs within your ITSM software tool. From there, you can begin building out SLAs.

Here’s how you can use task management in Vivantio to ensure your OLAs are being met.

TASK MANAGEMENT IN VIVANTIO

Task management in Vivantio can help companies meet OLAs and, in turn, meet target SLAs. Task management can be enabled in all ticket types in the Vivantio service management platform.

In Vivantio Pro, you can assign tasks to licensed technicians. Vivantio ITSM goes a step further and allows you to assign tasks to both licensed technicians and non-licensed end-users.

With task management enabled, technicians can create tasks for the different work required to complete the ticket. The list of tasks can be viewed easily from the ticket. Tasks have the same core capabilities as tickets, including their own set of configurations (categories, status, etc.) and of course a full history of the work done.

There are three ways that tasks are created in Vivantio: Ad hoc as needed, via trigger rules, and through Vivantio’s workflows. Regardless of the way tasks are created, you can easily view them from the ticket to track progress. Here are examples of creating a task using each way.

AD HOC TASK CREATION

Within Vivantio, users can create ad-hoc tickets as needed in order to request internal or external help to meet an OLA. Perhaps a technician is working on a P4 support request that came in with a corresponding SLA of 16 hours. While working on the request, they discover they’re not trained in a specific area of the required work and will need to ask their colleague for help.

To do this, they can manually assign out an ad-hoc task from within the ticket to their colleague – or if they don’t know who specifically to ask, an assignment group – describing what they need help with.

At this time, four hours have already passed on the SLA and only 12 hours remain. When assigning out the task, the technician gives the task an appropriate OLA to ensure that their colleague knows when they need to have the work completed in order to meet the ticket’s SLA.

This is a simple way to get started with OLAs. You might wonder why you don’t just re-assign the ticket, but there’s a few advantages in using task management. First up, you get to track each different piece of work separately; one ticket might need work to be completed by four different teams.

Vivantio will let you track the time each team/user owned the ticket, but it’s a lot easier to understand the timeline of a ticket when you’re using task management. Second, and we’ll talk more about the importance of this in a later blog, you improve the customer experience by ensuring the customer has a single named point of contact for their ticket so they don’t end up feeling like the buck is being passed.

Third, you make it very clear to other teams exactly what they do and don’t need to do so there’s no digging through the ticket history to find out their role in resolving this issue.

TASK CREATION VIA TRIGGER RULES

You can automate task creation within Vivantio using trigger rules. For example, when a request is logged reporting that a computer is lost or stolen, there are tasks that always need to be completed by both the IT team and the security team. Due to compliance reasons, it is required that this kind of request needs to be closed out within an eight-hour SLA.

Trigger rules can be created to automatically assign out the required tasks to the IT team and security team any time a lost or stolen computer request is logged. The tasks can have their own associated OLAs so that the teams know how long they have to complete the work in order to meet the request’s SLA.

The below screenshot shows two tasks that were automatically created via trigger rule due to the type of ticket that was logged.

Clicking into one of the tasks, we can see the SLA for the task, providing the target time to complete the work by.

This is a simple way to get your team started using tasks for repetitive work requests. Sometimes though, this isn’t quite enough. You need to ensure tasks are completed in a certain order, or tasks are only worked on after approval has been given. If that’s the case, then you need workflows.

WORKFLOWS

Automated workflows within Vivantio can also help you and your team manage your OLAs. For instance, say a customer of a software company submits a support request, which requires a specific process involving multiple people to complete. The request falls into a P2 priority request with a close SLA of 40 hours on a 9-to-5 working time plan, or five business days from the customer’s view.

Based on the category of the request, four different support teams will need to work on the request in a sequential order. In Vivantio, a specific workflow which automates the assignment of the process tasks is automatically kicked off using Vivantio’s trigger business rules.

Tasks are automatically assigned out to each team when it is their time to complete their portion of the work. In order to meet the SLA agreed upon with the customer, the total time in the SLA is broken down into OLAs, or smaller chunks of time which are allocated to each team.

There are several tasks that need to be completed by different teams and technicians during the workflow. In order to make sure to meet the target SLA, you can use operational level agreements for each task that is assigned out in the workflow.

This allows each person who is assigned a task to be aware of how much time they have in order to complete the task. The target OLAs for each task are set up to leave time for the transition between tasks and to complete the tasks themselves.

CONCLUSION

If you’re wondering why you aren’t meeting your SLAs, then implementing OLAs is a good first step in understanding why. Whichever approach you use for Task Management in Vivantio, you can use the reporting tools you’re already familiar with to review your performance, understand which teams are creating bottlenecks, and fix the issues at the source.