Why organizations implement ESM
The problems IT solved twenty years ago still exist in the rest of the business.
Requests in email inboxes. HR issues, orders, and contract reviews are often handled in personal inboxes, without traceability and without the ability to see how long tasks take.
The employee doesn't know who to turn to. A new hire needs an account from IT, a contract from HR, an access card from facilities, and equipment from procurement—four functions, four points of contact, and no one overseeing the big picture.
No one knows where things get stuck. Without shared tracking, it is impossible to see which part of the chain is causing delays.
What ESM solves in practice
A single entry point for the employee. A portal where all requests are submitted, regardless of which function is handling them. The principles are the same as for a service desk.
Shared processes with individual permissions. The same flow for registration, prioritization, and tracking—but HR only sees their requests, and finance only sees theirs.
Automated workflows across functional boundaries. A new hire can trigger tasks for IT, HR, and facilities simultaneously, with a shared status. See automation.
Traceability where it matters. Which is important for both auditing and GDPR.
Onboarding is the use case that sells itself
If you need an example to start with, it is almost always the hiring process.
A new employee requires accounts and equipment from IT, employment contracts and onboarding from HR, access cards and a workspace from facilities, and the procurement of anything missing. In most organizations, this happens in four parallel tracks held together by someone remembering to send an email.
With a shared workflow, a new hire triggers tasks for all four departments, with a common status that the manager can track. What usually convinces people is not the time saved, but the fact that fewer employees start their first day without a computer.
What every function needs
ESM does not mean that everyone has to work the same way. It means that everyone should work in a structured manner, within the same platform.
HR needs the strictest access control of all. Cases contain sensitive personal data, sometimes about people who did not create the case themselves.
Finance needs approval chains with spending limits and audit-ready traceability.
Facilities needs a connection to locations and premises rather than systems, and often simple mobile reporting for maintenance issues.
Legal needs version control and clear turnaround times, as the cases are often few but long-running.
The most common pitfall
Copying IT processes directly.
IT's priority model is based on impact and operational urgency. An HR case regarding parental leave is neither urgent nor operationally critical, but it has a non-negotiable deadline. The same model does not work for both.
Borrow the structure – registration, categorization, follow-up – but let each function define its own case types, lead times, and terminology. An HR portal that uses the word incident will not be used.
Start small
The most common reason ESM projects stall is trying to take on the entire organization at once.
Instead, choose a function with many recurring cases and clear workflows. Make it work. Let the next function see the results and ask to join in themselves.
There is an organizational reason why this order works best. ESM imposed from above is perceived as something IT has decided for others. ESM that spreads because one department saw that another got their cases in order meets significantly less resistance.
Do you need a new system?
Usually not. Most modern ITSM platforms handle multiple business areas in the same installation, with separate portals, custom case types, and distinct permissions.
It is also the most cost-effective path: you pay for the additional agents, not for a new platform. However, check the licensing model before you start – some vendors price users outside of IT differently.
