Wells Fargo worker found dead at her desk four days after clocking in | Hacker News Reader

Wells Fargo worker found dead at her desk four days after clocking in

theguardian.com

29 pointshoward94117 comments

Would it be bad form if I linked to this story every time someone here says RTO is essential for ‘vibrant and lively’ communication between colleagues?

I hear you. I think this story says more about a particular organization and/or individual’s role than it does RTO in general.

Yeah, and it's a bad example since the timeline could easily be that she was working until a bit later on Friday, passed away, and wasn't found until Monday afternoon. However, since this was submitted on a Friday the brain automatically thinks about it happening Mon-Fri if you don't read the article.

They weren't found until Tuesday afternoon.

Two full workdays in the office with no colaboration

Not a lot of communication with your colleagues when you die on Friday and nobody notices until Tuesday. People came in and worked an entire day while she was in her cubicle decomposing.

Oh I misread that initially, I thought it was 5PM on that Monday, jesus.

Don't you worry, they'll link it right back at you along with "This is why we need open office plans!"

So based I think I’m going to hurl.

I'm not sure that will send the message you expect.

> most employees at the Wells Fargo office work remotely

https://www.12news.com/article/news/local/valley/investigati...

There are also more comments in a related earlier submission "Wells Fargo employee found dead at desk after 4 days" at https://news.ycombinator.com/item?id=41396883

There wasn't even a cleaning crew or custodian or security person that at least passed by?

I mean, this isn't some frothy AI startup that has approximately zero chance of having any impact on the world. This is one of the largest banks in the country. They should, at the very least, have someone checking every office and cube, every night, to make sure no unauthorized personnel are there after closing.

It's also not like they wouldn't have reasons to double/triple check in this specific case without needing a general patrol policy: It should have been a security concern at the end of Friday that someone had badged in and not left. That's among basic reasons for having these badge systems, in the first place. Someone failing to badge out is a security risk. (It's also a Fire Marshall risk because another reason companies require accurate badge out is that in the case of a fire emergency and they have a badge in process, they are then liable for knowing every employee inside the building in the event of that fire emergency and helping make sure everyone gets out safely.)

Even if the company encourages sleeping at your desk overnight "for productivity", because companies sure do love underpaid labor and accidental burnout, there's an increased OpSec risk for every extra hour someone has access to secure corporate resources. You'd think in a bank where security is supposed to be important at least one security software would be paranoid and presenting alarms about someone still badged in over a full weekend.

Every office job I’ve ever had required me to badge in but I’ve never had to badge out. The badge in was just for security purposes.

I've had a mixture of the two in my years. The growing "Fire Marshall liability" thing (which obviously depends on your state, and other factors) has been pushing companies to do both, even in cases where they weren't convinced for security reasons alone. (Though security reasons alone you would expect a bank to require both in and out.) (ETA: And the article implies that they did have a badge out.)