Category Archives: IT Manager Tips

Helpful articles and tips

5 key components in getting IT projects approved

IT managers and CIOs can struggle when it comes to getting their projects approved. It’s usually because they lack one or more of the key pieces you need to get an IT project approved and funded.

Think of this scenario for just a moment:
The CEO of a small company sees his CIO walking down the hall and toward his office to talk with him. The CEO quite often wants to find a way out of the room to avoid having this conversation.

Why?

Because he knows two things are going to occur in this meeting with his CIO:

  1. He’s not going to understand what the CIO will be talking about because he always discusses things in technology terms and jargon.
  2. The CIO is going to ask him for money to fund a project.

If the CEO doesn’t understand what the CIO is saying, it’s hard for him to give his CIO the money.

You might be surprised, but this scenario happens quite often, especially in small and mid-sized companies.

It’s important to know what a CEO is looking for. Above all, the CEO looks for the “why”. What are the benefits in doing this project and what will it do for our company… WHY?

I believe there are five key components in the dynamics of getting any IT project approved.

1.  The project must address a legitimate business need or issue.

All project recommendations you make should be business-driven, plus there should be a business sponsor identified for each recommendation.

This business sponsor can come from the CIO, but most of the time it should be someone from the business operations of your company.

The project should eliminate or minimize a risk, achieve an opportunity, or address a material issue of the business.

The bottom line is that all IT projects need to help the business in some way, and it always helps when you identify IT projects that originate from a legitimate business need.

Projects that are business-driven always have an edge in getting approved.

2.  The project should deliver business value.

I identify “business value” as one of five specific things. A project should:

  1. Increase revenue,
  2. Decrease cost,
  3. Improve productivity,
  4. Differentiate the company, or
  5. Improve client satisfaction.

Learn more about this in my blog post, “Business value is key to IT success.”

3.  All projects must be cost-justified.

The benefits of doing a project should outweigh the cost and effort. In other words, there needs to be real benefit to the company to invest time and money into doing something.

If you can’t justify the cost of a project to senior management, odds are high you won’t get the approval you seek.

Cost justification can come in many forms, not just financial cost justification. Consider project justification in areas that:

  • Reduce risk,
  • Improve client satisfaction,
  • Improve employee satisfaction,
  • Reduce downtime,
  • Address regulatory or compliance requirements.

4.  The project must be in context with the company’s current situation.

You may have a project that addresses a high-risk issue and is easily cost-justified, but if there is no money available, senior management may not be able to approve the project right now.

They may choose to take the risk. Senior managers balance risk and business issues all the time, plus there are many other departments in the company that need funds to address their initiatives and needs.

If cash flow is tight, the best project to recommend might be a less important project  that creates a cash flow benefit or cost savings that helps your company afford to sign up for your primary project later.

5.  IT must have a proven track record.

Senior management won’t hear much of what you have to say if you lack credibility. The way to achieve credibility is by delivering projects successfully and doing what you say you will do.

Simply put, you have to establish credibility by delivering projects successfully once they are approved. This creates trust and a sense of predictability that will help you in efforts to get projects approved.

Summary

You want to turn the scenario I talked about at the beginning of this article from one where the CEO is looking to avoid having a discussion with his CIO to a situation where he wants to walk out and greet him because he knows the CIO is bringing him something worthwhile.

The CEO wants to hear his CIO when he is consistent in:

  • Making business-driven recommendations,
  • Recommending projects that address a business issue or need,
  • Recommending projects that deliver tangible business value,
  • Always providing prudent cost justification,
  • Delivering the goods once projects are approved.

This is how CIOs and IT managers become partners with the executive management team.

I hope this insight helps you get your next project approved.

Best of success.

Note: This article first appeared in my Practical Management Tips for IT Leaders BLOG on CIO.com.

Save

Save

Coach employees the fundamentals of IT support

Excellent client service does not happen on its own. It happens because IT managers create the proper environment and teach their IT employees what is required to deliver effective client service.

 

A big part of a manager’s job is teaching and coaching. It doesn’t matter if you are on a sports team or in a professional IT support environment.

 

Good managers coach and reinforce the fundamentals of what it takes to be successful. They teach at the individual level to help each employee succeed. When individuals succeed collectively, the team succeeds.

 

What are IT support fundamentals?

Well, my list is pretty simple as you might expect. They include the following:

 

1.  Follow-up  –  This is one of the most important of all traits we need. Simply put, when something is committed to a client, our staff needs to follow-up and close out their promise. In other words, “Do what you say you will do.”

 

2.  Communicate effectively  –   IT people tend to lack good communication skills. It’s important for you to coach your employees on what and how to communicate with our clients, senior management, and each other.

 

3.  Project management  –  Delivering  projects successfully is how IT organizations achieve credibility. You may need to teach your employees how to work on projects or how to manage them. In fact, you may need to create a project management culture if it does not exist.

 

4.  Quality  –  We want our employees to do the job right and to do their tasks completely, , , high quality. Finish the job and do the work once by doing it right.

 

5.  Productivity  –  At the end of the day, how much an employee accomplishes is as important as how well they do something. Time management is essential and is a great coaching opportunity.

 

6.  Professional conduct  –  “Dress for success!”, they say. Coach employees how to conduct themselves at work and understanding the importance of looking professionally is very important for IT success.

 

7.  Being on time  –  Seems like a small point but it’s a major issue. Being on time for meetings, completing tasks and other commitments on time says a lot about you as an individual and an IT organization.

 

8.  Be conservative  –  When making a commitment, be conservative so you can “over deliver”. No one gets upset if we complete the work earlier or less costly than expected.

 

9.  Teamwork  –  Whether working with a client or with other IT employees, we are all on the same team. Respect for one another and working together as a team is an absolute requirement to achieve success.

 

10.  Positive attitude  –  People who have positive “can do” attitudes achieve higher levels of success than those who do not. IT managers must not only coach this but they need to lead by example and become the IT organization’s best cheerleader.

 

Don’t assume your employees understand all of these fundamentals.

 

Professional sports team coaches constantly teach and reinforce the fundamentals of a player’s position with them, , , and these guys have been playing the sport for years.

 

What you see consistently is that teams who execute the fundamentals of their sport the best are the winners.

 

Instill the fundamentals of IT support within each of your IT employees and your IT organization will achieve many successes.

Do New Year Resolutions Really Work?

I create New Year Resolutions every year. In fact, I can go back to about 1980 when I think it all started.

usmc_mike-and-dorine-1

Dorine and Mike – March 1972

My wife “lives for today” and doesn’t get too hung up on what tomorrow will bring. I wish I could be more like her in this regard.

This is not to say she doesn’t think about the future, , , she simply does not have a need to focus nearly as much on the future as I do.

Whenever we talk about developing new year resolutions or discussing what we want to be in the future, she has two comments for me:

  1. “I’m not spending time on this.”
  2. “I don’t care what you become; I just want you to grow up.”

I still hear this today from Miss Dorine after almost 46 years of marriage. We will hit #46 next week on December 26, 2016. Dorine is my BEST FRIEND in the world, and she has been a wonderful wife and companion for all of these years.

Her lack of enthusiasm for goal setting or developing New Year Resolutions doesn’t deter me from pursuing what has become an annual tradition. It’s something I look forward to around this time of year.

Every year around the holidays I start jotting down a few goals for next year. At some point I started creating two sets: one for personal goals and one for professional goals.

new-year-resolutions

In the old days, I used to be fairly lengthy and spent probably more time on them than needed. Now, I spend just a few minutes to jot down a few things a week or so before Christmas and then add/update the list through the holidays. By January 1st, I have listed what I want to commit to myself for the new year.

It’s not complex, doesn’t take much time, and I think it makes a difference.

Over time my list has gotten shorter and shorter as I now tend to list just a few things that I really want to accomplish for myself, either personally or professionally.

Why spend time developing New Year Resolutions?
My sense is that when you write something down, it makes it more important. Studies certainly suggest this to be the case.

You rarely accomplish anything unless you make it a priority and commit to getting it done. For me, I believe it’s important to make a few commitments to yourself each year. You owe it to yourself and good things can come of it.

I can tell you that many of the things I’ve accomplished (both personally and professionally) are due in some part because I wrote them down and made a commitment to make it happen.

A recent example is that for 2016 one of my personal goals was to lose 16 pounds. Well, mission accomplished, , , this time I actually lost the 15 pounds that always seems to be on my list. Next year, I want to go for 10 more pounds and reach my ideal weight. It’s all about focus.

Best of success in the New Year!

Save

Save

Save

Save

Save

Save

Save

Save

Understand supply and demand to manage client expectations

project successOne of the keys to success in IT management is being able to manage your client’s expectations.

To manage your client’s expectations, you need to know some things about the concept of “supply and demand” and how it applies within an IT support organization.

Demand is the technology support needed by your clients to address their business needs and issues.

Supply is your IT organization’s capability and capacity to deliver IT support.

You have to understand the dynamics of what’s happening in both “Supply” and “Demand” within your IT support organization’s environment to manage client expectations.

In most situations, there will be more demand than supply, your clients need or want more from IT than your IT organization can deliver.

This is normal and exists for most IT organizations. That’s OK, but to succeed you are going to have to balance the two somehow and manage your client’s expectation to what you can deliver.

Let’s take a team of five programmers and use them as an example to discuss these issues.

programming teamHere, you see we have one great team of five programmers. Let’s assume they all work on the same software application to make our example easier.

The Demand Side

Our demand for programming work is defined by a couple of things:

  1. Day to day support required of the programmers
  2. Backlog of new programming enhancement requests – new reports, new functionality, etc.

Your Help Desk should give you some sense for the “disruptive nature” of day to day support issues that hinder a programmer’s coding productivity.

If you don’t have anything, do a 2-week time study and have each of your programmer’s chart where they spend their time for every hour of their work day.

You might be surprised! This simple exercise will tell you a lot about what’s being pulled out of your team’s programming capacity to handle daily support issues.

Maybe you think your team is totally isolated and immune from day to day support. Don’t be fooled, do the time exercise and discover the reality of your situation.

The second part of “Demand” is in your Programming Backlog for new requests (new reports, new functionality, etc.).

You should have a programming backlog database of some type (maybe it’s just an EXCEL spreadsheet) that lists every programming request and an estimate of how many hours it will take to program the project.

If you aren’t managing your backlog like this, then you don’t know what your demand for new programming is. If you don’t know, you can’t manage client expectations.

The Supply Side

On average, a programmer can produce about 100–120 hours of productive code per month.

There are normally about 160 hours in a normal month of work (4 weeks at 40 hours per week). When you pull out time for meetings, training, sick, vacation and holidays, what is left is the actual productive coding time you get from a programmer.

Some months will be less than this average of 100–120 hours of productive coding time, some months will be more.

Over 12 months time you should see a programmer’s average work out to be about 120 hours per month of productive coding, roughly 75 percent of their work time.

If you are delivering less than 100–120 hours per programmer per month on average for 6 or more months, you probably have a productivity issue that needs attention.

Note: This measurement may vary depending upon your company situation or part of the world you live in and the productivity culture that exists.

OK, if we have 5 programmers this means our supply of productive coding (or capacity) should average between 500 to 600 hours per month as a team.

Let’s assume the demand for coding new reports, enhancements, and new features for this application is considerably more than our capacity. How do we increase our output, our supply?

There are several ways to increase the output of a programming team:

  1. Improve the existing team’s productivity.
  2. Have the team work more hours.
  3. Pay programmers incentive pay to do certain projects on their own time (on weekends and holidays or in the evenings after work).
  4. Hire new programmers.
  5. Contract programmers from the outside.

I’ve used all of these and every option will work to improve your programming team’s output.

One caution though is that “requiring the team to work more hours” will work to an extent, but long term use of this approach can create morale problems and put your programmers at risk of leaving your company.

You essentially have three options to address a programming backlog that exceeds your capacity:

  1. Reduce the amount of backlog
  2. Take longer to do the work
  3. Increase capacity to attack the backlog

The bottom line though is that you aren’t going to get twice the capacity with the five programmers you have on board now. If need is truly significantly higher than your capacity to deliver, you have to manage your client’s expectations.

There are essentially three ways:

  1. Reduce the demand
  2. Increase your capacity to deliver
  3. Take longer

Usually the answer lies within all three of these. However, Item #3 (Take longer) really isn’t doing anything different and probably may not satisfy your client.

You attack the problem when you do something about reducing the demand and/or increasing capacity.

The next thing you need to have a good grasp on is, “How much of your capacity goes to day to day support?”

It might be 80 percent of your total programming capacity to troubleshoot issues, fix things, or provide day to day support for the users.

If it is 80 percent, that doesn’t leave much to develop new enhancements that are being requested by users.

You need to have a realistic estimate of what day to day support requires from your team. Without it, you are doomed.

To manage client expectations you not only need to know what the demand for programming services is, you must also know what your capacity to deliver is.

This “capacity to deliver” includes how much programming is required for day to day support plus how much is available to focus on new requests.

Without this understanding, it is virtually impossible to manage your client’s expectations.

Be conservative

The next thing is that when you make commitments to your clients, you must be conservative.

Remember the “Golden IT Rule”,

Projects take longer and cost more than you think they will

Always position your team to over deliver.

No one gets upset if you exceed their expectations.

Someone always gets concerned when you don’t meet expectations.

One method I use is that I always start managing a new programming staff with an expectation that we can deliver an average of 100 hours of code per programmer per month even though I know we should deliver around 120 hours a month of new code per programmer on average.

Now, when you do this you need to know that I consider these programmers to be truly isolated from day to day support issues. Their full time is focused on software development and producing new code.

I know that if we are operating properly, each of these programmers will actually deliver on average more than 100 hours per month. So, when I give my client a forecast that we can deliver up to 500 hours a month for the team (5 programmers * 100 hours), I’m positioning the team to over deliver.

Let me emphasize this: Position your team to over deliver!

One of the best ways to manage a client’s expectation is to position your team to deliver more than what the client expects.

To do this, you must be conservative in what you commit to.

My approach with programming is to commit an average of 100 hours per programmer per month to the client and deliver somewhere around 120 hours per programmer.

Summary

Four key things will help you manage your client’s expectations:

  1. Understand the demand for your resources
  2. Know your capability and capacity to deliver
  3. Realize how much is used for day to day support
  4. Be conservative in your commitments

Do these things with your programming staff and other parts of your IT support organization and you will be able to manage your client’s expectations much better, and this will help your IT organization achieve more success.

This article first appeared in my CIO.com BLOG, Practical Management Tips for IT Leaders.

Save

Save

Save

Are you using committees effectively?

questionmark1I received an interesting question a while back and thought it worth sharing my response. The question came from one of my followers and went like this, “What do you think of Committee decision making and/or problem solving? What would be required to ensure Committee success?”

My response:
I agree that committees tend to take longer and are potentially not as responsive as you need to be. It all depends on what you create a committee to do and the guidelines you establish for its mode of operation.

I’m a big proponent in having committees made up of business representatives alongside IT representatives. For example, one of the things I always try to do when managing a Programming Support organization is to create a “steering committee” to review the outstanding programming change requests that exist in our programming backlog in order to determine what gets assigned for the next period (usually monthly) and what does not get prioritized. There are several reasons:

  1. The business is in the best place to know what needs to be a priority, , , not our IT organization.
  2. The business needs to realize that our company can’t fund IT to have unlimited resources and therefore work has to be prioritized.
  3. If we (IT organization) are left to prioritize these jobs on our own, we will never be as responsive as our business clients want us to be. Never! Clients will simply want everything completed “right now”.

When your clients are in the middle of determining what gets worked on and when, , , it’s a struggle initially, , , but over time it simply becomes our normal process of how we manage the business.

I can tell you that when the business units are making the trade-offs and are ultimately responsible for prioritizing the work, it makes life much better for the client as well as the IT organization and easier to support the client in this area.

I don’t believe all things work well in committees. We don’t run companies or manage in a democracy, , , but in places like programming support, strategic project initiatives, project portfolio management, etc. a committee can be very helpful.

I still like the fact that IT is represented as a full member of the committee and the IT representative is often who facilitates such meetings. Certainly, IT must be able to influence decisions but getting the client positioned to feel they are more in the “driver’s seat” and in control of their own destiny is a good thing for everyone.

The downside about running your company “by committee” is that you can have gridlock if you aren’t careful. In my view, a committee is best when used as an advisory group to help the management team make good decisions. More brain power is a good thing but can certainly slow the process.

meeting-3When creating a committee, it is important to establish good guidelines that help focus the members of the committee on the it’s mission and objectives along with operating guidelines to work within.

Be sure your committee is assigned a role that does not slow an organization’s responsiveness if this is a key measurement of performance.

Finally, committees can be very effective when making decisions about company direction, determining key initiatives for an organization to work on, even deciding the priorities of your programming backlog, etc.

For example, in 1991 our company President created a senior management committee in March to focus on cutting company expenses during the 3rd and 4th quarter. We wanted to take the company public the following year and felt we needed to achieve major expense cuts in order to achieve our 3rd and 4th quarter financial forecasts because of an expectation we would not achieve budgeted revenue numbers.

This committee met initially to understand the issue and to identify a list of cost cutting ideas. We assigned each “cost saving initiative” to a manager from the group. We met a second time to deliver our recommendations for how much we could save in our assigned cost saving initiative areas along with how we should go after the savings and when we should be able to achieve the savings.

When we all left the 2nd committee meeting, each of us had specific cost saving initiatives responsibility to make happen for our company and we were required to report monthly on our progress. We focused on the opportunities plus the President of our company tracked performance.

This committee focus was a huge success in achieving our objective and it positioned the company for a successful public stock offering the following year.

Managers make decisions but a committee used properly can be very effective in supporting managers of your company.

IT managers may need to change their work behavior

changePeople who work in IT have very consistent work behavior tendencies. In fact, 90 percent or more have similar tendencies in three of four major personality categories. The bottom line is that IT attracts a certain type of personality.

These work behavior tendencies help us become successful as technology experts, but they can present major challenges when you move into a management role.

It’s important for any IT manager to be aware of these tendencies and “what makes IT people tick.” Understanding them can help you achieve more success in multiple ways:

  • Being aware of your own personal work behavior tendencies can help you identify areas that need adjusting in order to succeed in a manager position.
  • Awareness of IT employee work behavior tendencies who report to you can help you manage and lead them better.
  • Understanding the dynamics of work behavior can even help you resolve employee problems.

Background

I’ve used several personality evaluation tools in my career. Early on, I didn’t put a lot of credence in their value; I thought they were bogus. I was wrong.

For over 10 years I used these tools in my CIO role and discovered they are accurate in describing an employee’s work behavior tendencies and helpful in many ways. I learned first hand that understanding the work behavior tendencies of a person is powerful insight.

In one company I was the CIO of we acquired 35 other companies. I obtained the work behavior profile of all the IT employees that came with these companies. Their profiles were consistently similar.

Initially, I thought it was just a coincidence. After seeing the same profile over and over again, I finally concluded that a certain type of personality type is attracted to IT. In a similar way, consistent personality types are attracted to sales professions.

I also measured over 100 IT managers who attended my IT Manager Institute for four years. Again, their work behavior profiles were predictably similar.

It doesn’t matter what your role is in IT. Whether you are an IT manager, programmer, systems or network engineer, project manager, work on the Help Desk or even run IT support as the CIO. If you are in IT, your work behavior tendencies are highly likely going to be similar to everyone else in IT.

What’s the point?

It’s simple. The work behavior traits that help you become an excellent technician can prevent you from achieving success in an IT manager role.

Let’s take a look at each trait.

There are four work behavior areas in many of the personality evaluation tools like Myers Briggs and others I’ve used, and here is what I have discovered:

Trait #1:  90 percent of all IT employees are independent, self starters and technically oriented. No problem so far; these work behavior traits can probably help you as much in a manager role as in a technical role.

Trait #2:  85-90 percent of all IT employees have a high sense of urgency. To say we are impatient is an understatement for most of us in IT. High sense of urgency is a good thing for IT managers as long as you approach major problem situations like a system outage in a way that has a calming and stabilizing effect.

Trait #3:  Over 90 percent are high detail and like to do the work themselves. This is great for a technical employee. Programmers and other tech employees achieve success pretty much on their individual performance; they are in more control of their own success. In a manager role, you depend on your employees to get things done. This is a big transition challenge for most young IT managers. Letting go of the detail and depending upon others can be a major obstacle.

Trait #4:  Just over 70 percent are shy and introverted. This is a big challenge for IT managers. As a programmer or systems engineer, strong communication skills are not so essential, especially communicating outside their inner circle. In an IT manager role, strong communication skills are required. The problem with shy people is that they usually don’t develop their communication skills because they don’t deem them to be needed. In addition, shy people have a lower desire to communicate. All of these issues are major stumbling blocks to success for IT managers and must be overcome.

When you think of the first three work behavior traits being at 90 percent or more, it’s pretty much everyone in your IT organization.

One more thing

If you put all of these traits together to make a work behavior profile, it sums up to be an individual who looks at work this way:

  • Let’s do it (self starter),
  • Do it now (high sense of urgency),
  • Do it my way (high detail),
  • and I don’t want to talk about it (shy and introverted)

marineThis is the makeup of an authoritative management style that works well in the military but not so well in a professional business environment.

Modify the last trait by communicating more and you have a persuasive management style. This style is much more effective for IT managers in a corporate environment.

Technical experts who become IT managers need to do two things if they have the four traits discussed above:

  1. Let go of the detail they are so used to being in. Have you heard the phrase, “You need to get out of the weeds!”? Managers must depend on their employees to take care of the detail. It won’t be easy but it’s necessary for your success.
  2. Learn how to communicate effectively. Strong communication must become a core competency so learn what and how to communicate effectively plus put processes in place that force you to communicate.

The good news is that if we need to adjust a couple of our work behavior traits, it is a straightforward thing to do and more success is in your grasp.

This article first appeared in my CIO.com Blog, Practical Management Tips for IT Leaders.

Triple Threat to IT Success™

triple-threat-to-it-successThere are many issues that can cause an IT organization to fail, but there are three that are at the root of most IT failures. I named it the “Triple Threat to IT Success”.

My first article in CIO.com’s Practical Management Tips for IT Leaders blog was titled, 7 reasons IT managers have the toughest management roles. It sets the stage for why IT management is so difficult and provides insight into the unique challenges IT managers are presented with.

In this post we continue building a foundation of the dynamics that take place in many IT organizations by discussing the Triple Threat to IT Success™ and what causes IT failure.

triple-threat-to-it-success

Many things can cause an IT organization to fail but what I’ve observed in hundreds of companies and in more than 20 years of managing IT resources is that there are three main culprits:

  1. IT – Business disconnect
  2. Project failure
  3. Poor communication

Understand these three problems and do a few things to prevent them positions your IT organization to achieve much more success.

Threat #1:  IT – Business disconnect
Simply put, your IT organization is out of sync with what the business needs from you. The company needs you to focus on “A, B and C” but IT is working on “X, Y and Z”.

abc_xyz

Many studies over the years have suggested this happens over 50% of the time. Plus, CEO and CIO surveys consistently place “keeping IT in sync with the business” as one of their top concerns.

Interestingly, discovering whether or not a disconnect exists between IT and the business is a simple task and takes very little time for an experienced CIO or consultant. So why are so many IT organizations out of sync with the business operations they support?

An IT – Business disconnect occurs primarily because the senior IT manager or CIO does not realize his/her organization is focused on the wrong things. They are certainly not out of sync intentionally. In fact, they believe their focus is exactly what their company needs from them.

Threat #2:  Project failure
The second major threat to IT success is failing to deliver projects successfully.

You may not realize it but IT project failure was instrumental in creating the project management industry. Before computers were introduced in the 1950’s we did not have this concept called “project management”.

The Project Management Institute (PMI) was created in 1969 and project management took off as the IT industry grew exponentially in the 70’s and 80’s.

By the early ’90s, most companies of any size were using computers to process payroll, general ledger and other mission critical applications. The IT organizations of these companies were also building a reputation of failing to deliver projects successfully.

Project failure destroys IT credibility so it’s a key component for IT success.

Threat #3: Poor communication
The third threat is the biggest threat because it has a lot to do with what causes the other two threats. Let me explain:

An IT – Business disconnect occurs when IT management does not communicate well with the senior management team. If you communicate what you recommend the IT organization should work on and gain confirmation from the senior managers of your company, you won’t have a disconnect.

Project failure often occurs when IT people start working on a project before quantifying what the specific objectives, deliverables and timing will be and getting agreement from the project sponsor. You can’t succeed if you fail to establish these expectations on the front end of a project.

IT managers in general have historically had a reputation of being poor communicators. It’s a label we unfortunately earn because the fact is that most IT managers actually do struggle in this area.

A big reason for this is that from my research and experience I’ve concluded that over 70% in IT are shy or introverted. People with a shy and introverted personality trait do not invest in their communication skills and they don’t view communication as all that important.

IT employees are more technically oriented than socially oriented; it’s one of the traits that attracts people to IT type of work. There is nothing wrong with this but it can make IT management very difficult because effective communication is a key ingredient to achieving IT success.

Summary
I coined the phrase, “Triple Threat to IT Success™” in 2005 to help me discuss the three major issues that cause an IT organization to fail. Being aware of these issues and taking measures to overcome them will position you for more IT success.

Download a 1-page flyer that identifies the triple threat and includes tips to prevent them in your company at http://mde.net/triple.pdf.

triple_tips

This article first appeared in my CIO.com Blog, Practical Management Tips for IT Leaders

Don’t assume others know what you know

manager_coachWe often think others know something when in reality they may not. Don’t always assume your employees or your clients know what you know because they probably do not.

In many cases some of the simplest things in life are not all that well known by others you come in contact with. I can give you a couple of examples:

  1. I wrote an article for TechRepublic once about using a project scheduling template to help me monitor and manage a project. In just a few days there was over 15,000 downloads of this template. It was one of the simplest tools I have and I was amazed at how many downloads took place from that one article.
  2. My brother told me he had discovered this new technology gadget. When he tells me something like this, there is usually something pretty neat I’m about to learn about. Then he shows me a wireless PowerPoint Presenter device. I thought he was kidding because I carry one with me all the time and have used these devices for 10 years. He wasn’t kidding, , , he had just discovered it.
  3. Early in my management career I discovered the team I was managing didn’t know how to troubleshoot a client problem. They had significant experience with the technologies we were supporting but struggled in defining the problems and underlying issues causing them. It was a surprise and an example that employees can sometimes lack the basics. IT managers need to coach employees the fundamentals just like they do in sports teams.

The point of all of this is, “Don’t assume others know what you know.” I see it all the time in my IT Manager Institute classes, , , many of the basic processes or templates I share are game changers for some of our students, , , and sometimes they have been managers for many years.

An example of this is that I shared a New Employee Orientation Checklist with a class and the senior manager in the room thought it was great. He had been managing IT for 20 years and didn’t have anything like it, , , and as he said, “This is so simple and basic, I should have created something like it 15 years ago.”

Don’t assume others know what you know. It would be a big mistake.

Positive energy creates positive results

I’m a big believer that positive attitudes create positive energy and those around you feel it. Likewise, negative attitudes create negative energy and people feel that as well.

glass half fullI’ve always tried to look at the “glass half full” as opposed to “half empty”. It’s the same situation, the difference is just how you look at it.

When our son had his car accident in 1993 and we almost lost him, it was the most terrible experience a parent can go through, , , but Dorine and I kept looking and thinking about the potential, , , and not about the terrible challenges Eddie was facing.

Today, Eddie is 39 and still has physical challenges plus a significant short term memory loss problem. He can’t remember something that happened 30 minutes ago. But the upside is that his long term memory is intact and strong.

Eddie never has a bad day, , , something that is amazing to us considering his physical challenges and pain he deals with. But it’s true, he is the most positive person I know, , , maybe it has something to do with short term memory loss.

The point is that Dorine and I stayed positive and kept encouraging Eddie during the darkest of times. I could tell you dozens of stories that still give me chills of joy and some that caused grave concern at the time.

We believe our positive attitudes helped Eddie recover to the level he has and why he is such an inspiration to so many. Everyone who meets Eddie seems to be drawn to him because of his positive attitude, , , he truly has a special aura of positive energy.

Positive attitudes really do work. We have seen it over and over again in our personal and professional lives.

As an IT manager, it’s important for you to stay positive and to encourage others. Your attitude sets the tone in your organization. If you are not positive and positive energy doesn’t come from you, it’s very hard, if not impossible, for your team to be positive. It starts with you, , , never forget this.

Treat every day as a new day and a fresh start. Go into work with positive thoughts and look forward to the challenges that will come up today. Remember, if there weren’t challenges and problems, they probably wouldn’t need you and your position in the company.

Positive energy is a contagious thing, , , create positive energy and watch others respond to it.

Best of success

Is your IT organization in the fire prevention business?

fireman1Our technology people are great at fighting fires, , , or “fixing things”. They aren’t always so good at learning what causes the problems and identifying how to prevent the problem.

Preventing problems from occurring is far better than being good at solving problems and fixing things (fighting fires) after they occur. Much bigger than you probably think.

Eliminating problems from happening helps everyone:

  • Reduces your client’s loss of productivity
  • Improves your IT staff’s productivity
  • Eliminates aggravation and stress for everyone

There are many more benefits but these three are worth a lot.

One of the best stories you can tell your client is that your organization saw a set of problems, analyzed them to determine what was causing the issue, and then put in preventive measures that either reduced or eliminated them.

This is a simple story but a powerful one in that you are proactively looking at the “business of IT support”, not just working on technology and being reactive.

If you can show specific statistics or numbers, , , even more powerful!!!!

measure chart

Teach your staff to take the extra step and determine what is causing the problems they deal with day to day and try to determine how to prevent them. Preventing problems will do a lot for your IT organization in building trust and strong client relationships, , , something we need in order to achieve IT success.

Train your staff how to fight fires but teach them that we need to be in the “fire prevention business”. Preventing fires shows  proactive approach – POWERFUL!

Is your IT organization preventing fires or simply reacting to put them out when they occur?