Serio Blog

Friday, 18 Jul 2008

I'm asked to write about how Group Companies are incorporated into overall IT Service Management. Specifically, what happens if your own company either buys another company or starts another company that will be run as a separate entity (with it's own capital, directors, and premises)?

Of course, I can't answer the question for you - but what I can do is consider some of the issues you might have to work through. Some are conceptual, some practical.

Sometimes we at Serio are asked 'how should we incorporate them into Serio?' when the real question is 'How do they fit-in in terms of IT Service Management'.

I'll refer to the newly acquired company, or the new start-up company, as 'NewCo'.

What is the 'Strategic Vision' for IT in the whole Group?

There may be a Strategic Vision that outlines the approach you take - these usually originate at group Director level. It may be that this will guide you on what you need to do (for instance, many companies centralise IT services, others have a horror of 'Head Office' services and want everything as close to the business and customers as possible). If you are lucky there will be such a guidance, but there is every possibility there won't - at least in my experience.

Will NewCo Management want control over their IT?

The directors of NewCo will be focussed on creating or developing their business, and may see IT as a critical component of their strategy. If so, any suggestion of incorporation of their IT service delivery into existing ITSM services might be unwelcome. Remember that it isn't necessary for them to be tightly integrated in terms of IT to be able to send and receive emails, and share files, with the rest of the group - you can set-up web portals specifically for this purpose.

Will NewCo have its own IT Service Management function?

First of all, is there any NewCo IT Helpdesk or Service Desk? What you are trying to assess is if there is any local function to integrate in the first place. The important thing is how such a service is perceived by the directors of NewCo.

How much interaction between your existing IT service management function and NewCo will there be?

...or phrased another way, 'how much will NewCo use group services'. Try and imagine how many support tickets might need to be passed between the two groups - but be realistic. How much will NewCo and your own ITSM group need to work together (be realistic, and resist the urge to over-estimate).

What are the politics of the situation?

This is most poisonous aspect, particularly in cases where NewCo is an acquired company rather than a start-up. As soon as anyone mentions 'incorporation' or 'merger' of IT services people see their jobs and (most importantly) their prestige to be under threat, any hope of co-operation can go out of the window. People start firing-off their CV's, attitudes become negative, it gets harder to achieve any kind of consensus. Alternatively, you might find two groups of people whose skills complement each other. 

Monday, 14 Jul 2008

As some of you are aware, we've recently (as of Friday) relocated to new offices here in Livingston. BT's technology doesn't seem capable of allowing us to keep our old telephone numbers even though we've moved no more than 2 miles to Uphall Station, so we now have new telephone numbers which are:

Tel: 01506 438855
Fax: 01506 438868

Wednesday, 09 Jul 2008

This is a follow from the post last week, continuing the topic of Team and Agent metrics.

Quality of Completion - An interesting an often overlooked figure connected with Incident Management. How many tickets are re-opened after closure? Whilst it might be that there are legitimate reasons for re-opening a closed ticket, a high number might suggest issues with quality control (closure before it's really closed).

First Time Fix Rate (FTFR) - For call-handling teams, you can look at this figure both by Team and by Agent - either with examining actual results achieved, or by looking at a 3 month trend.

Speed of Resolution - For Helpdesks and Service Desks you might have underpinning contracts and might want to examine performance from a time perspective - either resolution against target or response against target. These can often reveal more insight into why your overall service targets are hit or missed.

Backlog or Assignment Status - Something you should probably be looking at at least weekly (and ideally daily) is a status report that shows you where tickets are currently assigned - both by Team and by Agent (you'll find such a graph under performance in SerioClient). If you see relatively large numbers against a single Agent or Team, you can take action by re-distributing or allocating other staff to the Team. 

Friday, 04 Jul 2008

I'm asked to address the subject of how you measure the performance of Helpdesk/Service Desk Teams and Agents - something that can be both useful, vexatious, misleading and controversial (and possibly all of these at the same time).

If you are asked to look at this subject, you need to be clear about what aspect of performance you want to look at - saying 'I just want to look at standard reports' usually means you haven't thought clearly enough about what you wish to examine, or what problem you are trying to solve. For example, are you concerned about a Team that seems to take a long time to resolve Incidents? Or a Team that seems to re-assign a lot of tickets that are assigned to it? Do you just want to get an overview?

Let's take a look at some different aspects of Team and Agent performance. You'll see that these are mostly subsets of overall ITSM service delivery performance.

Type of Ticket - Are you looking at Incidents, Problems, Service Requests or Changes? Or all four? You might find it helpful to consider each individually.

Rate of Resolution - Now by this I don't mean speed, I simply means out of how many tickets logged or assigned to a Team did that Team actually resolve? This may not be appropriate for all ticket types and for all teams - but for some it will be. The most obvious is a first line support team, and instances where you are trying to improve the number of tickets resolved without being passed to other teams. It might be hard to determine what the 'right' or 'acceptable' number is, so try looking at the figures over something like a 3 month period.

Number Resolved - This is probably the ultimate blunt instrument, so use with caution (yet bizarrely it's often the first measure managers look at, especially for Agents). The reason it's a problematic measure is that those Teams and Agents having more complex workloads and tasks will usually have a much lower rate of resolution than those with simpler tasks. One useful thing you can deduce from this is if a particular Team or Agent is being put under increasing stress by increasing volumes. You can also investigate issues where ticket closure figures are low for one or two Team members - but remember it might simply be they are doing other things, or handling more complex cases.

Churn - Here I'm referring to an overview of incoming tickets, the number resolved, the number outstanding and the number on-passed to other teams. You'll find a report in SerioReports that shows this, and can be used to get a view of how Incidents move between teams.

I'll post the rest of this article next week. In the meantime, I've made a companion spreadsheet to our Service Desk Metrics White Paper which contains some actual examples. Search this site for downloads and you'll find it.

Friday, 06 Jun 2008

In case you have been sitting on a desert island recently (and if so, lucky you), you'll have noticed that Microsoft have announced Windows 7. The public and press reception is probably summed up by the word 'underwhelmed' as shown here and here.

What caught my eye was Steve Ballmer saying 'Vista isn't a failure'. Oh yeah? I think even having to say that tells it's own story...

As someone that works for an ISV (Independent Software Vendor) I can tell you than new Operating Systems are like Acts of God like floods, typhoons or earthquakes, but with advance warnings - there's no point in moaning about it, you just need to prepare as best you can.

It's just that, with Vista, it was really hard to see what it gave anyone that was extra. OK, it looks much nicer, but it needs a relatively big, beefy computer to run it, and in many aspects (such as networking) it doesn't interoperate well with XP or Windows 2003, and most importantly doesn't run a lot of applications (derisively called legacy applications by Microsoft) that users want to run.

It seems most of you agree. Here at Serio, only our smallest customers have taken-up Vista, and for these it's not so much a choice as it is what came pre-installed on their newest computers. For companies with more than 300 computers it seems like Vista offers nothing in return for the considerable cost and time in upgrading. What evidence we have for actual use of Vista is discussed here and it's not particularly good reading for Microsoft.

So what about Windows 7 then? Well as far as we can tell it's all about touch - rather than exclusively using a mouse to interact with a computer, you'll directly interact with the screen as you do with devices like the Apple iPhone. We've been here before though, as we blogged about over a year ago.

Personally I take touch screen with a pinch of salt. For a start, it takes a good deal of energy to hold your arms directly in front of you (go on, try it), particularly if your company's health and safety police have moved your screen to the optimum distance away from your face. I can't see users doing this for more than a few minutes before they reach for the mouse again.

Secondly, a lot of people eat at their desks. Muck that is currently sitting on keyboard and mice will end-up on screens as well where you have to look at it.

I have to say that, right now, it's hard not to feel underwhelmed by the prospect of another desktop Operating System. I see Microsoft's need to release one (investor pressure) but I can't see a corresponding user need just yet. 

Wednesday, 04 Jun 2008

This is a follow-up to this earlier post which focused on some of the downsides of running in extended hours. This post however will take a more positive stance, with some of the things that can help ameliorate some of the points made in the earlier post.

Examine your budget, because it probably isn't enough. Lots of factors will come into play such as

  • Recruitment Agency Fees (if you use them). Negotiate a realistic rate and refund period, and plan for higher than usual churn.
  • Training budgets. Inevitably higher staff turnover has a double-whammy effect: it reduces your call throughput (less experienced staff), and increases training charges.
  • Don't spend your budget exclusively on bonuses and allowances, it might not be getting you the best value.

"We under-budgeted, or rather budgeted like it was 2 x 9 to 5. The project suffered for months as a result."

Consider the practicalities. Some staff, those without cars, find travelling at unsociable hours difficult. Whilst at the start of their employment in the bright summer months standing waiting for a 10:00pm bus sounds OK, it might not be so nice in the middle of December. See if you have the funds to offer assisted transport - taxis, minibuses and the like. This can help to reduce staff fatigue and churn.

"The change having the free minibus made on the 6:00pm till 11:00pm shift was significant. It was particularly appreciated by women who no-longer had to travel on late night buses, well worth the £6k a year it cost us."

Check how you are selling the jobs. There's no point in painting an overly-rosy picture. If shift working is unavoidable don't make it seem otherwise. If you are using an agency make sure you understand that your objectives and theirs are not necessarily the same - so make sure you have seen how the positions are advertised. If you like, make a test application to see if potential recruits are being soft-soaped.

Offer a career path. This is closely linked to 'how you are selling the job' above. If you offer this as a lure to fill shift-based you need to be seen to deliver this quite quickly (but remember it's a process rather than an event).

"Setting aside some time for training, and having a structured approach, is key. Training for actual qualifications (technical qualifications like MSCE or ITIL) is useful if you can afford it. The worse the job is, the more you've got to have this. Don't forget it's useful as well because you end up with better-qualified people talking your customers."

Flexible working. It's easy to see flexible working as another complication, but it can help in service delivery as well.

"Having had constant problems with retention, we created a pool of staff. We agree to give them a minimum number of hours each month, and I can then call and ask them to come in at different times. So it might be someone's week off, having worked 12 hours the previous week, and I say ' can you work tonight for 5 hours'. If they can they say yes, if they can't they say no. Then there are others who work longer and more regular shifts. I mix the two up to get a full rota.

It's been useful for women trying to get back into support or customer-service type roles after having children. They like the extra income it gives them, and makes childcare less of an issue if they are working evenings. Some people employed this way have been with us over two years. It was a great innovation".

Thursday, 29 May 2008

If you are asked to set-up a 24-hour support operation, where do you start?

I'll leave Service Level Agreements aside for now, and assume they are in-place. What I'm going to focus on here are staffing issues and staff costs.

There are really two different cases to consider: greenfield site, and an existing operation moving from a more normal 9 to 5 or 8 to 8 to a 24-hour or near 24-hour (for want of a better expression, I'll call this a brownfield site).

Out of these two, the greenfield site seems to easier - you can recruit staff who understand what they are getting into, rather than trying to persuade existing staff to change existing shift patterns. Except, it's not as easy as that, as the comments below make clear.

As part of the preparation for this post, I called a few service delivery managers with 24-hour experience (2 running genuine 24 hour operations, 2 having once run near 24-hour operations, all running Mon-Fri only), to ask what their issues had been, and are currently. Not scientific, but useful none-the-less.

Support staff morale and 'burn' was reported, not surprisingly, as the biggest problem. Some of the comments made are as follows:

"Even when you advertise that the job is shift work on an IT Helpdesk, it doesn't seem to sink-in for a lot of people what it actually means. They just see the 'IT Helpdesk' words and see an opportunity for a career change. Some people are just fine, but others get cranky within a couple of months and start to talk the job and the company down. You're better off letting these people go in my opinion."

"Money is a rotten motivator. Extra cash for working on Wednesday to Friday only works for a couple of weeks, after that sick leave goes through the roof."

"My most important time is still 9:00 to 17:00 but moving support to later and longer hours degraded the service for the core times as well, because the most experienced people left within the first 6 months."

"My biggest mistake was the budget. I had budget to include salaries and a bonus payment based on unsociable hours, and that was it. But each time I recruit someone my agency fees are well over a thousand pounds, and their refund interval is short. My company had a corporate agreement with these guys so I was stuck with them."

"New staff were recruited by our HR department and sent to me 'to save my time'. The new starts became belligerent within the first weeks. It turned out HR was downplaying the shift work element from 'this is a shirt-work job' to 'some shift-working may be required'. This allowed them to tick their box and left me looking like a chump."

"In my case training became a difficult as the people capable of giving the training we not working shifts, but the trainees were. I could devise no solution to this problem."

"In my case we bid for the contract at too low a cost. It was like running a marathon with a broken foot from day 1. Horrible."

I'll follow this post with some of the remedies that have been successfully applied, asking if their were any positives from the experience, and expand this topic buy considering budgets.

Monday, 19 May 2008

Well we've finally got Release 5 out. For those of you who haven't noticed, the Serio Release 5 Website is here. If you've not yet received a download email please contact Serio support – it probably means we have the wrong admin contact on file.

I'm pleased to report that the upgrade process seems to have gone very smoothly for those who have told us they have upgraded. The only problem reported so far has been by a customer who had made their own modifications to the Serio schema – something we tell customers not to do for that very reason (your upgrades will fail). Even then, we've been able to fix the problem.

The feedback has been extremely positive, with the Service Explorer being by far the most popular addition, with PocketSerio-i coming a close second. On the subject of PocketSerio-i, it seems the most popular use for this so far is out of hours support, for engineers on call. Customers log tickets through SerioWeb, and these are then picked-up and worked on through PocketSerio-i whilst at home, in the pub, or at a restaurant. As someone explained to me: 'it means I can do out of the house and do normal things, but still handle any issues that come up and still collect my out-of-hours fee'.

Release 5.1

We've already started work on Serio 5.1, which we are planning to be a smaller upgrade (5.1 has yet to have any kind of date fixed yet). A lot of Diary changes are planned or have already been completed – for instance, Diary changes are now audited, you can colour-code Diary entries, and we are probably going to move the Change Plan Diary and some other items into there as well, giving you a lot of control over what you see. We've also added Diary support into PocketSerio-i (a great, great addition).

We really would like to hear your feedback and thoughts on how we can make the Diary even better.

Aside from the Diary, PocketSerio-i and SerioClient Express will (probably) be the focus for Release 5.1.

A number of you have asked for more customisation options on the Service Explorer (such as customisable colours like in Incident Management). We are going to try something along these lines, so long as nothing detracts from the ease-of-use of the Service Explorer.

Friday, 25 Apr 2008

Sorry for the break in posting, everyone here has been focusing hard on Serio Release 5. It's looking pretty good and will be released on Monday. The Release 5 website is here.

Wednesday, 19 Mar 2008

One of my favourite new features in Serio Release 5 is the Service Explorer. It takes all the data you have in Incidents, Service Requests, Problems, Changes, Items and so on and presents the whole lot in a collapsible tree form.

The best thing is to show you a few pictures. Service Explorer 1

Figure 1 - Browsing Active Incidents in Service Explorer

For of all, Figure 1 showing me browsing to my Active Incidents using the Service Explorer. Notice the graphical columns as well - these are there by default, you don't need to customise them in. One of them shows SLA time to go as a 'progress bar', going from grey to amber to red as deadlines near.

You can display Incidents, Service Requests, Problems and Changes either separately or all together.Service Explorer 2

Figure 2 - Incident expanded in the Service Explorer

Whatever you are working with, it's expandable. Figure 2 shows what the Service Explorer looks like when you expand an Incident. Notice that some key items of data are expandable -like SLA, Item and Customer. This is so that you can easily 'drill down' and get to more data... as shown in Figure 3. Service Explorer 3

Figure 3 - Expanding an Item with the Service Explorer

Here you can see that by expanding the Item, I can see all the tickets we have on file (open or resolved) for Desktop Computer D10001. As these as themselves just Incidents, Service Requests, Problems and Changes they can be expanded as well - revealing their own Change Plans, Checklists, links, documents and relationships.

Service Explorer 4One of the unexpected benefits, for me at least, is that the Service Explorer makes the process of querying and drill-down easier. It offers many different ways of looking at tickets, as you can see in Figure 4 where I can see we've got just a single High Priority ticket open.

 

 

 

 

 

 

Figure 4 - High Priority ticket open in the Service Explorer

 

Extended Data

Another new feature is what we call Extended Data.

These are additional fields you can attach to tickets of any type. The data is structured, meaning you can have strings, checkboxes, drop down lists and so on, defaulting each if you so wish. As a test, I defined Extended Data for Incidents that is a food survey. Figure 5 shows you me actually entering the data, and Figure 6 shows what the data looks like when you view the ticket in the Explorer.

 

 

 

Figure 5 - Extended Data Editor

 

Service Explorer 5

Figure 6 - Extended Data field expanded in the Service Explorer

Pages