LinkedIn's "Kill List" – How to Ensure a Great Weekend

<p>In a more contemporary version of the old “Reply All” disaster, LinkedIn
employees found themselves in an awkward position recently when an internal
list of approximately 500 names became accessible to anyone within the company.
Obviously, the discovery triggered panic among workers who feared they might be
for the chop. Turns out, they were right.</p><p>Mysterious List Emerges on GroupID Tool</p><p>This startling revelation came about when a LinkedIn employee posted on
<a href="https://www.teamblind.com/post/LinkedIn-Layoff-508-in-Engineering-tWCmUs8h">Blind</a>,
an anonymous job-posting site that verifies employment via company email
addresses. The post referred to a potential "kill list" of employees
slated for upcoming layoffs.</p><p>Rumors began to circulate within the company following the Blind post.
The LinkedIn employee who had posted on Blind noticed a new list named
"OctoberUpdate" on LinkedIn's <a href="https://www.imanami.com/">GroupID</a>
tool, a third-party system. The tool enables employees to add themselves and
others to teams, manage group calendar events, and <a href="https://www.financemagnates.com/terms/e/exchange/">exchange</a> emails. </p><p>The list contained hundreds of names, causing a frenzy among LinkedIn
workers. Although it hasn’t proved possible to independently verify the list's
completeness, a LinkedIn spokesperson confirmed the <a href="https://www.entrepreneur.com/business-news/linkedin-employees-found-a-secret-layoff-list-with-500-names/463891">company's
use of GroupID</a> to create and manage distribution lists.</p><blockquote><p lang="en" dir="ltr">On Oct. 16, more than 600 LinkedIn employees were laid off after an internal "kill list" went public. <a href="https://t.co/J3hULDdJKd">https://t.co/J3hULDdJKd</a></p>— Black Enterprise (@blackenterprise) <a href="https://twitter.com/blackenterprise/status/1714336007019970973?ref_src=twsrc%5Etfw">October 17, 2023</a></blockquote><p>Access Denied and Unexplained Tool Glitches</p><p>The GroupID tool became inaccessible to LinkedIn staff on Sunday, and
many encountered slow loading times, which no doubt helped their anxiety no end.
The exact cause of the internal tool's inaccessibility remains uncertain, but
it is believed that a surge in user traffic led to the slowdown. Obviously, if
you’re concerned you’re on the list, you’ll be rushing to check it. </p><p>A wonderfully-worded email (that was seen by <a href="https://www.businessinsider.com/linkedin-employees-learned-layoffs-early-list-blind-post-2023-10">Business
Insider</a>) was sent out at 4 am by the company’s internal comms team:
"We've heard that you may be experiencing issues accessing Go/GroupID. We're
looking into it and appreciate your patience as we work through the issue.
There is no ETA at the moment."</p><p>What a response.</p><p>Lessons in HR?</p><p>LinkedIn eventually confirmed the layoffs, impacting over 600
employees, and sent a company-wide email to communicate this decision, which
was nice of them. Now everyone knows you’re gone. </p><p>In this situation, many LinkedIn employees found themselves in limbo, awaiting
an email to determine whether they were among those laid off. Those who
received notices had to attend meetings to discuss the logistics of leaving the
company.</p><p>LinkedIn assured impacted employees that they would be treated with <a href="https://news.linkedin.com/2023/october/october-2023-update">care and
respect</a> during the layoffs. How about not posting a list of soon-to-be-terminated
employees where it can be read by all?</p><p>The key to all this is to, perhaps, be a little more careful over where
you’re saving your documents, in an age where we all use communal, online
tools, perhaps we’re becoming a little lax.</p><p>We’re off to check what’s sitting in draft on our backend, or perhaps our <a href="https://www.financemagnates.com/" target="_blank" rel="follow">homepage</a>.</p>

This article was written by Louis Parks at www.financemagnates.com.

Leave a Comment

Leave a Reply

Your email address will not be published. Required fields are marked *