Skip to main content

What do you do when your Company is constantly having Outages?

Its been a while for me, but there was a period of my life where I was working for a company that was in a constant state of Outage.  They had a mix of services, and over the course of 2 years I was flown across the Country and around the World apologizing for the (lack) of services that my company provided.  While I love travelling and accumulating Air Miles, this was not my ideal of a trip as you can imagine.

So what did I do right and wrong?  Well I got very good at apologizing and grovelling and it helped me write my policy on dealing with Irate Customers.  While not exactly ideal I definitely learned a lot from this experience and I definitely made a positive impact to my companies bottom line.  How?  Well, simply put, the Customers stayed! As you can well imagine, when a business and its service is being impacted by a 3rd party the natural inclination of anyone is to pull the service and move to another vendor.  When SLAs are constantly being missed and month on month, services are not improving this is even more likely.

Now - its easy to say that I "saved" the customers ... but how?

Communication.  Its easier to say than to do - especially when you don't have any news or even worse when you have bad news (you expected it to be fixed in 1 day and its going to take 1 week!).  As I mentioned earlier, I quickly became skilled at speaking to Customer's face-to-face which happened with quite a few of our Tier1 customers.  I also became skilled at sending out mass emails, posts on message boards and forums and phone calls.  Setting a timeline for an update by any/all of these methods and then ensuring that I met that criteria was key.

Help Desk Practitioner's Handbook
Now communication is actually a two way thing.  Speaking to the Customers is great, but what if you don't have anything to tell them?  Support and Helpdesk teams and Management are frequently on the "short end" of the stick without any updates from Engineering and Programming teams.  More often than not, these internal teams have no concept of the impact that the service interruption are causing to the customers.  Its your job to persuade them that the Customers MATTER and the reason you & they are in a Job - working for your company is the money that your Customers are paying!!  They will take their business away eventually if you don't tell them what is going on.


Quality Control (8th Edition)OK, assuming that you're talking to your Customers and your other internal teams are talking to you ... what's next?  Well you need to ensure that your company is actually doing something to fix the problem!!  The company that I mentioned with constant outages?  Well they were all with different services ... each time one thing was fixed another in a different product was impacted.  From my point of view it was 2 years of hell, but  no one single customer was impacted for that total amount of time.  How do you fix this though, because it is extremely draining on your staff regardless ... well, Quality Control is useful.  Make sure that any new product launches are properly tested and tested and tested again before being released into a live environment.  Try to get your staff to break it if possible while its in the testing phase.  Make sure your documentation, release notes and training material are complete and accurate. Ensure that Senior Management get involved at the appropriate intervals based on your Escalation Matrix so that they are aware of the impact to the Customers ... DO NOT be afraid of escalating.  If you are ON CALL 24/7 so are they!  Money will be released when the phone rings at 2am!
Post a Comment

Popular posts from this blog

The Difference Between Incident Managment and Problem Management

Incident Management and Problem Management are both key components of the ITIL service model and have been defined and created in an effort to provide a better and more streamlined service to consumers.
ITIL itself stands for the - Information Technology Infrastructure Library - and comprises of the following books:
ITIL Service Strategy ITIL Service Design ITIL Service Transition ITIL Service Operation ITIL Continual Service ImprovementIncident Management and Problem Management are both elements of the fourth volume - ITIL Service Operation, which tries to define the best practice for dealing with interruptions to a customers service. What is an Incident? An incident is a single - unique - issue impacting one specific customer and their service. While there can be many similar incidents impacting multiple customers, each of them are in their fashion unique and need to be logged and treated as such.
An example of an incident is you losing your home Internet connection. While the underly…

What is PRINCE2

PRINCE2 stands for PRojects IN Controlled Environments and is a very popular method for effective Project Management.  PROJECT MANAGEMENTWhile PRINCE2 is one way of managing Projects, it is worthwhile defining what exactly a project is and why it needs management in the first place! 


A project is specific task/role that needs to be completed to meet certain objectives. In a managed project, you would have a defined beginning and end and certain "check points" throughout the process itself to ensure that you were on target to meet your overall objectives.

These checkpoints are referred to as "gates" and at each gate, you would have certain deliverable and targets to check your progress against. By managing a project in this fashion, you are able to ensure that you stay on track and that any issues or concerns are identified and dealt with at an early stage of the process versus waiting till the end.

The defined "end" to a project is necessary as it creates …

THE 4 P'S OF SERVICE STRATEGY

Competition is extremely fierce in the world of business, only a handful survive, and some can barely keep up with the demands of the times. That's why it is necessary to have an idea of what it takes to be successful and an integrated strategy to help maintain excellent service results.

ITIL discusses at length the four “Ps” of strategy- perspective, position, plan and pattern, each of which represents a different way to approach your service strategy. Brief summaries are provided here: Perspective - This is basically the vision statement of an organization.  Why is it in business, why is it doing what it is doing?  What are the plans and ideas for the future and how does the organization interact with its customers?  A perspective cements a service provider’s distinctiveness in the minds of the employees and customersPositions - What is the competitive landscape and how will the organization compete with other similar providers?  What is the key distinction between them and oth…

8 RULES OF GOOD CUSTOMER SERVICE & 8 STEPS TO DEFINE A SERVICE

In a similar fashion to interviewing and hiring people - the hardest and most expensive exercise is getting the right employee - getting people back into the door is exactly the same.  You want that repeat custom as that is what will save you money in your marketing and advertising.  One of the key components to this in addition to the quality of the product itself is the customer service that you provide to the customer in their purchasing and ordering decisions.  You can offer promotions and slash prices to bring in as many new customers as you want, but unless you can get some of those customers to come back, your business won't be profitable for long. Good customer service is all about bringing customers back. And about sending them away happy - happy enough to pass positive feedback about your business along to others, who may then try the product or service you offer for themselves and in their turn become repeat customers. 
Good customer service should be thought of as re…