I guess I should have expected this (but alas I didn’t) – the Capita ITIL, the IT service management best practice framework, joint venture with the UK government wasn’t big news. If anything, the story made ripples rather than waves; and from a UK government “finances” rather than IT service management (ITSM) best practice perspective.
It’s interesting to consider why – particularly when enterprises are so adamant on requesting ITIL-alignment in ITSM tool selection RFPs. But first a few links:
In a previous blog post, SysAid – a provider of IT management solutions – was kind enough to share some metrics/performance snapshots collected from its customers. As a quick recap, SysAid captures service desk benchmarking information through its customers’ use of its software (on an opt-in basis of course) for the benefit of all.
At some point we should sit down and compare the SysAid stats to those provided by HDI – a great independent source of service desk benchmarks – that’s a challenge to you Roy Atkinson … BTW, I hope the HDI 2013 event is going well in Las Vegas this week (the Twitter hash tag is #hdiconf13 for people, like me, who aren’t there). Anyway, back to those SysAid stats …
A selection of community-based service desk stats …
There are two points to note here: not all SysAid customers participate (according to its website, SysAid now has over 100,000 customer organizations); and I have cherry-picked a handful of the available stats from March 2013. There is also one caveat from me – there is no differentiation of organization size in these stats, we need to drill down further to account for any small or very large organization bias.
Percentage of incident tickets originating from the End User Portal, Average 60.31%
This blog has been contributed by Barclay Rae, an independent management consultant, and is the first of a new series of blogs written by IT service management (ITSM) thought leaders. Please read in Barclay's Scottish brogue ...
ITSMers often need help
Much of the demand for knowledge and support that I see in my regular consulting work centers around a simple request: “what are the key things to be doing for successful IT Service Management?”
People tell me they’ve read ITSM books and been trained (and certified) in ITIL and other frameworks, but because there’s so much content, plus multiple processes and standards. They lack a clear understanding of where to start and how to focus on what is important and successful in practice.
Focus on the critical activities
For me there’s a critical set of activities and actions that need to be achieved in order to deliver quality and effective service delivery – customer engagement, service definition, service desk quality, problem management, reporting and metrics, organizational change, and marketing. For many years this is what I’ve provided via workshops and consulting, and now I’ve turned this into a simple, straightforward, and practical approach and portfolio of knowledge – ITSMGoodness.
Forrester recently published “IT Service Management (ITSM) Case Study: Making The Transition From On Premises To SaaS With BMC” which is available to clients here. For non-clients (or hopefully “future clients”) I thought I’d create a blog on the good practices distilled from the discussion with the BMC client.
The situation … does it sound familiar?
The customer had found itself hamstrung by a highly customized on-premises ITSM tool that was: 1) too costly to run; 2) a poor fit to operational and customer requirements; 3) complicated and cumbersome to use; 4) unable to keep pace with the latest service management thinking; and 5) stranded on an out-of-date version because it would cost too much to upgrade.
The solution …
The customer used a honed set of requirements to select BMC Remedyforce from a shortlist of six SaaS ITSM offerings. In their words, they chose BMC Remedyforce because: 1) it was best suited to the agency's existing and future needs; 2) it was built on the salesforce.com platform; 3) its user experience was similar to (but better than that of) the incumbent Service Desk Express; and 4) it was the most cost effective.
Here's what they did:
The initial deployment managed requests and tasks from both customers and internal IT.
The customer took advantage of subscription-based licensing's ability to flex with demand.
They also used BMC Remedyforce in different scenarios: in internally and externally facing call centers and, in addition to traditional IT support, addressing customer support, app development issues, and human resources (HR).
It’s finally here. The Forrester Market Overview: SaaS IT Service Management Tools covers: a little ITSM tool history and how we have moved on, the benefits and risks of the SaaS delivery model, key selection criteria for selecting a SaaS (or on-premises) tool, and overviews of 23 tools (from 21 vendors) and their functional capabilities across the enterprise and midmarket marketplaces.
“Why on earth did you write a SaaS-only ITSM report?” I hear some cry
It’s simple – Forrester client demand. In 2012, a good 25% of my 400ish a year client inquiries related to IT service management (ITSM) tool selection; and the SaaS-delivery model (and the key vendors) was covered in nigh on all of them. That’s not to say the client ultimately went SaaS though, inquiries are very much about rapid information exchange in helping clients make important decisions. It’s not about making the decision for the client.
What the SaaS ITSM market looks like
The following figure shows the 23 vendor tools split by average customer subscription (seat) count (described as Enterprise, Upper Midmarket, and Lower Midmarket) and their degree of customer success (the number of paying customers):
There are of course other ITSM tool vendors who declined to participate for a variety of reasons. One would be that they were not briefing Forrester analysts and thus not on our radar.
My most popular blog of 2012 wasn’t written by me … but I guess you might have expected this if you’ve already read a few. That blog's author, an end-user (or is that a customer of an internal IT organization), now returns to look at the IT service desk through a customer and customer experience lens. I’ll let them continue in their own words …
So how is your customer experience?
It’s never been more important to build strong customer relationships (regardless of what type of service you're offering). Long gone are the days when the customer purchasing path was straight-forward, and when the only route of post-sales contact was the phone. In 2013, we need to be proactive and embrace consumer-driven change, harnessing the power of new technologies as well as improving older methods of contact.
Whether your interactions with customers are face-to-face, via the internet including social media, or over the phone; and whether they involve physical or virtual products; they now need to generate a good “experience” for customers. In the age of the “empowered customer” failure to manage these “experiences” can lead to missed opportunities and/or customer loss. And not just with the affected customer(s).
So what is “customer experience” and could it apply to IT service desks?
Forrester’s definition is simple: “How customers perceive their interactions with your company.” So for an IT service desk, could it be: “How end users perceive their interactions with your service desk”? And if so, how do you deliver this increasingly critical “customer experience”?
While attempting to clear my desk before the Christmas break I stumbled upon a bright-pink USB memory stick that contained the collected presentations from the 2009 itSMF UK annual conference. Having satisfied my curiosity as to the size of the memory stick (I’d forgotten that USB sticks were ever that small), I then wondered:
What were the IT service management (ITSM) hot topics in November 2009?
Which industry luminaries were presenting on them?
How many presentations would still make it to the 2013 itSMF UK conference?
Last week I had the opportunity to attend the 15th annual Black Hat security conference in Las Vegas. I have attended DEFCON in the past, but never Black Hat. The conference has grown significantly each year, and judging by the size of the expo floor, the vendors understand its significance. I enjoyed the conference and had great conversations with practitioners and vendors alike. Here are some observations from two of the sessions that I attended:
This week I did a webcast, Planning for Failure, which makes the assumption that if you haven't been breached, it is inevitable, and you must be able to quickly detect and respond to incidents. An effective response can be the difference between your organization's recovery and future success or irreparable damage. While I was working on the slides for the webcast, I started to reflect back on the 2011 security breaches that personally impacted me. Three breaches immediately came to mind:
There is growing evidence of a harmonic convergence of Infrastructure and Operations (I&O) with Security and it is hardly an accident. We often view them as separate worlds, but it’s obvious that they have more in common than they have differences. I live in the I&O team here at Forrester, but I get pulled into many discussions that would be classified as “security” topics. Examples include compliance analysis of configuration data and process discipline to prevent mistakes. Similarly, our Security analysts get pulled into process discussions and other topics that encroach into Operations territory. This is as it should be.
Some examples of where common DNA between I&O and Security can benefit you and your organization are:
Gain economic benefit by cross-pollinating skills, tools, and organizational entities
Improve service quality AND security with the same actions and strategies
Learn where the two SHOULD remain separate
Combine operational NOC and security SOC monitoring into a unified command center
Develop a plan and the economic and political justifications for intelligent combinations