Discussion about this post

User's avatar
Elaine May's avatar

Unfortunately, I've been through a lot of layoffs since 2001 including 4 consecutive rounds over 4 quarters that ended up laying off 85% of our engineering team. I definitely echo the "cut once, cut deep, cut decisively" advice. Not only is it incredibly disruptive to have a layoff every quarter, it also ties up senior leadership in deciding what to cut and what to keep. Finally, if you move people from project to project, you incur a learning period every time.

The other advice I would give which I don't think was mentioned is to have a contingency communication plan in case word leaks out early in the process. I was not part of nor affected by a layoff in 2020 that leaked early due to people's system access being cut off prior to them being notified. Managers (like myself) were asking for guidance/information, but that was not part of the schedule so we weren't informed until several hours after the news got out.

Expand full comment
onionking's avatar

I thought you are going to use Better layoff as example.

Expand full comment
4 more comments...

No posts