When an Incident Should Become a Problem Record

An incident should become a problem record when deeper investigation or coordinated prevention is needed beyond restoring that single incident. Problem management turns recurring pain and risk into investigation, known errors and preventive action.

• Set risk and recurrence triggers rather than relying only on incident count thresholds.
• Consider aggregate impact. In the article's example, three moderate incidents with the same signature trigger a problem because the trend indicates increasing business exposure.
• Capture links to related incidents and assign investigative ownership. Creating problem records with no capacity to investigate is a pitfall, as is waiting for a crisis.
• Measure incident-to-problem conversion quality, linked incident coverage and repeat occurrence as a set, with agreed baselines, data sources and owners. After the first cycle, ask whether repeat occurrence moved for the intended reason and whether any group experienced a worse result.
• Treat the approach as an evidence-led learning loop: establish the current position, make a controlled change, inspect the result and keep only what improves value, flow, resilience or experience. Problem management needs evidence and persistence beyond the first plausible explanation.