Downtime happens -- hardware fails, software has bugs, and human beings, even IT professionals, make mistakes. The real test IT service quality is not whether problems occur, but how often, and to what response. Problem response activities must be properly managed, using appropriate communication and customer service techniques, to ensure that negative perceptions don't get a chance to "set in". Read on to learn more about it.
If your end-users were asked how often certain systems are "down", what would they say? Whatever the answer might be, at the very least, you would hope it would be based in fact and not "perception". Problem event frequency and conditions are facts, borne out by actual performance statistics (i.e. the server is up 99% of the time, and outages last no longer than one hour). And logically, IT performance should be judged on that objective criteria. But, facts do not always tell the whole story, and end-user perceptions, no matter how erroneous, can play a large role in how problems and related IT performance are judged.
It may be unfair, but IT managers must be prepared to manage to both sides - the facts of the matter as well as the perceptions of the end-user community.
This discrepancy between fact and perception can arise from basic differences in point of view. End-users view technology problems and service interruptions based on impact -- i.e. "I can't work, I can't print, I can't send e-mail.....". On the other hand, IT staffers tend to view technical problems from a more clinical perspective, according to source, cause, degree of difficulty and the nature of the related resolution.
Perceptions are further complicated when IT problem events occur with more regularity (or severity) than one would like, or in relatively close proximity to one another. While the IT department may view each incident as a separate and distinct event, to the end-user community, any given problem event may be viewed as one long string of the same circumstance .... i.e. "this network is always down". The sad fact is that very few people acknowledge the norm - "as in server uptime", but they never fail to notice the exceptions - "as in server downtime". And, distinct problems can blend together so that they are perceived as one massive, ongoing systems failure. (Relating Reading: Closing IT Service Expectations Gaps)
You don't have to be a victim of a "perceptions problem". As a responsible and pragmatic IT manager, you must recognize that "perception problems" can and do exist, and take steps to minimize negative consequences and repair damaged relationships. It goes with the territory of wearing multiple hats.
"Actions speak louder than words". That's a sentiment that is certainly relevant to the perception problem scenario. At some point, the best way to resolve these issues is to face up to them and take consistent, specific actions to prove them wrong. It all starts by laying a solid foundation of IT capability, understanding the nature of the perception problem and then working consistently to share information, communicate and address expressed concerns. This is all summarized in the eight (8) key steps laid out below:
Are you ready to lead your I.T. department to become more valued, relevant and responsive? If so, then you need the IT Service Strategy Toolkit from ITtoolkit.com! The Toolkit teaches you how to "add value" to IT projects and services -- using our time-saving "service strategy process". It's ready for instant download, filled with 400+ pages of steps, guidelines, practices and templates. Find Out More
Strategic "project fast tracking" is a streamlined project management process, specifically used to overcome the most common types of project obstacles, including insufficient time, resource shortages, budgetary deficiencies and stakeholder conflicts.
Sign up for the ITtoolkit.com newsletter and be the first to know about our latest blog articles, templates, white papers, infographics, and special offers.
We won't overload your inbox and we don't share or sell subscriber information. Just enter your email address below.