Practice knowledge base
Communities of Practice
Communities of Practice bring employees together around a professional theme to share experiences, analyze cases, and align on work standards without a formal course.
Documentation sections
What it is
A Community of Practice is a regular group of people with a shared professional theme: analytics, sales, development, project management, or another area. Participants bring real cases, show solutions, discuss mistakes, and agree on approaches. The practice bridges the gap between training and daily work: knowledge is not left in courses, but translates into common ways of working.
When it helps
- Employees solve similar tasks in different teams, but rarely get to see each other's work.
- New approaches learned in training are not incorporated into work standards and are quickly forgotten.
- Expertise is concentrated in a few individuals, and teams struggle to find people with the needed knowledge.
- Internal practices vary significantly in quality, despite similar tasks and clients.
- Employees want to develop professionally, but see no regular environment for exchanging cases.
How to start
- 1 Choose one professional topic where there are already recurring questions, mistakes, or strong internal experts.
- 2 Appoint a moderator who gathers meeting topics, invites participants, and ensures practical outcomes from discussions.
- 3 Conduct the first meeting around one real case, not a general lecture about the development of the area.
- 4 Document the agreements after the meeting: useful techniques, open questions, links to materials, and owners of next steps.
- 5 After a few meetings, check which solutions participants have started applying in their projects and which topics require a separate in-depth discussion.
Expected effect
Communities of Practice help transfer experience between teams faster: fewer solutions need to be found from scratch, and work standards grow out of real cases. Managers can more easily identify subject matter experts and areas where teams need support.
Common pitfalls
- Turning the community into a mandatory top-down training course where participants listen but don't bring their own cases.
- Discussing an overly broad topic, causing meetings to become general conversations with no practical outcome.
- Not documenting agreements after meetings, so useful solutions remain only in participants' memories.
- Appointing a moderator without the time or authority to gather topics, invite experts, and drive next steps.
- Evaluating the practice solely by attendance, without checking which approaches participants are actually applying in their work.
Further reading
- Book: Etienne Wenger, Communities of Practice: Learning, Meaning, and Identity
- Book: Etienne Wenger, Richard McDermott, William Snyder, Cultivating Communities of Practice
- Article: Etienne Wenger-Trayner, Introduction to communities of practice
FAQ
Who typically initiates a Community of Practice?
Initiation can come from a functional leader, HR, or a strong subject matter expert. It is crucial for the community to have a moderator who gathers practical questions and ensures meetings result in clear agreements.
Can a Community of Practice be started without an external consultant?
Yes. For the first step, it is enough to choose a topic, gather interested employees, and analyze one real case. A consultant is only needed if there is no internal moderator or the topic requires a specific methodology.
How can one determine if a Community of Practice is effective?
Look beyond mere attendance. Useful indicators include participants contributing cases, reusing colleagues' solutions, updating internal materials, and more quickly locating subject matter experts.
What if employees don't want to participate?
Check if the topic addresses a real workplace challenge. Start with a short case analysis where participants immediately gain an applicable solution, and don't make participation a formal obligation with no benefit.