Project Management at Wells Fargo

Seriously - this is how it works:
Problem - 10 managers find an issue and assign it to an engineer
Said engineer says hey how can this be, I need help
A project is spun up - adding a bunch of service managers and their bosses
50 folks from risk management say this can't be without process
20 process staff weigh in and complain this is too fast, please we need more time
Lone engineer is given 30 different requests for information
Senior leadership is then updated on the lack of response from said engineer
Engineers Boss informed of low or non response of engineer
Engineer is given a PIP
Whole issue is now a section-wide directive to get results
Contractors are hired at 500/hr to figure out what went wrong
Managers are hired to watch over the contractors
Engineer says sc--w this and gets another job somewhere else
Contractors - after milking the system for 1000 hours says its not an issue
Managers of the contractors agree its "Job well done!"
Bonuses are given to the mangers for fixing the issue

and whatever it was....goes under the rug and all is well.......

Comment! It's anonymous!

13 replies (most recent on top)

This post is awesome! But is it really true of the project side of things? I see it in support and ops... consumer technology executives that just go around every single channel looking for issues to find AKA new teams to be spun up, more jobs to give. All because "women in technology" initiatives got them an exec position after career long rubber stamping exactly how it was described here.

Mangers finding problems is a joke. They can't find their a-s-s most of time and really only care about the money. Most were poor developers.

As an IT PM I can say this is true in some cases.

Not all, but some.

I blame upper management for reading white papers on subjects they do not understand, but think they do because mommy and daddy paid good money to get them an ivy league school they couldnt' get into based on their grades and that sheepskin on the wall is super real.

Also, Agile.

(I just like saying Agile because it's an action filled word that makes me sound like I'm driving the company forward and raising the ROI of the shareholders, maximizing shareholder value, and other stuff I read in a white paper that I didn't really understand).

You forgot engineer has no idea about the business because they laid off anyone who understood the business that he might have gone to.

Not that his code would get tested properly anymore even if they did find a solution because they got rid of those folks too!

Maybe because WF engineers always come back with excuses instead of solutions? Work against the folks assigned to help instead of working with them?

Needs to be a step in there for "Engineer suggests options to managment", followed by "All options ignored, and Engineer reprimanded for using the wrong tone of voice in communication to management".

didn't someone post this same thing a few weeks back

total bs

This is so ridiculously true I'm shook

I have such deja vu reading this post. I can’t figure out if it’s because it’s been posted before or I’ve lived through the exact described insanity so many times.

oh man this is so funny!! While being a repost, its still rolling on the floor funny! Thanks to whomever dug this back up!!

I do believe that there is truth to this, but I am not sure how much.

This describes so much at this company (and you can easily replace engineer with many positions).

Thread regarding Wells Fargo & Co. layoffs

Project Management at Wells Fargo

13 replies (most recent on top)

Post a reply