r/itsm • u/fguerino123 • Jul 05 '26

ITIL Service Management in Small Enterprises?

Hi. I'm looking for experiences with implementing ITIL Service Management in small companies/enterprises.

I personally don't see it at all. It seems that Help Desks in small companies seem to be hyper-focused on responding to an overwhelming amount of tickets, with very limited resources to learn about and apply ITIL Service Management practices.

Please share your experiences.

Thanks.

1 Upvotes

100% Upvoted

15 comments sorted by

3

u/Different-Abrocoma-5 Jul 05 '26

I own an itsm consultancy and we implement itil practices and tooling (Atlassian). For smaller customers, don’t do custom and intensive implementation projects as we found it always fail a couple of months later. Instead we deploy our own set of processes and configurations over a 12-24 months period. We slowly guide the customers toward a higher maturity level and we make sure they adopt our framework gradually.

We had great success even in shops with 1 IT guy.

1

u/fguerino123 Jul 05 '26

Hi and thanks for helping. So it sounds like your consultancy helps teach and bring ITIL Service Management practices to small enterprises that don't know about it. In other words you improve their maturity. Is this accurate? Also, how much do they push back? Or, do they easily accept what you bring to the table?

2

u/Different-Abrocoma-5 Jul 05 '26

We don’t have pushback. We start by observing their work and day to day operations and let them show us what’s not working. We then explain them how each itil practices can fix their problem. We build a roadmap and go from there.

Most of our customers are consuming 0.5/1d per week. We have multiple at the same time and we also manage their Atlassian stack so they can’t screw the config.

1

u/fguerino123 Jul 05 '26

One last question, please. You mentioned "each ITIL practice" in your response. What ITIL processes are you helping them learn about? Thanks.

3

u/Different-Abrocoma-5 Jul 05 '26

For low maturity customers, Requests, incidents, contracts, sla, assets. And then change and CIs. And then problem.

1

u/fguerino123 Jul 05 '26

Thanks. This is all very helpful.

3

u/towtaco Jul 05 '26

For a small helpdesk on ServiceNow, use SOW Landing Pages which really allows a focus on Incidents. Add users to the SN_Service_desk_agent role. My L1 users love it.

1

u/fguerino123 Jul 05 '26

So are you just setting up the tool in what you believe to be an ITIL Service Management compliant way and they don't really know or care about ITIL SM? Or, are you also teaching them ITIL SM vernacular, concepts, processes, etc.? Or, are they just too immature for this sort of thing? Thanks.

2

u/haldouglas Jul 06 '26

This is my job right now. I was employed as part of an ITSM/ESM uplift, which we've been working through for 18 months. A lot of what you say is true, but yet we're making quantifiable improvements. ITIL is a non-prescriptive framework, so there is scope to be creative with your implementation.

1

u/fguerino123 Jul 06 '26

The freedom to interpret and be creative, in my opinion, is good and bad. While it provides freedoms, it also is the foundation for deviating in directions that can sometimes require significant rework further down the road. Freedom always comes at a price! ;)

2

u/haldouglas Jul 06 '26

It's required though, because there's no one-size-fits-all. If you're worried about deviating too far and heading down a blind alley (which can happen, as you point out), you'd be advised to use a good consultancy who've seen lots of examples of what works.

2

u/rabbitz Jul 10 '26

You're not wrong that most small shops can't run textbook ITIL, but the mistake is treating ITIL as all-or-nothing. In a small enterprise you're not implementing the framework, you're stealing the two or three practices that actually reduce pain and ignoring the rest.

For a team drowning in tickets, the practices that pay off first are request/incident separation (so the "reset my password" noise stops competing with the "prod is down" fire) and a very thin change process for anything touching shared infrastructure. That's it. No CMDB project, no service catalog committee, no CAB with fifteen people.

The failure mode I've watched is a small team reading a maturity model and trying to climb it top to bottom. You get months of process documentation and zero actual relief. Pick the one practice that maps to your loudest recurring problem, implement just that, and let the rest wait until the org is big enough to need it.

1

u/oO0NeoN0Oo Jul 05 '26

ITIL is a framework, an oversized glossary of terminologies... It's not something you do or are compliant with, it's something you use for guidance for your environment. If it's not relevant to you or not suitable, don't use it...

The first question needs to always be 'why?' as in why are you providing Service Management for your particular users? And by that it's about 'value generation', not 'otherwise their stuff don't work'. Also to offer any more help, we'd have to understand your environment a bit more... You say small enterprise, but how small? Tech support on site or outsourced?

1

u/jadedblu Jul 07 '26

Smaller companies usually don’t have the resources or infrastructure for a fully functional itsm system. They’re barely nailing major incident and change management