ITIL in plain language: incident, problem, change and request.

ITIL is a widely used set of practices for running IT services. You do not need the whole framework, but four words explain most of it.

Incident

Something is broken or degraded: email is down, a camera is offline. The goal is to restore service fast. Incidents are given a priority based on business impact and handled to a response and resolution target.

Problem

The underlying cause behind one or more incidents. If the same printer fails every Monday, the incident is “printer down” and the problem is “why”. Problem management looks for patterns and removes the cause.

Change

Any planned modification to the environment: a firmware update, a new firewall rule, a server migration. Changes are assessed for risk, scheduled, tested, approved and recorded, with a way back if they fail.

Service request

A routine, expected ask: a new user account, a laptop set-up, access to a folder. These follow a standard procedure and do not need an emergency response.

Why it matters to you

When these four are separated, support becomes measurable. You can see how many incidents recurred, how many changes failed, and how long requests take. When they are mixed together, every call is an emergency and nothing improves.

A good support contract names them, sets targets for each, and reports on them monthly.