ITSM Consulting Australia Explained: What It Actually Fixes
Mostly, ITSM consulting is about the stuff that keeps coming back. The request somebody swore they’d action, the fault that returns every few weeks, the job nobody can say who owned. Sort those out and IT gets a lot quieter, which is what most Australian business owners are really after.
If you’ve seen the letters ITSM and wondered, it’s short for IT service management. Nothing exotic in it. Your business agrees on a way of handling IT requests, and then people actually stick to it. You won’t need new hardware, and nobody’s asking you to shell out for some big system, although a ticketing tool does earn its keep down the track.
Why IT ends up messy
Say a new starter’s laptop request goes to the one bloke who looks after IT. He’s up to his neck in a server problem, so the email sits there until Thursday. Meanwhile the new starter is peering over the shoulder of whoever sits next to them. Nobody did anything wrong, exactly.
Or the Wi-Fi in the back office drops out most arvos. Staff reboot the router, have a grumble, carry on. A month later someone else reports it like it’s brand new.
Pretty ordinary stuff, and it’s rarely a skills problem. Nothing connects one job to the next, so it all lives in somebody’s head. Heads go on holidays. Sometimes they resign.
What an ITSM engagement changes in daily operations
Mainly three habits. Every request goes to the same place and gets ranked by how much it hurts the business, so a dead payroll system beats a slow printer every time. Breakages and ordinary requests get treated as different kinds of job, because they are. And when something breaks twice, somebody’s asked to find out why.
Smaller shifts follow. People stop guessing who to ask. Say there’s a system update planned for Friday arvo: somebody tells the office first, so Monday doesn’t kick off with half the team locked out of the accounts file and nobody knowing why. Then there are the numbers. How long jobs take, what keeps coming back. Most owners have never seen a single figure like that about their own IT.
Some of this comes from ITIL consulting practices. ITIL is the best-known body of service management guidance, and it’s where words like incident, problem and change come from. Hardly anyone uses all of it. A ten-person office running the full paperwork would spend more time filing than fixing.
Where managed IT and a help desk come in
Managed IT providers and help desks do the actual work. ITSM is about how that work is set up, so it touches whichever one you’ve got.
With managed IT services, a review checks that what’s agreed on paper matches what’s happening, and that jobs pass between you and the provider without falling down the cracks. With a help desk, whoever picks up the phone gets proper categories, a way to escalate the nasty ones, and notes from last time. With neither, which is fair enough because heaps of businesses are in that boat, it helps you work out what’s worth keeping in-house. That call is a big part of what IT consulting at Loginet is for.
What a consultant does first
Asks questions, mostly. How do requests reach IT today? Who handles them? Where do they stall? What do your staff whinge about over morning tea? That last one gets more useful answers than you’d expect.
You come away with a short list of things to change first, explained without the jargon. It’s usually pretty dull: one place for requests, a few clear priority levels, a note of anything that keeps recurring. Change approval and reporting can come later, if they’re needed at all.
Then a check-in after a few weeks. People skip this bit, and it matters, because a routine nobody follows is worse than none. It just makes everyone feel covered.
So IT service management consulting, boiled down, is about making IT boring. Boring is the aim. The point of IT service delivery improvement is fewer repeat faults, faster fixes where it counts, and you chasing people a lot less.
Is it for a business your size?
Fair question, because a lot of the ITSM material out there is written for big organisations with whole service teams. For a smaller business it runs at a much lower volume. You aren’t buying a platform or hiring a process manager. You’re agreeing how your two or three IT people, or your provider, handle things, and jotting it down on a page or two.
Where does it pay off? Usually in a few familiar spots. The same couple of people get interrupted all day. You’ve changed providers and nobody can say what was promised. Or the business has grown and IT is still run like it’s five people in one room. If that isn’t you, no worries. You probably don’t need it yet, and a decent consultant will tell you so.
Questions people ask
Is this the same as managed IT services?
Not quite, no. A managed provider is the one doing the work, like monitoring, support and patching. ITSM is more about how that work is organised and checked, so it matters whether the provider handles it, your own people do, or it’s a bit of both. Plenty of businesses end up wanting both.
Do we have to follow ITIL?
Nope. Reading it cover to cover and applying every page would be overkill for a small business. Incidents, requests and changes are the usual starting points. Beyond that, how much you take on comes down to your size, what’s at risk if IT goes down, and what your team will realistically keep doing.
How would we know it’s working?
Have a think about how the week feels. If people stop chasing and the same gripe doesn’t come up twice, that’s a good sign. Then back it up with a few figures: time to close jobs, repeat faults, what staff say about support. Jot down what you’ll track before you start, or you’ve got nothing fair to compare against.
Worth a chat?
Recognise any of this? Loginet’s happy to go through how requests, faults and handovers work in your business right now, and tell you straight whether more structure would help or just add admin. No hard sell. Get in touch whenever suits.
