Viral Loops or Viral 'Oops'?Recently, MessageMe announced it had grown to 1 million users in a little over a week’s time. The revelation captured the attention of envious app makers throughout Silicon Valley, all of whom are searching for the secrets of customer acquisition like it’s the fountain of youth. “Growth hacking” has become the latest buzzword, as investors like Paul Graham profess it’s functionally that matters.

Clearly, everyone wants growth. To someone creating a new technology, nothing feels better than people actually using what you’ve built and telling their friends. Growth feels validating. Growth tells everyone the company is doing things right. At least that’s what we want to believe.

Good Growth, Bad Growth

Sometimes viral loops drive growth, because the product is truly awesome, while in other cases growth occurs for, well, different reasons. As an example of good growth, it’s hard to top PayPal’s viral success in the late 90s. PayPal knew that once users started sending money to each other, mostly for stuff bought on eBay, they would infect one another. The allure that someone just “sent you money” was a huge incentive to register.

PayPal nailed virality. Both sides of the transaction benefited from utilizing the platform and a classic network-effects business was born. In order for users to get what they wanted, they had to open an account and the product spread because it was useful and viral.

However, sometimes viral loops are less about the customer’s interests and more about short-term greed. When the product maker intentionally tricks users into inviting friends or blasting social networks, they may see growth, but it comes at the expense of goodwill and trust. When people discover they’ve been tricked, they vent their hatred and stop using the product. Unfortunately, we’ve all encountered the ways companies drive growth in deceptive ways known as “dark patterns.”

Viral Oops

Good and bad growth is relatively easy to identify. What is harder to decipher is the gray zone in between. A “viral oops” occurs when users unintentionally invite others, but when they look back on what happened, they blame themselves, not the app.

When MessageMe pre-selects everyone in my contact list as a default, I’m likely to think that only those who are un-checked will be invited. However, the opposite is true. With two taps, my list of hundreds of contacts gets swamped with a notification email personalized from my email account.

messageme selected allMessageMe invite

Could users really make such a mistake? After all, the send button is clearly labeled with the number of people who will be invited. I am also well aware of the convention that a check mark means the contact is selected and not the other way around.

However, say I was not in UX businesses? What if I were a tech novice living outside our little Silicon Valley bubble? What if I were slightly far-sighted? Or perhaps if English were not my first language (it isn’t)? Or maybe if I were attempting to make a quick decision while outdoors and couldn’t clearly see my dim screen? In any one of these scenarios, I could have easily triggered a viral oops.

The surprising math of viral growth reveals it doesn’t take many users to make this kind of mistake. Only 5 percent of users screwing up can get an app to a million downloads in two weeks, assuming the average user has 200 people in their contact list. The assumptions are for illustrative purposes (see note at bottom) but the point here is to show how powerful exponential growth can be, whether or not it is intentional.

Who Really Gets Tricked?

Admittedly, a careful review of the interface would reveal the user’s mistake. It’s hard to fault MessageMe. Though my requests for an interview were not returned, I assume their intent was not to trick anyone.

However, the example illustrates what makes the viral oops so troublesome. It is impossible to look into the minds of customers while they use an app. For all I know, MessageMe users intend to send the app to every single one of their contacts. But how would the app maker know if it was done in error? They wouldn’t.

A viral oops not only deceives the user, it fools the developer.

Unlike an intentionally deceptive technique, where the user gets angry and stops using the product or uninstalls the app, with a viral oops, users blame themselves. They’ll most likely keep the app and move on with life. With no metric indicating the user’s unintended mistake, the app maker is none the wiser.

A viral oops not only deceives the user, it fools the developer. There is no way to know if the invite was sent in error. Without an understanding of why users share the app, developers are liable to gloss over significant shortcomings that must be addressed for the app to achieve long-term success. Given how easy it is for us fallible humans to believe convenient truths, it is too enticing to interpret growth as validation instead of a mirage.

MessageMe just happens to be the latest hyper-growth app making headlines; I could have picked any number of other cases. In researching this article, I discovered multiple examples of the viral oops in companies large and small, and I’m sure the comments section will uncover others.

Developers should make sure they know why people are sending invitations to others and not be guided by growth for its own sake. App makers would be wise to be particularly careful in encouraging people to invite others before users really know how the app works. For example, prompting invites at first login is a remarkably common and potentially specious practice.

For creative people working on exciting new technologies, growth feels great. But we should be cautious of using techniques that have a high likelihood of being viral oops instead of viral loops.

Note: The virality math assumes a starting base of 1,000 users and a daily cycle time of 1 with a 10% invitation acceptance rate.

Thanks to Jules Maltz and Max Ogles for reading previous versions of this essay.

Photo Credit: Mel B

Get my latest blog posts by subscribing now!

Share this essay:

  • I remember when Dropbox first came out it sent everyone of my contacts an email. I didn’t mind and I don’t think my contacts did either. How come you think Dropbox pulled it off so well?

  • I don’t think this design choice was a misstake. Companies who are serious about growth measure this all through A/B testing. But that brings us to the more important point; being data-driven vs data-informed. Unfortunately it’s all too easy to be data-driven and build spammy apps like this. Which might end up in massive growth and then massive churn just like everybody’s favorite examples Viddy and Socialcam.

  • Olaf

    This happened to me on Path. Embarrassing for them and me. I hate them for it. Useless app anyway, but this made it far worse.

  • I think another great example here is BranchOut –

    It got to 25m users using a pretty aggressive Facebook viral sharing strategy. I’m not sure whether the users would have blamed the app or themselves for the sharing – I know that I mostly blame myself in these situations, especially as I am, as you say in the “Silicon Valley Bubble” and am comfortable with the functionality of privacy features like those on Facebook.

    How significant of a problem do you think “fooling the developer” really is? I feel that most developers would i) Be aware of a very frictionless sign up process and ii) Look at engagement metrics as well as adoption (if there is massive adoption with little engagement, it might suggest that users are not actually that excited about the app). That said, I appreciate that massive growth like this has intoxicating euphoric effects, and it can be hard to remain objective and data driven in such situations.

  • The viral oops was a good read and for a minute I thought, hey that can work!
    On take two, I am inclined to the Dropbox model as opposed to that of the Kardashian Game.
    Why did the Dropbox one work well? And do you have other recent examples of well executed viral loops apart from PayPal

    • Dropbox’s viral spread was not an accident. It is consciously done every time users share a file.