Chapter 01 · The brief
Five portals. None of them answered the question employees were actually asking.
Three hundred and forty misdirected requests per month. Eighteen minutes each.
A European manufacturing group with 4,200 employees across six sites had accumulated five separate service portals over a decade of departmental IT purchasing decisions: an IT helpdesk (ServiceNow), an HR self-service portal (SuccessFactors), a Facilities request system (home-built), a Finance procurement tool (Coupa), and a Legal intake form (SharePoint).
Employees didn't know which portal to use for which request. A request to add a contractor to site access systems involved IT, HR, Facilities, and sometimes Legal — but each department's portal handled only its slice. Requestors submitted in one place, were redirected to another, and frequently gave up.
The IT service desk was fielding approximately 340 calls per month that were misdirected — requests that landed in the wrong queue and needed manual forwarding. Each misdirected call averaged 18 minutes of handling time before reaching the right team.
Chapter 02 · Build
Process redesign before platform configuration.
The engagement had two phases: process redesign and platform implementation.
Before writing a single line of ServiceNow configuration, we ran a six-week process discovery exercise with each department's service team. The goal was to map what requests actually crossed departmental boundaries, who needed to be involved, and in what sequence. Seventeen cross-departmental request types accounted for 68% of the misdirection volume. The process maps became the configuration specification.
The platform shipped in three layers:
- Catalog architecture. The employee-facing catalog was organized by life event and task type — joining the company, leaving the company, changing role, requesting equipment, reporting a problem. Each catalog item sits above the departmental workflows; the employee sees one form, the platform routes to the right queues in the right sequence.
- Fulfilment workflow automation. Cross-departmental requests use ServiceNow Flow Designer to orchestrate sequential and parallel fulfilment tasks. An on-boarding request triggers IT provisioning, HR record creation, Facilities access card issuance, and an optional Legal NDA workflow in a defined sequence, with dependencies enforced.
- Integration points. The ServiceNow implementation was integrated with Active Directory (automated account provisioning/deprovisioning), SuccessFactors (employee record sync), and the Facilities badge system via a REST API the Facilities vendor built to specification.
Chapter 03 · Outcomes
Employees stopped asking which door to knock on.
Misdirected requests dropped by 61% in the three months following go-live — from 340 per month to approximately 133. The remaining misdirection was concentrated in three catalog items that were redesigned based on post-go-live data.
Employee satisfaction with internal services moved from 4.1 to 4.7 on a five-point scale. The primary driver cited in open-text responses was not speed — it was "knowing where to go."
The IT service desk redirected approximately 90 person-hours per month previously spent handling and forwarding misdirected calls. That capacity was redirected to Level 2 escalation coverage.
Chapter 04 · Stack
Technology stack.
- PlatformServiceNow ESM — single catalog, multi-department fulfilment workflows
- Workflow automationServiceNow Flow Designer — sequential and parallel cross-departmental task orchestration
- Identity integrationActive Directory — automated account provisioning and deprovisioning on role change
- HR syncSuccessFactors employee record sync — single source of truth for headcount and role data
- Facilities integrationREST API to badge access system — automated physical access card issuance tied to IT confirmation