Service management deep-dive · LessonBy Praveen T, ServiceNow Trainer, 9 yrs · Published · current release · beginner
Problem management
Find and kill the root cause so the same incidents stop coming back.
Quick answer
Where incidents restore service fast, Problem Management asks why it broke and stops it recurring. It trades speed for permanence, a smaller volume of records, each worth real investigation.
Key takeaways
- Incident vs problem
- Root cause, workaround, known error
- The problem lifecycle (state model)
- Proactive vs reactive
- Common mistakes
Where incidents restore service fast, Problem Management asks why it broke and stops it recurring. It trades speed for permanence, a smaller volume of records, each worth real investigation.
Incident vs problem
Incident
Restore service now. Measured on speed (MTTR). Many of them.
Problem
Find and remove root cause. Measured on prevention. Few, high-value.
Ten incidents about the same outage should map to one problem. The problem record extends task and links the related incidents so the pattern is visible.
Root cause, workaround, known error
The problem lifecycle (state model)
New --> Assess --> Root Cause Analysis --> Fix in Progress --> Resolved --> Closed
(the modern PRB state model; older instances use a simpler flow)
The permanent fix is usually delivered through Change Management, and the workaround is promoted into a knowledge article so it self-serves.
Proactive vs reactive
Reactive problem management responds to an outage that already happened. Proactive problem management mines incident trends and analytics to find brewing issues before they cause a major incident, the more mature discipline.
Common mistakes
- Treating every incident as its own problem instead of grouping.
- Closing problems without a permanent fix or a published workaround.
- No feedback loop, the workaround never reaches front-line agents.
- Only ever reactive, never mining trends proactively.
Practice challenge
+0 XPStreak ×0
Question 1 of 3
A problem record represents:
Frequently asked questions
What does the term Problem management refer to in ServiceNow?
Where incidents restore service fast, Problem Management asks why it broke and stops it recurring. It trades speed for permanence, a smaller volume of records, each worth real investigation.
Which tables and records are involved in Problem management?
The problem record extends task and links the related incidents so the pattern is visible.
What else is worth knowing about Problem management?
Ten incidents about the same outage should map to one problem.
What tends to go wrong with Problem management?
Treating every incident as its own problem instead of grouping. Closing problems without a permanent fix or a published workaround. No feedback loop, the workaround never reaches front-line agents.