Thread regarding Wells Fargo & Co. layoffs

CSBB re-org - discuss

by
| 3474 views | | 12 replies (last July 2, 2023) | Reply
Post ID: @OP+1nntKvjx

12 replies (most recent on top)

Amazing how the most toxic and incompetent leader I have ever worked for got a sweet a-s promotion. Let’s leave that person nameless.

by
| | Reply
Post ID: @2uqo+1nntKvjx

@ekt+1nntKvjx

No. There is little organization right now. Everyone is getting pushed to the cloud with different timelines.

Director level management doesn't care about the chaos. They want check boxes saying they moved their stuff to the cloud. It's all about beating peer directors in those pretty little PowerPoint decks about progress in cloud adoption.

I've never seen such a d*ck waving contest in my 25 years here at WF.

by
| | Reply
Post ID: @1pbd+1nntKvjx

@bkb+1nntKvjx Don't the "project engineers" and/or the "architects" of the two teams coordinate with each other? Isn't there a product development charter with well laid out dependencies? Hey with all of this thinking it should be easy to throw it into the now AI equipped Service Now. In the end shouldn't we be thanking Saul for his forethought?

by
| | Reply
Post ID: @ekt+1nntKvjx

Corporate cronyism

by
| | Reply
Post ID: @ehx+1nntKvjx

So, 3 different DRs will be responsible for Branch, can't wait for that cat fight to commence.

A CSBB Technology LoB by another name will be set up, another cat fight.

Small Business will be become "Business" and include companies up to $25M in revenues....CB's bu-----e must still be raw from that fu----g, but at least they'll be ready and gaped when CIB goes for sloppy seconds and takes them over.....again.

by
| | Reply
Post ID: @bcd+1nntKvjx

Tech was affected.

Saul created and left an environment where teams are scrambling to make change. The problem is teams are not all independent of each other and rely on products other teams support.

I'll give an example to show what is going on.

Team A must rework their solution or produce a new one. They are given a tight timeliness, say 3 months. Team A is dependent on a product from Team B.

Team A rushes their work, then finds out Team B is changing their product in the very near future, but with a deadline 6 months down the road. That deadline is outside of Team A's deadline, so Team A cannot shelve it until Team B has the new product up and running. Team A has to meet the deadline.

Team A then has to turn around and redo their work for the new product Team B is implementing. Or Team A finds out they can no longer utilize the product Team B supports because it is missing critical functionality and Team A then has to engineer a new solution and get it up and running before the dependency from Team B is no longer available.

Tech has become a place of constant churn, work, rework.

The planning by leadership has been horrible.

by
| | Reply
Post ID: @bkb+1nntKvjx

It's on Teamworks.
I'm in WIM and I'm a little shocked at JB, but good for her. KB was a carryover from the Kowach days, so I'm shocked she lasted this long.

by
| | Reply
Post ID: @djo+1nntKvjx

All Wells Fargo non-JPM senior folks have been getting pushed out one way or another since Saul showed up. His strategies are nothing but BS designed to promote himself. Customers are still leaving in large numbers. Soon only Saul yes people. Just look at Tracy Kerrins leading tech with no tech knowledge. This where the bank is going.

by
| | Reply
Post ID: @buc+1nntKvjx

Share some deets on the reorg, OP. We aren't all in CSBB.

by
| | Reply
Post ID: @qaq+1nntKvjx

Sorry you have to live with Saul. He totally destroyed tech with too much change too quick. Now tech is paralyzed.

by
| | Reply
Post ID: @amq+1nntKvjx

agree with JPH, coincidence? I think not. Just making room to hire his own peeps. Yes men, so to speak

by
| | Reply
Post ID: @spo+1nntKvjx

Cleaning house. Amazing how many senior people suddenly decided to all retire at the same time.

by
| | Reply
Post ID: @jph+1nntKvjx

Post a reply

: