Consulting · ITSM
ITSM
Most mid-market IT runs on people who know things. That works until somebody asks who owns a service, or what changed on the day it broke. [Draft copy]
The problem
Tickets are not the same thing as service management.
There is a ticket queue, and it works, in the sense that things get fixed. What there is not is a list of services with a named owner against each one, a change record that survives contact with an auditor, or a way to tell whether last quarter was better than the one before it.
The knowledge lives in three or four people. When one of them is on leave, resolution time doubles and nobody can say by how much, because nothing is measured against a baseline.
What enterprise-grade looks like here
The difference is ownership you can name.
Enterprise-grade service management is not a heavier process. It is a catalogue where every service has an owner, a change path that records who approved what and when as a by-product of doing the work, and incident and problem handling that are separate activities rather than the same person firefighting twice.
The measure is simple: when an assessor asks what changed in production on a given date, someone can answer in minutes, from a record nobody had to assemble specially.
This framing repeats on every capability page. It is the differentiator, and it reads consistently across all of them (§9 T3).
What we do
Four moves, in this order.
-
Build the service catalogue
Every service, its owner, its dependencies and what the business actually expects of it. Two weeks, and you keep the document either way.
-
Design incident, problem and change to fit how you work
Three processes, not eleven. Sized so people follow them, with approval paths that match your real decision rights.
-
Configure the toolset you already own
We work in your existing service desk rather than selling you another one. Where there is nothing, we will recommend against the enterprise tier.
-
Hand over the cadence
The service review, the change advisory rhythm, and the reporting pack — run by your team, with us in the room until it is theirs.
[Draft copy]
What you end up owning
Documents and configuration, not a dependency.
| Deliverable | Owned by |
|---|---|
| Service catalogue with named owners | IT leadership |
| Incident, problem and change process definitions | Service desk |
| Change record mapped to your audit obligation | Risk & compliance |
| SLA and service-review reporting pack | IT leadership |
| Runbooks and handover training | Operations |
[Draft copy]
Tell us what you are being asked to prove.
Bring the finding or the questionnaire. We will tell you whether service management is actually what is being asked for.
Start a conversation