ITIL® and Me

In the trenches with ITIL and ITSM.

Browsing Posts published by Michael

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.

After attending an itSMF event in which we were discussing BYOD, I was a bit annoyed to hear how some companies are forcing policies in which they meter application usage on personal devices.  In my opinion, that goes against the idea of BYOD, and here’s the result of that opinion…

Dear Corporation,

First, let me start out by saying thank you for embracing and exploring the concept of bring your own device (BYOD).  It’s comforting to know that as a corporation in today’s 21st century, you’re finally realizing that I, as an individual who embraces new technology, have the natural curiosity and intellectual hunger to find new ways to work quicker and more efficiently; ways in which most organizations do not have the ability to keep pace.  With the ever changing landscape that we now call IT, it’s apparent that a single human can comprehend and embrace new technologies faster than that of an entire culture.  Because of this truth, BYOD isn’t about the borg-like “assimilation” into the colony, but rather, the uniqueness and contributions of the individual that helps to make the entire organization successful as a whole.

There is one matter I’d like to touch upon during this manifesto, and it’s the concept of device vs. data.  Yes, I agree that using my own personal device to access your data can cause concern.  After all, you have no idea where my device has been, and even though I’m technologically savvy enough to make sure security has not been compromised, I understand that a blind-faith in device trust is simply not going to happen.  But I would like to remind you that the device is mine, and all personal content and data on that device is mine as well.  BYOD has now created a conundrum for us; one in which I want to retain ownership of my property, as well as the privacy rights that one enjoys with owning personal devices, and you want to control every aspect of your data, including any phsyical hardware that’s being used to access it.  While this type of problem isn’t a new one in general, the specific ways in which you want control is specific to your culture.

I would like to offer my point of view to a solution, one that I think is fair to the spirit of BYOD.  Please accept that BYOD means you now do not have any control of managing my device.  It’s now gone, finished…kaput.  In fact, I recommend that you not only accept it, but embrace it, because managing multiple devices is a cost that simply cannot be held to a reasonable level while allowing the type of flexibility that BYOD allows.  So if your idea of BYOD means forcing me to accept policies regarding application usage monitoring, please accept my sincerest laugh as I happily decline on that particular service offering.  Also, please don’t be offended if I decide to seek employment elsewhere, as such practices would actually make me feel a bit uncomfortable to be your employee.

In exchange for getting rid of device management and leaving my personal privacy alone, I will accept your terms for managing something far more important; your data.  I’m not without reason, despite what other people may say, so I’m willing to accept terms that dictates the actions you need to take in order to protect your information.  After all, BYOD really involves the concept of data management on multiple devices and platforms, not the managment of those devices.  So yes, I understand if you need to wipe my entire device when our relationship ends (hopefully on a good note), or if you feel that my device has had it’s security compromised.  I even understand the need that my device needs to meet certain requirements, such as hard-drive encryption or using a passcode lock; common practices that I, as a privacy paranoid individual, should be following anyway.  I do hope you’ve considered these scenarios and have come up with a solution, or solutions, that will minimize the security requirements for my device, but sometimes a little compromise can go a long way.

Now that you and I agree that BYOD is about data management, I think we can move forward on to a brighter future.  One in which I can switch from iPhone, to Android, to Blackberry (yeah, right), to Windows Phone, and back to the iPhone 7S, and have you never need to worry about the cost or headache of supporting the device…just as long as you worry about your data and I’ll worry about mine. Ultimately, it’ll work out for the best anyway, because I don’t think you care about my current run on Trivia Party, just as much as I don’t care about your emails once I move on to the big ITSM independent consulting dream job in the sky.

Sincerely,

ITIL and Me.

Dear beloved readers (both of you),

I have a confession to make.  As much as I’ve attempted to try and live the life that I preach, I failed in one facet that I hold in high regard.  I haven’t been 100% completely transparent in my ITSM dealings with software and service suppliers.  The reason for this is simple; I’ve always felt that I should keep my blog “vendor neutral” and never show favouritism towards one vendor over another.  My reasons for such agnostic tendencies are few but simple.  First, I live in a constant state of fear since it’s these same vendors that have resources and reputations that can ruin my professional aspirations.  Second, I can only write blog posts about the software I work with on a daily basis, so obviously there will only be a few vendors that ever get mentioned on this site.  Third, and probably the most important, I really think it’s hilarious to use asterisks to reference a company in the name of “vendor neutrality” when everyone knows who I’m writing about anyway (an idea I lifted from Howard Stern).  To be fair, I’m just a small fish in a rather large and complex ITSM pond and when I started writing over a year ago, I honestly had no idea where I was going with this blog site.  Actually, I still don’t have any idea where it’s headed, but that’s not the point.

I will most definitely state that my point of view is that of someone in the ITSM trenches:  The “regular” process nerd in the next cubicle that has the ITIL library in his desk drawer, lots of grey and thinning hair from process meetings, a well used coffee mug with the permanent coffee coating on the inside, and a never-ending hunger to improve the way IT works and to make the most out of the (very) few resources we have available.  In essence, I’m a practitioner that lives outside of the glamoured world of vendors and consultants and doesn’t see a single cent from any endorsement (positive or negative).

Will I always be successful at being transparent?  Probably not, but I can at least promise to try.  With that notion out of the way, I’ll do away with asterisks and from this point forward I decree S***-***w shall be written as ServiceNow.  I will be a little sad as many people have commented that they think it’s funny I remain “vendor neutral,” but yet I do a pretty bad job of hiding it.  What these same colleagues don’t know is that I’ve always been neutral towards the vendor community and have simply stated the facts (as close as my point-of-view allows).

To the vendors out there:  I promise to remain as true to our dealings as possible.  If I have reason to say why your software or services are fantastic, I’ll say it.  If I have a valid reason to be disappointed in our dealings, I’ll state that as well.  If I also think it’s absurd that you’re still handing out demo software on CD’s, you can bet your boots you’ll be getting a mention.  On the other hand, if you ever contact me to “set things right,” I’ll be more then happy to listen, have a dialogue, and write-up a nice little post about the encounter and give kudos for trying to improve your product or service.  In my point of view, when it comes to IT, nothing is perfect, but we should always strive for perfection anyway (which is a great basis for Continual Service Improvement).

Who knows, I’m sure I’ll eventually sell-out and this site will be plastered with advertisements and biased posts.  Until then, I plan to keep the faith… power to the people…damn the man…up the revolution…(you get the idea)…

Yesterday I had the chance to be a part of the Mobile and Social Product Summit panel at Knowledge 12 hosted by Dan Turchin (@dturchin on Twitter), and a strange thing happened. We didn’t really address any part of “mobile.” I honestly think this was a great injustice and the only way to right this wrong is to write-up a blog article.

As fantastic as social IT/social media is, it’s really not as powerful without the mobile aspect. Don’t get me wrong, I think the Live Feed in S***-**w will be the future of how we interface with ITSM (as Fred Luddy demonstrated), but making such services available on mobile devices increases the power and productivity several times over. It’s kind of like BASF – it doesn’t make social IT, it makes it better. But I bet you’re wondering, why should you or I care? The answer is simple; the world is moving towards mobility. Like millions of other people out there, I access my social streams through my iPhone. I can name a number of reasons why; convenience, ease of use, web filters at work, FOMO (fear of missing out), etc., etc. My point is that social media for me is something I want available 24/7/365 (that means when it’s a Leap Year, I do disconnect). Even if I’m not actively accessing my social networks, I still want to have the warm comfy feeling knowing that I can do so any time and, if someone wants to communicate directly with me, they know I’ll respond in a timely manner.

OK, so we’re all moving towards mobility, but why should that matter when everything can move with it? Our operating systems are being designed for it, email went mobile long ago, and applications have been developed so our mobile devices (phones and tablets) can function almost as well as a computer. In this case, let me throw out another thought – mobility needs social IT just as much as social IT needs to go mobile. I love my iDevices, but they’re still not at 100% with replacing my computer. The reasons are many; screen size, interface, lack of apps for certain programs, webpage incompatibilities…you get the idea. But when it comes to my social networks, they look nice and are easy to use. In fact, I prefer these interfaces over the desktop/webpage alternatives. Now that we established that I like the interface, what if I can then access incidents, problems and knowledge through it? In fact, not only could I access information, but what if I could then add to it? In this case, the social stream is now acting as my gateway to the ITSM world. The immediacy of the information on my mobile device can let me see what’s going on in real-time, and through that interface, I could then react accordingly.

At this stage in the game, I think it’s safe to say we’re heading towards a future in which the only personal computing device a person will own is their phone. On the same token, that same device will be a portal to social communication that allows us to work more effeciently then what’s possible today. So social IT and mobility are in a relationship that, for better or worse, requires them to evolve together. This marriage was shown at Knowledge 12 and all I can say is please, for the love of all that is holy, I really hope S***-**w hurries up with the mobile/social IT platform. One day, it’ll be the only platform we use anyway.