ESM in practice: service management for HR, facilities and beyond
ESM brings service management to HR, facilities and other departments. Learn how to do it pragmatically without copying IT processes one to one.
What IT has been doing for years with incidents, requests and knowledge is useful for every service department. Registering a new colleague with HR, reporting a broken door to facilities, asking procurement about a contract: it is all service delivery with a request, a resolution and an expectation. Enterprise service management, ESM for short, applies the working method of IT service management to those other departments. This article shows when that makes sense and how to approach it without repeating IT's mistakes.
What ESM is and is not
ESM is not a new tool and not a new framework. It is the idea that structured service delivery is not exclusive to IT. Every department that receives requests, distributes work and returns results benefits from a clear entry point, visible status and reusable knowledge.
What ESM is not: throwing IT's processes over the fence one to one. A change process designed for server management does not fit requesting a parking spot. Anyone who introduces ESM as "everyone must work like IT" gets resistance, and rightly so. The working method is the starting point, not the law.
Why departments themselves benefit
The gain of ESM is not only for the organization as a whole, but precisely for the department itself:
- One entry point instead of full mailboxes. Requests via email and walk-ups get lost or sit untouched. A shared entry point makes work visible and easy to distribute.
- Status without chasing. When the requester can see where their request stands, the "have you heard anything yet" questions that cost everyone time stop.
- Catch repeat questions with knowledge. The questions HR or facilities get every week can live in a knowledge article just as well as IT's can.
- Insight into your own work. Whoever sees which requests come in most often and where they get stuck can improve deliberately instead of guessing.
How to introduce ESM pragmatically
Start with a department that wants to
Do not pick the department that "needs it most", but the department that is genuinely keen. A motivated first department becomes your internal reference. Success sells itself further into the organization.
Start from their services, not from the process
Put the department's services at the center: what can colleagues request here and what may they expect? Build simple handling routes around that. Process names from ITIL are not relevant to the department; a smoothly running request is.
Use what is already there
Most ITSM tools can serve multiple departments perfectly well, each with its own entry point and its own work distribution. A separate tool per department is rarely necessary and actually breaks the shared entry point for employees.
Keep the entry point simple for the employee
For the colleague who needs something, it should not matter whether HR, IT or facilities picks up the request. One portal, clear language, and behind the scenes the work lands with the right team automatically.
What it delivers
Well-introduced ESM gives departments calm and overview: fewer loose emails, less chasing, more grip on their own work. Employees get answers faster because requests no longer wander. And the organization achieves more with the same people, because every department benefits from what service management figured out long ago.
Frequently asked questions
Do other departments have to learn ITIL? No. For them, ITIL is at most inspiration behind the scenes. The department only needs a clear entry point, a way to distribute work and knowledge, in its own language.
Do we need a separate ESM tool? Usually not. Most ITSM tools support multiple departments with their own entry points and permissions. Check what your current tool can do before buying something new.
Where do we start if several departments are interested? With the department that has the most motivation and a manageable set of services. A fast, visible first step works better than three departments at once.
Want to extend service management beyond IT without forcing departments into a straitjacket? book a call and we will look together at which department is best suited for the first step.
Further reading
Want to apply this in your own organization?
Schedule a no-obligation conversation. Together we look at where you stand and what the first step is.
Get in touch