Your IT partner just quit, doubling your workload with no pay increase? I’ve been there. Here’s a veteran’s survival guide on how to document, negotiate, and decide when it’s time to walk away.

So Your Teammate Quit and Now You’re a One-Man Army. What Now?

I remember it vividly. It was 2 AM on a Saturday, and my phone was buzzing like an angry hornet. PagerDuty was screaming that prod-billing-db-01 was completely offline. Not slow, not lagging—stone-cold dead. My partner, Kevin, the “database guy,” had put in his two weeks’ notice on Monday. The knowledge transfer was a 30-minute chat where he said, “It’s all in Confluence.” Famous last words. I spent the next six hours frantically reverse-engineering a recovery process that only existed in his head, all while the CFO was sending hourly emails in all caps. That night, I learned a brutal lesson: when you become a single point of failure, you’re not just a hero in waiting; you’re a victim in the making.

Why You’re In This Mess (And It’s Not Your Fault)

Seeing a thread like “solo admin for 300 users, no raise” hits a nerve because it’s a classic symptom of a deeper problem. This isn’t just about your colleague leaving; it’s about a business that fundamentally misunderstands technology’s role. They see IT not as a value-generator, but as a cost center—a utility bill they have to pay. When one of two light bulbs burns out, they don’t see the risk of total darkness; they see a 50% reduction in their electricity bill.

This situation is a textbook example of a “Bus Factor” of one. The Bus Factor is a morbid but effective metric: how many people need to get hit by a bus before your project or department is completely screwed? Right now, for your company, that number is one. You. This is not a badge of honor; it’s a massive, blinking-red organizational risk. Your job is to make them see it.

Step 1: The Triage – Stop the Bleeding

Before you can plan your next move, you need to survive the week. Your goal right now isn’t to be a hero who does two jobs perfectly. It’s to stabilize the situation, manage expectations, and start gathering data. This is damage control.

1. Document Your World

Your brain is now a critical, undocumented asset. Start dumping it. Use whatever you have—Confluence, a private Git repo, even a locked-down Word doc. What to document?

• The “Hit by a Bus” List: What are the top 5 things someone would need to know if you were suddenly gone? Think root passwords, firewall access, the location of the backup tapes, the one weird cron job on util-lnx-03 that syncs the sales data every night.
• Common Fixes: The five most common tickets and their step-by-step solutions. “Janet from Accounting can’t print” is probably one of them.
• Vendor Contacts: Who do you call when the SAN goes down or the ISP link flaps?

2. Automate the Annoying Stuff

You don’t have time to build a grand automation empire, but you can claw back a few hours. Find the most repetitive, mind-numbing task you do and script it. A perfect candidate is user de-provisioning. It’s critical, time-sensitive, and easy to mess up manually.

Here’s a hacky but effective PowerShell snippet to get you started. It doesn’t have fancy logging, but it gets the job done when you’re underwater.

# Quick and Dirty User Offboarding - Run with care!
$Username = Read-Host -Prompt "Enter username to disable"

# Check if user exists
Get-ADUser -Identity $Username

If ($?) {
    Write-Host "Disabling account for $Username..." -ForegroundColor Yellow
    Disable-ADAccount -Identity $Username
    
    Write-Host "Moving user to 'Disabled Users' OU..." -ForegroundColor Yellow
    $UserDN = (Get-ADUser -Identity $Username).DistinguishedName
    Move-ADObject -Identity $UserDN -TargetPath "OU=Disabled Users,DC=yourdomain,DC=com"

    Write-Host "Removing from all groups..." -ForegroundColor Yellow
    Get-ADPrincipalGroupMembership -Identity $Username | ForEach-Object {
        Remove-ADGroupMember -Identity $_.Name -Members $Username -Confirm:$false
    }

    Write-Host "$Username has been successfully offboarded." -ForegroundColor Green
} Else {
    Write-Host "User $Username not found." -ForegroundColor Red
}

3. Communicate and Reset Expectations

This is the most important part. You must, professionally and immediately, inform stakeholders that reality has changed. Send an email to your manager (and maybe HR) outlining the situation. Do not complain. State facts.

“With [Teammate’s Name]’s departure, our team’s capacity is reduced by 50%. To ensure critical systems remain stable, I will be prioritizing tasks in the following order: 1. System-wide outages, 2. Security incidents, 3. Critical business function support, 4. Standard user requests. Please expect delays on non-critical tickets as I manage the combined workload. I have opened a new ticket to track the documentation of [Teammate’s Name]’s former responsibilities.”

Pro Tip: This isn’t just an email; it’s a paper trail. You are creating a record that you proactively identified a risk and communicated the impact. When a non-critical task gets dropped, you can refer back to this.

Step 2: The Strategic Play – Make It Their Problem

After you’ve stabilized, it’s time to go on the offensive. You need to translate your pain (“I’m overworked”) into their pain (“We are at risk of losing money”). Managers respond to data and risk, not to complaints.

Compile a one-page report for your boss. Use a table to make the impact undeniable.

End the report with solutions, not just problems. Frame it in terms of business needs: “To mitigate these risks and restore service levels, I recommend we either: A) Open a requisition for a new SysAdmin immediately, B) Engage a managed service provider for Tier 1 support for ~$3k/month, or C) Accept the current level of risk and service degradation.”

You’ve now made it their choice. You’ve also shown you’re a strategic thinker, not just a burnt-out admin.

Step 3: The Nuclear Option – The Strategic Exit

Let’s be real. Sometimes, they won’t listen. They’ll accept the risk, pat you on the back for being a “team player,” and hope you just burn out quietly. If you’ve made your case and nothing changes—no raise, no help, no plan—then the only option left is to leave.

But you don’t just rage-quit. You execute a planned, strategic departure.

1. Update Your Resume. Yesterday. All that extra work? That’s not just pain; it’s experience. You are no longer “part of a team that manages 300 users.” You are “the sole System Administrator responsible for all IT infrastructure and support for 300+ users, including server management, network security, and end-user support.” See the difference? You’ve earned that title.
2. Interview Quietly, Accept Confidently. Start looking. With the experience you’re gaining, you are highly marketable. Don’t take a counteroffer. If they only value you when you’re walking out the door, they never truly valued you at all.
3. Leave a Clean Camp. Once you’ve accepted a new role, give your two weeks’ notice. Spend those ten days polishing that documentation you started in Step 1. You want to leave as a professional. Your reputation is the only thing you take with you from job to job.

Warning: The temptation to just “let it all burn” on your way out is immense, but it will only hurt you in the long run. The tech world is small. Leave with your head held high, knowing you did everything you could and made the right choice for your career and your sanity.

This industry can be tough, and it’s easy to feel trapped. But remember: your skills are in demand. Your health is not negotiable. And your value is not determined by an employer who refuses to recognize it.

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