ITIL® and Me

In the trenches with ITIL and ITSM.

Since I live in the tech world, I couldn’t not say something about Steve Jobs and his recent passing.  I won’t go into his brilliance or passion, since I’m sure millions are already tweeting/posting such things and his multi-billion status is concrete evidence of his success.  What I will state, is that it was really depressing to hear the news.  Now I’m not an Apple fan-boy, but I’m part of the generation that will never know life without computers.  To give a hint as to my age, I remember being 5 years old and my dad bringing home an IBM PC Jr.  The thing didn’t do anything except show a picture of the key that I just pushed – it was awesome.

Growing up in my house, I often heard the names Bill Gates, Steve Wozniak, and yes, Steve Jobs.  These are the guys I looked up to and were, and are, some of my heroes (as a teenager, having Gates as a hero guaranteed not getting a girlfriend in high school, but I didn’t care).  To have “heard” the news (it was actually on Twitter) that Steve Passed brought home the reality that my generation is getting older and some of the original builders of our IT society are no longer around.  So at this point I guess the IT torches of yesterday have been officially passed on to the Zuckerberg’s and Dorsey’s of today.  I just hope they can push the innovation envelope like Jobs did so well and for so many years, because honestly, if “poke” is the best thing Zuckerberg can come up with, then I really am not looking forward to the next era of IT.

(Note: I started the blog while waiting at the airport, but since it (obviously) takes less than 72 hours to return home, I finished the blog post while at my house. Needless to say, I am not changing any of the grammar to have the correct tense, however, I don’t mind putting this disclaimer in the beginning).

So here I am, sitting in Washington National Airport and recapping the events from the past few days while living at Fusion11. I really had hoped to type up a few blog posts throughout the event, but to be honest, I was having way too much fun which I’m now paying for in the form of a very powerful, and unwelcome hangover (thanks to the ITSM Academy for the most recent one). In the spirit of being direct and to the point, I’ll lay out a few lessons/observations from this year’s conference so if you didn’t attend, you’ll hopefully get a general feel of the conference.

1. Life is damn tough as a vendor: OK, I think I stated this from last year’s conference, and I know vendors are out there trying to make a living (like the rest of us), so they obviously have to attend, but it’s not an easy life. The vendor reps have to spend days away from their families, live out of suitcases, battle air travel, and then when they get to the conference, they have to try and talk to as many people as possible, which often means accosting (in a very polite manner) attendees to try and reel them in to their booths. I couldn’t do it, so I definitely salute your efforts. By the way, if you’re a vendor and reading this, I really do apologize for ignoring you. I’m sure your software and/or services are fantastic – I really just couldn’t pretend to be interested when all I want is to enter into your raffle. But I did collect business cards, so if I really need your products you can bet I’ll be contacting you.

2. Brilliance goes beyond knowledge: One of the keynote speakers touched on this one, but it’s very obvious from spending time with many of the ITSM heavy-hitters. There are a lot of bright and intelligent people out there, but what sets Malcom Fry, Chris Dancy, Gene Kim, etc., apart from the rest, is that they just have fantastic personalities. They are funny, outgoing, and know how to deliver wisdom in ways that I couldn’t fathom ever doing. I’ve been called smart before (I did pay them though), but after talking to a few of the very well known people in the ITSM industry, these guys/gals are down right brilliant and there’s a reason why they have thousands of followers on Twitter.

3. Networking, networking, networking….(a.k.a., partying): I did attend a few sessions while at the conference, and those few presentations were quite good, but overall, I have to say the magic of Fusion11 isn’t in the content, but in the networking. After all, itSMF has the motto “connect, learn, grow,” not “sit, take notes, return to hotel room and catch up on Forces of War.” There’s a reason why “connect” is the first item on that motto list; it’s because connecting leads to interacting and learning through the experience of others, which propels growth (without having to make the same mistakes). I really don’t mean to put down any of the sessions, and if you’re new to ITSM I highly recommend you attend as many as possible, but this is my second conference and between webinars, LIG meetings, white-papers, opinions and blogs, there was not a whole lot of new content for me (I hate to say it, even Malcom Fry repeated some of his jokes). On the other hand, I made a ton of new professional contacts, got to hang out with some very well known ITSM’ers (I should have gotten Chris Dancy’s autograph, but I didn’t want to be “that guy”), and really made connections from which I can learn more than what any session could offer.

4. Leave the laptop at home: There was no time to use it and getting it through airport security was just a pain.

5. Take every opportunity to talk to the “brilliant people:” I admit, I blew this one. Before leaving for the conference, my director suggested I take any opportunity to talk to Malcom Fry (even if he repeats jokes). I definitely agreed with the strategy but I have to admit, I chickened out on my opportunity. So there I was, last night of the conference and Malcom was chatting with some fellow in the lobby of the hotel. I seriously considered going up to him to somehow join in on the conversation, but I really didn’t have any smooth way to do it. Needless to say, I did not want to be “that guy,” and left for an after-party, at which point I got properly hammered and made a total schmuck of myself (I think). So, even if I didn’t follow this advice, I still stand by the advice as a lesson learned and say to meet with as many people as possible.

6. Incident Management – f**k it: This is a great lesson that needs some explaining. I met a british chap who also deals with Incident Management, but he also mentioned he’s working on Problem Management, and since rule #1 in Incident Management is never to have the Incident Manager be the Problem Manager, I was really curious as to how he was going to get the processes to work. His explanation; Incident Management works well without him, so f**k it. This is definitely a brilliant truth and one that I’ve thought of as well, which is…life as an Incident Manager seems pretty dismal, so if an organization has a need for Problem Management, it’s better to put the energy into that process instead of incidents. I don’t know if this lesson really fits in well with the Fusion 11 blog post, but the conversation occurred at Fusion so it fits into this list. By the way, sorry for the uncouth phrase and I hope the use of asterisks softens this up a bit. I considered rewording the saying, but nothing really can quite convey my feeling as well as one of the most prolific swear words in history.

There you have it, Fusion 11 in a quick and dirty blog post. Was there more going on? Absolutely. Do I have any comprehension of how much? No, but it was a great conference and I highly recommend attending Fusion 12. If you go, maybe they’ll have a mechanical bull at the conference. It’s in Texas, so my money is on “yes.”

So, I just returned from a two week trip in Israel and I have to say, it was fantastic. This is also the reason why I’ve been incredibly quiet on my blog lately (sorry to disappoint the conspiracy theorists out there that thought I joined the CIA).  Anyway, I had a great time but I noticed a few things in Israel that really make great ITIL and ITSM lessons.  Since I am still reminiscing about my vacation, I might as well type up a quick list of my observations before the regular mundane work life kills the part of my cerebral hemisphere that holds those memories.

1.  Be direct:  I’ve mentioned directness a few times already, but in Israel, it’s not just a habit; it’s a way of life.  Best example so far – I was reading a dessert menu and noticed an item titled “Chocolate cake for diabetics.”  In the US, it would normally read “low fat” or “low sugar” cake.  But there, they blatantly state “if you’re diabetic, eat this.” Besides the dessert example, I think my wife (who’s Israeli anyway) got into about four-hundred arguments in a two week period.  Nothing serious; people just get their thoughts and opinions out, and then move on their way.  There’s no such thing as holding it in and being repressed.
2. Be passionate:  I once heard a great saying about Israeli’s, they’re anashim chamim (אנשים חמים).  Literally translated, it means “hot people.”  Contextually though, it really means passionate people.  This is the same reason why directness works well; people seem more lively and passionate about what they do, which works well with explaining why there’s so many start-ups coming out of Israel.
3. Live in a sunny place:  This really has nothing to do with ITSM, but I got a great tan over the two weeks and coming home to rain and cold really was not fun.
4. Danger exists, so learn to live with it:  While we were out hiking to a natural spring around the Kinneret, we came across several signs that stated “Danger: Mines,” complete with a barbed wire fence surrounding the danger zones.  For some reason, I felt strangely comfortable knowing I was walking along a two foot wide path between minefields.  The same holds true with ITSM (or life in general).  Know the dangers and follow the safe path, or else you really won’t get anywhere.
5.  Find humour in everything:  This one seems a bit obvious, but there’s a lot in life that’s serious (and sometimes too serious).  Even during the most hectic of ITSM initiatives, there has to be some relaxing humour, or else everyone will go crazy.

I think that’s about it for volume 1.  Will there be a volume 2?  Who knows.  Since I’m still waiting for Mel Brooks to produce History of the World, Part II, I feel that having the title of volume 1 isn’t really that big of a deal.

I was recently reminded what I once heard from a CIO of a fairly well-known, multi-billion dollar retail company. Back in January, this CIO stated “We don’t practice ITIL. For us, we follow it more in spirit.” This may not be the exact word-for-word quote, but he specifically did say “ITIL” and “spirit” in the same few sentences. Needless to say, it was kind of a downer to hear. First, I’m an ITIL V3 Expert, so my bank account does not like to hear about companies who generally do not want to be associated with ITIL (I don’t blame them, but it doesn’t help my never-ending American need to make more and more money in employment endeavours). Secondly, it’s ridiculous for someone to state that they don’t follow “good practice” processes that have been published, in some form or another, since 1989.
So, let me get this straight. If a company follows ITIL in spirit, does that mean they only resolve incidents in spirit? Also, does that mean their change management really is just a spirit, and not an actual tangible process with policies and procedures? When it comes to such a company, I’d really like to sit in a CAB meeting and see if any of the members try to talk to the “spirit” to see if a change should be approved or rejected. I imagine such a meeting to have a ouija board, a few red candles, and maybe people in cloaked robes chanting in an ominous fashion.
If you think such a scene is ridiculous, so is a statement to follow practices in “spirit.” In reality, as a company with IT needs, there’s no spirit to some of the day-to-day activities. You’re fixing things that are broken, trying to manage changes to the infrastructure, and maybe every once in a while finding root causes to common problems. It doesn’t matter if you refer to ITIL or MOF to define these activities. Each of these frameworks have been written from real experiences and practices by people that have been in IT since, well….probably before I was born. So people may look at ITIL as being theory and many of the critics, and even some of the non-critics, don’t want to identify with ITIL in any way, shape, or form. But please, I really beg of you, don’t go on to degrade the value of IT practices so much as to say they should only be followed “in spirit.” If that mentality goes on for long, I’m wondering if the idea of following best practice in spirit will simply lead to that company becoming one.