The Account Is Locked: The Part Of IT Nobody Talks About

Most people think the hardest part of working in IT is the technology. The 2 a.m. outage. The ransomware scare. The migration that goes sideways on a Friday afternoon. Those are hard, sure. But they're the kind of hard you can fix with a runbook and enough coffee.

The hardest part of this job doesn't come with a ticket number. It comes as a calendar invite from HR with no description, or a quiet Slack message that just says, "Can you hop on a call for a second?" You already know what it is before you click.

Someone is being let go, and you're about to be the one who turns off the lights.

The Ticket You Never Wanted

Here's how it usually goes. You get a name, a time, and a list. Disable Active Directory. Revoke Okta or Entra sessions. Kill the VPN certificate. Wipe or lock the laptop. Forward the mailbox to the manager. Remove them from Slack, GitHub, Jira, Salesforce, the building badge system, and the eleven other tools nobody remembers we pay for until this exact moment.

The timing is precise on purpose. HR wants the accounts dead the minute the meeting starts, sometimes the minute before. You sit there with the PowerShell window open and your finger hovering, watching the clock, waiting for the go signal. It feels a little like being the person behind the curtain who pulls the lever.

And then it's done. Sessions revoked. Password reset to something nobody will ever know. Device marked for wipe. Total time: about four minutes.

What the checklist never mentions is that the name on that ticket is someone you ate lunch with last Tuesday.

"I Can't Tell You That"

The part that really wears on you comes next, and it comes fast. The phone rings. Sometimes it's the person themselves, still in the parking lot, voice shaking. Sometimes it's a text to your personal number because they don't have a work phone anymore. Sometimes it's a message on LinkedIn at 11 p.m.

"Hey man, I can't get into my email. Is something wrong with my account?"

Sometimes they don't know yet. The HR meeting is in twenty minutes and they've noticed their laptop just logged them out. They think it's a glitch. They're asking you, their IT guy, the person who has fixed every weird problem they've ever had, to just fix this one too.

And you can't say anything.

Not "I'm sorry." Not "Talk to your manager." Not even a sympathetic pause that runs a beat too long, because that pause tells them everything. You've been coached on this. Anything you say can create legal exposure for the company. So you say the only thing you're allowed to say, in the flattest voice you can manage:

"I'm not able to discuss the status of your account. You'll need to reach out to HR."

You hear the silence on the other end as they put it together. Then they hang up, or they say "okay" in a voice that will stay with you for the rest of the week.

I have done this more times than I want to count. It has never once gotten easier. If anything, it gets harder, because you get better at recognizing the exact moment the realization lands.

The Weight Of Knowing

There's a specific kind of loneliness that comes with this role. You often know before the person's own manager does. You know before their team. You certainly know before their spouse. You carry that information around the office for hours, sometimes days, nodding hello to someone in the hallway while a disable-account script sits queued with their name on it.

You can't vent about it. You can't warn them. You can't even look at them for too long, because you're worried your face will give it away.

And when it's over, there's no debrief. Nobody from HR checks in on the sysadmin. The person who got laid off gets a severance packet and, if they're lucky, an outplacement service. You get the next ticket in the queue. A printer is jamming on the third floor. Life goes on, apparently.

I don't say this to compete for sympathy with someone who just lost their income. Their situation is objectively worse. But it's worth naming that the person executing the offboarding absorbs a real emotional cost, and most organizations act as if that cost is zero.

Then Comes Facebook

If the workday ended when the account was disabled, that would be one thing. It doesn't.

The person you locked out lives in your town. They're in your Facebook friends list because they invited the whole team to their kid's birthday party three years ago. You're connected on LinkedIn because that's just what you do when you work with someone. You might be in the same fantasy football league, the same church, the same gym.

So that evening you open Facebook and there it is: "Well, after six years, today was my last day at [Company]. Not by choice. Grateful for the people, not so much for the way it ended."

Forty-two comments. Heart reactions. "You deserved better." "Their loss." "DM me, we're hiring."

And you're sitting there with your thumb over the screen wondering what, exactly, you're supposed to do. If you react, does that look like you're taking sides against your employer? If you don't, does it look like you don't care? Do they know it was you who pulled the plug? Do they blame you? Should they?

LinkedIn is worse in its own way, because it's professional and polite and everybody is performing. The "open to work" banner goes up. A week later there's a post about resilience and lessons learned. You see it in your feed between a vendor webinar and someone's certification announcement, and you realize you're watching the aftermath of a thing you were part of, scrolled past like it's content.

The Awkward Middle

Then there's the in-person version. You run into them at the grocery store. Or a former coworker who still works with you says, "Hey, I had a beer with Dave last night, he asked about you." What did he ask? Is he angry? Did he figure out that the account went dark two minutes before his meeting because I was watching the clock?

Most of the time, in my experience, they aren't angry at you. Most people understand that IT doesn't decide who gets laid off. We're the executioner, not the judge, and most people can tell the difference. But "most" isn't "all," and even the ones who understand intellectually can still feel something when they see your name.

I've had former colleagues reach out months later to ask for a reference, or for help getting their personal photos off a laptop that was wiped before they could grab them. Those conversations are strange. Warm, mostly. But there's always a moment where the thing we don't talk about is sitting right there between us.

What Actually Helps

I don't have a clean fix for any of this. But after enough years, here's what I've landed on.

Separate the role from the relationship. When you're on the call saying "I can't discuss that," you are the company. When you're at the birthday party six months later, you are you. Both are real. Neither cancels the other.

Push for humane offboarding. You may not control the decision, but you often have input on the process. Advocate for giving people a window to pull personal files. Advocate for the mailbox auto-reply to be something other than a void. Advocate for HR to handle the "your account is disabled" conversation so the person doesn't have to hear it from the one coworker who can't say anything.

Talk to someone. Not about the specifics, which you legally can't share, but about the weight. Other IT people know exactly what this feels like. It helps to say out loud that it sucked.

Decide your social media stance ahead of time. Mine is simple: I don't unfriend anyone over a layoff, I don't comment on the post, and if they reach out to me personally, I respond like a human being. Your rules may differ. Having rules at all is what matters, because in the moment you won't think clearly.

Don't pretend it doesn't affect you. The people who burn out in this field aren't the ones who admit it's hard. They're the ones who say "it's just a ticket" for ten years and then one day can't get out of bed.

The Quiet Part Of The Job

We like to tell ourselves that IT is neutral. Ones and zeros. Access granted, access denied. The machine doesn't care.

But we aren't the machine. We're the ones who type the command, and we're the ones who pick up the phone afterward and say the sentence we've been told to say. We carry the knowledge nobody else has yet, and we live in the same neighborhoods as the people we've locked out.

That's the dark side of this work. It isn't dramatic. It doesn't make the news. It's just a small, heavy thing you carry home, and then set down next to the last one.

If you do this job, you know exactly what I mean. And if you don't, the next time your access gets cut off two minutes before a meeting you didn't expect, remember that the person on the other end of that "I can't discuss your account" call probably wanted to say a lot more.