Let’s cut the corporate fluff: working in IT is mentally exhausting — and no, it’s not because you forgot to reboot the router. It’s because you’re stuck in a never-ending cycle of firefighting, micromanagement, unrealistic expectations, and “can you just” requests… all while pretending you’re totally fine.
But here’s the spicy truth:
Bad leadership is quietly wrecking mental health in IT, and it’s doing it with the precision of a well-timed logic bomb.
The “It’s Fine” Culture of IT (Spoiler: It’s Not Fine)
You’re expected to:
- Magically know everything from cybersecurity to fixing Brenda’s Wi-Fi.
- Be on-call 24/7 because “you’re so dedicated.”
- Make do with old hardware, outdated software, and a lot of duct tape.
- Attend meetings and do the actual work.
- Stay “positive” while your ticket queue looks like a CVS receipt.
And if you’re the only IT person in the building? Buckle up.
“Just delegate stuff to outside vendors. You shouldn’t waste your time on small things. We need it fixed now.”
Right. Because the fastest way to fix a flickering monitor is to call a vendor, create a PO, wait for someone to show up, and then explain to them where the power button is.
Here’s the reality: Some tasks just cannot wait. When the internet’s down during payroll or a switch dies mid-meeting, you don’t have time for bureaucracy. You just fix it. Because that’s what real-world urgency looks like — not another “strategic discussion.”
Shout-out to My One Intern
Yes, I have an intern. Just one.
They’ve been with me for a year. They’re smart, resourceful, and at this point, have enough battle scars to be considered a junior sysadmin with trauma.
But let’s be real — it’s still just the two of us. Two humans. No magic elves. No full-stack devops unicorns. Just caffeine, creativity, and the occasional miracle. And yet management still expects us to function like an enterprise-level MSP with a Red Bull sponsorship.
Leadership: The Real Denial-of-Service Attack
Let’s call it what it is: bad leadership is malware for morale.
- Micromanagement disguised as “just checking in.”
- Impossible timelines with zero resources.
- Outrage over minor delays but silence when the job gets done right.
- Delegation demands when you’re already solo — and somehow also the manager of five external contractors.
- Everything’s a fire drill… even things that aren’t burning.
And when you push back? You’re told to “write a report.” Because nothing solves urgent technical debt like PowerPoint.
So What Can Organizations Actually Do?
Aside from yoga classes no one has time to attend?
- Normalize mental health conversations. We’re not robots (although we run on scripts).
- Fix your leadership firmware. Empathy is not a memory leak.
- Set realistic boundaries. On-call doesn’t mean always-on.
- Trust your team. If your IT person says, “I got this,” don’t escalate to three vendors just because it’s 3PM and you’re bored.
- Respect real urgency. If it’s a critical service disruption — yes, fix it now. If it’s Brenda’s Bluetooth mouse acting up? Calm down.
- Give actual support. Tools, time, and trust go a long way.
Final Ping
IT work is tough. It’s demanding, technical, and somehow always urgent — even when it isn’t. If organizations keep ignoring the mental health toll (especially for solo admins and their battle-tested interns), they’re going to end up with fried systems and a goodbye note that reads:
“I Quit IT and Now Raise Goats in Cebu — They Don’t Use Printers.”
Fix the leadership. Respect the work. And maybe — just maybe — stop acting surprised when your entire IT department (yes, both of us) gets a little crispy after fixing your fifth “urgent” ticket before lunch.