FIXING IT PROBLEMS – HOW TO MEASURE THE TIME SPENT ON IT

Fixing IT problems takes a lot of time. Just think about it! What could you use 10 minutes of free time a day for? And ten every hour? And what if your colleagues and you could spend those ten minutes freely on anything at all?
Let's ask ourselves: does someone who runs a successful business, say in the food industry, need to understand what a system administrator does? How will they know that the specialist they hired really knows what they're doing, and also uses their time efficiently? The answer to the first question seems obvious: if the IT system works well, the administrator is doing a good job. But what numbers help us find the ideal way to manage our company's IT?
Why quantify IT work?
First, let's establish that our colleagues can only work efficiently in a smoothly running IT environment. In an office today, that has to be supported in some form. It's not enough to set up a few workstations and sit Gizi down to work.
It's important to know what to consider when setting up an internal network. These factors determine which modern tools let us achieve maximum efficiency, the highest availability and the greatest security. Essential for this is a competent team of IT specialists. Because IT has become so diverse, today the era of one-person tech support is over, since it's impossible for one person to keep up with every new IT trend.
A pill that cures everything usually cures nothing. System administrators don't work as developers.
It looks great when a company has its own administrator on staff and doesn't have to rely on an outside firm.
Numbers don't lie
So we're not just talking in the abstract, let's take a concrete example that could happen at THE COMPANY at any time.
An IT problem appears
- On Monday morning, the company administrator learns that THE COMPANY's intranet portal is down. The fault needs a fairly complex fix, and since colleagues share information and get updates there, it should be repaired as soon as possible.
- The printer that stopped working over the weekend also comes up now.
- And at 9 o'clock a new colleague starts who is completely new to THE COMPANY.
Since the new colleague's arrival was known in advance, the administrator was told and prepared the permissions, workstation and other equipment. Setting them up and explaining how the system works would be the administrator's job. But because of the morning server fault, he has no time at 9, as troubleshooting takes priority. And now the questions start!
- Who will hand over the equipment?
- Who will hand over the username and password?
- How secure is it to, say, stick them on the monitor with a Post-it where anyone can see them?
Not at all – so the administrator decides to deal with the intranet fault first and only then make time for the new colleague.
Fixing an IT problem with an in-house administrator
The administrator manages to fix the fault by 10. The intranet is now running, but the new user has been there for an hour and still hasn't been able to log in to his computer. By now the administrator is an hour behind, rushing and stressed.
Since nothing has happened with the printer for two hours, accounts clerk Béla Kis decides to fix it himself, having told the administrator in vain. He unplugs it, takes out the toner/cartridge, puts it back – and meanwhile his own work stops too, because he's not doing what he's trained for but something entirely different.
Meanwhile he notices that a sheet is jammed in the printer, which is why it's not working. Not knowing the printer model, he doesn't know how to remove the jammed sheet properly. He simply yanks the paper out, damaging the rollers, which from then on pull in paper with a painful squeak on every print.
Assessment
- Administrator: morning troubleshooting: 2 hours + 0.5 hours of documentation sometime during the day, if he has time.
- Setting up the new user's workstation: 0.5 hours + briefing the new user on the systems (file access, setting up printers, hearing any individual requests): 0.5 hours
- Checking the printer: 0.25 hours
- On top of that, the new colleague lost a whole hour waiting for the administrator, and Béla Kis wrestled with the printer for at least a quarter of an hour.
- In total: 5.5 hours.
What can we measure?
The big advantage of outsourced IT operations is that a team of specialists with varied knowledge can help with far more than a single IT person. Proof of expertise is continuous participation in training, which unlocks various vendor partnerships.
The more vendor partnerships an IT company has, the surer we can be that we're in competent hands.
Thinking purely in numbers, a monthly report tailored to the client can show:
- what was spent on what;
- what quality of service was received;
- how requests were handled;
- how efficient and fast the system operators were.
A ticketing system can be important for measurement, making it possible to trace both the time spent on a fix and its process, as well as who was responsible for the task.
Another big advantage of such systems is searchability: if the same problem comes up later, we search past tickets rather than our memories. The client can also follow the actual work, the processes and the current status of tickets, and give feedback. And if that's not enough, client-specific monthly reports help partners see clearly what they paid for that month.
IP phone systems measure customer service work. You can report on how many calls the call centre took, how long they talked, how many calls were dropped and what their response time was.
What the report doesn't show
Some parameters aren't so easy to measure. It's hard to express in numbers:
- how the new colleague feels on his first day,
- what impression the company makes on him,
- how competent he finds the IT person,
- or how well organised the onboarding process,
- and how much it sets Béla Kis back when he has to deal with fixing the printer.
Nor can we measure in numbers what it means when an IT person doesn't have to rush. When he has a quarter of an hour for a task instead of five minutes. What unit can we use for the fact that, by delegating work to the help desk, our administrator doesn't have to wrestle with minor faults beneath his expertise?
Both sides are more satisfied when the user doesn't feel like just another task to get over with as quickly as possible, but receives genuine attention. And that's something no money or report can measure.












