ITIL® and Me

In the trenches with ITIL and ITSM.

That’s it…I have had enough! Enough of “the cloud,” enough of the “SaaS,” or “IaaS,” or “PaaS,” or whatever funky initials (I don’t think they’re technically acronyms) you want to throw out there with over dramatized capitalization of the first and last letters. And yes “social media,” I am done with you too. You’ve been a great mistress in my IT career, but let’s face it, you’ve just been a fleeting plaything in my life. A victim of a “hit it and quit it” relationship that I have overly enjoyed in the past few years of knowing you.
Now that I’ve had a chance to start this blog post with a bit of a dramatic rant, I now get to explain what I’ve actually had “enough” of. OK, I admit it’s not really about quitting the endorsement of the previously mentioned technologies (“social media”…we’re stuck together and I love you), but rather the fragmented thinking in how IT relates to the various offerings that go beyond the standard IT infrastructure.
Infrastructure. Now there’s a word I need to harp on a bit. “Infra” is actually a Latin for “below,” while “structure” is used to define an underlying frame that helps to provide organization. So the cloud, aaS’s and social media (yes, I’m aware social media can technically be hosted within an IT department, but the best ones simply aren’t) all are not part of this “infrastructure.” They stand alone out there in the IT toolbox, some being tested by a few freethinking organizations, while others have been wholeheartedly adopted, but all never being considered an intertwined composite, or structure, of technologies. So while everyone is familiar with the tried and tested phrase of IT infrastructure, I can’t think of many people that have considered the IT ultrastructure (if you have, please let me know).
This is where I would like to propose the formal and official introduction of the IT Ultrastructure. Just like there are two sides to every Schwartz (per Mel Brooks), there are now two sides to every IT; one “below” the organization as hosted equipment, and another “beyond,” with physical care and integrity being provided outside of the same organization. And if you know my ITSM background, which would have to be present in any blog with “ITIL” in the title, you should know what I’m about to state…ITSM will be the integral discipline that can help organizations achieve value by providing services through the unified coordination of both environments (that actually sounds relatively intelligent). This means service catalogue management and business relationship management will be just as important, if not more so, than traditionally infrastructure focused processes such as incident management or problem management. Keep in mind, I’m not intending to state that some processes will overtake others in their importance. Rather, some processes will simply come to light as providing a higher level of value earlier in an organization’s maturity.
Will the IT ultrasctructure ever overtake its infra-brother? In the future, per a few opinions of very intelligent people I know (I’m referring to you J.D. as I don’t wan to take credit), it’s entirely possible. Will it ever really happen? Probably not for a very, very, very, very, very, very, very…very long time. But if you look at Google Docs, Gmail, Amazon EC2, Dropbox, Salesforce, Yammer/Twitter, ServiceNow, etc., etc….it’s a very real possibility that a company could almost run entirely as an ultrastructure (which means I can probably delete a few of those verys). So I may not be really crazy here. Or maybe I am and the voices in my head are telling me to type this blog post….

Share

In thinking about the latest happenings in the ITSM product industry (a.k.a. watching ServiceNow take over the market), I couldn’t help but wonder “where are we going?”  Most importantly, I’ve begun to wonder, “what’s next?”  It wasn’t too long ago in which we had a good amount of players in the product space that pretty much seemed to pass clients back and forth.  BMC, CA, HP, IBM…all top companies that have a long history of software development.  Please keep in mind that I’m not stating any product is better than any other; I still like the feel of CA Service Desk, and I always hear about BMC Remedy being a great product.  I simply have most of my experience on ServiceNow.  Despite that experience, and what other people may view as my fan-boy affinity for the product, I hold the belief that no technology will ever stay permanently on top.  Case in point, look at how only a few years ago Blackberry was the number 1 selling smart-phone and the iPhone and Android were lucky to even have a slice of the profits.  The same goes with Dell, Microsoft, and even Apple prior to the first fall.  No matter what, new and different technologies will rise to overtake the top performers.  It’s a cycle that simply will never stop.

Based on the fact that the tides of change are ever present, I’ve been wondering where technology will take us in ITSM.  It’s very obvious that much of the way we work is going mobile, so maybe it’s time for ITSM to do the same.  And I’m not referring to add-on apps for existing tools, or even HTML 5 based web portals to make the front-end work better on a mobile device.  No…I want to see an ITSM product that’s designed and developed solely for the mobile platform.  In fact, I would like to not only see mobile, but something built with a core of social media.  After all, if people are social creatures, doesn’t it make sense to make the tools with a foundation in social IT?

As I’m calling out for a new ITSM platform built with mobile and social in mind, I would like to bring attention to the fact that it’s not impossible that a current vendor won’t come out with a solution like the one I (briefly) described.  After all, it’s entirely probable software companies will simply adjust to the changing market and as their products evolve, they’ll evolve towards the mobile and social union.  Where I see difficulty is the lack of foundation for such products.  So far, nothing out there was built around social IT or for mobility.  Sure, some of the vendors have incorporated those aspects into their solutions, but it’s along the lines of add-ons and enhancements and not as a basis for fundamental ITSM workflow.

So there you have it – a fundamental request to all the developers and vendors out there in ITSM product land.  Will anyone come along to provide a product that can upset the IT world in such a way?  Maybe.  If they do, then I’ll have yet another chance to brag “I told you so” to my colleagues and peers.  If not, I won’t worry about it since opinions and ideas change and this can be passed off as another idealistic blog post.

Share

How quickly time has passed.  It seems like it was only a few months ago in which I was a youthful and naive ITSM practitioner, recently hired on to work as a ServiceNow (I’ll miss you hyphen) administrator and ready to go out and make a name for myself in the ITSM space.  Oh wait, that was only a few months ago…

So now here I am, nine months later and getting ready to start a new ITSM career with a consulting company.  As always, I won’t specifically name any people or companies I work for, or previously have worked for, but I’m sure with a little detective work you can probably find out anyway.  Since I’m moving on to the IT dream job in the sky, I couldn’t help but give a recap of some of my time here.

1.  First thing’s first; building gamification into ServiceNow has been one of the most fun and rewarding development experiences so far.  I’ll miss the sleepless nights, hair pulling tantrums, and thrills of excitement that comes with working on a cutting edge project, but alas, all good things must come to an end.  I’ve said it once and I’ll say it again; there’s no better way to learn something than to achieve what has never been accomplished.  As Chris Dancy would state, that’s the “first mover advantage.”

2.  As always, ITSM is one of the most difficult areas of IT.  Ironically, it’s also one of the least known.  With that in mind, I’ve gained invaluable experience from working in a place with very immature processes, while navigating a chaotic environment, and all the while trying to be the loud voice of ITIL and ITSM.  Was I successful?  Maybe a little.  Will I ever shut-up?  Probably not.  The most important thing is simply to “keep the faith,” which is great advice from Rob England.

3.  Blocking social media access only hurts productivity.  If you ask my (soon to be former) coworkers about me, they’ll probably say “he never shut-up about being blocked from Twitter,” and I would whole-heartily agree.  In fact, I often wonder how much time would have been saved by not blocking Twitter and forcing me to use my mobile device.  Not only would the data stream have been faster, but I’m sure the time to take the phone out of my pocket, type on the touchscreen, correct the typos on the touchscreen, and having to resend Tweets from a shoddy data connection would have added up to weeks worth of productivity.  Interestingly enough, I only use social media for work related purposes, so I’m actually trying to be a more valuable and productive employee.  I’ll never understand that one…

4.  Technology is fun, but ITSM really is my passion.  I learned this from working on ServiceNow as an administrator and developer.  As fun as it is to build custom applications in ServiceNow, it’s not something I could do nine hours a day, every day, for the rest of my life.  Believe it or not, I’m an ITIL V3 Expert and my passion is with ITSM.  Will I ever get away from tools and technology?  Absolutely not!  As I mentioned, it’s fun, but it’s only one minor piece in the grand ITSM puzzle of life.

5.  What happens in Vegas, stays in Vegas.  No additional comments to add to this one.

That’s really a very (very) short recap of the past few months of my life.  While I’m excited to take on new challenges, and consequently new successes, I’m also happy to stay connected with my former colleagues and can’t wait to see how things develop at my (soon to be) former place of work.  So long, and thanks for all the…

Share

A strange thing happened last week when I sat down with a couple of coworkers to discuss the recent purchase of an IT automation tool.  We didn’t talk about the tool.  Well, we didn’t talk about it beyond a few minutes of stating “awesome, we bought it.”  Instead of discussing the software, we talked about process and strategy, and how the organization will now be forced to mature its event and incident management in order to gain the most ROI on our investment.

To give you a little bit of a background, the software is called eyeShare and it was developed by a boutique software company called Ayehu (http://www.ayehu.com/).  I first came across this software over a year ago and through the wonderful world of social media (I’ll give LinkedIn credit on this one), I had a chance to meet with the Founder and CEO of Ayehu to get a personal demo on how the technology works.  The reason why I’m so excited to be part of a meeting focused on an IT tool, and not talk about the actual tool, is because this is a case where limitations have been removed, ease and flexibility have been introduced, and now people at my workplace don’t have the option of stating “we don’t have the system we need”  as to why we cannot push for any process improvements.  Ok, I understand ITSM is more about the people, processes, and products, and in that order of most to least important, but let’s not ignore the fact that we do live within limitations of technology.  I’ll go on to boldly state that one of the reasons why ServiceNow is so successful (I’ve worked on the product so I’m confident in being fairly correct on this one) is because it also removes limitations and makes my job infinitely easier by changing the question of “can we do it?” into the question of “should we do it?”  That simple change in questioning now forces us to change the focus of our improvements.  Since technology is no longer in the spotlight, we only see our processes and culture as being the hindrance to success.

So here I am with two powerful and flexible tools in my wonderful world of ITSM.  Could it get any better?  Absolutely!  The best part is that eyeShare has integration with ServiceNow.  So the tool that is handling event management with automated workflow is now talking to the platform used for managing tasks, pulling metrics and running the entire ITSM program.  It’s this integration I want to emphasize as being the key to success.  While it’s possible to purchase several different tools and technologies to cover the entire gamut of IT needs, I still want a single “go to” source for assessing the current state of our processes.  In essence, I don’t mind the purchase of another product as long as it integrates nicely into our existing infrastructure without taking any resources from our staff.

So I’m wondering; where do we go from here?  The answer is easy, however the work will be difficult and cumbersome.  We now get to start classifying our events, prioritizing those classifications based on our incident management process, streamlining the event management process, and eventually throwing in some automatic ticket assignments based on CI ownership.  As is the case with all ITSM process improvements, the journey will be long and arduous, but at least I’m confident we have the right tools for the job…which is something I don’t ever want to think about.

Share

Switch to our mobile site