Yay another meeting where we will learn nothing...
11 replies (most recent on top)
most interesting will be to see if relocation packages are offered/not offered when multiple people in different location on the same scrum team are affected
It's slow because they want people to quit and giving up the severance. They know those who have long tenured would stay, but there more who leave would be money saved for the bank.
This is all way too slow. Does anyone believe they will gain anything by taking so long? It’s not like they are actually concerned about knowledge transfer, so rip off the bandaid and move on. Btw, I am remote, not in hub location and not in wave 1 , so I’m bummed.
Maybe they will introduce a wave ver. 1.2.
It should start this month. 60 days warning, employee but kicked off network. Then getting our butts kicked out the door in April. That lines up with Q2 layoff. Buckle up kids.
Wave 2 starting in April
what they mean is people who are going to be affected in wave 1 have been notified now. they will then receive more information sometime in may.
Isn’t wave 1 supposed to start Q2?
Wave1 is now, when is Wave2?
If all remote are chopped in wave 1, my team is sc--wed. And it will directly impact the new data centers effort.
Some other folks I work around in tech went to the meeting for their area a few weeks ago….wave 1: remote workers, wave 2: locs w/less than 15 tech resources, additional waves hit locs based on # of resources from lowest to highest until all non-hub locs are wrapped up. Beyond going over what’s already been comm (displacement,reloc,exception scenarios) that’s about all that was covered.