PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchIn a September 2026 account, Serguey Shinder says his team reviewed 412 escalations and found that about two-thirds did not need an engineer. The cases were not evidence that escalation is usually wasteful: Shinder says about 130 genuinely needed senior support. The avoidable cases, in his account, pointed instead to permissions first-line staff lacked, fixes that were never documented, and tickets sent to the wrong queue. Read Shinder’s account on DEV Community.
What the two-thirds figure describes
The figure is Shinder’s report about one team’s review of 412 escalations from one month. It is not a cross-company benchmark or an independently validated study. The post does not detail how cases were selected or classified, whether categories overlapped, or how outcomes were measured. Its rounded counts are best read as the author’s account of what the team found, not as precise estimates for other service desks.
![Computer Networking Bible: [3 in 1] The Complete Crash Course to Effectively Design, Implement and Manage Networks. Including Sections on Security, Performance and Scalability](https://m.media-amazon.com/images/I/41H4YJnxKgL._SL160_.jpg)
As an Amazon Associate I earn from qualifying purchases.
Shinder’s central distinction is between work that required engineering judgment and work that was escalated because the organization had not equipped first line to handle it. He summarized the pattern this way: “About two thirds of them did not need an engineer. They needed a permission or a paragraph.”
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteWhat was behind the avoidable escalations
Routine actions were restricted
Shinder says 148 requests concerned four tasks first-line staff were not allowed to perform: adding someone to a distribution group, releasing a quarantined message, resetting a second-factor enrollment, or restoring a deleted file. The post says permissions had been tightened after a 2021 audit recommendation, using the product’s shipped roles rather than roles tailored to the tasks the organization wanted to delegate.
#1 Best Overall
The team’s response, according to Shinder, was to delegate seven narrow permissions and log them so they could be reviewed. That is different from giving a broad administrator role: the aim is to grant only the specific actions needed, with an audit trail. The post does not identify the product or describe the permission model in enough detail to reproduce its configuration.
Role-based access can govern knowledge-article actions as well as operational tasks. For example, Microsoft Service Manager documentation describes role profiles that control who can read, create, edit, or delete knowledge articles. That is an example of one product’s controls, not evidence that Shinder’s team used Service Manager.
Known fixes lived with individuals
Another 96 cases, in Shinder’s account, involved known faults with known workarounds that were held in the heads of two people rather than documented. The team’s rule became that a fault escalated three times must receive an article before the ticket could close: an engineer writes it, then a first-line colleague follows it without help. That follow-through matters. A document is not operational knowledge until the people expected to use it can apply it successfully.
Shinder says the team’s earlier knowledge-article effort ended in 2022 when its writer changed jobs. The episode illustrates a continuity risk: a knowledge base needs ownership and a repeatable way to capture fixes, rather than depending on one person’s role or memory.
Outdated categories sent tickets to the wrong queue
Shinder attributes 40 cases to an outdated ticket-category list that routed requests to the wrong queue. The team replaced its old category tree with a list based on the systems it actually runs. A useful category scheme should help route work to someone able to resolve it; a long or stale list can add misclassification without adding useful information.
What changed—and what the reported results show
Alongside the seven narrow permissions, the knowledge-article rule, and the revised categories, the team began reporting first-contact resolution by issue type. Shinder says the overall measure had stayed at about one-third for four years before the team broke it down this way. Segmenting by issue can reveal whether a low aggregate result reflects particular repeatable problems, routing, or a genuinely complex workload.
Shinder reports that first line now closes around three-fifths of incoming work, and that a second-factor reset takes six minutes instead of forty. These are the author’s reported outcomes; the post does not explain the measurement method, the period covered, or how much each change contributed. They should not be treated as a forecast for another team.
How to use the case in another service desk
The practical lesson is to inspect escalation reasons before treating the escalation count as a measure of technical difficulty. A review can distinguish work that needs senior expertise from work blocked by access, missing instructions, or poor routing.
Best Value
- Used Book in Good Condition
- Classify the actual blocker. Record whether each reviewed escalation needed engineering judgment, a routine action the first line could not perform, a known fix that was undocumented, or a routing correction. Define categories clearly and note when more than one applies.
- Review permissions narrowly. Identify repeated low-risk tasks, grant only the required actions where policy permits, and preserve logging and review. Security or audit requirements may still rule out delegation in particular cases.
- Turn repeat fixes into tested guidance. Capture recurring solutions, assign ownership for keeping them current, and ask a first-line colleague to follow the instructions without coaching before treating an article as ready.
- Check routing against the systems and queues in use. Remove obsolete categories and verify that each remaining choice directs work to a responsible team.
- Measure by issue type as well as overall. Track resolution and escalation patterns for comparable issue types, while retaining a path for cases that truly need senior support.
The review should not become a target to suppress escalations. Shinder says about 130 of the 412 cases genuinely needed someone senior, and his account does not suggest eliminating that route. The useful question is whether each escalation reflects the problem’s complexity—or a fixable gap in access, documentation, or routing.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
