Community of Practice
A group that develops shared capability through sustained interaction around a common domain, practice, and body of practical knowledge.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/community-of-practice/
01What it means
A community of practice brings together people who care about a domain and improve how they work through recurring participation. It combines a shared domain, relationships among members, and a developing practice of stories, methods, tools, examples, and lessons. Membership may cross formal teams and levels, and participation often varies over time.[1][2]
- Relationships
- Core, active, peripheral, and newcomer participation
- Case discussion
- Stories and real work
- Demonstrations + clinics
- Methods in use
- Peer review + mentoring
- Capability and feedback
- Shared artifacts
- Tools, examples, lessons
- Evolving purpose
- Adapt or close when value fades
Participation can vary over time; member value and practical learning matter more than meeting or documentation volume.
02Why it matters
Important knowledge is frequently contextual and difficult to transfer through documentation alone. Communities let practitioners compare cases, interpret standards, develop language, and help one another solve unfamiliar problems. They can connect isolated specialists, identify systemic capability gaps, and preserve learning that would otherwise remain inside projects or individual networks.
03When to use it
Form one when people across teams share recurring problems and have enough common practice to learn from one another. It is useful for disciplines, technologies, operational concerns, and emerging capabilities. Avoid creating a community merely because a topic appears on an organization chart; sustained member value is essential.
04How it works
- Clarify the domain and the practical value members should gain, while leaving room for the focus to evolve.
- Identify a core group willing to convene, welcome participants, and connect activity to real work.
- Use a rhythm of case discussions, demonstrations, clinics, peer review, mentoring, and shared problem solving.
- Capture useful artifacts and decisions without turning documentation volume into the main measure of success.
- Create accessible participation paths for newcomers, peripheral members, and people across locations or status levels.
- Review member value, learning, reach, and organizational support; adapt or close the community when purpose fades.
05A practical example
Researchers across several product groups form a community around inclusive research operations. Monthly clinics examine consent, recruitment, and accessibility cases. Members create adaptable templates, pair on difficult studies, and surface a recurring procurement barrier to leadership. Participation remains voluntary, while funded coordination time prevents the work from depending entirely on unpaid enthusiasm.
06Where it breaks
Communities cannot replace accountable delivery teams, formal training, or governance where decisions require authority. They may become exclusive social circles, presentation series, or hidden labor for enthusiastic members. Excessive central control can weaken ownership, but no support at all can make participation inaccessible to people with heavy workloads.
Common mistakes
- Launching a meeting series without a clear domain or recurring practitioner need.
- Measuring attendance alone instead of learning, relationships, artifacts, and changed practice.
- Expecting volunteer organizers to sustain organization-wide capability work without time or recognition.
07Sources
- Introduction to Communities of PracticeWenger-Trayner · Framework author overviewIntroduction to Communities of Practice
- Evolution of Wenger’s Concept of Community of PracticeNational Center for Biotechnology Information · Peer-reviewed open-access reviewEvolution of Wenger’s Concept of Community of Practice