ITIL® and Me

In the trenches with ITIL and ITSM.

Shortly after my (what I consider) triumphant success at the Pink Elephant conference last month (you know, that whole gamification thing I yammered on about for a while), I set my nose back to the grindstone and began an encore endeavour of fusing social media with IT service management.  I did this for two reasons.  First and foremost, I wanted to show off.  Second, I really wanted to see if I could use S***-**w’s social media feed to create incidents, search knowledge, and essentially prove that social IT can be used for facilitating ITSM processes beyond the general scope of communication.  After a few sleepless nights of development, I’m happy to say that I made some pretty good progress and am very pleased about the results (check out this Youtube video for proof – http://www.youtube.com/watch?v=wXltl4UMJg4).  But before I go any further on this project I would like to share my personal view on why my efforts are worthwhile, and not just something I’m doing to impress my colleagues (even though that never hurts).

To begin with answering the “why,” I’d like to bring up the general topic of social media.  It’s had a tough time in IT, and I think there will always be debate about where it exactly fits in with ITSM and how best to utilize it.  I’m not going to give evidence to sway your opinion one way or another, but I will state that, in my ever so humble opinion, I think we’ll be seeing more adoption of social media as a primary framework of how IT operates, as opposed to the pigeonhole of being a secondary form of communication or collaboration.  That being said, and along with the basis that the goal ITSM is about helping the “business” achieve value, we should start looking at social media and how to incorporate it into our regular IT processes.  So instead of communicating in one tool during the incident process, and then later going to another tool to create the incident, why not have both functions achieved in a single step?  OK, capturing chat history into an incident is not a big deal, but I’m not just talking blogging about capturing data.  I’m stating that eventually, we won’t need separate incident, problem or change forms.  That doesn’t mean we don’t need to capture that data, and it definitely doesn’t mean we can do away with those processes (sorry – I would keep your ITIL books – all 6.981 KG for 2011) .  What I am trying to describe is a type of environment where all our IT work is accomplished through the use of social IT (and for the record, I had a similar conversation with William Goddard while at Pink 12, so I won’t claim originality on the vision).

This is the part of the blog article where I would be expected to present evidence for justification of this “vision.”  My simple answer is for you is to visit a local college or high-school and ask a few students how they interact with their peers.  My guess, and I think it’s not far off, is that they’re using Facebook and Twitter for most social communication and phone calls are simply a last resort for when someone has been unfairly grounded from their iPhone.  The reason I point out the behaviours of the next generation is because these are the IT brains of tomorrow.  In fact, even if they don’t go into technology, they’ll likely be our customers/end-users.

To add one more thought on “the next generation will work this way” argument; I’d like to detract from a superficial explanation and dig a little deeper into some sociology (I’m qualified for such a task since my wife’s a behavioral therapist and I’m an aptly trained husband).  Why is social media so widely used by the youth and seems to have trouble gaining acceptance with “more experienced” generations?  My current theory, and it’s a theory and will go no further then this blog post, is that it’s not because it’s quicker for adolescents or young adults to learn new habits or behaviours, but rather, they live in environments where social change is very quick to occur and new innovations are willingly accepted by the culture.  Think about it; colleges are typically liberal havens where experimentation is encouraged and failure is overlooked (I should know, I failed quite a lot in college).  School in general has an environment conducive to learning and education, which in turn is furthered by trial and error.  So on that thought, it’s not so much that “young” people are quick to learn how to utilize social media, but rather, they live in cultures that are more accepting of change. This goes along with my belief that people are inherently social and would prefer to work and communicate in company, which means groups of humans that have no, or limited, cultural restrictions on change are likely to behave that’s most natural to them.  So it’s not that social media can’t succeed due to our inability to adapt (we naturally want to be social), but rather, there are some barriers that’s preventing us from doing it.

So now you (hopefully) understand why I see social media as gaining more acceptance as time goes on.  I have the (blindly optimistic?) belief that we, as humans, want to be social and it’s natural for us to work in that manner.  As cultures change, social IT will become more prevalent and it’ll eventually take the center stage with how we go about our IT processes.  So why not start incorporating our IT Service Management into social IT today, and be ahead of the curve for tomorrow?  I, as well as a few others out there, have the vision that we can create incidents, search knowledge, follow problems, create changes, request access, and complete a myriad of other ITSM tasks all through social media.  Will it ever be perfect?  Probably not.  Do I care?  Absolutely.  If things don’t go that way I’ll look like an idiot and probably regret writing this blog post.  On the other hand, if I’m right, I would have earned several seconds worth of bragging time on Twitter.

Let me begin by stating that I wasn’t sure if the next iteration would be ITIL V4, ITIL 20xx, or ITIL 7 (after Microsoft’s change in their naming convention that ITIL seems to be following), so I’m taking a gamble and sticking with the M$ pattern in the hopes that I once again can brag about how right I am.

While at the Pink 2012 conference I had the chance to attend the IT Skeptic’s presentation on his Tipu method for agile IT Service Management (http://www.basicsm.com/tipu).  Needless to say, I’m loving it (for right now anyway since I’m a bit fickle).  What struck me as a “duh” moment though, is that in the early parts of the session the Skeptic talked about the need to focus on people to make improvements rather than technology or processes.  No real surprise there since “changing” people is the real challenge related to the cultural aspect of ITSM improvements.  Fast forward a few days later and I was looking over a presentation from a newly met peer titled Emotional – Social Intelligence for Project Management.  I’ll admit that I don’t live in the project management space (as well as not having much of emotional or social intelligence), but after digging through related websites and reading some news in the Twitterverse, I’m getting the impression that the biggest challenge in IT Service Management isn’t process or technology, but rather the people (ok, I’ve known this for a while, but I’d rather use it to introduce my topic).  There has, and probably always will be, a lot of talk about changing attitude, behaviour and culture (if only someone could create a workshop covering the three).

So where am I going with these thoughts?  I hope you noticed the title of the blog says it all – Behavioural Management as a formal process.  Let’s face it, if ITIL is about delivering value, and the delivery of that value requires a person, or people, to constantly be trying to change behaviours and culture, it’s obvious that we should formally acknowledge and validate that there needs to be some process, or at least some function, wrapped around that goal.  Yes, I know that as ITSM practitioners, we tend to rely on our own intrinsic skills to make cultural change happen, and the most successful of us are fantastic at it, but how many organizations would benefit from a resource with a dedicated skill-set geared solely to help with the “people factor?”  Please keep in mind that my idea of “Behavioural Management” isn’t aligned with the movie A Clockwork Orange (even though I’ve considered it during some implementations), but rather someone that can help get the biggest value out of ITSM improvements by maximizing the way we influence the culture.  Think of it as a professional psychologist in the IT space; a role that has the background and skills to really look at all the projects and make recommendations to gain the most acceptance with the least amount of work (I am lazy and would prefer to do as little work as possible anyway).

So, am I crazy in thinking ITSM and ITIL could benefit from a purely psychotherapeutic role in IT?  Probably.  But the fact remains that people resist change and as practitioners, we recognize this as one of the biggest challenges.  So why not consider it as a formal process in ITIL?  I’m sure the authors are looking for more material to add to the next version anyway.

Another conference has come and gone and this time I had the privilege to present at the infamous Pink Elephant of 2012.  I’m not sure what one is called when they make such a feat in their life, so I’m going to state that I’m now a “pinkie” in the hopes it catches on and I can gain some bragging rights.  In my usual blogging fashion, I want to post a few lessons I learned from this most recent event.

  1. Thank you vendors:  As always, I like to give praise and thanks to those dedicated road-warriors out there that not only helped to make the conference possible, but spent days away from families, hours schmoozing, and thousands on food and alcohol to make it a great conference.
  2. Don’t consume alcohol while in Vegas:  I found out that while in Vegas, it’s plausible that the events in The Hangover could have been factual.
  3. If you consume alcohol, take notes on what you do:  This may be the only way you remember what happened the night before.
  4. If you do take notes, tear up the paper:  On second thought, you may not want to remember what happened.
  5. A big head requires a strong back:  So, I was part of a team that helped bring gamification out of the buzzword zombie world and into real life.  Am I proud of my accomplishments?  Damn right.  Do I have a big head?  Absolutely.  But I also say a strong back is required for two reasons.  Firstly, it did take a lot of work to get here.  Secondly, I know I’ll eventually get humbled.  The only way to survive a good ‘ole fashioned humbling is to pick up the pieces, work to put your head back together, and carry on with an average sized one.
  6. Sessions were great, but networking was even better:  The content at the conference was pretty good and is a great way to learn how your peers are succeeding in the ITSM industry, as well as come away with new ideas for your own organization, but the sessions eventually end.  On the other hand, the people you meet and relationships you build will carry on for years to come, especially when you need help or advice later in your career.  At least, this is my justification for getting little sleep and enjoying the Vegas nightlife.
  7. Thought leaders are people too:  I had the great privilege to meet and speak with industry leaders and I found that they are more then happy to talk about their ideas, listen to yours, and give unfiltered praise and criticism. There really are no egos at the conference (except for mine).
  8. Vendors – it’s 2012, you really don’t need CD’s anymore:  I was taken aback when I was talking to a vendor (they shall remain nameless, but I’ll say I thought of hummus when I saw their name) and the rep offered me a demo of their software on CD.  Did I just enter a time warp and was now talking to AOL?  I can’t remember the last time I opened the DVD drive on my computer to run such media; it’s now reserved for the original intended purpose as a coffee cup holder.
  9. QR codes are not replacing business cards, but Twitter might:  So, I wanted to run an experiment and instead of bringing business cards, I would show a QR code on my phone to be scanned.  I had two reasons for doing this. First, my organization hasn’t gotten me cards yet and this is a perfect excuse to cover it up.  Second, I wanted to sound superior and state “I don’t support legacy systems.”  Well, it didn’t go over too well and no one knew what to do.  What was interesting though is how many times during a conversation with a newly met peer one of us would say “are you on Twitter?” and minutes later I would get the familiar message on my phone that I have a new follower.  I’ll let you draw your own conclusions on that one.
Well, there you have it – my lessons from Pink 2012.  I was considering adding a tenth item to the list, but the “top 10 list” has already been done before and I’d rather be original.  Unfortunately, all good things must end and it’s now time for me to dive head-first into the regular grind of the ITSM battlefield.

 

What a great month it’s been so far.  Not only does Pink 2012 start this weekend, but I’ve been able to spend the past two days training my coworkers in the mysterious art of S***-**w.  I will definitely say I love the tool platform, and have an adoration for the tool similar to showing off a recently purchased Lambourghini, but I also ran into an interesting problem during the training sessions.  The problem, unfortunately, is social media.

S***-**w, like so many other applications out in IT, has it’s own social media feed similar to Twitter.  While proudly demonstrating how the feature could be used, I ran into resistance with (more than a few) colleagues that saw no point to it whatsoever.  Sure, a few people thought it was pretty cool (I’ll hint that most were of a different demographic then the non-believers), but overall I would say there was disbelief that anyone could communicate in any method outside of email.  Ironically, some of these people didn’t even recall receiving an email I sent last week regarding the training, so I have no idea how they even communicate short of a tin can with a string.  When asked why the social media feature was even present in S***-**w, I started giving the answer of “this is how the next generation communicates, so we better be ready.”

If you’re reading this and are over 30, please don’t get offended – I fit into that same demographic so I’m also insulting myself.  Unfortunately, we can’t ignore the fact that the next generation of IT people will be growing up with Twitter, Facebook and instant messaging as their main methods of communication.  I found this out the hard way when I wanted to get in touch with my college-attending cousins.  I always receive a Twitter or Facebook response, mostly receive a text reply, sometimes get my phone call answered, and flat out never get emails.  It’s just not what they do and let’s be realistic, when they enter the workforce they probably will communicate the same way.

If there’s doubt about the acceptance of social media in the world of IT (I’m thinking of you IT Skeptic), I’m not surprised given that this culture of communication is with the youngest generation and they not only have a low percentage of IT jobs, but also are not in the managerial and high level positions to help push the adoption.  I’m thankful that we have a few good evangelists out there trying to spread the message (Chris Dancy for sure), but we haven’t reached the tipping point of comfort for social media in IT.

Now I’m going to get a little biblical in my post, but please bear with me as it pertains to my answer.  Back several thousands of years ago the Jews, recently freed from slavery with the help of this stuttering guy named Moses, ran into a problem.  I won’t go into details, but the end result was they were forced to wander the desert for forty years as a type of punishment.  People have analyzed the bible and came to the conclusion that the reason for the wandering wasn’t so much of a punishment, but rather a training period in which the older generation was to grow and die off, allowing the next generation to grow up, and having never known slavery, would be more motivated to fight to keep in and not just roll over into shackles.

If you’re not following my line of thinking, I’ll spell it out; social media will become a part of IT when it’s part of the habitual way of working and communicating.  When will this happen?  When we have a majority of staff working in technology that comfortably, and naturally, use social media to communicate, find answers, and essentially use it minute by minute to do their jobs.  No, social media will never replace IT processes (which is why I’m still investing in my own ITIL future), nor will it replace the general reason for existence of IT to help “the business” realize value.  Social IT is simply just a different way to get things done and I’m not expecting to worry about it for another forty years.  Well, factor in the fast pace of technology, and it may be more like four.