Fantasy Football Flub Fair Flamer For Yahoo IT?Fantasy Football Flub Fair Flamer For Yahoo IT?

Another hard lesson from the Yahoo Fantasy Football Debacle: Customers Come First, Last, AlwaysA very real server glitch in the Fantasy Football world at Yahoo Sports on all-important draft day has hard-core customers angry and looking for answers. The bigger question: Does this point for the need for CIOs to map out "customer-critical" events such as this NFL fantasy draft day to ensure that during these times of heavy demand, customers enjoy outstanding online experiences?

CIOs often talk about "mission-critical" issues such as uptime, security, privacy, and such, and those are certainly valid. But here in late 2007, they're also assumed by customers to be table stakes. In the world outside the enterprise, the more-vital concern is becoming "customer-critical" issues: for example, online shopping just before Valentine's Day or Mother's Day, or airline-ticket reservations and purchases around Thanksgiving and Christmas. Or in this latest case, the day before the NFL season opens when many hundreds of thousands of online customers are deeply engaged in interactive sessions to draft players for their fantasy teams. Because the fallout from a technical glitch during these times that customers view as critical can be at best ugly and at worst damaging to a company's reputation and its bottom line.

Discussing the terribly timed Yahoo outage, a fantasy football fan who also happens to write about investments for BloggingStocks.com had this to say:

Many companies might reject this notion of gearing up for these customer-critical times because, they'll say, "we're bullet-proof all the time." Well, I'm sure Yahoo thought it had was up to and probably beyond that level of fitness -- but that won't change the impressions of customers who feel let down, treated badly, and ready to look for alternative suppliers. It's even a promise made explicitly on the Yahoo Fantasy Football home page, where in a big banner across the top of the page, a tagline under the logo says, "We don't drop the ball." And 99% of the time, I'll bet Yahoo is accurate with that claim -- the problem is, that other 1% happened to occur during a time of monumental importance to Yahoo Sports' customers. So the big question is, was that also a time of monumental importance to the Yahoo IT team? And does this situation offer a lesson to all CIOs about the need for becoming powerfully focused on not only traditional mission-critical issues but also the newly ascendant issues that are customer-critical?

Anyone mulling that question should heed these words of the BloggingStocks.com writer quoted above, who also said this:

(Thanks to my colleague K.C. Jones [[email protected]] for her work on the original story posted on information.com yesterday.)