Backlog Recovery
Nobody decides to have four hundred open tickets. The desk closed thirty-one a day for a year and received thirty-four. The difference, three a day, was nobody's fault and nobody's job. It became a mountain with a view. By the time anyone counts, the oldest ticket is older than the newest technician. Half the requesters have already left or solved it themselves. The number is embarrassing enough that the report has quietly stopped including it. A backlog is not a pile of work. It is a pile of unanswered promises, most of them small, all of them aging.
This series is about getting out and staying out. It covers how a ticket mountain forms and how to measure it, by count, by age and by oldest. It covers taking stock before you dig, so the plan is built on the real shape of the pile. Then comes the two-week dig-out plan with protected time and a daily target. It covers declaring ticket bankruptcy carefully: when it is justified and how to do it without burning trust. It covers keeping the backlog from rebuilding, which is the part everyone skips. And it covers explaining the backlog to management in one page with the numbers that matter. Digging out is a fortnight. Staying out is a habit, and this series spends more time on the habit.
Articles in This Series
- How a Ticket Mountain Forms, One Quiet Week at a Time
Inflow greater than outflow for long enough, the quiet accumulation, the aging curve, measuring by count, age distribution and oldest ticket, and a backlog measurement sheet. - Taking Stock Before You Dig: The Backlog Inventory
The inventory by age, status, category and assignee; triaging the backlog itself; the honest number to management before the plan; and the inventory table. - The Dig-Out Plan: Two Weeks From a Ticket Mountain to Daylight
Blocks of protected time, the order of attack, the daily target, the burn-down, and a two-week plan to copy. - Declaring Ticket Bankruptcy Carefully, Without Burning Trust
What it is, when it is justified, the message, the invitation to re-raise, what never to bankrupt, and the announcement text. - Keeping the Backlog From Rebuilding After the Dig-Out
Inflow control, closing discipline, the weekly aging check, the capacity truth, the early warning, and a weekly health check. - Explaining the Backlog to Management in One Honest Page
The numbers that matter, what caused it, what you need, and the one-page backlog brief.
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.