Enterprise Service Management (ESM) — the extension of IT service management principles to HR, Facilities, Finance, Legal, and other business functions — was gaining traction before hybrid work became the default. The transition to distributed work accelerated the need significantly. The informal channels that resolved most employee service requests had geography as a dependency. When geography changed, those channels broke.
What changed with hybrid work
In an office-centric environment, many service requests resolved through informal interaction. Walk over to IT, ask someone in HR, flag a facilities issue in person. These informal channels were largely invisible to service management systems — no ticket, no SLA, no documentation — but they were real and often faster than the formal process.
Hybrid work eliminated those channels. Requests that previously resolved through a two-minute conversation now needed a system. The volume of formal service requests increased significantly — in organisations we work with, the increase in the first year of hybrid work ranged from 30 to 80 percent, depending on how informal the previous culture had been.
The expectation of response time also shifted. Employees whose consumer digital experience includes same-hour response on service requests did not accommodate the lag of email-based service processes. The contrast between the consumer experience and the enterprise service experience — always visible in an office environment — became untenable in a hybrid one.
What ServiceNow ESM provides
ServiceNow's ESM capability extends the IT service management platform to cover multiple functions through a single employee intake experience. The employee submits a request through a unified portal — one front door regardless of whether the need is IT, HR, Facilities, Finance, or Legal. The platform routes the request to the appropriate function, applies the relevant SLA, tracks progress, and produces a documented resolution.
The key capabilities in a hybrid context:
- Employee visibility: Employees can see the status of their request without following up by email. This alone reduces inbound queries by 30 to 40 percent in most implementations.
- Function manager visibility: HR, IT, and Facilities managers can see queue depth, SLA compliance, and trend data — replacing the informal situational awareness that office proximity provided.
- Cross-function requests: Many real-world employee situations involve multiple functions. A new hire requires IT provisioning, HR onboarding, and Facilities access. ESM allows these to be tracked as related requests with dependencies, rather than three separate processes with no coordination.
- Knowledge deflection: ServiceNow's knowledge management integration routes employees to existing answers before a ticket is created — reducing ticket volume for common, answerable questions.
Where ESM implementations fail
Most ESM implementations that underperform do so for the same reason: the technology is deployed before the process design is complete.
The failure pattern is predictable. IT drives the ServiceNow implementation. HR and Facilities are brought in late, with insufficient time to define their service catalogue, agree on SLAs, or train their teams. The system launches with IT fully on board and other functions with partial, inconsistent participation. The single front door becomes a front door that works well for IT and poorly for everything else. Employee adoption is mixed. The business case is partially realised at best.
The organisational questions that need to be answered before implementation — not during — include:
- Who governs the platform? ServiceNow ESM is not an IT tool used by other functions. It is a shared enterprise platform. Governance needs to reflect that — which typically means a cross-functional steering group and a platform owner who is not exclusively from IT.
- What does each function's service catalogue look like? HR, Facilities, Finance, and Legal all need to define their services, request types, SLAs, and routing rules before go-live. This is weeks of process design work.
- How will data definitions be agreed? "Employee" means something specific to HR, something different to IT, and something different again to Finance. Shared definitions are a prerequisite for cross-function routing to work correctly.
The implementation reality
The organisations that succeed with ServiceNow ESM treat the implementation as a service redesign project that happens to require technology — not a technology project that affects service. The distinction changes where the effort goes.
In a technology project, the focus is on configuration, integration, and go-live. In a service redesign project, the focus is on process mapping, SLA definition, exception handling, and the organisational agreements that make the technology worth configuring. The technology is the easier part.
Practically: allow as much time for process design and function alignment as for technical implementation. Implement functions sequentially if cross-functional agreement is not achievable upfront — IT first, then HR, then Facilities — rather than launching a partially-configured multi-function system at once. Measure success by employee experience and SLA compliance, not by ticket volume or implementation timeline.