There are several factors that should be looked at when creating a collaborative working/learning space. I’ve previously referred to Column Two’s three tiers of collaboration – Capacity, Capability & Strategy and it’s a good model to start with. Part of capacity are the existing processes and culture of collaboration while capability includes the best tools for the job. It’s not easy for a group of individuals, who do not know each other, to work collaboratively from the onset. It is even more difficult to ask that this collaboration occur online when the participants are not in the habit of working on the Internet. The practice of sharing needs to be joined with the tools that work for the culture. Finally, strategy includes the leadership, direction and project management of getting things going to work collaboratively online.
It’s important to get participants/members first used to processing their information flow online. A framework such as Personal Knowledge Management can be used, but each person must be given time to practice, connect and get feedback. The community also needs to be nurtured, one relationship at a time, as the creators of Flickr realized:
A lot of our success came from George, the lead designer, and Caterina. Both of them spent a lot of time in the early days greeting individual users as they came in, encouraging them and leaving comments on their photos. There was a lot of dialogue between the people who were developing Flickr and their users to get feedback on how they wanted Flickr to develop. That interaction made the initial community very strong and then that seed was there for new people who joined to make the community experience strong for them too.
Because culture is slow to change I would recommend starting with the simplest tool-set possible. Turn off most functions and only enable new ones when people start asking for more. As with tools, the same minimization principle goes for content. It is more important to build relationships and to draft the right people than it is to build the best content. Community trumps content online. Therefore, the focus should be on building connections.
A model we used for a CoP prototype (the first of several to be implemented on a variety of “topics”) was based on these roles in the core team:
Process Lead (Communities) – Stays current on online communities, evaluates progress, helps members with knowledge-sharing, develops processes and records progress.
Recruiter (Early Adopter) – Identifies and connects with other potential Early Adopters.
Recruiter (Maven) – Identifies subject areas of interest to the community and finds knowledge or human resources.
Technical Lead – Identifies technologies and ensures that the community has the right tools.
Topic Lead – The “go-to” person on all questions relating to implementation. This person is supported by the other core team members.