ITSM · Enterprise Software · Active

Enterprise IT support system

An internal IT ticketing system designed so employees actually raise tickets instead of messaging someone directly.

Role: Architecture and delivery
Category: ITSM · Enterprise Software
Status: Active

The problem

Every IT team has a shadow queue: the requests that arrive by message, in a corridor, or from whoever sits nearest. Those requests get done, but they are invisible — so the team looks less busy than it is, patterns never surface, and nothing can be planned.

Approach

Reduce the friction of the official path until it is lower than the friction of a message. If raising a ticket costs more effort than tapping someone on the shoulder, the shadow queue wins, and no policy fixes that.

What it does

Low-friction ticket creation: The submission path is short enough that using it is easier than not using it, which is the only mechanism that actually works.
Employee-facing design: Built for people who use it three times a year and do not know the IT team's internal categories.
Operational visibility: Once requests arrive through one channel, the team can see load, recurrence and where time actually goes.

The hard parts

Competing with a WhatsApp message: The real competitor is not another ticketing product, it is a two-second message. That sets the usability bar.
Categories that mean nothing to the user: Internal taxonomies make sense to the team that wrote them. Asking an employee to classify their own problem correctly is asking them to already know the answer.

Detail

Client confidentiality

I'm not naming the organisation. I describe it here as an industrial manufacturing organisation in Saudi Arabia.

The measure that matters

Not tickets closed. The proportion of support work that arrived through the system rather than around it — that is the honest adoption metric, and the one I watch to know whether the design worked.

Stack