Prioritization Frameworks

Every ticket arrives marked Urgent by someone. The requester picked it because the form offered it. The manager picked it because the requester is in their team, and the technician left it because changing it felt like an argument. By lunchtime the queue has fourteen Urgent tickets. One is a payroll server that will not start and thirteen are not. The only way to tell them apart is to open each one. A priority that everyone has is a priority that nobody has. The tool did not do that. The absence of a written rule did.

This series is about the rule. It covers impact and urgency as two separate questions and how to combine them in the moment. It does so without redesigning the SLA tiers that another series owns. It covers who decides a priority and how to change a requester's choice with one courteous sentence. It covers the user for whom everything is urgent, handled with sympathy for why. Then comes why priority is not the order of work, and how to sequence inside a priority. It covers making business impact visible with an impact register, so Urgent means something you can point at. And it covers the one-page prioritization policy you can write this afternoon. The grid takes ten minutes. The sentence that lets a trainee lower a director's priority takes longer, and it is the one that matters.

Articles in This Series

• Impact Times Urgency in Practice
  Impact and urgency defined in plain words, the three-by-three grid and how its cells map to five named priorities, six worked examples, and the grid with definitions to copy.
• Who Decides the Priority of a Ticket
  The requester proposes, the desk decides, the manager arbitrates; changing a self-selected priority in one courteous sentence; recording overrides; and the priority-change reply.
• The User for Whom Everything Is Urgent
  Why it happens, the consistent response, the honest conversation, when their manager should hear it, and a joke-free script for the conversation.
• Priority Is Not the Order of Work
  Sequencing inside a priority by clock, age, quick wins and the ticket that unblocks three others; the daily pick order; Low tickets that starve; and a work-order rule set.
• Making Business Impact Visible
  The critical process list, the how-many-are-blocked count, the calendar of month-end and payroll day, VIPs without a shadow SLA, and an impact register to fill in.
• A Prioritization Policy You Can Write Down
  The one-page policy: definitions, examples per priority, who may change it, the review, what to do when the rule is wrong, how to announce it, and the policy page itself.

Explore More Topics

This series is part of the QuerySolv helpdesk topic library. It covers the foundations, processes, communication, knowledge, tooling, metrics, classic ticket domains, people and strategy behind a support desk that works. The library pairs well with the software we build: QuerySolv. It is a self-hosted help desk that runs as one Windows service on your own network. It is licensed once per installation, not per agent per month.