🚀 Executive Summary

TL;DR: A solo IT admin for 300 users, without a raise, inherited the workload of two people, facing an exploitative situation. The guide offers strategies to survive through automation, make a data-backed case for compensation, or strategically exit for a better opportunity.

🎯 Key Takeaways

  • Automate repetitive tasks like new user creation or password resets using scripting (e.g., PowerShell) to reduce workload and create breathing room.
  • Implement and strictly enforce a formal ticketing system to manage requests, track workload, and gather data for performance metrics.
  • Maintain a personal knowledge base (e.g., OneNote, Git repo) to document all fixes, server quirks, and vendor contacts, serving as both a personal asset and leverage.

2-man IT team → solo admin for 300 users, no raise. Stick it out or leave?

When you inherit the workload of two people with no change in pay or title, it’s not a challenge—it’s an exploit. This guide breaks down how to survive, make your case with data, or strategically eject from a no-win situation.

So, Your Co-Worker Quit. Now You’re a Solo Admin for 300 Users With No Raise.

I remember this moment like it was yesterday. I was a junior sysadmin, barely a year into my career. My senior, a guy named Mike, put in his two weeks. On his last day, he handed me a sticky note with the root password for prod-db-01 and said, “Don’t reboot it unless it’s on fire. And maybe not even then.” For the next six months, I was the entire IT department for a 150-person company. The stress was immense, the pager was my constant companion, and my reward for keeping the lights on was… a ‘good job’ in the hallway. That experience taught me a brutal lesson: being the hero who works 80-hour weeks doesn’t get you a raise. It just gets you more work.

The “Why”: Understanding the Management Playbook

Let’s get one thing straight: this isn’t happening because your boss is necessarily a bad person. It’s happening because from a certain management perspective, you just solved their problem for free. They had two salaries on the books for IT, and now they have one. The systems are still running, tickets are (mostly) getting closed, and the building hasn’t burned down. In their eyes, the department is now 50% more “efficient.”

They see IT as a cost center, a necessary expense like electricity. As long as the lights stay on, they don’t think about the wiring. Your job is to show them you’re not just the wiring; you’re the power plant, and it’s about to have a brownout if they don’t invest in its upkeep.

The Fixes: Your Three Paths Forward

You have three distinct strategies here. You can even use them in sequence. But you must choose one and commit to it.

1. The Quick Fix: The “Hunker Down & Automate” Strategy

This is your survival mode. You cannot do the work of two people indefinitely. Stop trying. Your immediate goal is to reduce your workload, create breathing room, and document everything. This makes you less stressed and, ironically, prepares you for the other two options.

  • Stop Being a Hero: You can’t fix every minor issue in five minutes anymore. Implement a formal ticketing system if you don’t have one. Be ruthless about it. A “quick question” in the hallway gets the response, “Great question, can you put that in a ticket so I don’t lose track of it?”
  • Automate the Annoying Stuff: What’s the most repetitive task you do? New user creation? Password resets? Automate it. Spend a few hours writing a simple script that will save you hours every week. A basic PowerShell script to onboard a new user is a great start.
# Super simple PowerShell example for new user setup
# Darian's "Save My Sanity" Script v0.1

$FirstName = Read-Host -Prompt 'Input new user first name'
$LastName = Read-Host -Prompt 'Input new user last name'
$Password = Read-Host -Prompt 'Input temporary password' -AsSecureString

$upn = "$FirstName.$LastName@techresolve.local"
$sam = "$FirstName.$LastName"

New-ADUser -Name "$FirstName $LastName" `
    -GivenName $FirstName `
    -Surname $LastName `
    -UserPrincipalName $upn `
    -SamAccountName $sam `
    -AccountPassword $Password `
    -Enabled $true -ChangePasswordAtLogon $true

# ... add them to default groups, create home folder, etc.
Write-Host "User $sam created."

Pro Tip: Document everything. Not for the company, but for yourself. Create a personal knowledge base (OneNote, a private Git repo, whatever). Every fix, every server quirk, every vendor contact. This becomes your leverage and your personal asset.

2. The Permanent Fix: The “Make Your Case with Data” Strategy

Once you’ve survived the initial chaos, it’s time to go on the offensive. You cannot walk into your boss’s office and say, “I’m overworked and need a raise.” That’s a feeling. You need to present an argument backed by data. You need to speak their language: money, risk, and efficiency.

For one month, track your metrics like a hawk:

Metric What It Shows How to Frame It
Tickets Opened vs. Closed Your raw workload and efficiency. “I’ve closed 150 tickets this month, but 180 were opened. The backlog is growing, which means users are waiting longer for solutions.”
Project Work vs. “Keep The Lights On” (KTLO) How much time is spent on reactive fires vs. proactive improvements. “85% of my time is spent on reactive KTLO tasks. That leaves no time for critical projects like the firewall upgrade, which is a major security risk.”
Time Saved via Automation Your value and initiative. “The user onboarding script I built saved an estimated 10 hours of manual work this month. This proves what we can achieve with proper investment in automation.”

Schedule a meeting. Present your findings calmly. End with a clear proposal. It should be something like: “Given that I’ve absorbed the responsibilities of a second team member and am successfully managing the infrastructure for 300 users, I’m proposing a title change to Senior Systems Administrator and a salary adjustment to $XX,XXX to reflect this new scope.” If they say no, you ask, “Okay, what is the plan and timeline for hiring a second person to get the department back to being fully staffed?” Their answer will tell you everything you need to know about your future at the company.

3. The ‘Nuclear’ Option: The “Strategic Ejection” Plan

Sometimes, you just have to read the writing on the wall. If management is unresponsive, cheap, or simply doesn’t value IT, no amount of data will change their minds. In this case, your job is no longer to fix their company; it’s to fix your career.

This is not “rage quitting.” This is a calculated, professional exit.

  • Update Your Resume NOW: Don’t wait. Your new resume headline is gold: “Solely managed all IT infrastructure and support for a 300-user environment, including servers, networking, and security.” You are infinitely more marketable now than you were two months ago. You’ve proven you can handle pressure.
  • Leverage the Chaos: In interviews, you have a killer story. When they ask about a challenge you faced, you can talk about how you single-handedly stabilized an entire IT department after a sudden departure. This screams competence and resilience.
  • Leave Cleanly: Give your two weeks’ notice. Spend those two weeks tidying up your documentation (that personal knowledge base you built in Step 1 is perfect for this). Do a thorough handoff to whoever they hire or designate. Leave on good terms. The tech world is small, and you never know who you’ll work with again.

Warning: The single biggest mistake I see engineers make is waiting until they are completely burned out to start looking. Start looking while you still have the energy. Your current job is now funding your search for a better one. Use your lunch breaks to browse job boards and talk to recruiters.

Ultimately, a company that doubles your workload without a conversation about compensation is showing you its true colors. They’re banking on your loyalty and your fear of change. Don’t let them. Whether you stay and fight for what you’re worth or you leave for a company that already values you, the key is to take control of the situation. You’re the one in the driver’s seat now.

Darian Vance - Lead Cloud Architect

Darian Vance

Lead Cloud Architect & DevOps Strategist

With over 12 years in system architecture and automation, Darian specializes in simplifying complex cloud infrastructures. An advocate for open-source solutions, he founded TechResolve to provide engineers with actionable, battle-tested troubleshooting guides and robust software alternatives.


🤖 Frequently Asked Questions

❓ How can a solo IT admin effectively manage a significantly increased workload without additional compensation?

The primary approach involves implementing a formal ticketing system, rigorously automating repetitive tasks using scripting, and documenting all processes to create efficiency and reduce reactive work.

❓ What are the strategic options for an IT professional facing a doubled workload with no raise?

The article outlines three strategies: ‘Hunker Down & Automate’ for immediate survival, ‘Make Your Case with Data’ to negotiate for a raise or title change, or the ‘Strategic Ejection’ plan to find a new, more valuing employer.

❓ What is a critical mistake to avoid when transitioning to a solo IT admin role under these circumstances?

A major pitfall is attempting to be a ‘hero’ by absorbing all the extra work without automation or documentation, leading to rapid burnout. Another is delaying the job search until completely exhausted, diminishing negotiation power.

Leave a Reply

Discover more from TechResolve - SaaS Troubleshooting & Software Alternatives

Subscribe now to keep reading and get access to the full archive.

Continue reading