Some of the most interesting businesses such as Facebook, Twitter or Pinterest are based on communities. Obviously they are very attractive because they
- create network effects which attract more users
- have decreasing customer acquisition costs as the firm grows larger
- are hard to copy because they are more than a combination of technical features
So far so easy.
But how do I get to this point? With frequency & surprises…
There is an important twist which make the most successful services so sticky and addicting. Interaction is
a) frequent
b) outcome is unclear
The frequency of interaction helps to ideally become a habit like checking emails or Facebook. The very best companies even become a verb. Think about statements like “I’ll google that later” or “Let’s skype”.
Interestingly, the underlying requirement is that the outcome of using the service is unclear. Consumers want to be surprised and discover something cool, fun or useful. Take pictures from a friends vacation for example, or a cool party that is planned for the weekend. Basically anything qualifies which is relevant to the user but what the user couldn’t predict before he opened the service and used it.
Another good example which illustrates this point is an Excel spreadsheet with your business plan. The outcome is clear (i.e. the calculations haven’t changed) vs the stock market or online news page where the outcome of opening the website is not clear. Which one do you check more often?
So what do we learn from this?
Lesson 1: Unexpected content must be relevant and to be that it must be within certain parameters. With Facebook you would expect an update from your friends vs. Linkedin where you would rather expect some information regarding your business contacts.
Lesson 2: This drives frequent visits and increases the likeliness that the service becomes a habit.
Lesson 3: The parameters need to be established over time and can’t be all planned upfront. The community needs to agree on a set of rules. The biggest danger here is that the community grows too fast in the early days and is not homogenous enough to really build out a core group which adheres to these rules. Or in Crossing the Chasm terms: with communities the early majority needs the guidance by the early adopters. The chasm still exists because the early majority are also pragmatists. For them the service or product is the combination of technical features and the community that already uses it.


