Thread regarding AT&T layoffs

Delay in RTO (a/k/a layoffs)

Some groups were expecting RTO (layoffs) to be announced Friday, June 16. It’s been delayed at least a week. Why? ‘Cause uncertainty, protracted poor morale and low productivity are a “clever” way to do business, amirite?

by
| 1928 views | | 7 replies (last June 16, 2023) | Reply
Post ID: @OP+1n9aTvRV

7 replies (most recent on top)

“The 6/22 surplus is no rumor. It is happening. If your group is affected you have been informed. The names have been chosen. Notifications are on 6/22 and off payroll 7/6.“

Just because you have not been informed, does not mean you are not affected. There were people in Anthony’s org last round that never had a “you are in an effected work group call”, but got the call telling them they had two weeks left with the company. It all depends on what sh*thead you report up to.

by
| | Reply
Post ID: @rbc+1n9aTvRV

The 6/22 surplus is no rumor. It is happening. If your group is affected you have been informed. The names have been chosen. Notifications are on 6/22 and off payroll 7/6.

by
| | Reply
Post ID: @hul+1n9aTvRV

Our group isn’t having explicit layoffs. RTO, which is intended to force quitting, is what will occur. And that is delayed until sometime before the end of the month.

by
| | Reply
Post ID: @kbq+1n9aTvRV

You are mixing two events. One is a surplus rumored to take place on 6/22. The other is the RTO / relocation for some/ new occupancy indicator notification. While some consider RTO a surplus, these are two different events. The RTO event is rumored to have been delayed til the EOM.

by
| | Reply
Post ID: @jxe+1n9aTvRV

The updated/reduced severance policy is still needing its final review.

by
| | Reply
Post ID: @oqo+1n9aTvRV

Bad planning? You give them far too much credit. There was ZERO planning. May 15ths email was the entire plan at that time. Just an executive order. This is not unusual.

by
| | Reply
Post ID: @veu+1n9aTvRV

bad planning, it's the AT&T way.

by
| | Reply
Post ID: @mnj+1n9aTvRV

Post a reply

: