Thread regarding Wells Fargo & Co. layoffs

Change Management

Wonder when WF will understand what rest of world does on Change management?

Process is long archaic and originally put in place to not break stuff, but things still break. This process need to be removed permanently, stage coach days are over, world has changed a lot since those days.

today, need to use automated process, devops process; if something breaks can fix faster than to back out. I would fire everyone here in change management, they are obsolete. Get rid of this archaic process, like companies that are successful did, much larger companies than Wells. Cant take months and weeks for this bottleneck in the company, holding it back from success.

by
| 1553 views | | 10 replies (last June 5, 2021) | Reply
Post ID: @OP+1baJZw23

10 replies (most recent on top)

Look, you can try to change the management but unless the management wants to change nothing is going to change.

by
| | Reply
Post ID: @2wxj+1baJZw23

Oh look, another "Change Management is the problem" post by the same person who started the 50 other "Change Management is the problem" posts.

Learn to fill out a CR properly the first time and your complaints will disappear. Learn to work out the bugs in your code before going into production. Bottom-of-the-barrel developers is a huge problem here. Wells pays down for lack of talent because it's "efficient".

Which "much larger than Wells" companies, which are just as heavily regulated as a Bank are you referring to?

by
| | Reply
Post ID: @1gwa+1baJZw23

Well if you write an application, then you are also supposed to go through BCP testing. It is easier just to stick to a single point of failure

by
| | Reply
Post ID: @xhb+1baJZw23

@wxn+1baJZw23, lol - Access databases, Op here, its worse than I thought!

by
| | Reply
Post ID: @qte+1baJZw23

For their convenience and job, all across Wells Fargo people are obsessed to dependencies on doctoring reproducing templates, procedures and reports in words doc, excel spreadsheets and access database, sharepoint files and so that have been like we are stuck in manual processing recycling garbage. We got to get out of that low tech business environment now.

by
| | Reply
Post ID: @thl+1baJZw23

So rather than have a small team maintain a simple CRUD application, you have extra labor hours spent on maintaining, downloading/uploading and possibly overwriting people’s changes to a document. That’s more efficient after the layoffs.

I swear it’s like a disease here

by
| | Reply
Post ID: @vox+1baJZw23

Hard to maintain something with all those layoffs and no script for the offshore to follow.

by
| | Reply
Post ID: @aix+1baJZw23

@wxn+1baJZw23
You use Access databases? Well, aren’t you fancy, we just keep updating the same spreadsheet and uploading to the wiki. “It works well enough”, they say. “If you write an application you just have to maintain it.”

by
| | Reply
Post ID: @jit+1baJZw23

Considering a lot of the rest of the world crams it in, regrets it later and the he-l with customer service, not sure that is an improvement.

As I said before, be a leader not a follower. Too many followers in the new management they bought in. Don’t forget this stuff failed at Chase before they finally fixed it.

by
| | Reply
Post ID: @geo+1baJZw23

Totally agree with this post. Also automate the EASP process. Bottlenecks this can cause also delay releases. Our technology is about 20 years behind in most divisions in this company. We still use access databases!

by
| | Reply
Post ID: @wxn+1baJZw23

Post a reply

: