What Is Enterprise Service Management?
Enterprise Service Management (ESM) means applying service management principles and tools beyond IT to every business area of an organisation. The idea: if structured processes, self-service portals and automation work for IT requests, why not for HR requests, facility requests or legal reviews too?
In Team Topologies, Matthew Skelton and Manuel Pais describe four fundamental team types, including the “platform team” – a team that provides internal services to enable other teams. ESM makes this concept concrete: every department becomes a service platform.
"A platform team's purpose is to enable stream-aligned teams to deliver work with substantial autonomy."
— Matthew Skelton & Manuel Pais, Team Topologies (2019)
Why ESM Is Becoming Relevant Now
The Silo Problem
In most companies, every department has its own processes, tools and communication channels. HR uses an HR portal, Finance has an ERP front end, Legal works with email and SharePoint. The result: employees need to know where to request what – and regularly fail at it.
In Thinking in Systems, Donella Meadows describes how subsystems that are optimised independently of each other can make the overall system worse. ESM solves this problem by putting one shared service layer across all departments.
The Employee Experience Factor
McKinsey, Gartner and Forrester have stressed it for years: employee experience is a strategic factor. Employees who search in frustration for the right form or wait days for an answer are less productive and less engaged. ESM creates one consistent, intuitive experience.
ESM with Jira Service Management: The Architecture
One Portal, Many Services
JSM lets you run different service desks under one roof. Employees see a single portal with categories:
- 🖥️ IT Support
- 👥 HR & People
- 🏢 Facility & Workplace
- ⚖️ Legal & Compliance
- 💰 Finance & Procurement
- 📋 Onboarding & Offboarding
Department-Specific Workflows
Every department gets its own workflows, SLAs and automations. HR requests go through different steps than IT incidents – but both run on the same platform with shared reporting.
Cross-Functional Processes
The real value of ESM shows in cross-department processes. Take onboarding: a new employee automatically triggers requests in IT (laptop, accounts), HR (contract, benefits), Facility (desk, badge) and Finance (cost centre) – coordinated by a single onboarding workflow.
ESM Implementation: The XALT Approach
Start Small, Think Big
We recommend not setting up ESM as a big-bang project. The proven approach from Lean Enterprise by Humble, Molesky and O'Reilly: start with one department, learn, scale.
- Pilot: One department (often HR or Facility) that is ready for it
- Validate: Measure the results (ticket volume, resolution time, satisfaction)
- Scale: Carry the lessons over to other departments
- Optimize: Establish cross-functional workflows
Building Governance
ESM needs governance: who defines the service catalogues? Who sets SLAs? Who maintains the knowledge base? Without clear ownership, ESM quickly gets watered down.
Further Reading
- Skelton, M., Pais, M. (2019): Team Topologies. IT Revolution Press.
- Meadows, D. (2008): Thinking in Systems. Chelsea Green Publishing.
- Humble, J., Molesky, J., O'Reilly, B. (2015): Lean Enterprise. O'Reilly Media.
- AXELOS (2019): ITIL 4 Foundation. TSO.
