Regroup and Refocus on Transforming your IT Organization

This week I find myself frustrated in the quagmire of politics and bureaucracy. My typical role in an IT organization is to remove barriers to success, and in parallel motivate and lead them in the right direction. At times however, the sheer amount of work that needs to be accomplished can be incredibly overwhelming. In maturing organizations even the smallest task can require a new policy or procedure to be written. To combat this, the only true solution is to fall back on basic principles of time management, prioritization and delegation. It may feel like the house is on fire, during a hurricane, with the basement flooding, while the volcano in the backyard is erupting and causing an earthquake. In reality however, the situation is only as dire as you make it.

The first step in calming yourself and your team is to have an overarching strategy towards turning a team around. A great example of this is the 4-s strategy can be found in a blog post on entitled “how to turn around a failing IT department” This may not work for everyone, but the key is to begin developing some level of structure to your change efforts.

Now, take a look at your core processes. I don’t mean your “nice to haves” or things that are exciting. I’m talking about the basic things. Examples include:

  • Can you buy things, and can your customers buy (or organization fund) your services
  • Who can make authoritative decisions about the IT organization, what are the limits
  • Can you process the hiring of people, can you terminate people?
  • How will you document new decisions and make them publicly available?
  • What failing services, truly prevent (not degrade) business functions?

It may sound counterintuitive, but address the “hows” first, establish procedure and get everyone doing things the same way. Take small iterative steps and adjust your plans accordingly. Remember, your first goal is to “stop the bleeding”

I’ll be writing more on this topic in the near future……stay tuned


Can anyone explain this? :)

10 Most Dangerous Species of Help Desk Analyst

The link below is a great description of the type of Service Desk Analysts to avoid. (And its pretty entertaining as well!)

What is a Netbook?

As the saying goes, if I had a nickel for every time I’ve been asked this question I’d be a millionaire by now. Many are of the opinion that a netbook is a small inexpensive computer based on a specific type of hardware. Such as an intel Atom processor, 10-inch screen, and less than $300. I’m going to take a different approach.

Here’s the reason why….

The basic premise behind a netbook is that you have an inexpensive laptop and that store your data in the “cloud.” I would argue that any computer can be used for this purpose, and could technically meet the definition of a netbook. I can buy an intel core 2 duo laptop with 2gb of RAM and a 15″ screen off of ebay for $200. If I treat it as a netbook, and only store my data in the cloud (or a home server for us IT geeks) then I have better performing device, that costs less, and in my opinion is a much better deal.

So next time I’m asked what is a netbook? I’d reply with its all about how you treat your laptop.

I just passed the Certified Virtualization Expert Exam


After 1 week of 8:00AM to 6:00PM of training I passed the CVE Exam! I always get excited about new certifications.