Public Timeline

I’m starting with the public timeline because, while it’s not the sexiest thing on this list, it’s critical for new users as a solution to the cold start problem. The public timeline is the first place new users will look for new content. It’s also how they will determine if they wish to join your community – the size, the tone, the cultural-norms, and the freshness of your community is easily communicated via the public timeline. And, of course, it’s also where new users can find other interesting users, which leads me to my next pattern.

Asymmetrical Follow

This has been written about before, so I won’t say much. Asymmetrical follow means I can follow the updates of a user without their permission. They, in turn, could follow me back but it’s not required. This allows for the kind of preferential attachment characteristic of scale-free networks, and it’s scale-free networks that are primed for viral propagation. When the goal is content distribution powered by network effects, it just doesn’t matter if you actually know the person or not. All that matters is if the person if a reliable source for interesting content. This is why social networks have failed to become anything more than social networks. Remember this graph from Brad Horowitz?

Only 1% of a community are content creators

Most people’s social networks aren’t large enough to contain more than a handful of super-star content creators. I believe the average Facebook account has 300 users. 1% of that is 3 – not enough to be a valuable source of content. If you think Dunbar’s number is a more accurate group size – which I do not with regard to online communities – then you’re only left with 1 or 2 people (1% of 150 = 1.5). Yes, you can argue that Facebook has done very well for itself living off of soap-opera like content – who is dating whom, who got drunk at what party, what was she wearing?!?) but there are natural limits to that growth. Their commenting feature will help drive page views, but there isn’t a whole lot of new value being created there.

Newsfeed

Nothing shocking about this. Now that your users have gone out and followed their friends and other interesting users, their homepage should now be the newsfeed that aggregates all of that content into one place. But it’s not sufficient just to include the stream of content. You need to also show who contributed that content (and, in the case of re-blogging, the other hands it passed through). Why? Because that’s how you can evaluate the people you are following (and, with re-blogging, discover new people to follow).

Re-blogging

I’m a huge re-blogging fan. It’s the engine that drives the content diffusion through the network. The concept is simple: if someone I’m following shares something interesting, I can easily push that same interesting piece of content out to everyone who is following me while providing proper attribution. Someone who follows me can do the same, and again, and again. This is really powerful, as the people who follow me are most likely not the same as the people I follow. Re-blogging provides a transport device for great interesting content to travel through connected components of the network (which are generally much larger than your immediate social network).

Social Proof

While judging the content someone shares is a decent proxy for evaluating whether or not to follow that person, social proof can help. Show how many followers the person has. Better yet, calculate their influence (like PageRank does for websites). Or, show how many favorites their posts have accrued or re-blogs their posts have had. It’s a quick and easy way for users to ascertain the reputation of a user in the context of your site.

Bonus: APIs and RSS

I promised five, but here’s an extra. Use APIs and RSS to amplify your power. Provide APIs so that others can build tools that extend your reach. Publish RSS feeds so that users can incorporate your interesting content into their existing routines. Make use of other companies’ APIs to publish your content out to them (like publishing to Twitter). It’s very difficult to create new habits, but it’s much easier to go where your users already are (Facebook, Twitter, Google Reader in my case).

Like I said at the start, I’ll be back soon with some commentary on how well (or not) various sites are implementing these ideas. Off the top of my head, I’m thinking about Blip.fm, bit.ly, and Soup.io. I’d love to talk about Etsy, but I feel like it wouldn’t be appropriate.

I was chatting with my friend Dan Nelson today after bumping into him at the Cornell Music Department library. He’s currently a Ph.D student at UPenn studying musical composition. He threw an idea at me and, after some collaboration, we came up with something akin to a Flickr for composed music.

It would work like this:

Everyone who registers gets a tumblog. (Side note: I love Tumblr. I thought about apologizing to everyone who keeps hearing me implement ideas with Tumblr, but I’m not going to. They deserve it for a job well done.)

Composers will use their tumblogs to publish 2 things. One, an mp3 of their composition. Two, a PDF of the score. Composers are encouraged to tag their content for improved discovery.

Everyone can use their tumblr dashboard to follow composers they like and heart music they like. Everyone can also use their tumblogs to re-blog music they particularly like and post about their experience with the music they’ve discovered.

Like Flickr, people can search for music or composers. Like Flickr, you can explore the most interesting compositions. And most importantly, like Flickr, you can pay to have a hard copy printed, bound, and mailed directly to you.

Your market is anyone who buys sheet music – basically every school and private music teacher in the country (and internationally). Sure, some people would just print out the PDFs for free, but I bet enough schools and teachers would pay for the nicely published and bound parts and score to make a profit. Like Chris Anderson has been saying since he wrote the Long Tail, you can be successful even if only a minority of your users pay.

If successful, what we will have done is broken the pre-Internet strangehold of the major publishing houses and academic elitism on composed music, similar to what Vimeo is doing for video and Etsy is doing for handmade goods. Something I thought about when I was at Etsy that applies here is, “An audience for every artist.” We can create a forum for quality composed music with a long tail. We can use social aggregation instead of editorial fiat to discovery great music. We can empower people to try their hand at composition even if they are a one-hit-wonder.

If anyone is interested in helping Dan build this company, please contact me – david.lifson at gmail – and I’ll pass your name along. It’s super simple, engineering-wise; Tumblr’s API is free and easy to use, storing the data and metadata is easy, slap a search index on the data, and you’re done. All that would be left is to set up a business partnership with a printing company like Subito Music, and the task of getting the word out and building up a community. And really, how many startups these days come with a business model, not to mention a highly targeted audience and a trove of user preference data.

Writing to say I won’t be writing this weekend. I’ve got my head buried in putting together a proposal for what I think Etsy can be in 3-5 years. It’s incredibly fun stuff, and I’m hoping I can get the rest of the company as excited about it as I am. In the mean time, you can follow me on Twitter (as usual) or on Google Reader (as usual). Also, I’m almost done with Clay Shirky’s book Here Comes Everybody – it’s incredible; I definitely recommend it.

Four hundred and twenty eight posts ago, I started a thread on the Etsy forums. The thread was intended to have two purposes. One was to simply get a sense of the community and introduce myself to them. Second, I wanted to get some better intuition as to how sophisticated Etsy sellers (the majority of forum posters) are about running their business and the e-commerce business generally. So I asked a basic prioritization question – would you rather us make search better or fix a bug that would occasionally reset the page views counter on your item listing pages? (For those curious, the views system is stored entirely in a cache, and when the cache gets full and a record gets evicted, the page view number resets to 0. Clearly, the system was not engineered to be used in this manner.) My follow up was, if fixing the view system is not a priority, would you rather we get rid of it entirely or keep it broken.

The danger is to get lulled into an urgency to please. When hundreds of users are demanding a feature, you may feel compelled to acquiesce and build the requested feature. Before you do that, stop and consider Henry Ford: “If I did what people said they wanted, I would have built a faster horse.” (or something like that.) Customers are excellent gauges as when something is wrong, but can be extremely misleading about both what exactly is wrong and how it should be fixed. Furthermore, customers do not (or should not) have better visibility than you do into strategic goals, key business metrics, engineering resources, etc. They don’t have your long-term vision nor your understanding of complex dependencies. So don’t jump the gun. Listen, follow the comments to the source, and solve the root of the problem.