‹ All essays

ServiceNow

ITSM Made Easy: How ServiceNow Standardizes Support at Enterprise Scale

What is ITSM?

ITSM (IT Service Management) is the discipline of delivering and improving IT services using standardized processes.

In ServiceNow, ITSM usually means workflows like Incident, Request, Problem, and Change.

I have seen too many implementations where teams treat ITSM as a ticketing tool and then wonder why operational maturity never improves. The process design matters more than the tool.

The Core Tables

Every ITSM process maps to a real table in the platform:

  • incident — break/fix records
  • sc_request / sc_req_item — service requests and catalog items
  • problem — root cause investigations
  • change_request — planned changes with risk assessment

All four extend the base task table, which means they share common fields like number, state, assigned_to, and priority.

The 4 Building Blocks (Simple View)

PracticeMain GoalTypical Question
IncidentRestore service quickly"How fast can we recover?"
RequestFulfill standard needs"How do we deliver access/device/software?"
ProblemRemove root cause"Why does this keep happening?"
ChangeReduce release risk"How do we change safely?"

Example Scenario: SAP Outage Weekend

Picture how the four practices divide the work after an SAP outage: the incident team restores service fast, the problem team digs into why (a recurring DB patch conflict), and the change team introduces a staged rollout with pre-check gates so the patch cannot break production again.

Outcome: fewer repeat outages and safer monthly release windows.

Why ITSM Programs Fail

  • Tool-first implementation without process ownership.
  • Too many mandatory fields with no operational value.
  • No clear SLAs/OLAs and no queue hygiene.

What Good ITSM Feels Like

  • Users know where to request help.
  • Support teams triage consistently.
  • Changes are assessed for impact and timing.
  • Recurring incidents trigger root-cause work.

Practical Rollout Tip

Start with incident + request standardization, then layer in problem and change maturity once data quality stabilizes.