Skip to main content

Problem management

Problem management looks for the root cause of recurring incidents, to eliminate them instead of fixing them again and again.

Updated on 14 November 2026

Definition of problem management

Problem management is the practice that looks for the root cause of incidents, especially recurring ones, to eliminate them for good. Where incident management puts out the fire, problem management looks for why it keeps flaring up.

ITIL distinguishes three stages: identify the problem, analyse it down to its cause, then fix it or, in the meantime, document a workaround (a "known error").

LongLife provides the raw material for this analysis on devices: the history of each machine and a view of the whole fleet, by model, site or department.

A real-world example

In one month, an SME's support team handles 14 blue screens. Taken one by one, each case is fixed by a restart. In LongLife, the fleet view shows that 11 of these blue screens affect the same laptop model, all with the same graphics driver. The problem is identified: the driver is updated on that model, and the blue screens disappear.

Incident, problem, change

ConceptQuestionWhat LongLife gives you
IncidentWhat is wrong right now?Continuous detection, recommended action, priority
ProblemWhy does it keep coming back?History of incidents and blue screens per device, grouping by model and site
ChangeHow do we fix it without breaking anything?See the devices concerned, signed scripts, report for each device
DecisionShould we keep this hardware?Keep, upgrade or replace, with the cost and CO₂e

Count a device's crashes

To see whether a device crashes often, count in its System log the blue screens and unexpected shutdowns over the last 30 days. One figure on one device says nothing. The same figure on 30 devices of the same model is a problem. That is the cross-check LongLife does for you.

LongLife, to find the cause and decide

  • Complete history of each device: incidents, blue screens, component condition, work recorded in the health log;
  • fleet view by model, site, department or group, to spot what keeps recurring;
  • DEX score, which measures the effect of crashes on users;
  • a costed decision when the cause is hardware: upgrade the part (memory, disk, battery) or replace, with the cost and CO₂e;
  • remote fix through a catalogue of signed scripts, written and tested by OPP!, that grows with every update, and possible repair at the OPP! workshop in Nantes.

Fewer repeated incidents, less time lost, better-targeted purchases. The free plan covers up to 15 devices. Book a meeting to analyse your fleet, or start with the simulator.

Sources

Frequently asked questions

What is problem management in IT?

It is the ITIL practice that identifies the root cause of one or more incidents and deals with it for good, so that the incidents do not happen again.

What is a known error?

It is a problem whose cause has been identified but not yet fixed, with a documented workaround. It allows the next incidents to be resolved quickly while waiting for the permanent fix.

How can recurring problems be spotted across a device fleet?

By grouping incidents by model, site or software. LongLife does this from each device's data: blue screens, detected incidents, component condition, which brings out the common causes.

Is problem management useful for an SME?

Yes, in a simple form. Noticing that the same laptop model racks up battery failures or blue screens saves dozens of interventions and guides purchasing.

Read also

See the real state of your fleet

LongLife measures the health of your Windows devices every day and recommends keeping, upgrading or replacing them, with the cost and CO₂e of each option.