ABOUT

  • Mainly about engagement and collaboration using social media and events, with some asides on living in London. More about David Wilcox and also how the blog started.
  • Search

    WWW
    http://partnerships.typepad.com/civic/

« Re-inventing membership online and off | Main | Barcamping with Government »

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a00d8341c266753ef00e54ff381658833

Listed below are links to weblogs that reference Do communities need boundaries?:

Comments

Hi David, all

For those of you who are not reading RSA Networks - I'm working with Andy Gibson on the RSA Networks online platform - just entering it's second phase:
http://openrsa.blogspot.com/2008/01/rsa-networks-version-2-in-testing.html

This is a fascinating thread. I have been somewhat frustrated at the fact that we haven't really been able to address this issue with the RSA Networks site as is - but it's really in these discussions (in and around the RSA itself - not exclusively with fellows at all - as Carl points out) that the right technical choices will be made.

Technically, it isn't a challenge to configure all kinds of levels of access at different times in a project's development - however, in my experience of online collaboration platforms, the needs of each project, each person and crucially each context in a distributed collaboration are very sensitive and changeable.

If we think through the off-line process of project development first, before thinking of the technology (which is something we've tried to do with the RSA Networks platform), it involves private conversations, meetings, affinities built up over time and in many contexts. It's impossible to model that level of subtlety in communication and avoid overload: imagine assigning highly granular permissions for each potential collaborator online.

My feeling is that as people become more aware of the potential of opening up different phases of their project development, it will become easier for us to model those processes online in contexts such as RSA Networks.

For now, people's levels of understanding are too varied, and working methodologies are too diverse for a universal policy to be applicable.

This being the case, it seems to me that complete openness is the best default position. People can be made aware that anything they post online is visible to all comers, and if there are problems, or people feel that their idea has been damaged by premature exposure - we can deal with the problems as they arise.

This is how the RSA Networks prototype has actually been designed. Despite the login - anyone may register. The login is actually there because with limited time and budgets, it was too complicated to define 'anonymous' roles within the system (define their access levels etc...).

So far, the system has about 300 users, 50 or 60 of which are regularly active. There are a mix of fellows and non-fellows using the site actively - and I'm sure there are useful statistics to be extracted from all the data somewhere down the line.

Personally, I came to the project knowing little about the RSA - and am now a new fellow - having been impressed by the tone and quality of the projects I saw on the site. So my feeling is that the RSA Networks platform - being open - could become a highly effective recruitment tool for new fellows!

How our research is absorbed into policy-shaping discussions about openness in this instance remains to be seen.

Saul.

Knowledge management specialist Patrick Lambe has now blogged on this, with references back to Ed's starter piece.

The comments to this entry are closed.