Category Archives: IT Manager Tips

Helpful articles and tips

IT manager resume advice

This weekend I traded several email messages with an IT manager in Egypt who just completed our IT Manager Institute Self Study. He reworked his resume and asked me to review it and provide feedback.

Before I opened the PDF file I could have told you what the resume would look like. Over 90% of the IT manager resumes I have seen look pretty much the same:

  • They are organized and provide a lot of information about the person.
  • They tell a lot about the manager’s technical knowledge.
  • They list the manager’s former companies and describe what he did.
  • They list technology training and education.
  • They list technical certifications.

Bottom line, , , most IT manager resumes are technical.

Most IT managers think that to get a technology manager job you need to provide lots of information about your competence in technology. Unfortunately, that’s not what senior managers are looking for, , , we need managers who can manage technology resources and get results. We aren’t looking for technology experts, , , this is handled by the staff.

What these resumes don’t do is stand out from all the other IT manager resumes you see. They provide a lot of “what” but not “why” a senior manager would want to interview you.

Put yourself in a senior manager’s situation. If he is looking for background in a specific technology, having this on your resume will hit his “hot button”. The problem is that this is a “hit or miss” and more of a “miss” than anything.

What you need is something on your resume that makes a senior manager want to learn more about you, , , makes him put you in his “top 3 candidates list” and truly want to interview you.

You need something that says “WHY”! You need to list specific results and benefits received from what you have accomplished.

IT managers almost always focus on “what” when they need to focus on “why”. It doesn’t matter if it is in a resume, part of an IT strategy document, or discussing the need to invest in upgrading your infrastructure.

“What” deals with technology, , , “why” deals with business perspective and justification.

Instead of just putting in your resume that you delivered a new scanning and imaging technology, , , add the results that were achieved, , , like “eliminated 50% of our paper and reduced handling and storage costs by $45,000 per year”.

Instead of just saying you delivered 80% of your projects successfully, add that it “improved client satisfaction by 30%”.

Instead of saying you delivered XYZ project, add that it “reduced the delivery time of a key service by two weeks”.

The point is you need to highlight the results you achieved in the points you make about former companies and experiences. Senior managers are looking for people who can make things happen and understand the importance in delivering business value.

It’s all about RESULTS.

Positive results achieved by your past actions create interest in learning more about you, , , and how you got your results. It says you are results oriented and realize the business purpose of your part in the company.

Senior managers don’t see a results oriented resume for a CIO or IT manager that often, , , they see the same old thing all the time, a resume with lots of information about the person’s technical knowledge but rarely anything about what the person accomplished. This is not what gets you an interview.

Another challenge IT managers have in writing their resume
Something else was immediately noticeable in the resume I reviewed this weekend. It was 6 pages long. This is not what I want to receive as a senior manager, , , it needs to be no longer than 2 pages.

Now, different countries and cultures have different preferences. Some countries place emphasis on listing all the training and education you have. In the US, we don’t tend to focus on an IT manager’s past technical training unless we are in the education industry.  

What I can tell you is that I probably would not give a candidate an interview if he sent me a 6-page resume. In it will be lots of detail and very little, if any, reasons for me to want to interview and hire him. Almost guaranteed.

IT managers are high detail and we think we need to give people all kinds of detail describing all that we know about technology. Not so.

Senior managers don’t care what you know nearly as much as whether you can get results for their company. Don’ t provide all this detail unless it’s the common thing to do in your country or the industry you work in.

My advice – make your resume more results oriented and less technical oriented.

My student from Egypt, , , he condensed his resume into a 2-page summary. He now has a long detailed version and a short version. He also revised his resume to be much more results oriented, , , it’s a resume that describes someone I would want to interview if I was hiring an IT manager.

Another post reinforces this point – CLICK HERE

Do the right thing

There are many times in your career when you will have a tough decision to make, , , one that causes a major internal conflict within you about what you should do.

I just had one of these issues occur in my personal life. I was asked to do something to help someone, a person who I’ve never been close to. We will never become close because I view this person as a “taker”, , , not a “giver”.

I try to align myself with “givers” and distance myself from “takers”.

Initially, my inclination was to simply decline the request, but I thought about it and discussed the issue with my wife and an uncle who I respect. Neither of them gave me the answer or advised me specifically on what to do, but they made comments and asked questions that were very helpful in me reaching a decision.

My final decision was to accept the request. The reason, it is the “right thing to do”. The other reason was the person was placing a lot of trust in me just by asking me to help him in this way, and he truly needed my help, , , something I take seriously. 

It’s always more important to do “the right thing” than to “do things right”. Your internal compass should always point to doing “the right thing”.

I’ve had to do some unpleasant things in my career, but the guiding principle I always tried to use was to “do the right thing”.  In the long run, you have to look yourself in the mirror and feel you have conducted yourself with character. Sometimes, this means you must put personal opinion and preferences aside.

IT employee work behavior – part 4 of 4

70% in IT have authoritative management style

I summarized the work behavior approach for the vast majority of us in IT in the last post and said I would tell you more in Part-4. Here is the summary for you once again:

Work behavior traits for groups A, C, and D are 90%, , , that’s essentially everyone in IT. Remember, it is managers, DBA’s, Desktop technicians, , , anyone in the IT organization from what I have seen with my research.

Group B is the shy and introverted group of traits. 70% of us don’t want to discuss the issue, , , we just want you to “do your job.

This profile is an authoritative manager profile:

  • Do it
  • Do it now
  • Do it my way
  • No discussion

Roughly 7 out of 10 employees in your IT organization are “wired” this way. They have authoritative management styles in their approach to work.

I’m “wired” this way, , , you are very likely “wired” this way. Roughly 7 out of 10 people in your organization are “wired” this way.

This is not necessarily a problem, but it certainly can be as you might expect. Here are a couple of reasons why:

  • People are resistant to change. If you do not explain it and convince them of some benefit to them, , , they quite often resist.
  • Clients do not like having things forced upon them.
  • Independent people (like 90% of us in IT are) do not like to do things “your way”, , , we prefer to do it “our way”.

Make one subtle change and you change your approach from “authoritative” to “persuasive”. Modify the part where you do not want to discuss the issue by explaining the reason for things and the benefits in doing things, , , and you become a persuasive manager versus an authoritative manager.

This is a big deal and is a much more effective management approach in most situations.

Let me explain the difference. In a military combat situation, , , you want split second decisions to be made and you want the troops to follow the commanding officer’s direction without flinching. In this situation, authoritative management styles work very effectively and are actually what you prefer to have.

However, in a professional setting like your IT organization, persuasive managers are much more effective and have a stronger following with team members.

One slight tweak makes you a much more effective IT manager.

But don’t get me wrong, , , changing your communication approach at work will not be easy. Remember, your “DNA” is telling you that you probably aren’t a very good communicator and you don’t like to communicate with people outside your immediate network.

In my personal situation, I intuitively made the change from authoritative to persuasive before I ever understood anything about work behavior. I believe I must have learned when I was in the US Marine Corps that you get a much better result from IT people when you explain things rather than simply give them orders.

Now, in the Marine Corps you can just give an order and can expect your men to carry out the order. If they don’t they can go to jail, , , it’s a pretty simple deal.

But, if you want the best results, , , your men need to understand why we are doing things and what’s in it for them, , , the benefit to them. Even things like going on a 3-mile run is something they need to understand, , , otherwise, they kick and moan about it and it’s not as good a result as you would like.

I saw this dynamic work in my early years of management so over time my approach at work became more persuasive than authoritative, , , I modified my work behavior by communicating more and the results got better.

Let me repeat, , , I actually modified my personality at work from a manager who tends to naturally want to just give orders and expect you to do the work and not ask questions to a manager who explains why we need to do these things.

Changing your behavior at work does not change your basic personality. In reality, , , I’m still deep down that authoritative manager and would prefer to have no discussions, , , but I have learned that I get a much better result when we explain and convince the team why we need to do something and the benefits we will receive. So, , , I have the discussions. It takes time and energy but it’s worth the effort.

At work, people see me as a more social and outgoing person than who I really am, , , I change my personality at work to do what is necessary to do a better job.

Other things happen at work as well, , , I force myself to communicate. I force communication events with employees, clients, senior managers, , , even vendors. It’s not something I inherently like to do but I know stronger communication is necessary to get the job done, , , so once again, I modify my personality at work and force myself to communicate with others.

This is why understanding the dynamics of work behavior can be so helpful in contributing to your success.

You have to learn who you are and identify if your approach to work will be effective. If you are lost in the detail, , , you have to find a way to “get out of the technology weeds” and depend more upon your people. If you aren’t communicating effectively, , , put processes in place that force you to start communicating more with staff and clients.

You can modify your work behavior approach and for many IT managers, you will need to if you want to be successful.

How do you learn “who you are”?
There are three tools I am familiar with and all three are effective tools in discovering what makes you tick:

  1. Personalysis
  2. Myers Briggs
  3. Predictive Index (PI)

If you follow my work in the ITLever Blog, read my books, or attend one of my classes, , , you will discover that I define what you need to do to be successful and how to do it, , , and give you tools to help you make it happen.

It’s your job to learn who you are and whether you have to modify your approach to do these things.

What you will also discover is that many of the processes and tools I use are specifically designed to overcome some of the work behavior tendencies that can cause an IT manager problems.

For example, let’s take the “lower desire to communicate issue” inherent in an introverted and shy person. I know I’m one of these people so two of the communication processes I initiate in a company is to hold monthly IT staff meetings and monthly client status meetings. We schedule them and it forces me to prepare for the meetings and to communicate with clients and employees, , , otherwise, I probably will not get around to it.

Learn about the dynamics of your personality and work behavior tendencies. It will help you become a better manager. Take it a step further and learn about your individual staff’s tendencies, , , it will help you manage and lead them more effectively.

Learn more by viewing an online training module taken from the IT Manager Institute Self Study program, , , go to my next post.

IT employee work behavior – part 3 of 4

Part 3  –  Challenges in who we are

Let’s review our last two posts. In Part-1, I asked you to identify the traits of what you would want to have in an IT manager. You could do the same exercise for any IT position.

In Part-2, I identified the traits that characterize most IT employees, , , whether they are managers, programmers, work on the Help Desk, or are heavy technical system administrators. If you are in IT, my research of more than ten years with thousands of employees and hundreds of IT managers from all over the world identifies these key work behavior traits in IT employees:

A.   90% are independent, self-starting decision makers who are technically oriented

B.   70% are shy and introverted

C.   85-90% have a high sense of urgency

D.   90% are high detail

What this says about an IT manager is this, , , we approach work as:
“Let’s do it, do it right now, and do it my way, , , and I don’t want to talk about it.” 

More on this in Part-4.

For now, let’s talk about what it means to have the attributes that so many of us in IT have. There are some good things and there are some challenges. We should take advantage of the positives and work on the challenges to be as successful as we can possibly be.

Before I start, let me emphasize something. There is nothing wrong with what anyone’s personality traits or work behavior tendencies are. What’s important to understand is that some of these tendencies can hinder your success. Knowing what they are and learning how to adjust to offset them will help you be much more successful.

What it means to be independent
Being independent works well as a programmer, , , your success is often based upon what you personally can accomplish. Being independent in an IT manager role is not a bad thing, but it causes us a real challenge. Depending upon others to do things to achieve success is tough, , , especially when your past experience has been pretty much based upon what you can do yourself.

Managers depend upon their employees to succeed at virtually anything. It’s a tough transition to go from the technical hero many of us were to the manager who is now dependent upon others to get things done.

Independent, self starters who are goal oriented like being the hero. As the manager, your job is to make your employees the hero, , , much easier said than done.

What it means to be introverted
Nothing wrong with being shy and introverted. As a Systems Administrator or programmer, you can focus on the technology and not worry about having to communicate a lot. In an IT manager role, effective communication is absolutely essential for success.

The challenge we have as IT managers who are more introverted, , , (I’m a perfect example of this), , , is that we typically don’t develop our communication skills unless someone has invested in this for us. This was my case, , , it’s not an area I would have developed but my senior managers fortunately knew the importance of communication and invested in developing my communication skills.

The second challenging part of being shy and  introverted is that our desire to communicate is lower. Our attitude is simply, “Why bother?”

Introverted managers (over 70% of IT managers are introverted) have to create processes that will force them to communicate. Otherwise, they just won’t get around to it.

What it means to have a high sense of urgency
85-90% of us in IT have a high sense of urgency. This means we don’t like to work on repetitive things. We would make terrible assembly line factory workers.

People with high sense of urgency are impatient and not so tolerant of others who might be slower or who make mistakes. This can cause internal conflicts.

Having a high sense of urgency is a good thing for an IT manager, but “in the storm”, you have to become a calming effect, , , not someone who is viewed as pouring gasoline on the fire.

What it means to be high detail
This is one of the tougher issues for IT managers. As technicians, we pride ourselves for knowing the technology inside and out and being able to control the technology. It takes precision and knowledge to do this, , , requires high detail focus so we excel in it.

As managers, we can no longer work at this level of detail. What’s important now is what we can get accomplished through our people, , , not what we can do ourselves.

Letting go of the detail and being able to work at a higher level is one big challenge, , , VERY BIG.

Transitioning from technical expert to business manager is one of the toughest challenges you will face. Far too many don’t succeed in it. This high detail issue is one to become very aware of and to realize how much of an obstacle it can be in becoming a successful IT manager.

IT employee work behavior – part 2 of 4

Part 2 – Who we are

If you have not read the first post in this 4-part series and completed the exercise, now is a good time to do it.  Click here to read the post.

Do you have the color combination selected of the traits you would like to have in an IT manager?

Most people who take this exercise pick one of two color combinations:

If you look closely, they are exactly the same except for the second color. In the first series, the second color is Red, , , and in the second series it is Green. The other three color options are the same in both series.

There are four personality areas I want to discuss with you. With what I’ve just laid out, you can already see that the majority of opinions select the same color combination in three of the four areas. The reason is because we are all quite a bit alike when it comes to how we approach work as IT employees, , , especially in three of the four areas.

Here are the keys that make it this way.

Traits Set #1, , , Technically oriented or social?
We want decision makers who are technically oriented managing our IT organizations. We do not want people who prefer to follow and are indecisive as managers. Therefore, RED gets the vote almost all the time.

Ninety percent of IT employees have RED tendencies in this area.

Traits Set #2 – Introverted or extroverted?
We would like our IT managers to be excellent communicators and comfortable in communicating with others. That’s what we would like but seventy percent have GREEN traits. This means most IT managers are shy and introverted.

It does not mean they can’t communicate well, but communication with people outside their immediate network like department managers and senior managers is definitely a challenge that must be overcome.  GREEN traits are where most IT people are in this one.

Traits Set #3 – High or low sense of urgency?
We would like an IT manager to have a high sense of urgency, , , not someone who is happy if we resolve a problem three days later. If a system is down, the IT manager needs to be in a hurry to get it fixed. At the same time, the manager needs to be a calming effect, , , not Chicken Little running around shouting, “The sky is falling!”.

Eighty-five to ninety percent of IT managers have a high sense of urgency, , , so GREEN traits get this vote.

Traits Set #4  –  High or low detail?
This is a tough one. As a programmer or a Systems Administrator, we need to be high detail to do a good job. Fortunately, ninety percent of us are high detail in IT. The challenge comes when we become IT managers. As a manager, you don’t want to be so detail oriented. Don’t get me wrong, there is a lot of detail when working as a manager, , , but now we have to delegate and let others take care of the technology detail.

Many of us have a difficult time letting go of the detail, and I can tell you this will impede your progress as a manager if you can’t make the transition from technical expert to business manager. It’s a whole different ball game when you become the manager.

So, RED includes the traits that are found in 90% of the IT staff.

Basically, you can say that 90% of all IT people are:
Independent
Self starters
Decision makers
Technically oriented
Have a high sense of urgency
Do not like repetitive tasks
High detail and knowledgeable about the job
Like to have things done accurately and their way

That’s essentially everyone in IT if it is 90%.

70% are shy and introverted. That’s also quite a majority of your people or of the IT manager community. If you are shy and introverted, it means two things:
1. You probably have weak communication skills.
2. Your desire to communicate is lower.

Not a problem too much as a programmer, , , but for an IT manager this one becomes a real issue.

In the next post, I’ll share some insights and challenges about the four personality areas that drive most of your IT staff:
– Independent and technically oriented (90%)
– Shy and introverted  (70%)
– High sense of urgency  (85%)
– High detail  (90%)

IT employee work behavior – part 1 of 4

The vast majority of IT employees have similar work behavior tendencies, , , or personality traits.  So similar it is scary.

We are all unique, but the way we approach work is remarkably similar.

Why is this important?
Because your work behavior tendencies can help or hinder your success. Understand them and adapt where needed and your success will be much greater. And remember, , , this applies to anyone and everyone in your IT organization.

Let me give you an example. If I were to walk into a room of 100 IT people made up of managers, programmers, BA’s, desktop technicians, Help Desk, etc. , , , I already know what the personality make-up of the group will be before getting to know any of them.

I’m so confident, I would bet you a lot of money I could define the work behavior traits of the group.  I’ve seen this repeated time after time.

How do I know?

I’ve observed and researched this issue for over ten years. Initially, I thought the consistency I was seeing was just an anomaly. Later, I understood that there is a certain personality type that’s drawn to work in the IT field. You will see a similar consistency in personality traits with sales people.

It doesn’t matter what position you are looking at in IT, , , years of experience won’t change it, , , doesn’t matter if you are in a large or a very small company, , , and it won’t be any different if you are in South Africa, China or the US. I’ve measured these results in all types of situations and in all parts of the world, , ,  if you are in an IT organization, there is a high probability your work behavior tendencies are going to be like most of us.

I use the terms “work behavior” and “personality traits” to mean the same thing.

In this 4-part post, I want to share things about the work behavior tendencies that exist in the majority of your IT staff. Being aware of this can help you understand why things happen, , , or do not happen.

It can help you realize why certain types of things are such a challenge for some of your people.

Understand this dynamic of “what makes us tick” well enough and you can even use the information to resolve employee conflicts. I know because I’ve seen it up close.

IT attracts a certain personality type

What I’m about to share applies to anyone in the IT organization, , , from CIO to the Desktop Technician. If you are in IT, the personality traits I’m about to share in this 4-part post applies to you.

OK, , , to start we are going to do a little exercise.
I want you to select desirable traits for an IT manager. You could work through this exercise for any position in the IT organization (IT manager, project manager, Systems Administrator, DBA, etc.).

For these purposes, I want you to focus on IT manager.

For each item, I will give you two groups of work behavior traits, , , a red group and a green group. I want you to select either the red group of traits or the green group of traits you would prefer in an IT manager.

There may be traits in both the red group and green group you would like in an IT manager, but you need to select the group of traits you would most prefer, , , it’s either “red” or “green” for each set.

Write them down to refer back to as we cover this topic in the next three posts:
Set #1  –  Red or Green?
Set #2  –  Red or Green?
Set #3  –  Red or Green?
Set #4  –  Red or Green?

Here we go:

Traits Set #1
Red
Independent
Self starter
Decision maker
Analytical mind
Creates change
Technically oriented

Green
Indecisive
Prefers to follow than lead
Unassuming
Agreeable
Lacks confidence in new areas
Willing worker

Traits Set #2
Red
Socially oriented
Warm
Friendly
Cheerful
Delegates authority
Talkative

Green
Reserved
Serious
Sincere
Thinker
Enjoys own company

Traits Set #3
Red
Relaxed
Patient
Methodical
Adjusts to repetition easily
Low sense of urgency

Green
Quick
Impatient
Fast learner
High sense of urgency
Ambitious
Drive to get things done

Traits Set #4
Red
Detail oriented
Careful
Thorough
Accurate
Conservative
Knowledgeable about the job

Green
Delegates details easily
Stubborn
Informal
Casual with details
Not obliged to conform
Lacks follow-up

Finished?

You should have four trait groups selected, , , something like “red, red, green, green”, , , or “red, green, green, red”, , , or “green, green, green, green”. Keep this handy for the next three posts.

Did you select one of the following combinations?

There is a high probability you did.

 

Let me give you some preliminary information about what’s to come.

In Part-2, I’ll discuss four key personality trait areas or work behavior tendencies we all have. The remarkable thing is that in three of the four areas, 90% of IT employees have the same tendencies. In the 4th area, 70% of all IT employees have a certain set of traits, , , and I’m guessing you missed this one in your exercise.

What you probably selected in this set is what is desirable in an IT manager but lacking in most IT managers unless they recognize it and do something to overcome it. I’ll explain in my next post.

In Part-3, I’ll share the challenges these groups of work behavior tendencies can give an IT manager. I’ll even share some things they do to challenge your technical staff.

In Part-4, I’ll summarize who you probably are as an IT manager and challenge you to modify a couple of your tendencies to become more successful.

If you subscribe to ITLever (it’s free), you will receive automatic email notification of new posts.  Simply select the EMAIL SUBSCRIPTION link in the right-hand column.

Teamwork is difficult for IT employees

Teamwork is essential for your IT organization to succeed. None of us would question it.

But did you ever consider that teamwork is not a basic trait in your IT staff. In fact, working on and within a team is a challenge for most of your IT people.

Here is why.

90% are independent, self starters who are goal oriented. Did you hear me say, “independent“?

Also, more than 90% are high detail people who like to do things their way. They are control oriented people who like to do the work themselves and have things done “their way”.

These two issues are not exactly made for teamwork. In fact, they can work against good teamwork.

Does this mean IT employees can’t be good team players? Certainly not, , , but it is important for IT managers to understand that it’s not a natural thing for 90% of your staff who have these two traits  —  independent and high detail.

What this means is that the IT manager must work hard to ensure teamwork is created in your organization and people know how to become good team players. As an IT manager, you want to reinforce teamwork and client service  all the time.

Help your IT staff understand that “we will all be successful together”. If the IT organization (the team) is not successful, there won’t be any successful individuals. It’s about the team, , , not about the individual. When the team is successful, we can all achieve success.

In a functional team, people have very specific assignments and responsibilities. They know how to do their jobs and when everyone succeeds in their work, the team succeeds. Failure in any area can cause the team to fail so people need the tools and knowledge to do their job and you as manager must be certain all things necessary for success are addressed.

People need to look out for one another, , , and help one another. It’s very difficult for someone who is highly independent and goal oriented to want others to succeed or to be the hero. We want those accolades for ourselves.

Learning how to become cooperative and eager to help others succeed is a key strategy you want to reinforce with your team, , , even reward this behavior when you see someone exhibit it.

You have to teach your IT staff fundamentals, , , like a football coach teaches blocking and tackling. Fundamental skills like teamwork, project management, communication, and client service are essential for your success.

Don’t forget to look at yourself when you think about this, , , 90% of all IT managers are also independent and high detail people.

Sitting on the fence can be hazardous to your health

Do you sit on the fence or do you take a position?

I hate it when I see someone in a situation and they can’t make a decision, , , or give you specific feedback to your question.

Sitting on the fence is unacceptable.

It’s OK to say, “I don’t know.” That’s acceptable and takes a position, , , albeit a neutral “don’t know” position.

It’s not OK to hum haw around and talk but say nothing and not take a position when someone asks you about something. A simple, “I don’t know.” will suffice, thank you.

You may think it is the safe thing to avoid taking a position, but I believe it causes you to lose credibility. Senior executives want your position on things, , , even if it’s an “I don’t know.” If they ask you a question they want your input, not a bunch of rhetoric that ends up telling them nothing.

Do this a few times and you will discover senior management asks for your opinion less and less.

Have you ever asked for input and the person talks a lot but doesn’t say anything? I hate it when this happens, , , as do most executives.

As a manager, your job is to get something that’s gray to black or white. Instead of sitting on the fence about an issue, your job is to determine if it needs to be on one side or the other.

Get the issue to one side of the fence and you can move forward. We don’t make progress when we are “on the fence”. Even if you make a mistake and take the issue to the wrong side, you can correct the mistake and move forward.

Time to assess where you are

OK, five months of the year are complete, , , only seven months to go. Now is a great time to assess a few things:

1.  Are you completing your IT strategy?
Hopefully you are making great progress in completing the big items planned for this year. If not, you need to step up the pace, , , five months has passed very quickly and the end of the year will be here before you know it.

2.  How is your budget looking?
Better check where you stand with your budget and forecast out the trends of your major expense categories. If you are already behind in achieving your budget for the year, you need to make corrective action quickly, , , waiting until September or October will be too late. If you see certain expenses trending higher than what they need to be to make your plan, , , anticipate the result and make corrections as needed to achieve your plan.

3.  Are you taking care of your people?
Have you done anything nice for your staff this year? The next few months is a good time to do something. Take care of your people and they will be motivated and encouraged to take care of you. It doesn’t require lots of money, , , just pay attention to them and do something fun from time to time and show them you appreciate their efforts. Telling them you appreciate them is also very helpful.

4.  Does senior management know what you are doing?
Are you communicating with senior management and department managers so they know what your IT organization is getting accomplished, , , and are you translating these successes into business value components where they will “get it”. If you don’t know what I mean by “business value”, read the post titled, Business value is key.

5.  How are your clients feeling about IT support?
Are your clients happy with what you are doing or do you know? If you aren’t sure, now is a good time to check with them to insure your team is on course for a successful year.

Mid-year inspections are valuable to help ensure you achieve what you want to achieve this year. The freshness of a new year has worn off by now and we are now into the drudgery of the work, , , it’s time to highlight some things and create renewed focus on what you and your team are trying to get accomplished this year.

Your staff and you may be getting a bit tired or a bit down so make it a point to do something that shows you appreciate them. Have some fun.

Staff will begin taking vacations, , , be sure they do so they can come back fresh and ready to go. Be certain you do this for yourself, , , and when you take vacation, try to actually take a true leave of absence and get completely away from the work. It will help you and make you more productive when you return.

Assess where you are, make adjustments as needed, and push forward to make the progress you need to make this year.

Does your company do an “IT chargeback”?

An IT chargeback is an internal accounting procedure where your company charges departments for the cost of IT support.  They do this to help organizations understand that IT is not free.

You see, it’s easy for a department manager to think IT support is free when the IT employees are part of the same company. So, if they want programming customizations, they merely submit an endless wish list of new enhancements, changes, etc.

The problem, , , IT is not free, , , IT support costs your company millions of dollars each year.

If a department had to obtain programming support from an outside company, they would pay anywhere from $50 to $150 per hour for the work they request. Our company has to pay for this whether it uses internal programming resources or an outside company, , , so it’s always a real cost to provide these services.

In order to reflect IT support usage, companies sometimes charge the non-IT departments a percentage of the total IT cost based upon how big they are. It’s called an “IT chargeback”. I’ve seen this calculated by department revenue, by number of employees in the department, or just flat percentage rates the company imposes.

What accounting will do is spread the total IT expense out to all the departments of the company, , , until the “net expense for IT shows $0.00. It’s only an internal accounting procedure to spread support costs out to the organizations using the support.

Usually when a company decides to do this, they add budget dollars to non-IT departments who will receive these allocations. If the IT department spends exactly what they budget for, there will be a zero budget impact to the non-IT departments.

If your company plans to implement a chargeback policy, be prepared for some push back by the non-IT departments. They don’t like it.

They view their department being charged for things they don’t do and it possibly affecting their financial performance. In reality, it won’t affect financial performance at all because the non-IT department gets additional budget dollars added to their budget to cover it, , , but I can tell you firsthand there will be resistance from the department heads.

When implemented well, all organizations gain a better understanding of the costs associated with IT support and have more incentive to manage their IT support need.