Knowledge Management Review lastest issue talks about the differences between the Communities of Practise and Teams. Communities and teams have different ways of sharing information an learning practises.
It defines Community of practise as a group that shares knowledge, learns together and creates common practices. COPs share information, insight, experience and tools about an area of common interest. This could be a professional discipline (such as reservoir engineering or biology), a skill (like machine repair), a topic (such as technology), an industry or a segment of a production process.
Consulting companies usually organize COPs around both disciplines, such as organizational change, and industries like banking, petroleum or insurance. Community members frequently help each other to solve problems and develop new approaches or tools for their field. This makes it easier for community members to show their weak spots and learn together in the "public space" of the community.
Teams and communities are differentiated on the following parameters:
Teams are tightly integrated units driven by deliverables, defined by managed tasks and bound together by members' collective commitment to results.
COPs are loosely knit groups driven by the value they provide to members – defined by the opportunities to learn and share what they discover and bound by the sense of collective identity that the members form.
The heart of a team is a set of interdependent tasks that lead to an objective. The heart of a community of practice, on the other hand, is the knowledge members share and develop.
Since community members apply their knowledge on teams outside the community, it is not possible to predict exactly what knowledge will be important to the community.
COPs therefore follow opportunities for sharing knowledge as they arise, and as a result the "hot topics" in a community shift over time. As topics shift new people join the community, adding their perspective and shaping its direction.
It defines Community of practise as a group that shares knowledge, learns together and creates common practices. COPs share information, insight, experience and tools about an area of common interest. This could be a professional discipline (such as reservoir engineering or biology), a skill (like machine repair), a topic (such as technology), an industry or a segment of a production process.
Consulting companies usually organize COPs around both disciplines, such as organizational change, and industries like banking, petroleum or insurance. Community members frequently help each other to solve problems and develop new approaches or tools for their field. This makes it easier for community members to show their weak spots and learn together in the "public space" of the community.
Teams and communities are differentiated on the following parameters:
Teams are tightly integrated units driven by deliverables, defined by managed tasks and bound together by members' collective commitment to results.
COPs are loosely knit groups driven by the value they provide to members – defined by the opportunities to learn and share what they discover and bound by the sense of collective identity that the members form.
The heart of a team is a set of interdependent tasks that lead to an objective. The heart of a community of practice, on the other hand, is the knowledge members share and develop.
Since community members apply their knowledge on teams outside the community, it is not possible to predict exactly what knowledge will be important to the community.
COPs therefore follow opportunities for sharing knowledge as they arise, and as a result the "hot topics" in a community shift over time. As topics shift new people join the community, adding their perspective and shaping its direction.
While teams often have clear boundaries and membership, COPs have many partial, part-time, and marginal members. Like a double-knit fabric, they can stretch as topics and needs evolve.
No comments:
Post a Comment