Hacker News new | ask | show | jobs
by apocalyptic0n3 1216 days ago
From the administrative/IT point of view, I understand it entirely. It's a simple risk/value proposition. If an employee gets mad they were laid off (and that does happen) and decides in a fit of rage to start deleting Slack channels, damaging or even just accessing production environments, deleting shared logins in the team password manager, downloading company/employee/customer/client data, stealing company IP, etc., they could seriously hurt the company. Even if what they do is illegal or you can sue them afterward, it's a very significant short term loss and in some cases, they may be able to do damage that cannot be reversed like deleting Slack channels.

Obviously, every company should have good access controls in place that would prevent this from a regular employee. But that's not always possible and at the end of the day, some employees have to have those privileges. It's easier to just immediately lock them out of anything and avoid any potential damage. It seems cold to you (and it probably is), but even one ex-employee going rogue before lock-out could be disastrous. And that's without going into the "ex-employee drags down team morale by ranting about company/job" aspect and in many cases insurance companies will require it. It's just not worth it, even at a much smaller company than DO like where I work.

2 comments

On paper I agree with all of that but in practice folks who are getting laid off already had access to all of those things every day.

Why do you trust them every day but not on the day of being laid off? Unless you're extremely close friends with them at a personal level you don't know what their state of mind is while employed without being laid off. They could do all sorts of destructive things at any point in time (both subtle and obvious).

I guess where I'm going with this one is you're always at risk for short term loss by hiring anyone. If you trust the people you hired then the short term loss outcome won't happen if you fire them. If you don't trust the people you hired then why did you hire them and give them access to do those things? All this does is optimize for bad actors and make the experience horrible for someone being fired who doesn't have intent to take the company down with them, they just want to say goodbye to their co-workers.

Plus, like you said, there could be legal actions taken against them. Who's going to risk getting sued by a corporation in the US by destroying as much as they could before they lose access? This action could potentially ruin the rest of their life from debt.

You don't. But you're also not purposefully doing something that is going induce undue stress and potentially upset or anger the employee. You don't know how anyone is going to react to being told they've been let go. That's not an easy thing to be told and I have seen people get violent afterward.

As an example, about a decade ago, we let go an underperforming employee. His reaction was to walk out of the room before the conversation had finished, take a trash can and dump it onto his desk and computer, then go outside and into his car, pull a gun out of his trunk and start walking around the building rambling like a mad man. We had to go on lockdown and wait for a police response. Prior to that moment, he had never shown a single indication he would react like that and was trustworthy, he just wasn't performing well. If he had been someone with elevated privileges anywhere, he could have instead reacted by going back home or even into his car, accessed systems, and done damage that way.

I get what you're saying, but you're discounting how big a deal it is to lose your job and the things it can do to you mentally. Some people come out the other side of that a completely different person for a while.

> Why do you trust them every day but not on the day of being laid off?

Because they had a job to care about before being laid off. It's entirely possible that being laid off triggers them to take malicious actions that they never would have when they were employed.

> Even if what they do is illegal or you can sue them afterward, it's a very significant short term loss and in some cases, they may be able to do damage that cannot be reversed like deleting Slack channels.

I was recently tasked with revoking access to systems during my companies recent round of layoffs. We had it timed so that when the departing employee found out they were leaving they'd already have no access.

Unfortunately for us, they were a brand ambassador and took to their personal social media to tell their followers that we were embezzling client funds (not true).

I don't know what happened from a legal stand point (if they were sued or there was any other consequences) but sometimes new customers find out they said that and are distrustful of us.

Exactly. We've had some similar issues. We also time it so they get locked out as they are being told (we do it in-person/over-call rather than via email as DO did). We've never had an issue preventing them damaging systems, but we have received a few laptops from remote employees that were clearly damaged in rage and in a few cases, had employees start calling up their clients and trying to persuade them to leave us for literally anyone else. It can be rough as a smaller company trying to convince clients they're jilted ex-employees that aren't telling the truth about anything.