What it is (plain English)
Where Incident Management fixes the symptom, Problem Management finds and eliminates the cause. When the same thing keeps breaking, a "problem" record tracks the investigation into why, documents the temporary workaround so every technician knows it, and drives a permanent fix.
Problems it solves
- The same incident keeps coming back and each time someone re-solves it from scratch.
- "I've had this issue for weeks, it keeps happening, and nobody fixes it for good."
- Known workarounds live in one technician's head instead of being available to everyone.
- IT is permanently firefighting with no mechanism to reduce the fires.
What must exist first
Platform Core Setup is the only hard prerequisite. In practice, Incident Management is a strong recommended precursor — problems are usually detected from incident patterns and linked back to the incidents they explain — but Problem Management can stand up without Incident being live if you're driving proactive detection. A maturing CMDB sharpens root-cause analysis considerably.
What the customer needs to provide
- A problem manager (or at least a named owner) — this process runs on analytical skill and accountability more than tooling.
- Willingness to dedicate time to investigation work that isn't tied to an open outage — this is the cultural hurdle where problem management usually fails.
- Your top recurring pain points to seed the first problem investigations.
- Agreement on when an incident pattern deserves a problem record (thresholds, triggers).
Where it can go next
Permanent fixes almost always mean changing something — Change Management gives those fixes a safe path to production. Trend analysis matures into proactive problem detection using platform reporting.