Communities of Practice

Not all knowledge lives in documents, databases, or anybody's personal notes. A significant portion — arguably the most valuable portion — lives in communities: groups of people who share a concern or passion for something they do and learn how to do it better through regular interaction. These are communities of practice, and they are the oldest and most natural form of knowledge management. They predate writing, let alone computers. The medieval guild was a community of practice. So is the group of nurses who eat lunch together and swap stories about difficult patients. So is the open-source project whose contributors have never met in person but collectively maintain a body of knowledge that no individual could hold alone.

This chapter examines what communities of practice are, how they differ from other organizational structures, how they form and evolve, and how they can be cultivated — a word chosen deliberately, because communities of practice cannot be manufactured, only nurtured.

Wenger's Framework: Domain, Community, Practice

The concept of communities of practice (CoPs) was developed by Etienne Wenger, building on his earlier collaboration with Jean Lave. Wenger's framework, articulated most fully in Communities of Practice: Learning, Meaning, and Identity (1998), identifies three essential dimensions:

Domain: The shared area of interest or competence that gives the community its identity. The domain is not merely a topic but a shared set of issues, problems, and knowledge areas that members care about. A community of practice around information security has a domain that includes threat modeling, vulnerability management, incident response, compliance, and the tools and techniques associated with each. The domain defines the community's boundaries — who belongs and who does not — and its purpose.

Community: The social fabric — the relationships, trust, and mutual engagement that bind members together. A community of practice is not merely a collection of individuals who happen to know about the same things. It is a group whose members interact regularly, help each other, share information, and build relationships. The community dimension is what distinguishes a CoP from a mailing list or a database: it involves ongoing social relationships that create obligations, expectations, and a sense of belonging.

Practice: The shared repertoire of resources — tools, methods, stories, frameworks, vocabulary, experiences — that members develop through their sustained interaction. Practice is what distinguishes a CoP from a social club: the members are doing something together, developing shared ways of doing it, and continuously refining those ways through collective experience. Practice includes both the explicit artifacts (documents, templates, tools) and the tacit understandings (norms, conventions, unwritten rules) that members share.

All three dimensions must be present for a genuine community of practice to exist. A group with a shared domain but no community is just a category of professionals. A group with community but no shared domain is a social network. A group with practice but no community is a set of isolated practitioners who happen to use similar methods. The intersection of all three is where learning, knowledge creation, and knowledge transfer happen most naturally and effectively.

Legitimate Peripheral Participation

Before Wenger's solo work on communities of practice, he and Jean Lave developed the concept of legitimate peripheral participation (LPP) in Situated Learning: Legitimate Peripheral Participation (1991). LPP describes how newcomers learn by gradually moving from the periphery of a community to its center through increasing participation in its practices.

The concept emerged from Lave and Wenger's studies of apprenticeship in diverse settings: Yucatán midwives, Vai and Gola tailors, naval quartermasters, meat cutters, and nondrinking alcoholics in Alcoholics Anonymous. Across these very different contexts, they found a common pattern: learning was not primarily a matter of instruction or knowledge transfer but of participation. Newcomers began by performing simple, low-risk tasks at the margins of the community's activities, gradually taking on more complex and central tasks as they developed competence and earned the trust of established members.

"Legitimate" means the newcomer's participation is sanctioned — they are recognized as a nascent member of the community, not an interloper. "Peripheral" means they start with limited, manageable tasks rather than being thrown into full expert practice. "Participation" means they are engaged in actual practice, not merely observing or studying.

LPP has profound implications for knowledge management. It suggests that the most effective way to transfer complex, practice-based knowledge is not through documentation or training but through structured participation in a community of practitioners. A junior developer does not learn to write good code primarily by reading coding standards documents; they learn by writing code, getting code reviews from experienced developers, pair programming, and gradually taking on more complex tasks. The knowledge transfer is embedded in the social practice, not abstracted from it.

This does not mean documentation and training are useless — they provide orientation and reference. But they are supplements to participatory learning, not substitutes for it. Organizations that rely exclusively on documentation and training for knowledge transfer, without providing opportunities for legitimate peripheral participation, will find that the most important knowledge — the tacit, contextual, judgment-based knowledge that distinguishes competent practice from expert practice — does not transfer.

How CoPs Differ from Other Structures

Communities of practice are often confused with other organizational structures. The distinctions matter because each structure serves different purposes and requires different support.

Teams are defined by a shared task or deliverable. A project team exists to complete a project; when the project ends, the team disbands (in theory). Teams have formal membership, assigned roles, and accountability to management. A CoP, by contrast, is defined by a shared interest, has voluntary membership, and persists as long as the interest and relationships sustain it. Team members are selected and assigned; CoP members choose to participate.

Networks are sets of relationships between individuals who may or may not have a shared domain or practice. Your professional network includes people across different domains and practices. A network facilitates information flow and connection-making; a CoP facilitates deep learning and practice development within a specific domain.

Working groups or task forces are formed to accomplish a specific objective and dissolved when the objective is met. They have formal mandates, defined outputs, and fixed timelines. A CoP has no specific deliverable other than the ongoing development of its members' capabilities and the shared practice itself.

Interest groups share a topic of interest but do not develop a shared practice. A book club is an interest group. Members discuss books but do not develop shared methods, tools, or professional capabilities. A CoP involves collective practice development, not just collective discussion.

The key differentiator is practice. CoPs are defined by the fact that their members are practitioners who learn from each other by engaging in and reflecting on shared practice. This gives CoPs a distinctive role in knowledge management: they are the structures where practice-based, tacit knowledge is created, shared, refined, and maintained.

The Lifecycle of a Community of Practice

Communities of practice are not static. Wenger and his colleagues (particularly Wenger, McDermott, and Snyder in Cultivating Communities of Practice, 2002) describe a lifecycle with five stages:

Potential: People with similar concerns or interests recognize the potential for a community. Informal networking begins, and a shared domain starts to crystallize. At this stage, the community is not yet a community — it is a set of relationships and a nascent shared interest.

Coalescing: Members begin to come together more deliberately. They explore their shared domain, identify common challenges, and begin to build relationships and trust. Activities might include informal meetings, email exchanges, or shared projects. The community develops a sense of identity — a name, a purpose, a sense of "us."

Maturing: The community develops a clearer sense of its domain, establishes routines and practices, and takes on a more defined role in its organizational context. It may develop shared resources (templates, guidelines, toolkits), establish regular meetings or events, and attract new members. The challenge at this stage is maintaining energy and focus as the initial excitement fades.

Stewardship: The community is established and focuses on maintaining its relevance and vitality. It continues to develop its practice, manages its knowledge assets, and refreshes its membership. The risk at this stage is stagnation — the community becomes a comfortable club that stops challenging itself and stops attracting new perspectives.

Transformation: Eventually, the community may transform into something else (a formal organizational unit, a professional association, or a series of sub-communities) or it may fade as the domain becomes less relevant, members move on, or the practice is absorbed into mainstream organizational routines.

Not every community passes through all stages, and the stages are not rigidly sequential. But the lifecycle framework helps community sponsors and coordinators understand what to expect and what kinds of support are appropriate at different stages.

Cultivating Communities of Practice

Communities of practice cannot be created by management fiat. You cannot order people to share knowledge, build trust, and develop a shared practice. But you can create conditions that make CoPs more likely to form and more likely to thrive. Wenger, McDermott, and Snyder identify several key roles and practices for cultivating CoPs:

The Coordinator

Every thriving CoP has someone who serves as a coordinator (sometimes called a moderator, facilitator, or community manager). The coordinator does not lead the community in a hierarchical sense but performs essential connective and organizational functions:

• Organizing events and activities (meetings, workshops, conferences, online discussions).
• Connecting members with complementary interests or expertise.
• Identifying and engaging potential new members.
• Managing the community's knowledge assets (documents, tools, shared spaces).
• Maintaining the community's energy and focus, especially during periods of low activity.
• Acting as a bridge between the community and the broader organization.

The coordinator role is often underestimated and under-resourced. It requires social skill, domain knowledge, and organizational savvy. Communities without effective coordination tend to either stagnate (no one organizes activities, so nothing happens) or fragment (subgroups form and lose connection with each other).

Sponsorship

In an organizational context, CoPs need sponsorship from management — not control, but legitimacy and resources. Sponsorship means that management recognizes the community's value, provides time and resources for participation, removes organizational barriers, and uses the community's outputs in decision-making.

The most common way organizations undermine CoPs is by supporting them rhetorically while failing to provide the time for participation. If community activities must compete with billable hours, project deadlines, and individual performance metrics, they will lose — every time.

The Right Technology

Technology supports CoPs but does not define them. The right technology depends on the community's needs, size, and distribution:

For small, co-located communities: A shared physical space, a whiteboard, and a coffee machine may be sufficient. Regular face-to-face meetings are the core technology.

For distributed communities: Asynchronous communication tools (forums, mailing lists, Slack/Teams channels), shared document repositories (wikis, shared drives), and regular synchronous meetings (video calls, webinars) are essential.

For large communities: More sophisticated tooling may be needed: community platforms with member directories, event management, knowledge bases, and analytics.

The technology should match the community's natural communication patterns, not impose new ones. If community members already communicate via Slack, the community's digital home should be a Slack channel, not a separate platform that requires a separate login and a separate habit.

The Role of Storytelling

One of Lave and Wenger's most important insights — and one frequently confirmed by subsequent research — is that storytelling is a primary mechanism of knowledge transfer in communities of practice. Practitioners learn from each other largely through narratives: war stories, case studies, "here's what happened to me" accounts that embed knowledge in concrete, memorable, contextually rich form.

Julian Orr's ethnographic study of Xerox photocopy repair technicians (Talking About Machines, 1996) is the classic documentation of this phenomenon. Orr found that technicians learned their craft primarily by telling and listening to stories about difficult repairs — stories that communicated diagnostic strategies, machine behaviors, and troubleshooting heuristics in a form that manuals could not match. The stories were memorable because they were narratives with characters, conflicts, and resolutions. They were instructive because they embedded abstract principles in concrete situations. And they were trustworthy because they came from fellow practitioners with shared experience.

Storytelling works as a knowledge transfer mechanism because:

Stories encode context. A story about a specific incident includes the circumstances, constraints, personalities, and environmental factors that shaped the outcome. This contextual information is precisely what is lost when knowledge is abstracted into procedures and rules.

Stories are memorable. Human memory is organized narratively. We remember stories far better than we remember facts, rules, or procedures. A story about a catastrophic system failure caused by a misconfigured DNS record will stick in memory long after the relevant configuration documentation has been forgotten.

Stories convey tacit knowledge. The pauses, the emphasis, the "and then I had a feeling something was wrong" moments in a story communicate knowledge that cannot be stated as propositions. The listener absorbs not just what the storyteller did but how they thought, what they paid attention to, and how they exercised judgment.

Stories build community. Sharing stories creates bonds between tellers and listeners. It establishes shared reference points, shared vocabulary, and shared identity. "Remember the time the production database went down on Black Friday?" is not just a knowledge artifact — it is a piece of community identity.

Organizations that want to harness storytelling for knowledge transfer should create spaces and occasions for it: brown-bag lunches, retrospective sessions, mentoring conversations, and online forums where practitioners can share experiences. They should also consider capturing stories in some form — written case studies, recorded narratives, video interviews — while recognizing that captured stories are a pale shadow of live storytelling, just as a recorded concert is a pale shadow of a live performance.

Online vs. In-Person CoPs

The shift to remote and distributed work has accelerated a trend that was already underway: the migration of communities of practice from physical to digital spaces. This migration brings both opportunities and challenges.

Opportunities of online CoPs:

• Geographic reach: A distributed CoP can include members across cities, countries, and time zones, drawing on a far wider pool of expertise than any single location could provide.
• Asynchronous participation: Members can contribute when it suits them, accommodating different schedules and work patterns.
• Persistent memory: Online discussions, shared documents, and recorded sessions create an accessible archive of community knowledge.
• Lower barriers to entry: Joining an online community is easier than finding and attending physical meetings, making it easier for newcomers to begin legitimate peripheral participation.

Challenges of online CoPs:

• Relationship building: Trust and rapport are harder to build through screens than through face-to-face interaction. The casual, serendipitous encounters that build relationships — the hallway conversation, the post-meeting chat, the shared meal — do not happen naturally online.
• Engagement: Online communities suffer from the "90-9-1 rule" (or some variation thereof): roughly 90% of members are lurkers who consume but do not contribute, 9% contribute occasionally, and 1% are highly active contributors. Maintaining energy and participation is a constant challenge.
• Nuance: Text-based communication strips away tone, gesture, and facial expression, increasing the risk of misunderstanding and making it harder to convey the subtlety that characterizes expert knowledge sharing.
• Information overload: Active online communities generate volumes of content that can overwhelm members, leading to disengagement.

The most effective distributed CoPs typically combine online and in-person elements. Regular video meetings provide synchronous interaction and face-to-face connection. Asynchronous channels (forums, chat) provide ongoing conversation and knowledge exchange. And periodic in-person gatherings — annual conferences, quarterly meetups, or occasional co-located work sessions — build the deep trust and relationship capital that sustains the community between meetings.

Examples Across Contexts

Open Source Communities

Open-source software communities are among the most successful and well-studied examples of communities of practice. The Linux kernel community, the Apache Software Foundation, the Python community, and hundreds of others demonstrate how CoPs can operate at massive scale, produce high-quality knowledge artifacts (code, documentation, standards), and sustain themselves over decades.

Several features of open-source CoPs are instructive:

Meritocratic governance: Influence is earned through contribution, not conferred by organizational position. This creates strong incentives for knowledge sharing, since sharing knowledge (through code, documentation, code reviews, and forum answers) is the primary path to status and influence.

Transparent practice: Code reviews, mailing list discussions, and issue trackers are public, creating a persistent, searchable record of the community's knowledge and decision-making. Newcomers can learn by reading the archive — a form of legitimate peripheral participation.

Structured onboarding: Successful open-source projects invest in "good first issues," mentoring programs (Google Summer of Code, Outreachy), and contributor guides that create explicit pathways for peripheral participation.

Distributed, asynchronous collaboration: Open-source communities have developed sophisticated practices for collaborating across time zones and cultures, including code review norms, communication protocols, and governance structures that do not require synchronous interaction.

Professional Associations

Professional associations — the American Medical Association, the IEEE, the Bar Association, the Project Management Institute — function as large-scale communities of practice. They define and maintain professional domains (through standards, certifications, and scope-of-practice definitions), facilitate community (through conferences, local chapters, and special interest groups), and develop practice (through best-practice guidelines, continuing education, and peer review).

Professional associations are an instructive example of CoP cultivation at scale, but they also illustrate the tensions that arise when a CoP becomes formalized. Formal certification and credentialing can create barriers to entry that conflict with legitimate peripheral participation. Standard-setting can rigidify practice and resist innovation. And the governance structures needed to manage large associations can become bureaucratic, alienating the practitioners they are meant to serve.

Corporate CoPs

In corporate settings, communities of practice have been deliberately cultivated since the mid-1990s. Shell, World Bank, Caterpillar, DaimlerChrysler, and many other organizations have invested in CoPs as a KM strategy, with varying degrees of success.

The World Bank's thematic groups, launched in the late 1990s, are a frequently cited example. These groups brought together Bank staff working on similar development challenges (health, education, infrastructure) across different regional offices and country programs. The groups shared knowledge through databases, help desks, and regular meetings, and they were credited with improving the speed and quality of the Bank's development work.

Caterpillar's communities of practice, established in the early 2000s, connected engineers and technicians across the company's global operations. Each community focused on a specific technical domain (hydraulics, electronics, materials) and maintained a knowledge repository, held regular meetings, and facilitated expert-to-expert connections. The communities were credited with reducing product development time and improving problem resolution.

The corporate CoPs that succeed tend to share several characteristics: strong sponsorship that provides time and resources without imposing control, effective coordination by respected practitioners (not managers), alignment between the community's domain and the organization's strategic priorities, and visible evidence that the community's knowledge actually influences decisions and outcomes.

The corporate CoPs that fail tend to share different characteristics: top-down mandates that create communities without genuine shared interest, inadequate time allocation that forces community activities to compete with project work, management co-option that turns the community into a reporting mechanism, and lack of evidence that participation makes any difference.

CoPs and Knowledge Management

Communities of practice are not a KM technique in the same way that taxonomies, knowledge bases, and after-action reviews are KM techniques. They are, rather, the social infrastructure that makes those techniques work. A lessons-learned database without a community to populate and use it is a digital graveyard. A taxonomy without practitioners who understand and apply it drifts into irrelevance. A knowledge base without contributors is empty.

Conversely, a thriving community of practice generates and transmits knowledge even without formal KM systems. The knowledge lives in the interactions, the stories, the shared practice, and the relationships between members. Formal KM systems can amplify, extend, and preserve this knowledge, but they cannot create it. Only communities can do that.

This is why the most effective KM strategies combine technological and social components: knowledge bases and communities, documentation and storytelling, search engines and personal networks, AI-powered retrieval and human conversation. The technology captures and scales; the community creates and contextualizes. Neither alone is sufficient. Together, they constitute a knowledge management capability that is greater than the sum of its parts.