Thread regarding Wells Fargo & Co. layoffs

Who messed up COVID Return to Office Communications?

Everyone seems to have heard a different message. Ultimately I would have to think that HR dropped the ball. HR is probably the most unorganized department although Corporate Communications rivals them in that aspect.

Does anybody know who dropped the ball here?

by
| 3670 views | | 21 replies (last ) | Reply
Post ID: @OP+1efzKbVe

21 replies (most recent on top)

@2xyg+1efzKbVe

In case you’re not aware, “Center of Excellence” invariably indicates that 80% minimum of the work will move offshore. Charlie has actually done this in his last 3 companies, all of which were run into the ground.

by
| | Reply
Post ID: @2goa+1efzKbVe

Its more of a mandatory invite. Invite is a polite request.

by
| | Reply
Post ID: @2ner+1efzKbVe

Who in tech got the definitively going in the office email only to see on TW today that tech is now invited to RTO? Which is it?

by
| | Reply
Post ID: @2oos+1efzKbVe

The blame lies with Corporate Communications, Bill Daley and Barri Rafferty. She let go of most of internal Comms and then a huge amount of employees quit or left for better jobs -including the head of Employee Communications who ran for the door because working for Barri is terrible. Brilliant Barri created a “Center of Excellence” for Employee Communications. Our internal Comms is far from excellent and far worse than it was a year ago.

by
| | Reply
Post ID: @2xyg+1efzKbVe

As mentioned above. The change in order has nothing to do with customers and collaboration as they have been spouting for the last 22 months, as CF naturally would be the first ones to return. It has everything to do with vax vs non vax statuses. NCF roles are vax at much higher percentage rates than CF roles. They want someone in a seat come 1/10 they don’t even care if it’s the wrong group based of customer interaction. They want to tell the board and shareholders someone came back. Do not believe what they are saying. The flip in RTO is only due percentage of vaccination. They are not even sure how they are going to bring CF back at how low the rates are. They were absolutely shocked at how low the rates were, which is crazy to me bc typically NCF roles education requirements are higher. There is definitely a correlation to education levels and vaccination rates. The fact it took them to Dec to realize the correlation is insane to me. As a result they scrambled and change plans last minute. It caught management completely off guard. It’s hard to manage communications with middle of the night decisions.

by
| | Reply
Post ID: @2jsb+1efzKbVe

This is sadly hilarious. We have no talented leaders who can either plan or communicate.
How long before the regulators slam on the brakes for us?

by
| | Reply
Post ID: @1rxi+1efzKbVe

@1dfi+1efzKbVe

Just because Schart is remote doesn’t mean that he isn’t working. But apparently he isn’t achieving any deliverables for WF.

by
| | Reply
Post ID: @1pmk+1efzKbVe

I tend to blame the board and then Charlie. Charlie started at the top and stayed there, never really having managed anything outside of his own net worth. But the board hired him and these folks really should have known better. We are now what… over two years with him and zero achievements?

by
| | Reply
Post ID: @1kxh+1efzKbVe

Part of the problem is that there's been so many 'fake RTOs' / cry wolf situations that a lot of people see an email about it and just shrug and move on, not even bothering to read it. Why invest the time when it isn't happening anyway? Naturally this leads to chaos when it finally does happen.

by
| | Reply
Post ID: @1zgt+1efzKbVe

My friends in HR and CPG told me that they decided to flip the order because call center and tech ops people are less vaccinated and also it would be easier to pull the plug on RTO before they started going back. That created a huge mess because the businesses weren't ready for the changing dates because nobody gave them any warning it was coming. The big fail is with Scott and Charlie and their little circle of suck-ups because they all believe in sharing as little as possible about why they decide to do things and they think the other execs and the rest of WF employees are basically id--ts and should be treated as silly little children.

by
| | Reply
Post ID: @1wsh+1efzKbVe

they've had how much time to sort out a plan? I get that there needs to be some flexibility given the ever changing pandemic but at least have a plan in place that can be implemented when ready. and when was the last time we heard anything from CS? Does he even work here any more?

by
| | Reply
Post ID: @1dfi+1efzKbVe

I'm fairly certain that each department was in charge of their own sc--w ups. HR certainly was last to communicate (literally the email went out Friday at something like 3pm Eastern Time). If HR was in charge of all the emails, all the groups would likely have felt that same impact. 24 hours was great compared to what HR got.

by
| | Reply
Post ID: @1nvt+1efzKbVe

I heard tech was affected

by
| | Reply
Post ID: @1etc+1efzKbVe

If I did ask what would you say?

by
| | Reply
Post ID: @1vyr+1efzKbVe

No, you may not

by
| | Reply
Post ID: @1pwh+1efzKbVe

May I ask what happened?

by
| | Reply
Post ID: @1gdt+1efzKbVe

@1gqo
What confusion happened outside of tech? I didn’t realize the other leaders were also scrambling. What a mess!

by
| | Reply
Post ID: @1dlz+1efzKbVe

All the senior leaders were scrambling to clarify after SP's message came out about the updated schedule of events. It took over 24 hours before we heard from our leader. I don't know if anyone dropped the ball or if this was an intentional move to exert power (a big FU essentially)

by
| | Reply
Post ID: @1gqo+1efzKbVe

People hear what they want to hear near as I can tell and reading comprehension doesn't seem to good either. Add that to poor communications and there it is.

by
| | Reply
Post ID: @1bxv+1efzKbVe

The magnificent SVB dropped the ball.

by
| | Reply
Post ID: @1vxd+1efzKbVe

Please.. those in the know only…

by
| | Reply
Post ID: @awi+1efzKbVe

Post a reply

: