Thread regarding Wells Fargo & Co. layoffs

Are processes and procedures in place for a reason or out of incompetence?

I paid more attention during the last week to how much time and energy I had to dedicate just to paperwork, following the specific procedures and compiling reports. Oh, and regular meetings. My estimate is 70% of the time. I’m not talking about the actual substance, just the procedure setup. The whole system is so obviously bloated by unnecessary steps, forms and other similar cr-p. I can’t even begin to think about possible reasons this would be by design. It must be incompetence and bad mgmt, right?

by
| 992 views | | 12 replies (last ) | Reply
Post ID: @OP+1uA1qCts

12 replies (most recent on top)

I just hope that they did something called DESIGNING before they role out these processes. With Design you can TEST and INTEGRATE the process. I recommend to all of us who are quietly quitting is that we go back to school and learn about modern day process design.
Topics such as hyperautomation, generative AI in process management (creation/optimization), automated business process discovery, Low-Code/No-Code BPM, Process Mining and Process Analytics, Agile BPM, Cloud-Based BPM, and Human-Centric BPM should be on you task list. Prompt "what is the latest ideas on process design and management especially for bank managers?" into you favorite AI chat bot.

by
| | Reply
Post ID: @bzu+1uA1qCts

They are changing procedures to make you stress. They want to burn you out so you'll quit.

They don't want to pay you severance.

They'll slowly lay off people and push the work to their peers. This along with knowing that you're at a dead end job will increase the chances that you'll quit.

by
| | Reply
Post ID: @jwu+1uA1qCts

We are legally required to have basic procedures that outline our processes. Does it need to be this complicated? Well, yes and no. Yes, since it had to be a thorough accounting of what the process is and detail every painstaking step. No, since it shouldn’t be this hard to run a report to check for X but think about why that is. So, there are all these manual controls in place because our systems and tech (ware not the people) are limited in their functions. If we could simply turn something on/off and not F up everything over there then no one would need to pull a report. The systems are the problem. This “firm” is too big. On top of that, you do have people trying to thing of ways to complicate things so they have “job security.”

by
| | Reply
Post ID: @aij+1uA1qCts

The processes are in place so that Sal can show off his shiny new (now old) ServiceNow acquisition. It got him ahead ... didn't it?

by
| | Reply
Post ID: @fsc+1uA1qCts

God ! What a cr-p ! Is it how it’s going to be ?? Time to find another role when market is up ! So much documentation and they have no idea what they are up to !

Wheh will you do the work ? Hours and days to find evidences for features you delivered 3 month back ! So much cr-p for some fall out last year ! You won’t stop with he fake accounts then money laundering what’s next ?? Who is suffering now ?

by
| | Reply
Post ID: @ygt+1uA1qCts

Most of the documentation I am directed to do is CYA to survive the never-ending internal audits. Artifacts, attach the email alert to that ticket then download that ticket as a .pdf...then upload that .pdf to DMS...

Yeah. 70% of tasks spent on documentation sounds about right on most days. Career dead-end. But beats asking, "Do you want fries with that?"

by
| | Reply
Post ID: @hla+1uA1qCts

Yet it’s called automation.

by
| | Reply
Post ID: @kej+1uA1qCts

What do you expect from teams that were told to handle 3x the work with 60% of the staff? We had to throw up process blocks to slow down the volume of work coming our way as well as enforce some standards just to slow down the amount of rework we have to do.

What you call useless process work may be a government/regulator/OCC requirement. Yes, one or two people can enact bad policy but if you want really bad policy, get at least 218 people to approve it.

by
| | Reply
Post ID: @urk+1uA1qCts

"Legacy employees who can’t wrap their head around this want it the old way where small teams knew and managed everything for their space so there were no impacts."

@qyo+1uA1qCts - dude it was never that way. the silos never "managed everything for their space". the silos had to collaborate and they did so horribly with alot of red tape and fingerpointing. Inside the silos the team members were at each others throats as well. Wells has just plain su-ked for a long time. I'm sick of hearing some of the old farts wax nostalgic about how things were better in the good ole days or pre-wachovia or whatever. It was sh1te back then too I'm sure.

by
| | Reply
Post ID: @ywp+1uA1qCts

It's by design, certain teams throw red tape in front of any request for them to do actual work. Welcome to the new order of things.

by
| | Reply
Post ID: @neb+1uA1qCts

It is because those who generate the ask don’t know what they are asking for. And those who execute have no idea what they are doing.

End result, customer impact and bad press.

All this is are growing pains. Wells is moving from silos to actual Organizational-wide big picture. And people don’t like change and they don’t like rules. Legacy employees who can’t wrap their head around this want it the old way where small teams knew and managed everything for their space so there were no impacts.

by
| | Reply
Post ID: @qyo+1uA1qCts

Neither. It's a scam make-work project for the functionaries and the leader to empire build.

by
| | Reply
Post ID: @kty+1uA1qCts

Post a reply

: