A hilarious Reddit saga where a remote worker blamed the IT support team for his lack of productivity, only for system logs to reveal he barely works at all.
Hey folks, if you've ever worked in IT support, MSP, or sysadmin roles, you know that being the scapegoat for technically illiterate users is basically in the job description. But today, we've got a glorious plot twist from Reddit: the guy screaming the loudest about your "hot garbage" IT setup is actually covering up the fact that he doesn't work!
Here’s the scoop. OP manages a 30-person company. Things have been smooth for two years until one remote support guy turned into an absolute nightmare. This dude constantly complains: his VPN is dead, the ticketing system freezes, the RMM agent disconnects, and the IT response time is trash. He even escalated it to his boss, claiming his productivity has ground to a halt because the IT team’s setup is practically a war crime.
OP's team went full detective. They dug through the cloud vps logs, checked endpoints, monitored session history. Nada. Everything was perfectly fine. They fixed a couple of minor glitches like timezone syncing, but couldn't reproduce 99% of the issues. Yet, the guy kept loudly whining, and the owner started asking OP why things were broken.
Then came the accidental mic drop. The client uses Intelogos (a productivity monitoring tool) on all machines. While checking it, OP discovered this loudmouth is logging a solid... 10 to 12 hours a week. On a 40-hour schedule. That's an average of 2 hours a day!
The constant complaining wasn't about broken tech; it was an elaborate smokescreen to hide his chronic allergy to working. OP has a 1-on-1 with the client owner on Monday to discuss some ai tools and is wondering: Do I drop the nuke and expose him, or do I stay quiet to avoid looking like a creepy snooper?
You mess with the IT department's reputation, you get the horns. The Reddit sysadmin community immediately rallied, offering some top-tier weaponized compliance strategies:
1. The "Just the Facts, Ma'am" approach The absolute consensus: Leave emotions out of it. Never say "Hey, your employee is slacking off." Instead, bury them in metrics. Present a polite, dry report: "The user's machine shows an average of 12 hours of active engagement per week. At all times the user reported network outages, our systems showed zero disruptions and we could not replicate the errors." Let the boss connect the dots.
2. The Ticket Police Strategy Enforce strict protocols. Tell the owner that to efficiently troubleshoot these "phantom" issues, the user must submit a ticket exactly when the disruption occurs, not days later. No ticket, no problem.
3. The "Oops, look what I found" maneuver One brilliant commenter suggested treating it like a mechanic finding a broken belt while doing a routine oil change. "Hey Boss, while we were doing a deep dive into the logs to figure out why Bob's system keeps 'crashing', we stumbled across this data discrepancy regarding his online hours. Just thought we should flag it as a side note." Absolutely ruthless.
Listen up, fellow techies. Let this be a lesson: Log files don't lie, but users absolutely do.
When a user tries to throw you under the bus to save their own skin, never bring emotion into a data fight. CYA (Cover Your Ass) isn't just a corporate buzzword; it's a fundamental survival mechanism in tech. Document everything, stick to the verifiable facts, smile politely, and watch the trash take itself out.
Reference: Based on the Reddit thread: Client's employee keeps blaming us for everything. Turns out he's barely working
