ITIL® and Me

In the trenches with ITIL and ITSM.

Alright, I know I probably should be vendor neutral and for the most part I think I do a pretty good job keeping my posts that way.  But I also believe in giving credit where credit is due, and so I have to give a big thank you to Brian Vanderhorst over at CA Technologies.  Brian read my last post on pleading with vendors to give high quality pens (http://www.itilandme.com/?p=270), and he went the extra mile and made sure I got a really nice box of high quality pens.

On a side note – no Brian, the implementation isn’t as bad as I make it out to be; I admit I was being overly dramatic for journalism’s (or faux journalism’s) sake.  And yes, I’ll go easy on my kvetching from now on.  For the record, CA Technologies is not “the vendor that shall not be named.”

One last thought…I’m now pissed I didn’t title my last post “Vendors:  Want my business?  Give away iPAD 2’s (or Playbooks).”

pens from CA

Pens from CA

As I mentioned a few times over, we recently purchased a new Service Management tool (and as I’ve also mentioned, I think the implementation is driving me to drink – more than usual).  So I was sitting at my coworker’s desk and I noticed she had a pen given to her by an ITSM vendor, and I thought “damn, I lost that pen and I miss it.”  This thought then led to a memory in which we were at Fusion10 and when I was going through the goody bag each person receives, I came across a pen by another vendor (one in which I already didn’t like), and the pen was so cheap I happily dropped it on the ground since I didn’t feel it even deserved my energy to take it to the trash (I know that’s littering, but I was with coworkers and I was making a point; besides, I think one of them picked it up….and if you tripped on a pen on the ground, I’m sorry).

So here’s where I’m going with this rambling blog post; give away good pens.  In fact, give away great pens.  Make sure it’s got weight, preferably metallic and writes with a fine, crisp line.  If the “vendor that shall not be named” had only included a very nice pen that I’d be proud to use, I may have eventually forgiven them and quite possibly, endorsed their product.  But that’s not how it happened – they shall always be remembered for giving away crappy pens (besides other crimes against humanity).  Since this is my blog site, I appeal to all vendors out there, big or small, IT or cosmetic, foreign or domestic, alien or earthling, dog lover or cat lover…please please please, spend a little extra and hand out high quality writing utensils.  You never know when it can make the difference (and if you want bonus points, give me an iPAD 2).

As I mentioned in my previous post, I was up late on Friday night (or maybe Saturday morning) with my mind racing on quite many thoughts, one of which was about how IT and “the business” are going to be merging in the future.  So, if this merge is in the future how is it supposed to happen?  Should we go with a big bang of merging, or maybe take things slowly through evolution?  Since I’ve got a biology background, I’m going to stick with evolution and here’s my idea on a place to start.

Take the role of Incident Manager out of IT and put it under “the business.”  Now, I don’t mean to say that Incident Management is going to be owned by the business and IT won’t ever do it again (sorry analysts – Incident Management is here to stay).  But I do mean to move some accountability, as well as authority, of Incident Management away from IT and hand it over to the business, on a nice silver platter with extra pudding on the side.  Here’s where I get to answer the question, why on earth would anyone want to do such a thing?

First, this is going to help give a better idea of what kind of impacts Incidents are causing to the business.  After all, when things don’t work, who can better say what can’t be done then the people that are now not able to do their jobs?  This means the Incident Manager should be able to give more accurate prioritization on Incidents.

Second benefit:  You now have no one that can “filter” metrics before they reach the business.  Much like an audit performed by an external company, the Incident Manager would have an opportunity to collect and analyse data without anyone manipulating the numbers to that could skew IT’s performance (this would be a major problem in general and I really hope your IT group/department isn’t experiencing anything like it).

Third benefit:  You’d be getting the business side to take a closer look at IT, and ultimately, start bringing transparency to daily operations.

Fourth benefit:  Improve communication between IT and business leaders.  Since communication seems to be a common issue in general, why not start breaking down departmental silos by taking some of the daily Service Operations people and having them report within the business?  This isn’t to fix broken communication processes, but rather put key players inline with each other.

I could probably give a fifth and sixth reason (maybe even up to ten), but with the average attention span being about 140 characters, I don’t want to take too much of your time.  My overall point is that daily operations for business and IT are going to merge (so I’ve heard since I can’t predict the future), so I’m going to make the case that if we’re going to start somewhere, let’s start with Incident Management.  So long Incident Manager!

Oh wait, that’s me…

I got invited in on this month’s itSMF’s monthly podcast and it was great.  Unfortunately though, I made some dumb jokes which I’m currently neurotically thinking about – so… since I can’t sleep at 3:30 AM, my mind was racing and I came up with some great thoughts.

What’s up with protests in the middle east these days?  First Tunisia, then Egypt and now Libya.  Don’t forget Iran from a while ago.  There are tons of protests and rioting going on and since I love to think in terms of ITIL, I think I can explain it.

The people just want “Good Practice.”  Let’s face it; democracy is a good practice in government.  No matter how you slice it, the longest stable governments with (relatively) happy populations have been democracies (China may be an exception, but with the high suicide rates at Foxconn, can they really be happy?).

Now take a moment and answer this next almost completely random question.  How many times have you had a water cooler conversation about how your department “should” be doing a “good practice?”  At my current place, I can think of at least a handful of very talented and caring individuals that I’ve shared water cooler space with, discussing how we can “do better.”  Like myself, they want to see positive changes and to achieve productive results with as little headache as possible.  So to go on a limb I’m going to assume that individually, everyone wants “Good Practice.”

I hope you see where I’m going with this, and if you’re starting to think “ok Michael, so you may be right.  Should we all protest?”  My answer is, yes; but not by forming a mob outside of the CIO’s office, demanding change and waiting for the military to start hosing you down with tear gas (ironically, that’s similar to an OSU football victory over Michigan).  Besides, protesting is just a form of communication through actions.   So I propose that if your IT group doesn’t like being without some “Good Practice,” start taking some action.  Form a committee, start a chain email, start talking about ITIL, get involved with your local itSMF chapter, blast the itSMF USA podcast at work, print off mass copies of this ITIL and Me blog post – whatever it takes to get the “higher-ups” to notice that you, and hopefully most of your IT group, wants to be the best damn IT department out there, period.

Now, here’s my last parting words that throws a little bit of irony into this post.   The best way to change the culture is from the “top,” yet this post is about initiating that change from the “bottom.”  So which is the best?  I’ll tell you…I don’t really know.  Change is definitely easier when starting from the higher levels in a business, but I’m advocating protests from the regular “citizens.”  So here’s an idea; let the executive decision makers know that others out there want to follow “Good Practice,” and maybe they can start changing from the top while others push for change from the bottom – much like “divide and conquer.”

Now go start mob rushing your CIO’s office before they read this post and disable Twitter at your workplace.