Monday 2 February 2009

What is it for?

A few brief thoughts - and I claim no generic rightness or indeed completeness for them - on what I thinks some of the web 2.0 things I'm familiar with are and are not for.

Facebook
For:
  • Finding out what people are doing when you haven't seen them for years and don't actually ever want to see them in real life again;
  • Keeping abreast of what people are doing in their day-to-day lives, and commenting on it;
  • Creating an online image of yourself, whether you are an individual or an organisation - the groups you belong to, the apps that you add all serve as badges;
  • Setting up and promoting events.
Not for:
  • Group discussions. Even though it has forum-style functionalities, it's amazing to me how comparatively few group discussions happen on Facebook. I reckon it's because of the third point above - belonging to a group on Facebook is more about wearing a badge than being part of a community.
Blogs
For:
  • Getting your opinion out there - either as a post, or as a comment on someone else's post;
  • Writing about stuff you're genuinely interested in;
  • Discussion with other people who are interested in the same stuff - as you gain audience and people start interacting with you and each other on the blog, you'll end up with at least some community discussion.
Not for:
  • Promoting your organisation generically - people look for a more genuine, personal view on a blog;
Twitter
For:
  • Alerting people to stuff - events, news, a new blog post;
  • Finding out what people are saying about you/your organisation;
  • Keeping people abreast of your current thoughts/interests/ideas - Twitter seems to be a more ideas-sharing community than Facebook, search me why;
  • Getting to know new people.
Not for:
  • Actually I'm not sure about this one, it seems to do everything :-). I guess it's not for anything you can't say in 140 words.
Wikis
For:
  • Projects you have in common with a group of people, where everyone has a contribution to make and everyone is happy with the idea of editing a common document to achieve this;
  • Projects where you want to tap into "common wisdom" and, crucially, have given others the motivation, tools, understanding and structure to contribute.
Not for:
  • Making your department look cool because they have a wiki;
  • Putting some pages up and hoping someone else will do the work of sorting them out for you. You'd be surprised how unlikely it is that another user will even correct a typo on your page unless they know why they're helping you out.
I think I'm running out of ideas here, but I'd welcome further thoughts/comments.

1 comment:

Anonymous said...

For Twitter see also private organisational microblogging networks such as Yammer or ShoutEm - these tools are great for sharing information within companies, encouraging engagement across departments and generally fostering debate, interaction and learning.

Downsides can be encouraging (universal) adoption, particularly across large organisations with traditional cultures or a heavy emphasis on hierarchical management styles.