5 fundamental social design patterns

In the last 2 years, a few different sites have implemented some very successful social designs. I’ll lay out 5 social design patterns here and then follow up with case studies in subsequent posts. These apply to sites with user-generated content where the content is the primary object.

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

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.

8 Comments »

  1. Christopher Clay said,

    December 11, 2008 @ 4:18 pm

    Interesting list — looking forward to your analysis of how we at Soup.io implemented those patterns!

  2. Daryn said,

    December 12, 2008 @ 12:35 am

    Great post, David. Thanks!

  3. A Digital Outrigger / Library Usability Links 12/11/08 said,

    December 12, 2008 @ 8:12 am

    [...] SocialStartup.com identifies five fundamental social patterns: [...]

  4. Chris Pallé said,

    December 12, 2008 @ 12:35 pm

    Good post, Dave. I question about the public timeline, though. I’ve never quite see the value in it anymore. I think I remember first joining twitter spring of ‘07 and went to the public time simply because i was fairly new to social networking in general. Now as a veteran (ha ha) I don’t go to them as readily. I look for the usual suspects (friends) and with whom they’re talking.

    An important element (possible pattern?) is the @. I’m finding myself noticing an @ handle in emails and other random places (non-twitter related) and immediately go to twitter, put in the name after the slash and poof, i’ve found them.

    @ was so popular because of email back in the day because it meant {some person} AT {some online place}… but now it’s like the the other way around… {some online place} AT {some person} Thoughts?

  5. dlifson said,

    December 12, 2008 @ 12:53 pm

    Thanks for the comments, everyone. Actually, Chris, you are illustrating my point exactly (re: public timeline). New users really benefit from it, and it’s usefulness degrades gracefully. The fact that twitter doesn’t make the public timeline the default homepage is a smart move – it’s there for those who still need it. I imagine that many people, as brand new users, went to the public timeline for their first to get a feel for twitter and find people to follow (I know I did, and it looks like you did).

    I totally agree on @, though without good support for watching @replies at you it’s hard to implement successfully. Another reason for providing APIs, I’d say.

    RE: [some online place] AT [some person}, that’s a pattern that has roots in programming – namespace resolution. If you program Java, for example, you will import libraries like java.util.HashMap. it goes from biggest to smallest. IP addresses are the same way – it starts with the biggest IP address space and narrows as you move left to right.

  6. Chris Pallé said,

    December 12, 2008 @ 1:18 pm

    Sorry, wasn’t clear. I agree with you that the public timeline might be good for new users trying to understand a community’s purpose, but the point I was trying to make is that I question how valuable the public timeline is for people who are already comfortable using SM in general. ie those who already use twitter, facebook, etc.

    For instance, I just joined blip.fm (from your invite) and the public timeline meant nothing to me, even as a new user – to _that_ community. Honestly, I was numb to it like a banner ad, BUT put a little context around that timeline and it starts to become useful. Something like a search. I did a search on Blip.fm and found songs that matched, then after “blipping,” I found a list of others who blipped to the same song. That list was interesting, but that was after I began playing with the site, though. Not really new anymore. If a “public timeline” with a little context (similar music tastes) was provided, then it becomes more interesting. Dunno, is that more clear?

    I also wonder how valuable the *general public* timeline is for someone with zero SM experience. It’s a good pattern for the intermediate maybe, but I still think a dash of context is needed for usefulness.

    Interesting factoid from the system-side. I had no idea…. we’re all becoming nodes. :-) … wait, becoming???? what am i talking about ;-)

  7. james governor said,

    December 14, 2008 @ 7:17 am

    for reblog see retweeting. same pattern. Be Kind, Retweet, or @idarose recently put it “be sweet, retweet”

    http://www.redmonk.com/jgovernor/2008/11/25/be-kind-retweet-on-the-timeless-way-of-building-networks/

  8. james governor said,

    December 14, 2008 @ 7:18 am

    chris – interestig to bear in mind that @ was a user driven convention.

RSS feed for comments on this post · TrackBack URI

Leave a Comment