Difference between revisions of "Communities of Practice"

Difference between revisions of "Communities of Practice"

From Learning and training wiki

Share/Save/Bookmark
Jump to: navigation, search
 
(42 intermediate revisions by 6 users not shown)
Line 1: Line 1:
{{Term|COMMUNITIES OF PRACTICE (CoPs)|A process of social learning where a group of people who share an interest, a concern, a set of problems, or a passion about a topic, collaborate to share ideas, find solutions, and build innovations without necessarily being in a formal work meeting. CoP members are bounded one another through exposure to a common class of problems, common pursuit of solutions, and embodying a store of [[Knowledge|knowledge]], by shared practices and common beliefs. Community of practice generally cut across organizational boundaries and helps create and share knowledge. It is the best way to :  
+
{{Term|COMMUNITIES OF PRACTICE (CoPs)|A process of [[Social Learning|social learning]] where a group of people who share an interest, a concern, a set of problems, or a passion about a topic, collaborate to share ideas, find solutions, and build innovations without necessarily being in a formal work meeting. CoP members are related to one another through exposure to a common class of problems, common pursuit of solutions, and embodying a store of [[Knowledge|knowledge]], by shared practices, tools, common beliefs, and language. Communities of practice generally cut across organizational boundaries and help create and share knowledge. It is best to: <ref>[http://www.wikipedia.org Wikipedia] (16 April 2008), [http://www.km4dev.org www.km4dev.org](16 April 2008), [http://www.kstoolkit.org www.kstoolkit.org] (24 September 2008) </ref>
 
   
 
   
 
* Learn while doing.
 
* Learn while doing.
 
* Ensure effective creating and sharing of knowledge and experience.
 
* Ensure effective creating and sharing of knowledge and experience.
* Co-learn about related practices across projects.<ref>[http://www.wikipedia.org Wikipedia] (16 April 2008), [http://www.km4dev.org www.km4dev.org ](16 April 2008), [http://www.kstoolkit.org www.kstoolkit.org] (24 September 2008) </ref>.
+
* Co-learn about related practices across projects. }}
  
See also: [[Communities of Interest]] }}
 
  
{{Term|Main components of a CoP|
+
{{Tool|Implementing a CoP|
#'''Community''' : active members interested to share their knowledge.  
+
__NOTOC__
#'''Domain''' :
+
== ''' Main Components'''==
#'''Practice'''  
+
#'''Community''': active members who are interested in sharing their knowledge and who dedicate their time to the community.  
#'''Motivation/engagement'''  
+
#'''Domain''': it must be a  compelling topic; one of interest to many people and of relevance to their work.  The potential members must be passionate about the subject for collaboration.
#'''Mission'''
+
#'''Practice''':  the ability to compare one's own work practices to those of others is one of the foundations of the CoP.
#'''Structure'''  
+
#'''Motivation/engagement''': the existence of the community is based only on the motivation of its members.
}}
+
#'''Structure''': it is important to find a balance between formal and informal structure. Most  communities have a concentric structure at triple level (core group, closer circle, outside circle). <ref>[http://www.deza.ch www.deza.ch] (29 September 2008)</ref>
  
 
+
==''' Step by Step'''==
{{Tool|Processing a CoP|
+
__NOTOC__
+
=='''Step by Step'''==
+
 
#'''Creating:'''  
 
#'''Creating:'''  
#*Decide what topic you wish to address in a community in order to identify the domain.  Pick a compelling topic that will be of interest to many people in your organization, will be relevant to their work and will build on the core values of the organization.  The potential members must be passionate about the subject for collaboration and the domain can itself invite involvement.
+
#*Decide what topic you wish to address in a community in order to identify the domain.   
#*To encourage people to participate, start a discussion on a domain or a smal problem and raise ideas for resolving this problem.  
+
#*To encourage people to participate, start a discussion on a domain or a small problem and present  ideas and/or solutions for resolving this problem.  
#*Find a  committed leader or coordinator for the community.  Volunteer to be the community leader, or identify someone else with the right attributes and well-respected.  The community leader should know the subject, have energy for stimulating collaboration, have sufficient time to devote to leadership, and then regularly spend time increasing membership, lining up speakers, hosting calls and meetings, asking and answering questions, and posting information which is useful to the members.
+
#*Find a  committed leader or coordinator for the community: volunteer to be the community leader yourself or identify someone else.  The community leader should know the subject, have energy for stimulating collaboration, regularly spend time increasing membership, lining up speakers, hosting calls and meetings, asking and answering questions, and posting information which is useful to the members.
 
#*Identify thought leaders to legimate the community and potential members to leverage knowledge. The community will need a critical mass of members.  You usually need at least 50 members, with 100 being a better target.  Try to take advantage of existing networks.
 
#*Identify thought leaders to legimate the community and potential members to leverage knowledge. The community will need a critical mass of members.  You usually need at least 50 members, with 100 being a better target.  Try to take advantage of existing networks.
#*Decide on a initial technology platform and create one or more tools for the community to use (threaded discussion forum, collaborative team space, web site or portal, Wiki, Blog or newsletter).
+
#*Decide on an initial technology platform and create one or more tools for the community to use (threaded [[Discussion Board|discussion board]], collaborative team space, web site or portal, [[Wiki|Wiki]], [[Blog|Blog]], or newsletter).
 
#'''Starting-up:'''  
 
#'''Starting-up:'''  
#*Once your community is established, publicize its existence to help recruit new members (sepcial event, articles, incentive to join).
+
#*Publicize the existence of your community once it is established to help recruit new members.  
 
#* Watch the production of intermediate results, summaries and conclusions of the discussions.
 
#* Watch the production of intermediate results, summaries and conclusions of the discussions.
#*Gather a core group (leader, exoerts, stakeholders) and maintain 1 closer circle (involved members) and 1 outside circle (interested members, contributors, readers).  
+
#*Gather a core group (leader, experts, stakeholders) and maintain one closer circle (involved members) and one outside circle (interested members, contributors, readers).  
 
#*Keep the community active : regular conference, periodic events, weekly meetings and collect examples of value.   
 
#*Keep the community active : regular conference, periodic events, weekly meetings and collect examples of value.   
 
#'''Developing and sustaining'''  
 
#'''Developing and sustaining'''  
#* Maintain interest and commitment by organizing work-shops and face-to-face meetings on major topics
+
#* Maintain interest and commitment by organizing workshops and meetings on major topics.
 
#* Introduce new and challenging perspectives.  
 
#* Introduce new and challenging perspectives.  
 
#* Maintain the energy by recruiting new members.
 
#* Maintain the energy by recruiting new members.
 
#* Rotate roles and responsibilities between members over time.
 
#* Rotate roles and responsibilities between members over time.
#* Manage knowledge by creating [[ Knowledge Map| knowledge map]], processing [[ Knowledge Sharing| knowledge sharing ]],  organising resources, identifying knowledge gaps.
+
#* Manage knowledge by creating [[ Knowledge Map| knowledge maps]], processing [[ Knowledge Sharing| knowledge sharing ]],  organising resources, and identifying knowledge gaps.
 
#'''Closing:'''  
 
#'''Closing:'''  
 
#*Ending the CoP when the domain is less relevant or the purpose ended.
 
#*Ending the CoP when the domain is less relevant or the purpose ended.
 
#*Celebrate its life and achievements by organizing a special event.
 
#*Celebrate its life and achievements by organizing a special event.
#*Create a new CoP on a different topic. <ref>[http://www.kstoolkit.org www.kstoolkit.org] (24 September 2008), [http://www.kunnskapsnettverk.no www.kunnskapsnettverk.no] (25September 2008), [http://www.communities.hp.com www.communities.hp.com] (29 September 2008), Ramalingam, B., Tools for Knowledge and Learning, odi, 2006 </ref>
+
#*Create a new CoP on a different topic. <ref>[http://www.kstoolkit.org www.kstoolkit.org] (24 September 2008), [http://www.kunnskapsnettverk.no www.kunnskapsnettverk.no] (25September 2008), [http://www.communities.hp.com www.communities.hp.com] (29 September 2008), Ramalingam, B., Tools for Knowledge and Learning, odi, 2006 </ref>}}
  
 
=='''Job Aid'''==
 
=='''Job Aid'''==
 
+
[[Image:pdf.png]] [[Media:Toolkit_Template_Community_of_Practice.pdf‎‎|Implementing a Community of Practice]]
}}
+
  
  
 
== References ==
 
== References ==
 
<references/>
 
<references/>

Latest revision as of 14:52, 25 July 2013

Term2.png COMMUNITIES OF PRACTICE (CoPs)
A process of social learning where a group of people who share an interest, a concern, a set of problems, or a passion about a topic, collaborate to share ideas, find solutions, and build innovations without necessarily being in a formal work meeting. CoP members are related to one another through exposure to a common class of problems, common pursuit of solutions, and embodying a store of knowledge, by shared practices, tools, common beliefs, and language. Communities of practice generally cut across organizational boundaries and help create and share knowledge. It is best to: [1]
  • Learn while doing.
  • Ensure effective creating and sharing of knowledge and experience.
  • Co-learn about related practices across projects.


Toolkit.png Implementing a CoP

Main Components

  1. Community: active members who are interested in sharing their knowledge and who dedicate their time to the community.
  2. Domain: it must be a compelling topic; one of interest to many people and of relevance to their work. The potential members must be passionate about the subject for collaboration.
  3. Practice: the ability to compare one's own work practices to those of others is one of the foundations of the CoP.
  4. Motivation/engagement: the existence of the community is based only on the motivation of its members.
  5. Structure: it is important to find a balance between formal and informal structure. Most communities have a concentric structure at triple level (core group, closer circle, outside circle). [2]

Step by Step

  1. Creating:
    • Decide what topic you wish to address in a community in order to identify the domain.
    • To encourage people to participate, start a discussion on a domain or a small problem and present ideas and/or solutions for resolving this problem.
    • Find a committed leader or coordinator for the community: volunteer to be the community leader yourself or identify someone else. The community leader should know the subject, have energy for stimulating collaboration, regularly spend time increasing membership, lining up speakers, hosting calls and meetings, asking and answering questions, and posting information which is useful to the members.
    • Identify thought leaders to legimate the community and potential members to leverage knowledge. The community will need a critical mass of members. You usually need at least 50 members, with 100 being a better target. Try to take advantage of existing networks.
    • Decide on an initial technology platform and create one or more tools for the community to use (threaded discussion board, collaborative team space, web site or portal, Wiki, Blog, or newsletter).
  2. Starting-up:
    • Publicize the existence of your community once it is established to help recruit new members.
    • Watch the production of intermediate results, summaries and conclusions of the discussions.
    • Gather a core group (leader, experts, stakeholders) and maintain one closer circle (involved members) and one outside circle (interested members, contributors, readers).
    • Keep the community active : regular conference, periodic events, weekly meetings and collect examples of value.
  3. Developing and sustaining
    • Maintain interest and commitment by organizing workshops and meetings on major topics.
    • Introduce new and challenging perspectives.
    • Maintain the energy by recruiting new members.
    • Rotate roles and responsibilities between members over time.
    • Manage knowledge by creating knowledge maps, processing knowledge sharing , organising resources, and identifying knowledge gaps.
  4. Closing:
    • Ending the CoP when the domain is less relevant or the purpose ended.
    • Celebrate its life and achievements by organizing a special event.
    • Create a new CoP on a different topic. [3]

Job Aid

Pdf.png Implementing a Community of Practice


References

  1. Wikipedia (16 April 2008), www.km4dev.org(16 April 2008), www.kstoolkit.org (24 September 2008)
  2. www.deza.ch (29 September 2008)
  3. www.kstoolkit.org (24 September 2008), www.kunnskapsnettverk.no (25September 2008), www.communities.hp.com (29 September 2008), Ramalingam, B., Tools for Knowledge and Learning, odi, 2006