Fire Jeff Smisek Facebook Page (LOL)
 

There is a fire Jeff Smisek facebook page in case anyone wants to take a look at it.

https://www.facebook.com/#!/groups/321572711266692/

Coincidence that "666" is in the number of the group page?

-RM

Just joined....this page is off the hook!

Him and his CIO (Chief Information Officer). Unreal; we're almost two hours into their worldwide system outage. This has to be costing them millions of dollars...

Are we taking bets yet? I say not before 4pm PST (didn't want to start a new thread) edit: And just found the main thread, looks like I lost that bet lmao.

True. But don't forget how much they saved by switching to SHARES!

I've said it before and I'll say it again. The decision to use SHARES should cost many people their job, starting with Smisek, then all the other Exec and Senior VP's that too sided with this decision. Pick another industry to work in.

+1

How much money do they save with SHARES?

How much money is lost due to system failure, lost revenue and extra human costs? :confused:

SMI/J and his gangs who made the SHARE decision should be fired.

Good idea. I just joined.

The way this usually works is that the managers who make these decisions design the metrics to provide the outcomes that they want. So, they measure the savings the way the want to measure the savings, and they fire anyone who suggests measuring the costs, such as those you have articulated.

The beauty of this system is that the managers who make these decisions get to congratulate themselves on a job well done, get promoted, and collect huge bonuses.

I've got no insight into the reality at COdbaUA, but this is how I've seen similar things play out in other organizations.

I personally think this was a planned outage, wanting to give everyone worldwide a manual IRROPS lesson and in preparation for this Winter season. In other words, OTJ training. Can't get ready soon enough.

A strategic by-product is it also gives Smi/J plausible deniability on August DOT complaints, On-time performance and Revenue misses. Based on what everyone is posting about their accounts, it sounds like they had to load in a back-up from who knows when. I bet it could take a while for them to fix all the data corruption, which could mean several days of, pick a flight, any flight and pick a seat, any seat.

Mainframe guys out there. Doesn't this kind of system usually have a back-up procedure, or is that what we just saw in 2-3 hours?

Also, based on what some/most of us have experienced since 3/3 and the occasional system outage since then, there is no doubt this is a very unstable system. Meaning, this isn't the end of it. Dollars (revenue and expense) will continue to be sucked out of the business over some period of time until better minds prevail. Can't wait.

It's cute, but I have better things to occupy my time with. Seriously, do we really need another site to post endless rants on? Whatever.