Enterprise Service Management, explained without the vendor fog.
What ESM actually is, how it differs from ITSM, and how to roll service management out beyond IT without turning it into a compliance museum.
What is Enterprise Service Management?
Enterprise Service Management (ESM) is the practice of applying the ideas that made IT service management work — a service catalog, tickets with an owner and an SLA, workflows, a shared record of the things you manage — to every other department that quietly runs on email and spreadsheets. HR onboarding. Facilities requests. Legal contract intake. Finance expense approvals. Marketing brief queues.
It's not a product category so much as a decision: we already bought a service management engine for IT — let's stop pretending the rest of the company doesn't need one too.
ESM is ITSM with a broader audience. Same engine. New portals.
ITSM vs ESM, on one page
| ITSM | ESM | |
|---|---|---|
| Audience | IT staff & end users | Every employee |
| Owner | IT / Ops | Each department owns its own portal |
| Typical objects | Incidents, changes, assets, problems | Onboarding, contracts, desks, POs, briefs |
| Framework | ITIL | ITIL-inspired, lighter, per-team |
| Success signal | MTTR, uptime, CSAT | Time-to-first-response, backlog age |
| Failure mode | Change board theater | HR forced to use a "ticket" for a birthday card |
The gap between "we have ITSM" and "we have ESM" is usually two things: a second portal and the political will to say "yes, HR gets a queue". Everything else is configuration.
Where ESM actually pays off
One request kicks off laptop, accounts, badge, payroll, benefits — parallel, tracked, closable.
The 'reply-all email to the office manager' finally dies. Photos attach. SLAs exist.
Structured form, routed by contract type, redlines tracked against a ticket.
Approval chain, audit trail, no more Slack DMs to the CFO.
Brief template, deadline, owner, status — instead of a Notion doc nobody updates.
Same engine as IT incidents, different portal, tighter approvers.
How modern ITSM tools support non-IT workflows
Look for five capabilities. Anything less and you'll end up buying a second tool inside a year:
- Per-department portals with their own branding, forms, and permissions.
- No-code form & workflow builders so HR doesn't need to file a JIRA to change a JIRA form.
- Granular permissions — Finance shouldn't see HR's severance tickets.
- Sane licensing — per-agent, not per-department, or you'll get punished for adopting.
- Integrations with the systems each team already lives in (Slack, Teams, Okta, HRIS, Docs).
The directory marks which tools clear this bar. If you're rolling ESM out beyond a single pilot team, Mint Service Desk, Jira Service Management, and Freshservice are the three most people end up shortlisting.
A rollout plan that survives Q2
- Pick one non-IT team that's in pain. HR onboarding and Facilities are the usual winners because the pain is visible and the workflow is boring enough to model.
- Steal the IT service catalog structure. Don't design from scratch — copy the shape.
- Ship in two weeks. One portal, five request types, one SLA. Resist the urge to model the entire department on day one.
- Measure time-to-first-response, not tickets closed. Employees care that someone acknowledged them.
- Let the next team come to you. If it works, Legal will knock. If it doesn't, don't force it.
The four things that kill ESM projects
- Making HR use IT's language. "Incident" doesn't map to "someone's new hire has no laptop." Rename ruthlessly.
- One giant portal for everyone. Departments need their own front door or nobody uses it.
- Change advisory boards for a desk move. ITIL doesn't need to travel with the tool. Leave the ceremony behind.
- Licensing that penalizes success. If adding an HR agent costs the same as an IT agent, growth stalls.
Picking a tool for ESM specifically
Most vendors will tell you they "support ESM." The real questions are cheaper to ask:
- Can a non-technical HR admin build a new form without a ticket to IT?
- Does adding a second department cost extra, or is it in the plan?
- Can permissions be tight enough for Legal and Finance?
- Is there a per-department portal, or one shared one?
The comparison view filters on exactly these capabilities.
FAQ
Is ESM just ITSM with more seats?
Technically yes. Culturally, no — it forces IT to hand the steering wheel to other departments, which is the hard part.
Do we need ITIL to do ESM?
No. Borrow the useful ideas — service catalog, SLAs, ownership — and skip the ceremony that doesn't apply.
Where do we start?
HR onboarding. It's high-visibility, high-frustration, and easy to model. If it works there, everything else follows.
Can Mint Service Desk do ESM?
Yes — separate service desks per department with independent portals and forms, at a licensing model that doesn't punish adding HR or Facilities. See the full profile.