Roles, Responsibilities and Organisational Structures
Who does what
ITIL 4 does not prescribe job titles, but the exam expects you to know typical accountabilities and to keep them distinct.
- Service desk manager - accountable for the practice: performance against targets, staffing and rota, budget, escalation point, continual improvement of the desk itself.
- Team leader / supervisor - day-to-day queue management, scheduling, coaching, quality monitoring and real-time reallocation of work.
- Service desk analyst (agent) - first human point of contact: logging, triage, resolution within competence, communication, knowledge capture at the point of contact.
- Adjacent roles - incident manager (owns major incidents and communications), problem manager, knowledge manager, service level manager, fulfilment and technical teams, and increasingly a self-service or virtual-agent product owner.
A RACI or similar model makes accountability explicit; role confusion between service desk manager and incident manager is the classic failure.
Structure options
Centralised - one desk for the whole organisation: consistent, economical, weaker local context. Local/distributed - on-site presence and language fit, risk of inconsistent answers. Virtual - dispersed agents joined by technology. Follow-the-sun - hand-offs across time zones to sustain 24×7. Outsourced/managed - contract-driven, so strong service level management and knowledge transfer are essential. Swarming teams - cross-skilled groups pull work by competence.
Competencies the exam rewards
Clear communication, empathy and emotional intelligence, ownership through to resolution, technical breadth sufficient to triage, disciplined knowledge capture, and awareness of cost and commercial impact.
Worked example
A firm has users in Manila, London and Dallas needing 24×7 coverage with consistent answers. Follow-the-sun across the three regions on one shared queue and knowledge base fits: local desks alone cannot cover nights without overtime, and outsourcing adds governance overhead without solving consistency. Reasoning: choose structure from demand pattern, coverage requirement and consistency risk - not from headcount alone.
Traps
Assuming every organisation needs tiered escalation; describing roles as ITIL-defined functions; confusing the manager's accountability with the incident manager's authority.