Archive for IT

Should IT Communicate Less?

Posted in General Technology, Rants, Technology in Education with tags , , , , on November 29, 2010 by TechChucker

I have been struggling over the last several months with communication issues that end up making the IT Department look bad and administration that doesn’t see why their staff not communicating is something they should address.

Over the last 5 and 1/2 years our IT Department of 3 people have changed, adjusted, tweaked, and accommodated our communication methods and styles to ensure IT addresses all of the requests and issues our end users have.

Each year we increase our communicating and adjust our methods we find that our end users communicate less and are more frustrated.

How does more communication from IT create less and worse communication from end users?

I thought I had a solution when I asked myself that question. Initially I thought that our communicating more was either alienating or annoying our end users. Perhaps we were now giving them too much information and we have made all communication from the IT Department seem unimportant and thus end users disregard our attempts to communicate.

More communication does not reciprocate less communication back.

I discovered that the more our department communicates, does not mean our end users as a whole are communicating back less and in a less effective way.

What will happen when IT communicates more?

There are a few things that happen that can create the illusion of worse communication from end users.

  • Those who communicate effectively and efficiently have less patience for those who do not
  • Those who do not communicate well are identified quicker & are more visible on a day-to-day basis
  • Managers may not have identified bad communicators that IT has

Expounding further on these explains the reason why increased communication by one department can create that illusion of decreased communication by another department.

Those who do communicate effectively and efficiently are going to have little patience for those who do not. Those who now communicate well find it relatively easy to do so, thus have higher expectations for those they communicate with. This is a good thing and should help encourage others to follow suit, but can create the illusion of more bad communication even though there are fewer bad communicators. A good communicator understands good communication and bad or no communication now seems worse simply because of perspective and expectations.

Those who do not communicate well will typically be identified quickly by those who do communicate well and will immediately cause problems. A bad communicator may not know they are a bad communicator, but those who have to communicate with them do and it is very frustrating, if not infuriating depending on the ramifications of their poor communication skills. A bad communicator will often have more interaction with IT simply because they aren’t able to express the issues they are having and are thus more frustrated themselves.

The most frustrating issue is that many of the managers of these poor communicators may not have identified who their poor communicators are. If they have, often they have no idea what to do to fix the problem. Their response is usually to make excuses or minimize the problem. A manager that doesn’t deal well with a bad communicator may have some of their own problems communicating which will amplify all poor communication from that department.

What can be done?

Identifying the problem is only part of the solution. Often, the IT Department has little to no power to change another department, especially if management is blind to the problem or is sweeping the problem under the rug. There are, however, ways to decrease the effects of poor communication and change the culture of bad communication.

  1. Don’t stop communicating
  2. Don’t stop adjusting and perfecting your communication techniques
  3. Don’t ignore poor communicators
  4. Don’t get angry
  5. Be open, honest, and prepared if submitting official complaints

A first response might be to simply stop communicating or reduce the amount of communication your department does. This is a big mistake. Think back to the day you began. The number of bad communicators then is likely to be less than there are now. You did make a considerable difference with the work you have done. Your increased communication hasn’t gone unnoticed. Most end users have seen your increased communications and appreciate it. You don’t hear about it because you are doing a good job and technology has likely become less of a problem for the majority.

In addition to continuing your communicating, make sure you continue adjusting and attempting to perfect your communication techniques. If you are always adapting and changing to make communication easier and more effective people will notice.

If you have identified a bad communicator don’t do what others do and ignore them. Don’t just brush off a bad communication incident, it will come back to bite you. Bad communicators typically will have multiple incidents one right after the other. This means the 3rd incident, though technically less important, will be the straw that breaks the camels back. Never let bad communication slide. Address it with your supervisor if you have one. If the incident requires, address their supervisor. Sometimes it is ok to confront the poor communicator but typically it is not your place as you are not their supervisor and have no authority to reprimand.

The hardest part when trying to create better communicators is to not get angry. Allowing yourself to truly become mad or angry at the bad communicator puts you at a severe disadvantage. A poor communicator doesn’t always think things through which is sometimes why they don’t communicate well. They may not know how to express the issue they are having, so they choose to ignore it or complain to others about it. Taking it personally is not useful. The bad communicator isn’t usually trying to make you mad, they just don’t understand what they have or haven’t done that has caused the issue. Getting mad yourself simply wastes your energy and gets in the way of solving the problem.

The final and most important part about dealing with bad communicators is to be prepared, honest and open to other ideas when you do bring a complaint to your manager or their manager. Being prepared means you need to document how much communicating you have done and then show how you have not gotten any responses or bad responses from the bad communicator. If this person is habitually a bad communicator it is best to show the trend and how it has caused problems such as wasted time, wasted money, safety or security lapses etc. Going in with no proof makes you look bad and thus less credible.

There is no single way to fix poor communication in a department or district, but you as an IT Department can effect change even without the authority to write policy or punish staff. In the end, your measure for success is to show that the IT Department is not the problem but part of the solution. Showing that your department has constantly made attempts to improve can put the ball back in the poor communicators court where it is now their turn to show what they’ve done to make a difference.

Bad communication is the single most common issue in any workplace and is typically the largest issue that most employers have. Always remember that you’re not alone in your frustration and as long as you are working to improve, nobody can point their finger at you as the cause.

Who Sets the Priority?

Posted in General Technology, Technology in Education with tags , , , , , on September 17, 2010 by TechChucker

I often get this question at staff workshops and throughout the year.

Who prioritizes the HelpDesk requests?

How do you answer this question as an IT Professional?

Before you blurt out the answer to your staff you need to remember that the questioner is often upset or disappointed in service recently received or not received. Take that into account before you answer with something like:

I do, do you have a problem with that?

Very rarely will that help the situation. Whether you like it or not, when you take a job in IT, you are in a service job and must act like someone who works in service. That means, you must be polite and you must let angry people and comments go. Your job is to keep the peace and get the job done. Your job is also to keep people calm. If you aren’t calm, how can anybody else be calm about the situation.

This brings me back to answering the question of who sets the priority. Answer the question honestly and confidently. If your district has put you in charge of the IT Department then it is your job to prioritize the HelpDesk.

Your best bet is to answer the question with a confident response of:

I set the priority of all HelpDesk requests based on this criteria.

Answering in this way answers their next question before they can ask it. In the end what the questioner really wants to know is how they can get their requests put at the top of the list. If you can catch the question before it’s asked you can usually diffuse any further conflict in the conversation.

We answered the first question but the second question is the one that will actually get more scrutiny, and you better have a good answer that makes sense, otherwise you’ve lost your credibility and your HelpDesk. You need to remember that your staff are just as intelligent as you are, and they can see through a poor excuse. They may not know all the technical aspects of how your job works, but they know when they’re being brushed off. Don’t let that happen.

Your Answer Should Be

We base priority on the following criteria:

  1. Safety of staff & students
  2. Quantity of staff & students affected
  3. Order HelpDesk requests are created

The ultimate goal is to give staff a feeling of confidence that their IT Department will treat everyone fairly and consistently. Never allow your department to drop everything for one 3rd grade teacher but nobody else. Rather make all wait the same amount of time. This can and will cause some conflicts, but most people will respect your department more if they see and hear the same message.

What if my priority criteria is questioned?

Saying this is your method for prioritizing and doing it go hand-in-hand. If you tell people this is how you prioritize but don’t follow through, people will catch on. Some may ask what you mean by each of those items. Your answer should be short and simple. 

  1. If a request is submitted that affects the safety of staff or students that becomes top priority.
  2. Requests that affect more people get higher priority over those that affect only one.
  3. The order in which requests are received will determine any and all priority once priority 1 and 2 requests have been determined.

 It is important to note that some requests can be resolved quicker than others, and often it is legitimate to resolve a quick question or setting change right away. There are always instances in which this will take place, but you should never go on to an easier problem and leave a hard problem just because it was a difficult or time-consuming problem.

Be Smart, Strategize

At the end of the day it’s your department, but your staff are your customers. If the staff aren’t happy, then you haven’t run your department very well. IT is much more than just technology, it requires people skills, leadership, mentoring, teaching, and service all in one. If you don’t like people, people won’t like you.  Make sure you’re personable, tactful, smart, and calculated in your approach to running your department and your helpdesk and you’ll be successful.

 

Follow

Get every new post delivered to your Inbox.