I know there are small layoffs at WFC all the time, but today seems to have been different. I know of at least three different areas that were hit and I see some more mentioned here. This worries me because there was zero mention of a more significant round and yet here we are. Just more fodder for my anxiety.
28 replies (most recent on top)
What does "clicking the button" to deploy the code have to do with code quality/issues? The code doesn't change when you deploy it, that is software 101. Does anything in the current CR process help catch those types of issues?
did a spot check - DBAs, contractors, Clearing Services, Software Engineers, Customer success, Retirement consultants, tellers
“It doesn’t matter who clicks the button.” Wow...just...wow.
I guess we don’t have to wonder anymore why we keep having problems with our code.
I have no problem with a paper trail... I have a problem with the fact that it takes 2 weeks using software from 1992 and dozens of stupid fields to fill out to get my paper trail created. Every damn click we make is logged and tracked, everything has an audit trail. My CR should have a date/time and link to the deployment to be done. That deployment has links to everything and anything an auditor could want to know, it doesn't matter who clicks the button.
It sounds like there is a problem with someone who doesn’t like a paper trail when our regulators expect one. You just can’t drop whatever you want into production anytime you want like the cloud in a place of business under regulatory scrutiny. Good lord people, I wish you all you think before you hit send, seriously.
I wouldn't complain about the CR process, except it adds no value to the products I deploy and takes entirely too long. How do people who know nothing about my products/customers tell me when to deploy things? For an activity that literally would take me two hours to install in Production, I have to spend two weeks filling out paperwork, so I can spoon-feed the process to someone over a chat anyway. Have your app in the Cloud? Deploy when ever you want... If your app isn't resilient, that's tech team fault. The CR process sure as he-l won't catch that.
Maybe you should build a relationship with your change coordinators. Understand what they are looking for instead of fighting and complaining about them. It will make your life less stressful.
There should be standard CR templates with a few fields, mostly those for time and date. That would be true templating.
@1ccm+1aXIXyiE. Again, I don't understand why you cannot comprehend that we have templates for every single CR. Templates that were agreed upon in meetings with the Change Coordinators. Then some dim bulb Change Coordinators will still arbitrate on agreed upon verbiage.
You keep creating strawman about the quality of submissions. Maybe you are lucky and your LOB Change Coordinators are not like this. But ours are.
Some people do the work and some people slack off and collect a paycheck. I think you just told us where you were.
"...50 hours a week.."
That is funny.. I haven't worked a full 40 hours since I started here... Why? There is nothing going on in our area of ICS aside from work creation to show value.
@1kdp is whining about people being unable to change, but all they are doing is sitting here complaining that they have to change their own behavior.
Again, as I've said before, learn to clearly communicate your change request text (I've opened more CR's than most people) and you won't have an issue. Every field has an expected format and people just hate taking the extra 10 minutes it takes to alter their hastily typed up blurb into a professional, clearly worded format.
Upper management could easily be automated away. I could easily write a script that would do everything Chainsaw, SVB, or any of the other bigwigs says in a town hall meeting or AMA. Heck, coding is manual, we should automate that away as well.
Some of the arguments on here from the dead weight/change management are the only problem/rip your career id--ts are hilarious with how lacking they are in self awareness.
@1yva+1aXIXyiE It still goes right back to the Change Coordinators no matter how you want to spin it. We spend time standardizing templates with the Change Coordinators to avoid arbitrations. The entire point is to cut down on wasted time.
And it still doesn't matter.
Then we will have locked CRs with most of the approvals done and get a notice from Change Coordinators that want something different and those CRs in flight get arbitrated and have to be changed, sometimes requiring them to be reopened and approvals sought again. It's really not cool when it is a CRL1 that requires coordination on dates with other teams. Especially when you know, you already met with the change advisory board.
Then the process starts again of having to work with them to sign off on our templates.
Change Management as it is today is the opposite of agile.
If differing CR requirement interpretation by that team's various analysts is all you have I rest my case. There are hundreds of other more important problems to fix at the bank than CR requests that lack accurate details. This goes back to employees who don't bother to strive for excellence.
@1uxy+1aXIXyiE. That is a cop out excuse. It was the same verbiage used by everyone else, even CRs put in after that were not arbitrated.
There is little standardization in Change Management. It is all about who looks at it.
We're all human and make mistakes. Perhaps the process of putting changes in needs improvement. Another set of eyes on the CR details before submitting should be in order for each team. While I agree someone could have figured that out, consider the scrutiny the bank is under by regulators. Regulatory institutions don't do subjective interpretation.
For those of you who've been doing manual tasks for the last several years you'll be gone soon. It may not be your fault, most of our low to mid level managers have zero ability to think strategically and have likely caused you career harm within WF. That being said, hopefully you all take this moment to consider some personal career responsibility that we've all fallen so far behind our industry standards on all levels that you'll do something about it. Don't complain that you stuck your head in the sand, didn't know what was happening, and blame current/former management. Change is never easy, it must happen, and we should all embrace it.
@1flq Some of us are already putting in at least 50 hours a week and we just lost valuable teammates. So now, we will have even more work to do.
Then we have id--ts in change management who do little but come up with ever changing requirements for CRs, so they can keep their arbitration numbers up like they are actually doing useful work.
To give you an example of the stupidity, a coworker just had a CR arbitrated by a Change Coordinator. Within the CR. He had a start time listed of 9:00PM ET. Then he had a description saying it would take approximately two hours from the CR start time...
Bo-m.. Change Coordinator arbitrate and asks for the CR install window.
It literally says Start Time 9:00PM ET. And that the install will take approximately two hours from start time.
But it didn't say. 9:00PM ET - 11:00PM ET.
So he had to waste time responding. Any id--t could read his description and understand what it meant. But this is what these clowns do all the time so they can show up on reports and make it look like they are helping prevent system issues.
Chainsaw is weak...we need big changes and we need them fast. All the dead weight(you know who you are) need to be gone immediately. These folks are whining, not getting anything done, and this slow reduction in force is causing what decent employees we have to leave.
What about SORM? I heard that they were hit hard
Billing QA was another area impacted.
Not enough...
69,420
I see that few Project Managers and Project coordinators were laid off. This is within CLT.
Other than IAM, what groups are impacted that you know of, OP?
Between 0 to 250K. Your pick
Seriously you expect someone here knows the answer? SMH
No one knows. They laid off too many IAM folks to get around to ZZing everyone.
A common sense approach would be to make the cuts to the teams who add and remove employee access AFTER the layoffs are pretty much wrapped up.
But you know.. WFC, so everything is done backarsewards.