PDQ: IT Admin Workload Doubled, Salary Stayed the Same

Name: PDQ: IT Admin Workload Doubled, Salary Stayed the Same
Uploaded: 2026-10-02T07:37:22-04:00
Duration: 1 min 10 s
Description: Story originally posted on Reddit. #shorts #informationtechnology #sysadmin #revenge #corporate Can't get enough PDQ? Subscribe and enable notifications! • Join us on Discord!: https://discord.gg/pdq • Our blog: https://www.pdq.com/blog/ • PDQ Connect...

PDQ

10/02/2026

0 (0%)

Report Like Favorite

TL;DR

A co-admin quit and was never replaced, leaving one IT admin to absorb both help desk and infrastructure responsibilities at the same salary with no discussion.
The ticket math looks almost acceptable on paper — 290 handled solo versus 340 shared — but 50 tickets per month are silently failing, closed unresolved, or never raised at all.
Critical risks are accumulating invisibly: a security patch untested for three weeks and a DR plan untouched for six weeks that leadership will never see in any report.

Summary

This short, narrated Reddit story puts a human face on a systemic IT staffing problem: when a co-admin leaves and isn't replaced, the remaining administrator silently absorbs the full workload with no salary adjustment and no formal acknowledgment from leadership. The narrator lays out the math plainly — two admins previously handled 340 tickets a month; now one handles 290, but that apparent efficiency masks 50 tickets per month that are missed, closed without resolution, or never filed because users have given up. More critically, the hidden costs are invisible to management: a security patch sitting untested for three weeks, a disaster recovery plan untouched for six weeks, and a DR test indefinitely deferred. The video closes with a quiet warning that resonates across the sysadmin community — the admin is making daily triage decisions about what doesn't get done, and no one in leadership is asking what those decisions are. When something on that silent list eventually fails, the admin will be the only person who saw it coming.

Chapters

0:00 - The Co-Admin Leaves
0:16 - Full Workload, Solo
0:25 - The Ticket Math
0:43 - Hidden Risks Leadership Won't See

Key Quotes

0:32 "That sounds like progress. It's not."
0:34 "It means 50 tickets a month are either passed SLA, closed without resolution, or never opened, because users have learned that raising a ticket takes longer than just living with the problem."
0:54 "I'm doing the job, but I'm making choices every day about what doesn't get done, and nobody is asking me what those choices are."

FAQ

Why does the ticket count dropping from 340 to 290 actually represent a failure rather than efficiency?

The 50-ticket gap isn't being resolved — those tickets are either past SLA, closed without a fix, or never opened because users have learned that submitting a ticket takes longer than tolerating the problem. The number looks better on paper while the underlying service quality has deteriorated.

What specific risks are going unaddressed in this scenario?

The narrator identifies a security patch that has been sitting untested in the queue for three weeks and a disaster recovery plan that hasn't been touched in six weeks. The DR test originally scheduled for September has been indefinitely postponed to 'when I have time.'

Categories:

» Data Protection

Tags:

Show more Show less

TL;DR

Summary

Chapters

Key Quotes

FAQ

Ensuring Compliance Through Audit Evidence: From CJIS to FERPA

Risk in Real Time Demo Series: Virtual Patching: Protection at the Speed of Exploitation

Harnessing Data Governance for AI with Cyera and Snowflake