9.2 Prioritizing Work & Managing Queues

ITIL 4 Specialist: Create, Deliver and Support Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Structure & Service Value Stream Fundamentals

1.1 CDS Exam Structure, Format & Certification Strategy 1.2 The Service Value System & Value Stream Architecture 1.3 Value Stream Mapping & Flow Metrics

2 Chapter 2: Organizational Structures & Team Culture

2.1 Organizational Structures & Team Models 2.2 Collaborative Culture & Positive Communication 2.3 Workforce Planning & Competency Models

3 Chapter 3: Integrated Information & Modern Technology

3.1 Information Models & Integrated Toolsets 3.2 Analytics, Collaboration & Work Visibility 3.3 Automation, RPA, AI/ML & CI/CD Pipelines

4 Chapter 4: Value Stream for Designing & Transitioning New Services

4.1 Anatomy of the New-Service Value Stream 4.2 Designing & Architecting Value Streams 4.3 Transition, Validation & Testing in Value Streams

5 Chapter 5: Practices for New-Service Creation

5.1 Service Design & Software Development Management 5.2 Deployment Management & Release Management 5.3 Service Validation, Testing & Change Enablement

6 Chapter 6: Value Stream for User Support

6.1 Anatomy of the User-Support Value Stream 6.2 Shift-Left Strategy in User Support 6.3 Multi-Tier Support vs. Swarming

7 Chapter 7: Practices for User Support & Restoration

7.1 Service Desk & Incident Management 7.2 Problem Management & Known Error Database 7.3 Knowledge Management & Service Level Management

8 Chapter 8: Monitoring, Event Management & Continual Improvement

8.1 Monitoring and Event Management Practice 8.2 Continual Improvement Models & Waste Elimination 8.3 Metrics, Reporting & Value Stream Telemetry

9 Chapter 9: Managing & Structuring Work

9.1 Managing Work as Tickets 9.2 Prioritizing Work & Managing Queues 9.3 Managing Backlogs & Work Bottlenecks

10 Chapter 10: Sourcing, Buy-vs-Build & Service Integration (SIAM)

10.1 Sourcing Models & Commercial Considerations 10.2 Buy vs. Build Decision Framework 10.3 Service Integration and Management (SIAM)

9.2 Prioritizing Work & Managing Queues

Key Takeaways Explain This Topic AI

Prioritization in ITIL CDS balances scarce operational capacity against demand by evaluating business Impact (harm/value scope) alongside Urgency (time sensitivity).

While FIFO is administratively simple, high-velocity environments rely on advanced models: Shortest Job First (SJF), Cost of Delay (CoD), and Weighted Shortest Job First (WSJF) to maximize business value.

Queuing theory demonstrates that operating near 100% resource utilization triggers exponential increases in wait times, necessitating intentional 15-20% buffer capacity.

Multitasking inflicts severe cognitive context-switching penalties, whereas Work-in-Progress (WIP) limits governed by Little's Law (Lead Time = WIP / Throughput) systematically collapse lead times.

Uncapped WIP leads directly to ticket gridlock, where all items are marked 'in progress' but cycle times expand toward infinity.

Last updated: September 2026

9.2 Prioritizing Work & Managing Queues

Quick Summary: Prioritizing work and managing queues is critical to sustaining flow in ITIL 4 Create, Deliver and Support (CDS). Balancing scarce capacity against operational demand requires moving beyond simplistic First-In, First-Out (FIFO) queues. Combining the classic Impact-Urgency matrix with economic models like Cost of Delay (CoD) and Weighted Shortest Job First (WSJF), applying queuing theory, and enforcing Work-in-Progress (WIP) limits governed by Little's Law prevents ticket gridlock and collapses lead times.

In technology operations, demand routinely outstrips engineering capacity. Without deliberate prioritization, teams default to chaotic execution: the loudest stakeholder gets serviced first, invisible backlogs swell, and wait times expand. ITIL 4 CDS provides rigorous frameworks to evaluate competing work and optimize queue dynamics.

The Classic Impact x Urgency Prioritization Matrix

The foundational model for operational prioritization evaluates two distinct demand dimensions:

Impact: Objective measure of business detriment or value disruption. Impact reflects the scope of operational damage, such as affected users, financial loss per hour, regulatory exposure, brand damage, or disruption of core transactions.

Urgency: Time sensitivity of the issue. Urgency reflects how rapidly impact escalates if unaddressed, or the presence of an imminent deadline (e.g., payroll processing, market opening, regulatory reporting).

Priority is derived as a function of both variables (Priority = Impact × Urgency):

Impact vs. Urgency High Urgency (Immediate Action) Medium Urgency (Time-Sensitive) Low Urgency (Standard Window)

High Impact (Enterprise / Critical) Priority 1 (Critical / Major Incident) Priority 2 (High) Priority 3 (Medium)

Medium Impact (Departmental / Degraded) Priority 2 (High) Priority 3 (Medium) Priority 4 (Low)
Low Impact (Single User / Workaround) Priority 3 (Medium) Priority 4 (Low) Priority 5 (Planning / Minor)
Disentangling Emotion from Objective Priority

A key exam challenge involves differentiating customer distress from business impact. An executive unable to print a presentation exhibits high personal urgency, but business impact is low. Conversely, a silent batch corruption job affecting financial ledgers exhibits critical impact despite zero initial complaints. CDS practitioners must objectively evaluate both criteria before setting priority.

Alternative and Complementary Prioritization Models

Beyond incident management, modern service delivery leverages broader economic prioritization techniques:

First-In, First-Out (FIFO): Servicing items in arrival order. While simple, FIFO is hazardous in heterogeneous environments because trivial inquiries block high-impact enterprise issues.

Shortest Job First (SJF): Processing lowest-effort work first. SJF reduces queue length quickly, but risks starving complex, high-value tasks.

Cost of Delay (CoD): An economic framework quantifying money and business value lost per unit of time if work is delayed, combining user value, time criticality, and risk reduction.

Weighted Shortest Job First (WSJF): Originating in Lean/Agile and integrated into CDS, WSJF calculates optimal work sequence by dividing Cost of Delay by job duration: WSJF = Cost of Delay (CoD) / Job Duration (or Size)

Prioritizing items with the highest WSJF score mathematically guarantees maximum economic return per unit of team capacity.

Dynamic Triage: Fluid reassessment of incoming tickets by a multidisciplinary team during demand surges, rapidly re-routing low-priority work to self-service.

Queuing Theory in IT Service Management

Queuing theory mathematically models work behavior while waiting for capacity:

Arrival Rate vs. Service Rate: If arrival rate exceeds service rate over time, queue length expands infinitely.

The Cost of High Utilization (Kingman's Formula): When team utilization exceeds 80%, wait times escalate exponentially rather than linearly. A team operating at 98% utilization suffers queue times up to ten times longer than at 80%. Maintaining responsiveness requires preserving 15% to 20% buffer capacity (slack).

Batch Sizing: Large batches create severe queue spikes. Small batch sizes smooth delivery cadence and reduce average wait times.

Work-in-Progress (WIP) Limits and Little's Law

Managing Work-in-Progress (WIP) —the number of items active within the value stream—is a central operational discipline in ITIL 4 CDS. High WIP: [T1][T2][T3][T4][T5][T6][T7][T8][T9][T10] ──> Multitasking Chaos ──> High Lead Time

WIP Limit=3: [T1][T2][T3] ──> Focused Collaboration ──> Rapid Completion ──> Short Lead Time
The Cost of Context Switching

Multitasking degrades cognitive output. Gerald Weinberg's research reveals:

Managing 2 concurrent tasks consumes 20% of productive time in switching overhead.

Managing 3 concurrent tasks consumes 40% in context switching.

Managing 5 concurrent tasks wastes 75% of cognitive capacity simply switching mental states.

Little's Law: Mathematical Formulation

Proven by John Little in 1961, Little's Law governs any stable queuing system: Lead Time = Work in Progress (WIP) / Throughput (Completion Rate)

Throughput = Work in Progress (WIP) / Lead Time
WIP = Throughput × Lead Time
Calculation Walkthrough

Consider a support team with a steady completion rate of 5 tickets per day :

Scenario A (Unrestricted WIP): The team has 50 active tickets in progress.

Lead Time = 50 tickets / 5 tickets/day = 10 days .

Scenario B (Strict WIP Limits): The team caps active work at 10 tickets . Throughput remains 5 tickets per day.

Lead Time = 10 tickets / 5 tickets/day = 2 days .

Capping WIP yields an 80% lead time reduction without hiring staff.

Ticket Gridlock

When teams fail to cap WIP, ticket gridlock occurs: every technician has 20 active tickets, spending their days writing status reports and context-switching. Throughput plummets, lead times explode, and flow halts.

Critical Exam Traps & Practical Takeaways

Warning
Exam Trap: Equating 100% Resource Utilization with Efficiency

Running operational teams at 100% utilization guarantees catastrophic queue expansion and SLA breaches. High-performing teams protect buffer capacity to absorb demand spikes.

Tip
Practical Rule: 'Stop Starting, Start Finishing'

When queues swell, the natural instinct is starting more tickets. ITIL 4 CDS enforces the Lean rule: Stop starting, start finishing . Restricting WIP forces teams to complete active work before pulling new demand.