Are you prepared for a disaster?

We’ve all heard things like ” We need a disaster recovery plan”, “Be sure your data is backed up”, “We need off-site backup”, etc.

I’m sure most know of or have experienced firsthand situations where a company experienced a disaster and had to go through a recovery. I’ve seen many because of having jobs in companies where we supported hundreds of other companies using our technologies. I can tell you that it’s always a difficult and tough situation to go through.

The question is, “Are you prepared for a disaster?”
I can hear most of your answers already, , , “Sure we are. We have backups and a disaster recovery plan. We are good to go.”

Well the next question is, “Have you tested your disaster recovery plan?”

If you haven’t shut everything down and truly tested a recovery, then you don’t really know.

Two examples

  1. My last company had a disk failure 6 months before I got there. When they pulled in the backup tapes, they couldn’t read them. Net result was mission critical systems down for over two weeks. Wonder why senior management decided to find a new CIO?
  2. I had an IT Manager Institute student have to return to his company prematurely because of a system failure and their recovery procedures not working. He was able to return to the next class but I think you see my point.

Recommendations

  1. If you don’t have a disaster recovery plan, create one.
  2. If you haven’t tested it, be sure to conduct a recovery test to insure it will work.

Model #63 – Escalation

One of the models in my IT Management Models book is about escalating critical support issues.

Description:
Escalation steps should take place automatically for certain circumstances. Develop processes and teach your IT staff how and when issues should be escalated and to whom the escalation needs to go.

Every type of business has circumstances that justify escalation to higher level managers. Establish your IT escalation procedures to protect the business and to help your team be successful.

There are times when issues need to be escalated to more experienced people in your organization. Sometimes, the information may need to be escalated to senior management outside of your organization. It is important to establish clear escalation procedures in your organization so critical business issues get the proper amount of attention at the earliest possible moment.

Escalating when appropriate should be automatic and simply part of the process of supporting the technology.

Define escalation procedures: What, when, and to whom – When defining the escalation procedures you need in your IT operation, you must be specific as to what requires an escalation act. Define clearly to whom the escalated message should go to or what does one do in the escalation procedure. You also should define when an issue gets escalated. In my IT operations, I will set up escalation procedures for all types of business situations when I believe it will improve our support operation. In a few cases, I want to be notified immediately so I can be sure we are looking at the problem with a management perspective as well as a technical one.

Build escalation procedures that help your team succeed – Escalation procedures can help your team be more successful because they position the team to be more responsive to problem issues that can occur. Getting stronger skills on a “down system” issue quickly in order to minimize the downtime you might incur is a positive thing for all involved.

Escalation procedures protect the business – Protecting the business is our job when it comes to managing technology. Responding quickly and if necessary with an “all hands on deck” response to a critical issue is appropriate when we are talking about mitigating business continuity risk.

Coach your team so they are “automatic”
– You want your escalation procedures to take place automatically. Coach employees, inspect the process with simulated drills, and do what is necessary to get them handling escalation steps automatically; you will be glad you did when they have to escalate an issue.

Click here to learn more about IT Management Models.

Two “Bits of wisdom” that helped my career

There are two very important concepts that one of my favorite managers gave me. Bryan Hathcock was a senior Systems Engineer (SE) Manager for IBM when I showed up in the late 1970’s. He became a mentor and a good friend and still is today. I learned a great deal about managing effectively from him.

The very first week at IBM, Bryan began coaching me and molding me into a strong SE. His management style was persuasive and not authoritative. He was more comfortable in pointing out the direction for you to take than micromanaging an employee on how to do everything. To say he empowered me to do the job is an understatement, , , I learned a lot about empowering employees from him.

In the first week, he gave me some advice that I still adhere to today. It has been something that has made a real difference in my career as a manager and professional, possibly even as a human being.

I know that may sound quite strong, but I believe it to be true.

Bryan’s advice, “Observe others and incorporate what you see as strengths into your own style of doing things.”

The context of these words of wisdom was when he was telling me about his plan to pair me up with senior SE’s and Marketing Reps over my first six months at IBM to learn about the business. He suggested that I would see some very different, even unique, approaches to dealing with various customer issues, opportunities, and problems.

Bryan’s advice was to observe how different people go about their business and when I saw something that worked well and was a strength, to incorporate this approach or skill into my own way of handling situations. As for those things that do not work well, exclude them from your repertoire.

I took this advice to heart and to this day I still observe others and learn from the actions of others. You might say that over the years I have been a “student of management”. I pick up sound management techniques from all types of sources.

It might be from a management situation I observe taking place, from a movie, even from my wife who makes comments about a situation. Management situations occur all over the place; I tend to look for these situations and learn from them.

One of the best examples of management in a movie is in the first five minutes of Gladiator. If you are looking for it, you learn a lot from a very short segment such as things like respect, commitment, motivation, strategy, and leadership. Don’t laugh, I see every one of these concepts every time I watch this part of the movie. When I need a morale boost, I put my Gladiator DVD in the box and watch just 5 minutes of the movie. It’s great because I’ve identified 15 management traits from the first 5 minutes..

Bryan gave me another piece of advice at the time I was about to leave the SE organization and move into the Sales organization. Part of my career path was to become a Marketing Rep after three years as an SE because having sales experience would be beneficial to my future career as a manager.

In one of our last meetings as Bryan’s employee, he gave me some extremely good advice that I’ve used in counseling many of my employees over the years.

His advice, “When you move into a different role, be sure to focus on aspects of the new role and what it takes to succeed in the new role.”

What he meant in this case was that I needed to drop the technical skills and focus I had on technology from my SE experiences once I became a salesman. Having strong technical skills is not what will make you a good salesman. It certainly won’t hurt, but if you continue to focus on the technology, you won’t be developing your sales skills and doing things that are going to make you successful as a salesman.

This is some of the best advice I have ever had in all of my career !!

I believe this advice is what helped me eventually leave the technology behind when I became a manager and focus my full attention on what it takes to succeed as a manager. It was a very difficult transition for me just as it is for most of us who are initially technical experts who become IT managers.

The problem, of course, is that as an IT manager, you simply don’t have the time to maintain your technical skills at the expert level and also do what you need to do as a manager to be successful.

Something has to give.

If you don’t focus your time and energy on management issues and in developing the skills that are needed in this discipline, your team and company suffer and your organization’s results will not be to the level they should be.

Managing an organization is totally different than managing technology issues as a technology expert. All of a sudden, you have to get things done through other people and not yourself. This was probably the hardest part for me to learn because I was so used to doing things myself and only being accountable for myself. It is one of the more difficult transitions for all of us to make and it is possibly the most important aspect of becoming an effective IT manager.

Management is a full time job and so is being a technology expert. Both disciplines can be very rewarding for a person, but it is very difficult, if not impossible, to be effective in both areas.

Conclusion
I learned a lot from Bryan, but these two concepts have probably been the most important in helping develop my career.

  • I continue to observe others all the time and learn from them.
  • I look for management situations that add value to my existing skills and understanding.
  • When I take on a new role, I quickly try to focus on what’s important to be successful in the new role rather than focusing on what I know from my past.
  • I keep the past in the background and use these experiences when they are helpful, but the concentration and focus is placed on developing skills and dealing with issues that will make me successful in the new role.

Incorporate these two pieces of advice Bryan gave me in your own approach and you will find that they will benefit you for years to come.

Don’t beat around the bush

When coaching an employee you need to be direct and to the point, , , you don’t want to “beat around the bush” or avoid discussing the issue.

I’ve seen some managers try to address a poor performer and they avoid telling the problem employee what the problem is, , , they avoid the real discussion that’s needed.

You can’t do this; it isn’t fair to the employee. If the person is not performing up to the level needed to succeed, you owe it to the employee to let him know. To avoid this is failing as a manager and also failing to support both the problem employee and the rest of your team, , , plus failing your company.

It’s not negative to tell an employee they are not doing well and then list specific examples of why that’s the case. It’s actually a positive, , , especially if the employee rectifies the situation and becomes successful as a result.

Many managers don’t like conflict so they avoid discussing the problem. When you do, you are letting everyone down including yourself. Prepare for the meeting, get your facts together, be prepared to show the employee what he needs to do differently to be successful and be supportive in your efforts, , , you can avoid conflict when you are genuinely trying to help the employee succeed, , , but you ultimately create a real conflict of some kind down the road if you allow a poor performer to continue along without telling him about the problem.

If there is an “elephant in the room”, be sure to point it out and be direct, honest, and supportive in your discussions.

Keep a journal

You may not realize it now but 10, 15, maybe 20 years from now you may look back and discover that right now is one of the very best times of your career.

I’ve had a super career, , , , worked for some great companies, , , worked with some of the best people in the industry, , , and I have truly enjoyed most of the aspects of my 20-plus years working in a corporate setting in IT manager and CIO roles. The last 10 years of running my own training company has been icing on the cake.

There have been a few downside moments but for the most part it has been good.

Something I do now that I wish I had started earlier in my career is to maintain a journal. I actually keep two journals. One is a personal journal and the other is what I call my business journal. Both were started some ten years ago when I started my company.

I don’t write in them every day nor every week and not even every month. I write in them when I want to log something that I feel is an event worth remembering, , , or that I would want my son to read when he is 60 years old long after my career is over and done with.

I add photos, charts, do a little drawing (albeit my artwork is very crude, , , and I use the term “artwork” carefully), and make comments that I believe will be worth recalling when I’m 80 or worth sharing with others.

Things like:

  • How it felt when I received my first set of published books
  • Sitting at the airport for my first trip to South Africa
  • Launching my IT Manager Institute Self Study from The Point at our Camp Liberty cabin
  • Learning something that boosted our business
  • Strategies I put into place to grow the company
  • A special “date night” with my wife
  • A funny event that will make me laugh every time I read about it

Little things, , , big things, , , what is important is that there are things taking place in your life that you will want to remember. I recommend you write them down in a journal because one day you will be mighty happy you wrote a few comments about that special event you had with your employees, , , an award you received from your company, , , how you felt when you finally got the big promotion you’ve been working for, etc.

Keep it simple and make it something that is special for you, , , because if it is it will be special for someone else to read one day.

What’s the Russian’s plan, son?

One of my favorite lines was in the movie Hunt for Red October when the Captain of the US Aircraft Carrier asks the young officer, “What’s the Russian’s plan, son?”

The young officer had just laid out the scenario about the Red October submarine Captain Rameus (played by Sean Connery) defecting from Russia and how the entire Russian Navy was looking for him.

The Captain asked, “What’s their plan?”

Tired and without sleep for two days the young officer goes to temporary quarters set up for him to get a little rest. Upon rising, he showers and shaves before heading back to the ship’s Bridge for follow-up discussions with the senior officers. As he shaves, he looks in the mirror and starts asking himself questions, , , “What’s their plan?”, , , “How does a nuclear submarine and its entire crew defect?”, , , “the entire crew defecting doesn’t seem possible”, , , “How do you get 100 sailors off a nuclear submarine?”

You can watch the movie to get the full context of the situation, , , but here is a question for you,

“What’s your plan?”

Do you have a plan?

“A plan for what?”, you might ask.

Well, , , anything, , , but at a minimum you ought to have a least two plans:

  1. Your IT strategy and plan for supporting your company
  2. Your personal career plan

Let’s focus on the second one – your career plan. The question I ask everyone I have a career planning discussion with is, , , “What do you want to be when you grow up?”

Do you know what you want to be? Have you given much thought to it? What do you want in your career and in life? Or are you simply floating along?

Nothing wrong with drifting along, but those who achieve great success identify what they want and put an action plan in place to prepare themselves to achieve it.

They go for it !!

If you want to be the best programmer, invest in your programming skills, learn new technologies that will help you be a better programmer with more productivity and quality in your work, , , and become the best programmer.

If you want to be a great project manager, invest in your project management and people skills. Start tracking your projects to quantify the results you are getting. Do you know what percentage of your projects are delivered on time, delivered within budget, and meet client expectations? Do you know why certain projects failed and now how to prevent these issues from occurring in future projects? Can you also quantify the benefits each of your projects have delivered? If not, learn how to do all of this better and better and become a great project manager.

If you want to become a successful manager, learn what it takes to succeed in the management role you are shooting for and what paths are appropriate to get a shot at management. When you get the opportunity, hopefully you have invested in yourself to be prepared. Many aren’t and do not fare well as a result.

Leading and managing others requires a whole new set of skills than what you may have developed in your technical role so learn what is required and go prepare yourself. It may seem obvious that those who are prepared tend to get the assignment and do well as a result over those who are not prepared. Seems obvious but many miss the obvious.

So, , , what’s your plan? If you don’t have one, now may be a good time to start thinking about what you want in your career and begin developing a plan to get there.

Need help? Take a look at Develop a Career Plan for some quick tips and a career planning tool.

Two more IT Manager ToolKits awarded

In the last two weeks we awarded two more IT Manager ToolKits to random selections of the Subscribers to our ITLever Blog. That makes 9 ToolKits we have awarded and the big drawing will be December 5th when we select a recipient for an Apple iPad.

Most recent winners are:

  • Edwin Lee  –  Luzerne, Singapore
  • Dave Stringer  –  Sydney, Australia

We have subscribers from all parts of the world and appreciate your support.

Click here for a list of all winners.

Is your IT Organization just a “cost center” ?

How does senior management of your company view your IT organization?

Do they see you as simply a cost center, , , an organization that spends lots of money, , , something that’s probably necessary but hard to identify the value they get from such expenditures?

Do they understand what your IT organization is spending money on and why?

Do they think you and your IT employees have an insatiable desire for technology, , , new toys that are pretty darn expensive but may not contribute to the well being of the company?

If you haven’t asked yourself these questions you need to. It’s vitally important for your success to learn how your senior management team views the company’s IT organization. IT is an investment and you hope they view your organization and what you are doing as a very good investment.

It’s very easy for senior management to see you as simply a cost to the company. Over 90% of all IT organizations do not create revenue for the company so every dollar you spend truly is a cost to the company.

The question is this, “Is the IT expense incurred a good investment or not?”

Another question of sorts is that you should realize how much most senior management teams want to spend in IT. Do you know the answer?

It’s pretty simple, , , most senior management teams want to spend $0.00, , , nothing, , , nadda. Most senior management teams would spend no money in IT if they could.

The problem is that your company needs technology for people to do their jobs, , , and technology has to be supported, , , so we need an IT organization. But what’s more important is that your IT organization needs to provide so much real value for the company that senior management wants to find ways to take advantage of the leverage IT offers the company.

That’s right – leverage.

Your IT organization gives your company more leverage than any other organization in your company. IT is the only organization that can positively impact every other organization in the company. Providing technology solutions can improve productivity or help reduce cost in every organization of your company, , , real leverage.

But, , , if your senior management team sees your IT organization as a cost center, they don’t understand the leverage possibilities you offer. And if that’s the case, they look for ways to limit spending in IT, , , not for ways to take more and more advantage of the leverage possibilities you offer.

How do you find out?
Simple, , , go ask them. Ask your senior managers how they view their IT organization – a value add, a tangible business value, a necessary expense, or a drain on resources?

Can they articulate and define the business value your IT organization provides in quantifiable and specific terms?

If they can’t, it’s very possible they don’t really have a good indicator as to what the value is that you bring to the table, , , and they probably see you as a cost, , , or “cost center.”

Better yet, , , can you define the business value your IT organization provides to your company? Not in a general way, but in very specific terms that identify quantifiable and tangible business value resulting from the work IT is doing. If not, there is much work to do.

Do you know what business value is? If not, I recommend you read the post titled, Business value is key right now.

IT can be a super star
Become an IT organization that does three things consistently and you are golden.

  1. Your IT recommendations always have tangible and quantifiable business value objectives.
  2. Every IT recommendation can be clearly cost justified.
  3. Your IT organization delivers what you commit to deliver.

Every day you must earn your company’s respect.

Every day you must help your company understand the business value IT is providing. If you don’t communicate this to managers of your company, they won’t know – GUARANTEED !!

Create this understanding and gain their respect by delivering what you say you will do and senior management will help you do more for them by funding more and more IT initiatives. It’s the key way to becoming a partner with the senior management team of your company.

Don’t allow your organization to be considered just a “cost center”. You and your staff deserve a lot more, and the ball is in your court to do something about it.

Force yourself to communicate

Are you aware that over 70% of us in IT are shy and more introverted as opposed to being outgoing and extroverted? I’ve been studying IT personality types since 1990 and have measured hundreds of IT managers and technical resources. The results are so consistent it’s almost scary.

If you work in IT, I can guarantee you that there is a 70% or better likelihood that you are shy.

You may not appear to be shy around your immediate network (your pals), , , but when it comes to socializing with people outside your network it is a struggle for most IT people.

Doesn’t matter if you are the CIO, a seasoned IT manager, a programmer, project manager, or desk top technician. If you work in IT, the odds are high you are more introverted.

Two traits of introverted people
Before I give you these, let me just say that there is nothing wrong with being shy and introverted, , , nothing at all. What it does mean is that certain things you need to do to be successful will be more difficult.

Trait 1 – Poor communication skills. Shy and introverted people have more difficulty in social settings and being able to communicate effectively, , , unless they have recognized this problem and made efforts to develop these skills.

Trait 2 – Lower desire to communicate. This may be a bigger issue than actually being a poor communicator. This lack of desire to communicate with people outside your immediate network can be a big problem for any IT manager. To succeed you must communicate effectively with several groups of people:

  • Senior management
  • Department managers
  • Employees
  • Vendors

Put things in motion
I’m one of the majority of IT managers who is introverted and shy. If you were to attend one of my classes or meet me in person, you probably wouldn’t believe so or recognize it in me, , , but I can assure you I am. My wife of almost 40 years would also verify this for you, , , and she certainly knows me, even better than I know myself I think.

Because I know I’m shy and introverted and I understand the challenges this trait creates, , , I put some things in motion that will force me to communicate as soon as I start managing an IT organization.

Let me repeat, , , FORCES me to communicate !!

  1. Monthly IT Support Status Meetings with key clients
  2. Monthly IT Staff Meetings with my IT employees

These monthly meetings require me to prepare and to communicate with clients we support (viewed as senior managers and department managers of the company) and the employees in my IT organization.

Communicating with your clients and employees on a regular basis is critical in keeping them informed and giving you the opportunity to coach and manage expectations. When you fail to communicate you lose credibility and essentially lose touch with the people you need to be close to.

When you know one of these meetings is coming up, , , you will prepare for it and communicate with the group you plan to meet with.

Make it simple for yourself. When you join a new IT organization, create a schedule to meet with your staff for 1-2 hours the first week of every month. This schedule will take the guesswork out and also eliminate your procrastination. If you don’t schedule it, things will come up and you won’t get around to it.

Do the same with your clients by scheduling monthly status meetings to cover the support issues and status of key projects that impact your client.

Schedule your communication events and make it happen.

Donald Trump and Project Managers

One of the few reality TV shows I like to watch is Apprentice with Donald Trump, , , one of the most successful real estate developers in the world.

I find it interesting to watch the dynamics among the participants trying to become Mr. Trump’s new apprentice, , , to go to work for him.

In this particular series, every participant is without a job. All have been successful in the past but due to the bad economy they have been impacted by layoffs and downsizing that have occurred in the last two years. Each candidate is looking for work.

To give you just a bit of background of the show, , , the participants are divided into two teams and each week they compete in a business project of some type, , , it could be selling ice cream on the streets of New York City, creating an ad display for a new product announcement, hosting a charity event, , , or any type of thing a company might get involved with.

Every week each team selects a project manager (PM) and the teams are given basic information about the project objectives and key things that will make it successful. Then the two teams go their separate way to develop the project and deliver on the objectives that have been communicated to them.

Pretty simple – right?

You would think so, but it never fails to amaze me how weak most people are in managing a project, , , and some of these people are supposed to be quite capable professionals.

It also never fails to amaze me as to the dynamics that play into a project because of the different personalities and egos of people on the team. It can be quite ugly at times and illustrates the difficulty that can exist in trying to manage people.

Does the vision of “herding cats” ring a bell?

Rarely does a contestant manage the project really well. Basic things like confirming the objectives and deliverables up front almost never occur. As a result, many projects deliver less than what they should or miss the target completely.

Most conduct a Project Kickoff Meeting of sorts but the quality ranges from excellent to unsatisfactory with most leaning toward the poor side.

This week’s episode was quite interesting and showed just how frustrating a manager who is responsible for projects in his company can be, , , in this case, Donald Trump.

The objective was to conduct a fashion show that night for a large company to highlight their shoes and the “walkability” of the shoes. The guests were to be a list of celebrities and friends of Donald Trump.

One team did a great job, , , the other team was simply awful.

At the end of each project, Mr. Trump fires someone after meeting with all the participants in a Board Room session to critique the two project teams and to announce a team winner.

In this case, Trump was so disappointed (and probably embarrassed) with one team that he ended up firing both the Project Manager and one of the key participants in the project.

The key participant was the person assigned the task of MC (Master of Ceremonies), , ,  or announcer who described the shoes each model wore as they walked down the fashion show runway to display the shoes. Nice guy but just a terrible speaker in that kind of setting, , , and totally unprepared.

Trump focused in on the key points in the Board Room as he ripped the project manager (PM) and a couple of members of the team who had done so poorly, mainly the participant assigned the task of Master of Ceremonies for the event.

Trump asked a few key questions any manager should ask his PM:

  • Was the person (MC) capable of doing what you asked of him?
  • Did you inspect to validate he was capable?
  • Why didn’t you have a real rehearsal beforehand?
  • How can you expect to succeed with no rehearsal?

There were several problems in this project:

  1. The PM did not assign people tasks they were capable of.
  2. The PM did not inspect to insure each task would be executed well.
  3. The MC (presenter) had no clue about how to prepare for a presentation of this type (more on this in a second).
  4. There was no real rehearsal to prepare so they ended up “winging it”.

The bottom line is that the PM did a terrible job and allowed some of his team members to be put in a situation where they had no ability to succeed.

Being named Project Manager does not mean the PM will actually deliver.

Having a credential that says you are a PM does not guarantee success.

And certainly just because someone tells you they can do something as in the case of the MC does not mean they can actually do it.

If the PM had inspected the MC before rehearsal time, he would have discovered that the MC was making a mountain out of a mole hill. He was developing detail notes to use to talk about the shoes as a model walked down the runway. When I say detail, , , it must have been minute detail, , , way more than what you need for such an event.

When the show started and they handed the microphone over to the MC, he gets up there with a laptop in hand and starts, , , or let’s say “tries”, , , to introduce a model and talk about the shoes she wears. Right off the bat it was obvious he was not prepared, and holding the laptop was awkward and looked idiotic.

He scrambled and was obviously uncomfortable, , , mispronounced many words, , , did not describe the shoes properly and when he did it was not what you want to say about them, , , had long pauses of uncertainty.

TERRIBLE !!!

All he needed was a 1-page PowerPoint slide for each model with a couple bullet points on a card describing simple elements of the shoes that reinforced “walkability” and “style”, , , simple, , , easy, , , and to the point. It took the MC all day to develop his comments, , , for a task that should have taken 30 minutes, , , OK, maybe an hour at most, , , there were only 8 models.

Get rid of the laptop and walk up there with a few note cards, , , and above all know what you are going to say. Much easier.

The only thing that did not go wrong was that the laptop battery lasted through the presentation. If the battery had died I’m not sure it would have been worse.

The key problem, , , the MC did not know what he was doing or even how to go about his task so he over complicated it, , , and the PM was not close enough to the project task to determine if it would be successful.

Mr. Trump was truly frustrated with this team as any manager would be. They failed dismally and embarrassed him in front of his friends and the company he was conducting the projects for. He skipped through some of the protocol he normally goes through in the Board Room and fired both participants without giving it additional consideration, , , first time to ever do this.

A couple of lessons in all of this, , ,
– You can learn a lot by observing others.
– Assign tasks to people who can do the work.
– Inspect to insure they can do the work, , , and are completing the work.
– Make adjustments when you see something isn’t working.

At the end of the day, the objective of any project is to succeed. Making an adjustment might hurt someone’s feelings but that’s better than failing and getting yourself and possibly others fired.