Thread regarding State Farm Insurance layoffs

ET Migration Stabilization Office - A JOKE

Wth - we talk all about reducing cost and producing more business outcomes from ET yet we let the idiots in MSO decide what a great idea it is to go through a JOP process that has inundated analyst and managers with absurd postings...1,000’s of JOPs filed for handfuls of jobs and still no real work being done..: Maybe MSO leadership should of “competed” for theor jobs!!!

by
| 2553 views | | 10 replies (last April 15, 2018) | Reply
Post ID: @OP+SExyRIN

10 replies (most recent on top)

ECS was crap! The crappiest of the turds! Before that was reflections from the stone ages. How did I do Idiot?

How did you do at what? Making a point or making it clear who you were responding to? At both things you failed miserably.

No one has any idea whatsoever what you're talking about. I highly doubt anyone cares.

by
| | Reply
Post ID: @3rbz+SExyRIN

ECS was crap - a crap decision from business to buy a crap application from Accenture and force it into the State Farm infrastructure. If Systems had been allowed to deliver their design, it would have been better, stronger, faster, and cost less.

by
| | Reply
Post ID: @3ojt+SExyRIN

ECS was crap! The crappiest of the turds! Before that was reflections from the stone ages. How did I do Idiot?

by
| | Reply
Post ID: @3scm+SExyRIN

Bill Gates could have written State Farm code when he was 5 years old. A toddler could. Wasted time and lots of $$$$$$$$'s.

You're an idiot.

You have zero idea what you are talking about, and are clearly trolling. If you think all that code is wasted time and money, pull the plug on it and watch what happens. The entire company would come grinding to a halt. It would make this current re-organization look like a picnic in the park.

by
| | Reply
Post ID: @1kbo+SExyRIN

Bill Gates could have written State Farm code when he was 5 years old. A toddler could. Wasted time and lots of $$$$$$$$'s.

by
| | Reply
Post ID: @1gqb+SExyRIN

@iegr. Absolutely correct!

by
| | Reply
Post ID: @1yxp+SExyRIN

Has Systems ever delivered anything?

Yes. State Farm has the second largest privately owned network in the country. All that hardware did not assemble and configure itself. And the amount of data crunching that takes place on that hardware daily would blow your mind. There are millions of thousands of lines of code on platforms ranging from Linux to Windows to Z/OS. Some would call the latter "technical debt," but it's the glue holding everything together in quite a few departments.

Prior to CDE, Systems projects ran remarkably smooth. Yes, they were wasteful (in typical State Farm fashion), but most of that waste at the time was the result of over-specialization, which was a direct result of the last big re-org. But in any case, wasteful though they were, these projects had a better than average (as compared to the industry) track record of delivering what the business wanted on time/budget.

The biggest issue in Systems prior to CDE, as far as I can tell, was over in Corporate (not Corporate South), where business managers would often disagree about what should be in scope, and if one Chief didn't get what he wanted (even if he was contradicted by another chief), the reputation of the whole Systems unit suffered.

People often try to argue that the problem with Systems was that it wasn't "modern" enough. But the truth is, modern was never a priority among the people controlling the purse strings. If they had truly wanted "modern," it could have been give to them.

And while CDE certainly threw lots of money at the modernization effort, the leaders didn't really want modern. They wanted stuff done "fast," with no regard for what would truly be required to realize the vision of CDE/ICP. So fast is what they got. Plus, they made it impossible to get anything done at any pace with their mindless re-org of everything under the sun.

CDE torched Systems. We became bloated and bogged down with a bunch of business people who had no Systems training and who were, remarkably, expected to replace our seasoned business analysts. This didn't work. Hence the executives are now busy burning down what they've already destroyed.

And I have to say, even in the midst of all this turmoil, State Farm implementations are remarkably smooth as compared to what goes on in most organizations. I've worked in companies where implementation was a three week fire drill of catastrophe. That never used to happen at State Farm. Since CDE, it happens more than it should though.

by
| | Reply
Post ID: @1egr+SExyRIN

Has Systems ever delivered anything? Seems they just deliver large invoices from vendors. No results =more money

by
| | Reply
Post ID: @1ueq+SExyRIN

Everyone knows that Systems isn't going to get anything don for at least the next 18 months. Yeah, they'll deliver some crap (and a frighteningly high percentage of it will be just that), but Systems has been a mess since CDE and was only beginning to stabilize when the executives decided to screw it up all over again.

by the way, not everyone cut was spending their days generating "red tape." Quite a lot of us were producing a work product that Systems is going to have one helluva time replacing. I was a Java developer with a lot of application-specific knowledge, but I was purged because I was remote and unwilling to relocate. The Systems I was responsible for are how swinging in the breeze.

by
| | Reply
Post ID: @gvt+SExyRIN

They've been given an impossible task. Playing cross-country musical chairs with analyst positions is bound to cause disruption. Especially when they're removing a lot of chairs and not addressing the (often unproductive) work those people do. If it's not adding value, then get rid of it.

The second half of the year is going to be untrained analysts spending their time trying to learn their new roles while trying to work through all the red tape garbage that the cut analysts were doing.

We're being told to wrap a lot of work up by July 1 because of the uncertainty

by
| | Reply
Post ID: @oai+SExyRIN

Post a reply

: