IT Service & Operations · IT Service Management (ITSM)

Change Management

Implementation path

Prepare firstCMDB Foundation Incident Management

● This moduleChange Management

Works well withDiscovery Problem Management Vulnerability Response (VR)

Capability comparison

Incident Management and Change Management

Incident Management restores service fast and minimizes business impact. Change Management controls the lifecycle of production changes so fixes don't cause the next outage.

Incident Management provides

Structured intake, prioritization, and routing of incidents from any channel
Workflow and automation for diagnosis, investigation, escalation, and resolution
Service-level tracking, dashboards, and reporting on incident resolution performance
Knowledge search and reusable resolution guidance that helps agents resolve repeat issues consistently
Self-service, agent workspace, and communication tools that keep requesters informed through restoration

Change Management provides

Systematic change lifecycle control with risk assessment, approval, and scheduling
Change Advisory Board (CAB) Workbench for planning and managing CAB meetings
Conflict detection and blackout windows to prevent overlapping or risky changes
Service Maps integration showing change impact on business services at a glance
Change approval policies that balance governance with DevOps velocity
Automated change-task orchestration, notifications, and approval routing that support controlled execution

Consider it when

The IT team already handles incidents well but changes are ad hoc, high-risk, or cause their own incidents.
Leadership wants formal change governance, audit trails, CAB reviews, or risk-based approval before production changes.
DevOps teams need change policies that accelerate approved standard changes without blocking velocity.
Do not treat Change Management as a prerequisite for Incident Management - adopt it when the volume and risk of production changes demands systematic control.

Where the capabilities overlap

Both are core ITSM processes sharing the same platform, CMDB, and CI context - an incident may trigger a change, and a change may cause an incident.
Both can feed and consume data from the same operational sources, but Incident Management is about restoring service now while Change Management is about controlling what is deployed next.

Sources

Incident Management ↗Change Management ↗IT Service Management ↗

Incident Management and Change Management can be adopted independently. The sequence shown is practical implementation guidance, not an installation prerequisite.

What it is (plain English)

A controlled way to modify anything that could impact an IT service - updating a server, deploying an application, swapping network gear. Each change gets assessed for risk, approved by the right people, scheduled to avoid collisions, and reviewed afterward. The goal isn't bureaucracy; it's making beneficial changes with minimum disruption.

Problems it solves

Outages caused by changes nobody knew about or assessed.
Two teams changing related systems at the same time and breaking each other.
No record of what changed when something starts misbehaving ("what changed last night?").
Approvals happening in email threads with no audit trail.

What must exist first

Define change models, ownership, approvals, risk rules, schedules, and governance. CMDB Foundation improves CI-based risk and impact assessment when reliable CI context is available, but it is not a universal product prerequisite for using Change Management.

What the customer needs to provide

Your current approval reality: who signs off on changes today, however informal - and who should.
Risk appetite decisions: which kinds of changes are routine enough to pre-approve (standard changes) vs. needing review.
Maintenance windows and blackout periods that matter to the business (month-end close, retail seasons).
Whether a Change Advisory Board (CAB) exists or is wanted, and who sits on it.
For dev teams: which deployment pipelines/tools should raise changes automatically.

Where it can go next

DevOps Change Velocity automates change records from CI/CD pipelines so developer changes flow through governance without slowing down. Change success rates feed back into Problem Management when changes cause incidents.