Commentary

Bob Evans
Senior VP, Global CIO  

Fantasy Football Flub Fair Flamer For Yahoo IT?

Another hard lesson from the Yahoo Fantasy Football Debacle: Customers Come First, Last, Always

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.


More Global CIO Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

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

"Yahoo Inc. (NASDAQ: YHOO) today notified my friends and I that the time we spent last night on our fantasy football draft was wasted because of server problems. Excuse me? How can Yahoo not have enough server capacity to accommodate the scores of fantasy drafts that happened last night? It's not like Yahoo hasn't done this before or that this weekend's start of the football season is a closely guarded secret... People who play fantasy football are desirable to advertisers since they stay on Web sites for long stretches of times while they live out their NFL dreams. That means they are more likely to notice advertisements. As it faces growing competition from Google Inc. (NASDAQ: GOOG) and everyone else under the sun, Yahoo can't afford to anger its loyal users particularly for popular features such as fantasy football users."

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:

"[Yahoo] set up a new draft for my league for this evening. I'm not sure my friends and I are going to bother."

(Thanks to my colleague K.C. Jones [kirconley@cmp.com] for her work on the original story posted on InformationWeek.com yesterday.)


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links