Problem Management Roles, Responsibilities and Organizational Structure
Practice roles
This domain tests who does what in problem management and how the practice is organised. ITIL 4 uses practice roles rather than prescribing a single departmental structure.
- Practice owner: accountable for the practice's purpose, performance, maturity and continual improvement.
- Practice manager: manages day-to-day operation - problem records, prioritisation, known error database, reporting, and coordination with incident, change and knowledge management.
- Practice members: problem analysts and technical specialists who perform analysis, define workarounds and propose fixes.
- Service desk: detects patterns, records symptoms and supplies incident context.
- Incident manager: drives restoration and escalates candidates for problem management.
- Change enablement: authorises and schedules fixes; suppliers may own problems in their services.
Organisation may be centralised, with a dedicated problem manager, or federated, with coordinators in technical teams. Whatever the model, accountability for the problem record, the known error database and cross-team follow-up must be explicit. Use a RACI or similar agreement to avoid gaps between service desk, technical teams and suppliers.
Worked example
A problem manager spots a recurring email incident trend. The service desk supplies incident timestamps and symptoms; a messaging specialist analyses the cause; the problem manager records the known error and coordinates a change; the practice owner reviews the backlog and recurrence metric. Reasoning: the problem manager coordinates and owns the record, but does not personally perform every technical analysis.
Traps
Assuming the problem manager must fix every problem; confusing practice owner accountability with incident management; leaving the known error database unowned; allowing technical teams to bypass change enablement; and excluding the service desk from identification.