Thread regarding Wells Fargo & Co. layoffs

Exceptions

Seems to me that WF has adopted a stance where upon learning that a
technology / platform / process / practice is being retired the first words out of a team member's mouth is "how do I request an exception?". I've said it myself, many people have said it to me also. Even when I tell them the deadline is more than a year away, they're asking for exceptions.

Makes you wonder why/how RIFd people can't ask for exceptions as well, right?

by
| 1113 views | | 9 replies (last ) | Reply
Post ID: @OP+1t7JavLp

9 replies (most recent on top)

CSBB tech here. Five years ago we were told that we needed to eliminate tech exceptions. There were over 3,000 approved exceptions in Operations alone. Nobody had even identified all that were in the general bank at that time. More than Ops for sure. We went on a huge push to eliminate exceptions. Small almost useless apps, telecom exceptions, Operating system exceptions, etc. Made huge progress early on with some strict rules. Then came the business pushback, then the financial squeeze, before you knew it we were stopped cold. Try teaching India staff how to work the exceptions. Anyone wonder why payments sent major $$ to the wrong customers. Waiting on displacement here. Making small changes in the name of Agile that get moved to production but never activated. Sad that I cant even point to one business improvement to the bottom line in 2 years.

by
| | Reply
Post ID: @2hsp+1t7JavLp

The blame lays at the feet of the TLT who doesn’t take responsibility for anything and pushes blame down hill.

The TLT does nothing wrong, ever, in their minds.

by
| | Reply
Post ID: @1obu+1t7JavLp

Watch out. They are beginning to realize that these reactive "exceptions" lead to inefficiencies. Remember this place works on being reactive, not proactive. User testing not unit or integration testing. (expanding on @lxe+1t7JavLp) Everything is maintenance not creation. This place looks like it might become radio-active.

by
| | Reply
Post ID: @1mmz+1t7JavLp

Echoing other comments here. After 20+ years of working in Technology, only the WFDC image was a true triumph. Every single thing after is and was bunch of nonsense.

All we do is jump on ideas at the whims of management, duct taping this and that, rolling out whatever whenever, listening to customers complain and ask for exceptions.

Tech at WF is rotten to the core, as the bank does not care about its people.

Ask any tech manager, they live by fear of being identified as a source of friction by upper mgmt. It is much better to duck and cover, ignore pain and move on.

How is this a good way to run tech? How is it we can't talk about realities of the day while also serving up good wholesome solutions brought about on the backs of the technology professionals entrusted to act in best interest of the company?

There you have it. Zero trust in the people, thus zero trust in the technology. Exceptions don't bother me one bit and I hope the exception process is as painless as can be.

This freaking place.

by
| | Reply
Post ID: @1sgl+1t7JavLp

We ask because WF technology has never once rolled out an upgrade that was.

by
| | Reply
Post ID: @1gjq+1t7JavLp

This is the world we live in. Everyone thinks they're special.

by
| | Reply
Post ID: @chx+1t7JavLp

You say this as if it's something new. Exceptions have been a band-aid for as long as I can remember. They've simply added a bit more scrutiny around it, but not enough still.

by
| | Reply
Post ID: @ves+1t7JavLp

we ask because once rolled out it’s not going to work properly no matter how much “user testing” was involved

by
| | Reply
Post ID: @lxe+1t7JavLp

No different than the long-standing practice of escalating to get your way when someone tells you no.

by
| | Reply
Post ID: @gbz+1t7JavLp

Post a reply

: