How should tickets be prioritized?

• A. Safety → Customer/Production impact → Severity/SLA → Dependencies → Effort/skill availability.
• B. Highest revenue impact first
• C. Random order
• D. Only consider ease of completion

Answer: (A)

Prioritization in this context starts with safety. If a ticket involves a condition that could harm people or cause equipment damage, it must be addressed first to prevent harm or incidents. After safety, focus on the impact on customers and production—the work that affects critical services or the largest number of users should come next, because it directly ties to service reliability and business risk. Then assess the severity and the service level agreements in play; tickets with higher severity or tighter SLAs should be resolved sooner to protect commitments and minimize downtime. Next, consider any dependencies—understanding what tasks must be completed before others helps avoid blockers and improves overall workflow. Finally, factor in how long the work will take and whether the necessary skills are available; this helps allocate resources efficiently and prevents wasteful delays.

Choosing instead to maximize revenue impact can ignore safety and reliability, increasing risk of outages. Random or arbitrary ordering lacks structure and can lead to inconsistent outcomes. Focusing only on ease of completion ignores critical issues and dependencies, potentially breaching SLAs and harming service quality.