In short:
- ESM applies to non-IT departments the service management practices born in IT: catalogue, request portal, workflows and measured turnaround times.
- The four functions most often involved are human resources, facilities, finance and legal.
- An ESM initiative is not a tool purchase: it starts with a written service catalogue and its committed turnaround times.
- The ITIL 4 framework describes 34 management practices, a large majority of which apply as-is outside the IT perimeter.
What Enterprise Service Management covers
Enterprise Service Management means applying, across the whole organisation, the service management principles formalised in IT since the 1990s. The reasoning is straightforward: a badge request sent to facilities and a password reset sent to IT raise exactly the same organisational problem. Who receives it, within what deadline, following which procedure, and how does the requester track progress.
An extension of practices born in IT
IT structured those answers first, because it was the first function to absorb a volume of requests that email could no longer handle. The service catalogue, the ticket, the priority level and the committed turnaround time are inventions of the IT service desk. ESM observes that nothing in those objects is specifically technical.
Departments involved beyond IT
| Department | Catalogued service | Typical request |
|---|---|---|
| Human resources | New joiner onboarding | Account creation and workstation setup |
| Facilities | Premises management | Room booking, air conditioning fault |
| Finance | Expense claim processing | Approval of an out-of-policy expense |
| Legal | Contract review | Review of a non-disclosure agreement |
Onboarding a new employee illustrates the value of the approach: it simultaneously involves HR, IT, facilities and sometimes finance. As long as each department handles its part in its own channel, nobody knows where the case stands.
What separates an ESM initiative from a tool
Three elements separate a genuine ESM initiative from a software rollout:
- A written service catalogue naming every service delivered and its owner
- Turnaround commitments owned by the department delivering the service, not imposed by the tool
- Shared measurement, visible to requesters and delivery teams alike
The rest is configuration. This is also why the differences between ESM and ITSM are organisational rather than technical.
Where to start
- Pick a single willing department, ideally the one facing the most informal requests
- Write its service catalogue, limited to the ten most frequent requests
- Open a single intake channel, before discussing automation at all
Platform selection comes afterwards, once the scope has settled. The criteria are covered in our ITSM platform selection grid, and first-line organisation in our article on the service desk.
Frequently asked questions
What is Enterprise Service Management?
Enterprise Service Management, or ESM, means applying to non-IT departments the service management practices that originated in IT: a formalised service catalogue, a single request portal, handling workflows and measured turnaround times. Human resources, facilities, finance and legal are the most frequent beneficiaries. The approach rests on method before it rests on tooling: without a written service catalogue, an ESM platform merely relocates the mess.
What is the difference between ESM and ITSM?
ITSM covers the services delivered by the IT department. ESM applies the same principles to every support function in the organisation. Technically, both often run on the same platform and the same workflow engine.
Do you need a dedicated tool to start with ESM?
Not necessarily. Most ITSM platforms already handle several service catalogues and several handling queues, which is enough to cover a first non-IT scope.