What are you thinking?!?

The concept of IT Service Management accompanied with the ITIL Framework elicits many different responses from all levels of the organization. From the Management side, the general focus question is “What will it cost me?” From Middle Management it is; “How will I allocate resources?” and to the man or woman on the front lines it is “What are you thinking!?” The latter is always the voice that is often missed in communicating the benefits to the organization.

There is plenty of talk targeting the implementation of ITSM or ITIL revolving around defining business requirement to drive IT Services. Processes and steps to providing these services in the most efficient and cost effective manner is not always addressed. Even with the best intention of proactive management of IT environments to predict and support future business growth or potential weak points, communicating that is often an uphill battle day one.

These are all very valid points in delivering a true Service Management environment to any business. In order to achieve this, one area is consistently overlooked; the role of the individual. This can be attributed to the fact that unlike processes or tools, it is extremely difficult to discover, identify and document. It is the intangible element.

Processes can be defined, people can’t. Many implementers, whether internal to an organization or brought in from the outside to consult on what needs to occur to improve IT Service to the Business are very versed in the tactics needed to implement any of the areas of IT Service Management. The challenge is convincing the individual that what is being proposed can inevitably make their lives easier.

Communication needs to be tailored to the hands-on audience, much in the same light as you would with Management or even Middle-Management. There is a benefit that needs to be explained to gain buy-in. Explaining the monetary benefits and ROI to senior Management is only one piece of the puzzle. Determining the most effective methods of resource management and reporting to Middle Management is also part of the critical path. Understanding and communicating the true benefit to the individuals who are tied up with daily projects, firefighting or disgruntled users must not be approached as an afterthought.
The term “Grass-Roots” is often thrown around in various seminars and case studies but there are living, breathing people who comprise this Grass-Roots element that are vital to the success in moving forward with any attempt to become a high performance organization. True leaders realize this; successful programs are ones that focus on all levels of the organization.

So what is the key? Some believe that a complete buy-in and enforcement from Senior Management by default, forces the organization to comply. This is not to say that Senior Management buy-in and commitment is not important, but to get to the goal faster, having a motivated, mobilized workforce behind the effort will accomplish tasks and milestones more effectively if the troops are made to feel as if they are part of the solution on delivering the end product.

The truth of the matter is, everyone has their processes. Some good, some bad and some definitely ugly. Nevertheless, they are processes that people put time and effort into developing to make their own contribution to the organization better. Discounting these efforts by pushing new unfamiliar process framework from the top down is not necessarily the right approach. The fact is, that people take pride in their work and are resistant to anything new or mis-branded to make their job seem inefficient.

Then there is the concern about Job security. Many only see a program on Process Improvement, standardization and enhancements, coupled with terms like improved resource management as buzz words to cut head-count. If you are in the position of deploying an IT Service Management Agenda across your organization you have to take into account the human side of the deployment and recognize what is not always being spoken.

It is critical that you provide comfort in the new processes as much as you do selling the need to enhance them. Ignoring the on-the-ground concerns in any implementation of process improvement will only result delays and push back as walls are put up in sub-conscious efforts to protect the domain of the individual. Then you have a nasty mutiny to deal with.

When defining the roles of those charged with driving these new process initiatives, give some thought to the soft-skills side of the communication process. Simply being good at translating the ITIL Framework or Service Management process in general terms is not good enough.
Being able to “dumb-down” ITIL-Speak in a way that can convey benefit and value to be digested by the organization is critical. It takes time and understanding of who you are dealing with, but this is time well spent in terms of moving the program ahead. It is always easier to form an alliance up front than to tear down walls later.

Introducing Process

ITIL_LOGO.jpgTechnology is evolving. By its very nature, technology is an industry that is full of processes that are dependent on other processes. Whether you are writing code where sub-routines are dependent on other sub-routines or setting up a network where IP Addresses are depending on Routing Tables there is always a need for order and process. This is no different in the world of IT Service.

The shift towards viewing IT as a business service has introduced the concept of IT Service Management. This is a time when Technologists at all levels are exploring various methods of operating as a process driven organization. Frameworks or methodologies such as Service Development Life Cycle (SDLC), Service Oriented Architecture (SOA) and the IT Infrastructure Library (ITIL) are becoming all the rage. What is also occurring in the environment is that individuals who for years have performed the fire-fighting roles of IT Service are now being recruited to fill structured roles within a process driven environment.

For the most part this is a great career opportunity for the individual who thrives on providing quality service to their clients, however not all members of the Service community are in it for the sake of providing quality service. These individuals who were not suited for Service as a career to begin with, will more than likely not be suited for operating in a more structured environment designed to align technology with business goals.

First Look: ITILv3 Bridge Course

ITIL_LOGO.jpgIn early 2008 I attended the ITIL version 2 to version 3 Foundation bridging course. For those who may not be familiar with what this is or do not understand the significance of the course, allow me to explain. Many people have been certified as an IT Infrastructure Library (ITIL) professional at one level or another. This past year the ITIL Governing body release a complete re-write of the IT Infrastructure Library in its 3rd version.
One of the main concerns for the industry has been what happens to those certified as ITIL Version 2 Professionals. The solution was the development of a course designed to bridge between the two programs at the ITIL Foundation Level, the entry point to the entire Certification process. Not the full blown Foundation Certification but basically a “This is what is new/different in version 3″ course. The idea is that if you attend the one day course and pass the certification exam, your Foundation Certification becomes a version 3 Certification. Thus allowing you to traverse the new ITIL version 3 certification ladder. For me, I think the course was well worth it.

I will say that despite previous notions, from the average individual who has not “Lived” ITIL as I have, but has only a Foundation Certification obtained from some point in the past, this course is a must, as there are many changes in the basic concept as compared with v2. In addition, items like terminology and structure of ITIL have also taken a new look and feel. There is however, a caveat to that statement so please read the “Suggestions for ’09″ below.

The major shift in my own logic, in terms of this course, is not how each ITIL Process has shifted into more a modular representation, but that the overall emphasis, at least from what I gathered from this course, is that the concept of service is pushed to the forefront and in some ways more-so than process.

My general take away was that when we were used to saying “Process BEFORE Tools” should actually now be “Service BEFORE Process BEFORE Tools.” This became evident to me as the day progressed. Having a strong background In the IT Service world, digesting Service Strategy, Design and Transition, winding up with Service Operations was a flow that made sense to me, more so than what I got out of the original version 2 Foundation Certification course.

As with the v2 Course, this Bridge Course saw the introduction of several new concepts (Service Assets, Utility vs. Warranty etc.) as well as terminology, definitions and the major focus on the Service Portfolio.

It was clear that this course WAS NOT a course designed to provide the full explanation and content of a Foundation Certification (as expected), but an attempt at showing you what is different in v3. For that reason the course served its purpose.

Course/Session Review

The actual course itself was interesting. Everything you needed to know crammed into a single day. Oh, and you have to take an exam at the end to upgrade your certification which you won’t find the results on for another 2 or 3 weeks. The course began like any other, books provided, introductions conducted then mentally, it felt as if we were scalped and a ton of information was flowing directly into our brains.

We started the day with Service Strategy. Here is where the bulk of change occurs between v2 and 3. From that point it was onto Service Design and part of Service Transition before breaking for lunch. The afternoon finished up with Service Transition and moved into Service Operations. At the end of Service Operations we were supposed to move into the practice exam which was cut due to some miss-communication with the Examiner who showed up early and administered the exam about an hour earlier than planned.

My personal opinion is that the pace was extremely fast and difficult to absorb in the morning session, thus a bit overwhelming. I started following with the presentation pages in the book, taking notes at a fevered pace. I quickly found that I was unable to keep up with the nuances of what the instructor was saying because I was trying to take notes on material that was flying at me fast. Finally, I gave up and simply began highlighting key areas in the book that he pointed out while focusing on what he was saying to absorb his descriptions of these v3 topics. Thank goodness module covered at least provided a short test on the material that we went through first answering individually, then walking through the answers as a group.

I think one day for this course is too short and should be split up to alleviate the stress and sense of being rushed into a certification at the end of the day. There was no real time to review notes or content to prepare for the exam. If the content could be presented on one day and the exam the next morning then at least one could have the time overnight to brush up new material provided.

Suggestions for ’09

Unlike the v2 Foundation Certification process, I believe organizations will need to be focused on providing training based on operational roles. It has to be from a cost management perspective. There are still organizations out there offering certification for the sake of certification. Practical application is king and the ability to manage demand as it applies to actual work needed to be performed will further demonstrate the ability reduce costs and deliver results. The Bridge Course is a very valid course for those certified in ITIL Version 2, but not necessary for everyone.

The Foundation Certification as a whole will shift from v2 to v3 at some point regardless. But for now it appears as if the industry is still working out the main certification process for all areas of ITILv3. If you want a head start, the Bridging Course is a safe bet. Anything above that, for me, I would prefer to wait a bit until the dust settles and all of the bugs in v3 Certification are worked out.

New World Order

techfansDowntime kills a business and for the first time, businesses are beginning to realize that technology is not simply a tool, but a strategic business line to be invested in. The simplistic view that technology is simply an application on a desktop is one that is shifting due to the pain realized from technology failures that are not right in front of a user. If something breaks, people want to see smoke and fire. In IT when things break they just stop working. Nothing visible, no strange odor of burning rubber… nothing.

Today, more and more businesses are moving away from looking at IT as a means to an end and more as a business capable of adding true value. The key to doing this involves developing and supporting the proper implementation and management of IT. Not too unlike that of a sales force or any other business line.

What you now have is an environment where the business understands the impact technology has on its bottom line. You also have IT management breathing a sigh of relief that they now have the attention of the business. The challenge for IT is to change direction from focusing on “time to market” growth demands to one of stability and strategic growth in a managed amount of time. In most industries this amounts to a shift from a “whatever it takes” mentality to one that is very much structured and process driven. The latter also introduces a new era of two way communication between IT and the business.

In a very real sense, the skills needed to succeed in technology are also shifting. Of course the demand for core technology specialists is still required, however, a hybrid specialist is needed to fill the gap in areas of technology that are process and strategy driven. An individual who is very much aligned with the business vision to assist technology in realizing the contribution to the overall goal while at the same time, someone who can also introduce new technology to the business which outlines the value add of implementing the new technology.

It would appear that the only individuals who are living in this space between the business and technology are the ones who already have the skill set needed to fill a more strategic role in the organization. These are the IT Support professionals, Project Managers and Business Analysts. The new world order is expanding their previously over looked value to the organization in bold, new, career enhancing ways.

As an individual whose second career has evolved from swapping Ultra 5s and 21″ CRT monitors on a trading floor, managing an IT service desk, managing IT vendor relationships/contracts, back to the IT Support Account Manager for the previously mentioned trading floor and now to a role that is part of this new world order, I see the potential, the value and therefore have become a “Champion” of the cause. This is my Camelot.

How Business Fails Technology

With the introduction of strict regulatory requirements being imposed on most industries today, the curtains allowing corporate technology to operate in a vacuum are being drawn back to expose some interesting landscapes from which technology operates, or doesn’t in some cases, as a business.

Another reason for change is a direct result of technology’s impact to the bottom line in terms of stability and failures. Failures which occur due to bad software development or hardware failure contribute to millions, if not billions of dollars annually in lost opportunities, revenue streams and downtime of personnel unable to perform their work. A very painful example of where business suffers when technology goes wrong.

But who is to really blame? There is a term called “Time to Market” In a business environment where margins are shrinking and more competition is vying for the same customers, getting your product out the door and on the street first is the one way where you can quickly gain competitive advantage over your competition. As a result, technology is sometimes forced to do whatever it takes to get it done.

The shortcuts taken or processes skipped are sometimes viewed as acceptable risks to get to market. The view that once the short term goal is achieved, time can then be taken to go back and work to reduce the risk of stability introduced. When a technology failure occurs, IT is always accountable to the business. But in most cases, it is the business who has failed technology.

For the past 20 years the pace at which technology has evolved has been mind-boggling. Because of this evolution there has been an equally aggressive push by business to take advantage of new technology to increase the bottom line. The problem is that the speed of thought will always surpass the physical world, which is to say that technology has, in many instances, sacrificed proper design and implementation processes which take time, in order to meet an aggressive time to market as set by the business.

The Fear of Change

My philosophy has always been that change is good. It is refreshing, an opportunity to improve, to explore and generally move forward. Unfortunately, when attempting to change a work culture evolved from years of good people operating in silos, it is guaranteed that sooner or later you slowly begin to see that as the business grows, so does the complexity of the technology deployed.

This is where I would like to use a very effective analogy. When I was in Marine Corps boot-camp, we were required to become “Swim-Qual’d.” It isn’t something many think about when enlisting in the Marines. As such there are always those who either don’t know how to swim or have very poor swimming skills. The Marines don’t care. You enlisted, you will be given basic instruction on what is required, and you will qualify.

For me this was not a problem. For others however, this was a different experience, one that involved a certain amount of anxiety and panic. The Marine swim instructors made one point very clear. Do not panic in the water. If you are in trouble, they will assist. If, in your moment of panic you resist the instructors, you will be let go of. The reality version of the term “Sink or swim.”

Changing the culture of technology, introducing new industry standards and processes, essentially altering the way people have worked for years is one of the most difficult things that an implementer faces. This is made even more difficult when the implementer is embedded in a chain of command that doesn’t fully understand the method or complexity in achieving the value of change.

Many technology publications outline the benefits of ITSM, ITIL, Six Sigma, SOA, MOF and others practices. These are outstanding motivators to the technology manager faced with a business demand for growth and stability in the technology environment. It is the typical gap that is missing the analysis. Business demand and instability, those are the triggers that begin the search for solutions or “magic beans.” ITSM and corresponding frameworks and practices are right there to appear to provide the solutions. Not much thought is given to the road that must be travelled to achieve a managed service.

That road is the path of change. It can not be ignored, it can not be underestimated and most of all, it should not be feared. For to not support, embrace and champion that change will only result in delays, frustration and failure.