Thread regarding Target Corp. layoffs

They laid us off and now

They firing us !!!!!


by
| 9584 views | | 41 replies (last October 30) | Reply
Post ID: @OP+1k8pkdyew

41 replies (most recent on top)

@eq they didn’t come after the people who downloaded the excel so if you just viewed ur fine

by
| | Reply
Post ID: @j5+1k8pkdyew

Did anyone get in trouble for viewing it?

by
| | Reply
Post ID: @eq+1k8pkdyew

person who posted the xl also got fired, his slack didn't get deactivated for some reason for a few hours. it's gone now

by
| | Reply
Post ID: @em+1k8pkdyew

I agree that posting the information on Slack was at the very least a bad idea. However, they would not have been tempted to find and share the information if leadership had done a better job of communicating. Line managers did not even know which of their direct reports were getting laid off. They literally had to ask each employee if they were laid off in order to know how their own team was affected. I'm not saying leadership should have shared all the names to everyone, but at least give something to people who need to know, like how many from which teams, etc.

Then to fire the people on the spot? That's extreme. Not even a warning and a chance to correct the mistake? As if morale wasn't already at an all time low...

by
| | Reply
Post ID: @e0+1k8pkdyew

Agostino said names of teams and people who were let go in a team meeting today, when's he getting fired for leaking names?

by
| | Reply
Post ID: @dg+1k8pkdyew

@d4 I saw the comment and its preview as it was posted. It didn’t look like a list of names since I saw bar charts. I clicked the file but it was deleted almost immediately after so the file didn’t load for me.

by
| | Reply
Post ID: @da+1k8pkdyew

One person started a thread about the AD group and another person posted the list with names in comment, now both of them are fired. It's definitely not a good thing to post names of the people impacted

by
| | Reply
Post ID: @d4+1k8pkdyew

@at person who posted the list is also fired

by
| | Reply
Post ID: @d3+1k8pkdyew

I don't have any sympathy for people sharing lists of laid off employees getting fired... You should have let these people have some privacy. I don't think it's a big deal for people who have the knowledge to figure out the information but to start sharing it with everyone just feels gross to me.

by
| | Reply
Post ID: @cs+1k8pkdyew

@c1 yelling is an internal slack channel at Target. It’s just kind of a water cooler channel where people type in all caps (aka yelling). And there’s been a lot of posting in there since the news broke Thursday.

by
| | Reply
Post ID: @c2+1k8pkdyew

What is the yelling slack channel?

by
| | Reply
Post ID: @c1+1k8pkdyew

It takes a lot to get fired as Target needs to cover their a-s and ensure there are appropriate grounds for dismissal. I assure you that they are not in a position to start firing people in situations like this without first having the legal team and HR vet it out. The full situation with 100% visibility to all the details was reviewed by the appropriate people at Target and it was deemed necessary to terminate their employment.

by
| | Reply
Post ID: @b4+1k8pkdyew

We also might not have the full picture here - perhaps HR already had a dossier on the affected individuals and this incident may not have been a fireable offense in isolation but it was the straw that broke the camel's back for these particular people

by
| | Reply
Post ID: @b3+1k8pkdyew

@b1 the ad group is the only way you can access the list. Why would you want someone else fired?

by
| | Reply
Post ID: @b2+1k8pkdyew

@aw "You don't mess around on company servers, especially when it comes to listing names of laid off people. Termination is not only legal but appropriate."

Read carefully: the people fired did not share the names of people laid off. They shared the name of the ad group. There were no names of people in their post. The person who shared the doc with names did NOT get fired.

by
| | Reply
Post ID: @b1+1k8pkdyew

@ap That is not what the policy says. The information does not look or feel any different than what is generally accessibble, this is retaliation.

by
| | Reply
Post ID: @b0+1k8pkdyew

What about the ones that are unknown? ☹️

by
| | Reply
Post ID: @az+1k8pkdyew

@av the worrying part is 2 KNOWN people were fired

by
| | Reply
Post ID: @ay+1k8pkdyew

everyone relax. if you merely saw confidential information, no one cares. just delete it and move on, like you would with any other confidentail information you might stumble across doing your job. don't share it though.

by
| | Reply
Post ID: @ax+1k8pkdyew

Corporate common sense 101... You don't mess around on company servers, especially when it comes to listing names of laid off people. Termination is not only legal but appropriate.

by
| | Reply
Post ID: @aw+1k8pkdyew

@at 2 ppl were fired for posting

by
| | Reply
Post ID: @av+1k8pkdyew

@as But that's not the person who was fired. The person who was fired posted the name of the group. The person who posted an excel doc with that information you're talking about was not fired.

by
| | Reply
Post ID: @at+1k8pkdyew

@ar someone literally posted a full list of actual names. It was not up long before it was pulled down but it was definitely a list of actual names. Definitely misuse of Target information..

by
| | Reply
Post ID: @as+1k8pkdyew

@ap The original person was fired for posting the name of a distribution list/ad group. AD group names are not confidential, they are internal. Distribution list names are not confidential, they are internal.

security@target.com
ethics@target.com

These are all distribution lists in some form. Posting these should not get you fired. They are just as publicly discoverable internally but the members of the list are private. That isn't the case for the group name that was posted so it should matter even less.

Claiming this is about infosec is bogus. This is HR's fu-kup, security's fu-kup, someone in IT's fu-kup. It's an overstep to terminate someone for posting a name of a group.

by
| | Reply
Post ID: @ar+1k8pkdyew

@ap wish I could up vote this 100x. Spot on!

by
| | Reply
Post ID: @aq+1k8pkdyew

It was definitely grounds for termination. The employee accessed information they shouldn’t have and then it was a misuse of private target information. Doesn’t matter if the list was “only” shared internally. It was a pretty straight-forward open and shut case. If the information was meant to be shared it would have. You don’t have to be a genius to know this was grounds for dismissal and the person who did this was a liability to keep around. Obviously the don’t have common sense and do t have good judgement.

by
| | Reply
Post ID: @ap+1k8pkdyew

@a7 So fun fact TARGET DID PUBLISH IT, because they shared the internal mailing group. The employees were just using that. Same classification.

by
| | Reply
Post ID: @ak+1k8pkdyew

@a3 Do you have proof the information was confidential? It looked internal. Also thaat yelling channel has historically solved many problems so fu-k off

by
| | Reply
Post ID: @ah+1k8pkdyew

@ae Fu-k off with that. The data is available for any target employee to see. Slack and this data share the same classification, also the person fired posted no list. They only posted a visible group to a public chat, someone else got the list and shared it. This was 100% a move to stop people from getting information as to what happened.

by
| | Reply
Post ID: @ag+1k8pkdyew

Imagine surviving a layoff, where those let go were invited to a PRIVATE meeting to break the bad news, then sharing that list of TM’s via a link in a all internal Slack channel for everyone else to see, then getting fired for it? Even more alarming, people are defending them for such poor judgement. Maybe Target can bring back one of their peers to replace them.

by
| | Reply
Post ID: @ae+1k8pkdyew

@a7 bro morally the right thing to do is not pi-s off customer base then donate to Trump and also not lay off people before cutting executive salaries

by
| | Reply
Post ID: @ac+1k8pkdyew

@a9 FAFA for sure

by
| | Reply
Post ID: @aa+1k8pkdyew

Natural selection. Why would you make yourself a target on a day like today? Either Naive or ignorant to treat slack like TMZ. Did they think all the private meetings were scheduled like that for sh--s and giggles?

by
| | Reply
Post ID: @a9+1k8pkdyew

@a7 Target has long gone past caring about what's moral, why are they pretending to give a sh-t now?

by
| | Reply
Post ID: @a8+1k8pkdyew

@a4 if Target wanted to publish the name they would have, it’s not anyone else’s freedom to do so. Morally, it was the wrong thing to do.

by
| | Reply
Post ID: @a7+1k8pkdyew

This is so scary why can’t they just give us a break. I don’t even talk in the channel just lurk but I watched everything play out in real time ☹️

by
| | Reply
Post ID: @a6+1k8pkdyew

mind you shared only in a internal enterprise slack channel + everyone in that slack channel already has access to the website with the information

by
| | Reply
Post ID: @a5+1k8pkdyew

The distribution list that was used to email people who were laid off was shared. The distribution list itself is accessible to everyone internally on this site that you can use to access all distribution lists in the company

by
| | Reply
Post ID: @a4+1k8pkdyew

@a1 for sharing confidential info in a childish #YELLING Slack channel of all places. How fitting. Guess they didn’t take the info security training every year

by
| | Reply
Post ID: @a3+1k8pkdyew

@a1 They seem to have a hit list based on innocuous things people said in one of the company slack channels….

by
| | Reply
Post ID: @a2+1k8pkdyew

Post a reply

: