Case Study: What We Learned From Mountain Dew

16 Aug

By now, you may have heard of the fiasco that was Mountain Dew’s “Dub The Dew” contest, where they crowdsourced the name for their new Granny-Smith-apple-flavored Dew. If you’re a dedicated reader, you already see where I’m going with this. I’ll just cut to the chase, since this picture pretty much sums it up:

Disaster area. 4chan’s /b/ board got ahold of it, and in their typical fashion, overwhelmed the contest with their sheer numbers and pushed all the other entries out of the top 10 positions, replacing them with flavors like “Gushing Granny”, “Diabeetus”, and “Hitler did nothing wrong”. As of my writing this, the contest site is blank, but the damage is done.

Fortunately, we can make a case study out of this and actually learn something. Here are a few tips for dealing with your crowd if you happen to be a big company holding a contest on the Internet:

  • Seriously. Know your audience. I can’t be the first person to tell Mountain Dew that their product is overwhelmingly consumed people who use the Internet a LOT. The law of averages hurts Dew in this case, since it would stand to reason that at least one of these Internet users would tell 4chan about the contest, and this is not the sort of low-hanging fruit 4chan leaves alone. Especially because you didn’t…
  • Validate your contributions. If this is a real contest, treat it like one. Make people sign up to enter or vote, even if it’s just Facebook validation. It’s annoying, and you’ll lose some voters, but you won’t have as many cases of the sort of chaos that pure anonymity can breed. Look at Lay’s Facebook contest to name a new potato chip flavor; I don’t see any “Fapulous Apple” there. A little accountability goes a long way, especially when it means that you can block offending accounts or IP addresses. Speaking of technological failures…
  • Security is still super important. See that bit of anti-Israel vitriol at the top of the screenshot? Surprisingly, Mountain Dew didn’t put that there themselves. That was the result of a hacker with the smallest amount of talent and five spare minutes. See, the site lacked something called “input validation”, meaning that programming code entered in the contest entry box would actually appear on the website. It’s a little complicated, and explained better in this Reddit thread, but the gist of it is that this was Web Security 101, completely and easily avoidable, and Mountain Dew dropped the ball. I’m sure this didn’t help vote hacking, either.

So it looks like Mountain Dew threw together this contest with minimal research or development, and now they’re receiving results indicative of their lack of effort. The sad thing is, this is the sort of event that makes entire industries shy away from crowdsourcing as a method. But it’s just that: a way to do things, a tool. If you hold a hammer by the wrong end, it’s not gonna get that nail down, and you’re gonna look like a freakin’ idiot in the process.

Learn, and try again.


One Response to “Case Study: What We Learned From Mountain Dew”


  1. Dominos Call For The Ultimate Delivery Vehicle Illustrates Importance of a Solid Platform « Tiny Work - August 27, 2012

    […] and the site’s sign-up verification features took away just enough user anonymity to prevent disaster. So when you browse through the contest entries, you don’t see the normal mix of 90% crap and […]

Sound Off in the Comments

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: