ITIL® and Me

In the trenches with ITIL and ITSM.

I’ve been wanting to write a blog post dealing more with “what we can really learn” from Social Media, and then I read this:  Social ITSM – A Skeptical View.  Needless to say, I immediately had two thoughts after reading the article.  The first one went along the lines of “damn, this guy knows how to write well” and the second one was “I need to get off my tuches and post that article.”

While I don’t have any cool descriptions surrounding the hype currently in IT or ITSM (trough of disillusionment is a great one), I’ve already eluded to the fact that I’m tired of buzzwords in IT.  I agree with the Skeptic that Social ITSM is in a hype cycle, but I also want to chastise my peers and colleagues for lacking creativity in the realm of applying elements of Social Media into our tools and processes.  I’d also like to add that I should probably be included in my own chastisement and am not any more innocent than the others, but since this is my blog, I’m going to refrain from making this a self-deprecating article (I have an inferiority complex and do it enough anyway).

Have you stopped for a minute to ask “why is Social Media so widely used?”  I’ll give you a hint; they don’t call it “Social” for nothing.  But let’s not stop at a generic answer of “people want to be social.”  Let’s take it to the next level and ask “why?” one more time.  People want to be heard, helped and valued.

Being heard is not new.  In the medical world, doctors aren’t sued for simply being terrible at their jobs.  They’re more likely to face a lawsuit from simply not listening.  The same is true in IT.  I’ve worked on a helpdesk before and taking two extra minutes to hear the full details from the caller, instead of immediately jumping to what may thought to be the correct solution, is more of a critical factor for customer service than just resolving the incident.

Being helped on Social Media is one that I’m still getting used to, but it’s a growing trend so I can’t ignore it.  As the Skeptic pointed out, Social Media (is anyone else getting annoyed at typing capital letters for that phrase?) is really just a communication tool.  A while ago I tweeted out advice on my purchasing of an Android vs. iPhone.  A few (very few) people responded, but it helped to give advice and by relying on a few people I know and trust I saved time hunting through hundreds of tech blogs on the subject.  While I would never email spam my friends and colleagues with such a question, Twitter makes it very easy to send inquiries without feeling any guilt.  For more in-depth questions that require more than 140 characters, I can post to the user groups in LinkedIn.

Being valued is a basic human need that lives in everyone’s psyche.  It’s the same reason why positive reinforcement helps to shape our behavior far more effectively than negative reinforcement or punishment.  I want to feel that my actions are valued and that I have a positive effect on the world.  OK, so maybe it’s also narcissistic to feel like one person can sway the world in any manner, but why else would “president” be an answer for children when asked what they want to be when they grow up (or prime minister if you’re a Brit/Israeli/Kiwi/anyone in the rest of the world).

When it comes to planning the use of social media (damn the capitalization) with ITSM, not having all three of these elements means you’re probably not going to get anywhere.  So where can social media/IT and ITSM get together and succeed?  I think if that question was easy to answer the IT Skeptic wouldn’t be doubting the “fervor” of this particular buzzword (then again, his very nature means he’d be skeptical).  Here’s my attempt at an answer:  Give up.  Not on the concept, but on expecting the user community to jump onto a solution provided by IT.  Keep in mind, I’m stating a “solution provided by IT,” not social media in general.  This means that if a social network is readily available in your work environment, tap into it and exploit as much of it as possible.  If one doesn’t exist, don’t worry about trying to force something on your users.  Start with the small groups of people that will utilize the communication tool and hopefully, one day, the value will catch on.

One last thought of where we can really get some value out of social IT.  We should be looking at incorporating elements of social IT platforms into those used by IT.  OK, so I get to gloat a little more of my work on a project to put gamification into a ticketing tool, but what other elements from social media?  Best example; why not get rid of incident categories and use hashtags instead?  If people already have behaviours of using hashtags from Twitter, why can’t we just build on those already existing habits and save time by not forcing the dreary practice of using drop-down menus?  I don’t know about you, but I #love the #idea and I’m already used to using #hashtags each day anyway.  Once again, I’ll point out that we can take how people work and conform our software to fit the people, not the other way around.

Unfortunately for my hopeful optimism, the IT Skeptic has a valid point that social media is pushing the boundaries of hype.  In due time we may find that people simply don’t want to be social about IT.  Really, when was the last time you saw millions of people Tweet about a new chipset that’s being released?  According to trendsmap.com, boozer is on the top list of popular hashtags.  I’ll let you draw your own conclusion on that.

An idiot.  OK, let me elaborate on this one for a while.

I love tools.  Ask my wife and she’ll tell you that I’ll plan a new project just for a chance to buy a new tool (finishing it is another story).  When I look at tools I see potential.  These are devices that help me take my processes and resources, and change my environment for the (sometimes) better.  The tools we have in IT are no different.  There are hundreds, if not thousands, out there which are all designed to run through processes and work-flows and deliver specific results.

In my workbench I have a very loving fondness for one special tool.  I simply call it my “rotary tool,” but in reality it’s a platform.  I have a half dozen or so attachments to a base that allows me to accomplish a variety of tasks.  In fact, an enjoyment of mine is perusing the very aisle at my local hardware store that has all the attachments in the hope there’s one I don’t own (but soon will).  I can’t even begin to name how many home projects/fixes I have successfully accomplished, all because of this one item.  The technologies in IT are much the same.  We have tools, and then we have platforms.  During the past few months I’ve had the privilege to work on a platform, and let me tell you, the boundaries are almost endless.  With a platform, I feel like an IT superhero that can go out and handle all of our ITSM problems with only a few clicks of the mouse, and maybe a tap or two of the keyboard.

But now there’s another problem.  If a fool with a tool is still a fool, what happens when that foolishness is multiplied by a hundred times?  Now you know why my initial answer is “idiot.”  Since a tool is limited, a fool really won’t get anywhere.  On the other hand, a platform can expand on foolishness several times over.  Why am I so worried about this that I’m dedicating a blog post to the subject?  I’m really not that concerned since a fool with a platform probably wouldn’t know what to do with it anyway.  I just happen to like the saying and wanted to work it into a brief post about the differences between tools and platforms.  If you’re a vendor and reading this, please know my preference is for platforms.  It’s not that I don’t like tools or think of them as useless, and in most cases we still need tools to accomplish our tasks in IT, but a platform can evolve with IT as it itself matures.

Or…I could be wrong and am just a fool with a platform.

OK, so there’s no secret that I’m working on building gamification into an ITSM tool out there (and vendors, if you’re reading this, I recommend doing the same with your software).  So we’re almost ready to go release this thing into the wild, and I swear there’s something I’m missing.  But what could it be? We have the badges built, graphics are uploaded, back-end rules are in place, the tables are ready….it’s all pretty much there for phase 1.  While checking in on Foursquare tonight, it occurred to me.  We’re missing a “personal” touch.

See, the idea of gamification is to use a person’s natural desire for competition to drive behavior.  It’s natural to be competitive, and often we really don’t have many places in society where we can truly compete (except in academics, sports, and my wife’s family).  So gamification is about giving people an opportunity to compete, and win, against their peers.  But there’s something even greater in competition when it comes to a personal level, and that’s the element I saw tonight in Foursquare.

Foursquare has a nice feature in which after checking in, it shows your score compared to your friends.  What I saw tonight immediately caused me to grind my teeth; I was (and have been) losing to a specific friend of mine.  In fact, he even took the mayorship at my place of employment, which prompted me to consistently check-in to liberate it from him.  And that’s the part of our gamification that’s missing – a certain personal element.  Sure, we’ll allow people to see scores against a general scoreboard, but that may only be good enough for the top three or four competitive people.  With limiting competition to a few “friends,” it now narrows the scope of the game from a general population to a specific group.  A group with it’s own social culture, behaviors, and even peer pressures.

Is all lost that we don’t have some sort of “friends” list?  Absolutely not.  ITSM is about continuous improvement; a type of evolutionary approach to IT.  I now know what else to build into this gamification project and it’s a definite feature to include for phase 2 (or 1.5).

OK Matt Beran, this post is for you…

So, as I mentioned in a previous, unfinished post (http://www.itilandme.com/?p=498), I’m working on building gamification into S***-**w.  In my original blog article, I wanted to go over more details as to exactly how we’re building our game, but then my smart-ass conscious got the better of me and I went into a rant about buzzwords.  Well, after some requests for finishing the blog (actually, it’s one request, but I want to be the first to write an authentic article on my topic, before it gets stolen), here’s the continuing saga of gamification in S***-**w.

For our first phase of gamification, we’re building a badge system. In S***-**w, this requires a few extra tables.  So, I created a new table to contain all the badge information (name, requirements to achieve, active, etc.).  But a table containing the badges isn’t enough.  There has to be some way to keep track of the scores.  So, there’s a second table listing each “player,” as well as their respective badges.  I affectionately called this the rewards table, but feel free to name it anything you want (I won’t be insulted…much).  Each one of the entries in the rewards table contains the information to track and increment each score for every badge in the system.  This means to build and maintain the table, there needs to be a some mechanism in S***-**w to allow new records to be written.  Alright, now we’re getting into rules!  So, we built a rule to keep track when a new badge is created, and then go through and creates a new entry for every player.  Consequently, there then needs to be a rule for when a new player gets “added” to the system, so I better touch on that for a minute.

In our instance of S***-**w, we have something like 20k+ users.  I don’t think we need to have all those people play our game (plus that’s a lot of entries for when a new badge gets added).  So, how do I want to limit the players?  Obviously, the game is designed for IT people, so we can limit it to the ITIL role.  But, what about tying this in to Social Media?  Here was my thought; if people join the Livefeed (S***-**w’s answer to Twitter), then they get to play.  So, there’s now a rule that watches for when a new user entry is created in the Livefeed, and then it goes through existing badges and creates the entries for the new player.

OK, so a couple of rules are in place.  But two are not enough to run this thing.  Originally I went with building a rule for every badge that would get entered into the game.  As you can imagine, this is a bit tedious.  I also won’t claim I’m a S***-**w guru (I’ve only been working on the platform for a few months, and if you haven’t already noticed, this blog has “ITIL” in the title, not “S***-**w”), so I needed a partner, specifically one that helps to bring things to Fruition and goes by the name of Jace.  With his help, we built a general rule against the task table that would take parameters from the badges, and then check for the conditions that would increment that badge.  Besides that general rule for the conditions, we also have a few global rule that actually runs the actions when a condition is met.  Those actions include incrementing the “count” field, checking if a badge has met the criteria to go up a level, and also posting the level increase in the Livefeed (we need to give people the ability to brag).  And by the way, yes, I know global rules can hit performance.  We’re going to look at using script includes down the road.

Tables, rules, what else do we need?  Oh yeah, I almost forgot – this thing needs to look relatively decent.  The final piece to the wonderful puzzle is just getting a user interface for the players.  In general, we can use the S***-**w platform with its already pre-built lists and record forms, but why not make things look cool? (Or as my colleague says, she wants it “sexy.”)  Once again, I’m still a newbie and I’ll be more than happy to admit when I need help.  But when someone helps, they also provide a Service, and once again, people are willing to do it Now.  So, we now have a very cool guy by the name of Tyler helping to make the UI page in Jelly (who uses Jelly anyway?  This is the first time I’ve heard of it, outside of a related peanut butter sandwich).  The first UI page is just to show the badges and allow users to see what else they can still achieve, but as we move along I’m sure that’ll evolve as well.

There you have it, a brief overview of what we’re doing to build gamification into S***-**w.  Is this a very easy project?  No.  Is it fun?  Yes, but we still have a few kinks to work out, and honestly, I’m worried about performance when this thing goes into production.  In the spirit of ITIL Continuous Service Improvement (there, I worked ITIL into this article so I don’t feel so bad focusing on a specific product), we’ll improve upon it as we go.  If anything, at least it’s helping to push a buzzword out of blog posts and into the real world.

And by the way, thanks to Chris Dancy for the best advice.  It went something along the lines of “just do it, be first, and improve upon it later.”  Who can really argue with that?