PTENES
MODULE 3.10

👥 Community of Practice

How internal networks for collective learning—Etienne Wenger's Communities of Practice—sustain and amplify an innovation culture far beyond what any formal program can do on its own.

6
Topics
45
Minutes
Advanced
Level
Culture
Type
1

📚 What Is a Community of Practice

In 1991, researcher Jean Lave and social theorist Etienne Wenger coined the concept of Community of Practice (CoP) by studying how learners actually learn—not in classrooms, but by practicing alongside masters. Wenger developed the concept over decades, formalizing it in “Communities of Practice: Learning, Meaning, and Identity” (1998). The definition is precise: a CoP is a group of people who share an interest or profession and learn to do better as they interact regularly.

Core Champions Active Active Active Active Periphery Periphery Periphery Periphery Active Community Periphery Periphery Structure of a Community of Practice

📝 Wenger’s 3 Constitutive Elements

Domain

The shared area of knowledge that gives the group its identity. Example: "digital product innovation." Without a clear domain, a CoP is just a chat group.

Community (Community)

Relationships among members—who helps whom, how they share experiences, and how trust and reputation are built over time.

Practice (Practice)

The shared repertoire: tools, frameworks, stories, cases, vocabulary, and ways of solving problems that the group accumulates over time.

📊 CoPs in Numbers

  • World Bank: reduced report production time by 40% after implementing sector-specific knowledge CoPs (Wenger, McDermott & Snyder, 2002).
  • Schlumberger: saved US$ 200 million over 5 years by reusing knowledge through engineering CoPs (McKinsey Quarterly, 2003).
  • Xerox: the “Eureka communities” of field technicians generated more than 5,000 tips that saved US$ 100 million in redundant service calls.
2

🌎 Why CoPs Sustain an Innovation Culture

Formal innovation programs depend on budget, sponsors, and strategic priority—three things that change with each leadership cycle. CoPs are different: they survive through social legitimacy, not hierarchical mandate. When an engineer learns something useful in a CoP and solves a real problem the next day, the community gains organic credibility that no top-down program can buy.

🔗 The 4 Mechanisms Through Which CoPs Cultivate Innovation

1
Transfer of tacit knowledge

Tacit knowledge (how to navigate politics, how to get quick approval, which shortcuts work) can only be transferred through social interaction—not documentation. CoPs are the natural channel.

2
Expanded psychology of safety

Within a CoP, members experiment and make mistakes in front of peers who respect them—not bosses who evaluate them. This reduces the perceived cost of risk and increases the frequency of experiments.

3
Cross-pollination

An innovation CoP brings together people from different areas around a shared domain. When IT and sales solve the same problem together, solutions emerge that neither would have come up with alone.

4
Innovator identity

Wenger argues that participation in communities shapes who we are, not just what we know. Being an active member of an innovation CoP helps people identify as innovators—and that changes behavior.

✓ CoP that sustains culture

  • •An agenda guided by members, not HR
  • •Voluntary participation with intrinsic value
  • •A body of knowledge generated by the members themselves
  • •Success measured by impact on real work

✗ CoP that turns into bureaucracy

  • •An agenda set by the manager or the program
  • •Mandatory attendance is recorded in a system
  • •Corporate Slides Recycled at Every Meeting
  • •Quantity KPI (members, meetings, posts)
3

🌟 Roles: Champions, Sponsors, and Facilitators

Wenger and colleagues found that successful CoPs are not democratic in the sense of having no roles—on the contrary, they have clear roles, but validated by the community, not by hierarchy. Confusion between an organizational role and a role in the CoP is one of the main causes of early mortality.

🏆 The Three Essential Roles

C

Champion (Community Leader)

The engine of a CoP. Knows the domain deeply, catalogs the repertoire, and is recognized by peers as a go-to resource — independent of the formal title. In Wenger’s model, the champion is elected by the practice, not appointed by management.

Typical commitment: 20-30% of the time. Examples: the engineer everyone consults before opening an incident; the designer who organizes the monthly retrospectives.
S

Sponsor (Executive Sponsor)

Someone in middle or senior management who removes operational barriers—frees up calendar time, secures budgets for in-person events, and advocates for the CoP in portfolio meetings. The sponsor doesn’t take part in day-to-day work, but protects the space.

Classic mistake: the sponsor becoming the "owner" of the CoP and setting the meeting agenda. This eliminates the autonomy that drives genuine engagement.
F

Facilitator (Core Team)

A small group (3-7 people) that co-leads the community with the champion. It handles logistics, onboarding new members, content curation, and organizing rituals. The role should rotate every 12-18 months to prevent oligarchy.

Reference: Wenger, McDermott & Snyder (2002) call this group the "core group" and recommend a maximum size of 15% of the active community.

💡 Practical tip: separate hierarchy from role

Never appoint the champion based on their job title. Ask team members: “Who do you go to when you have a difficult question about X?” The group’s answer identifies the natural champion. Formalize this role without changing compensation — symbolic recognition (internal visibility, invitations to external events) is already enough in most organizations.

4

📅 Rituals, Channels, and Cadence

Wenger describes the shared repertoire as one of the three pillars of a CoP—and much of this repertoire is built through rituals. Rituals are recurring gatherings with a recognizable format that create a sense of belonging and continuity. Without rituals, the community is a group with good intentions; with rituals, it has an identity and a history.

🆕 Recommended Cadence

Weekly
Asynchronous channel (Slack/Teams)
  • • Insight post / article of the week
  • • "What I learned this week"
  • • Open question for the community
Biweekly / Monthly
Synchronous meeting (60-90 min)
  • • Case sharing: someone presents a real problem
  • • Hands-on workshop (tool, framework)
  • • External guest / researcher
Quarterly / Semiannual
In-person event (half-day)
  • • Internal domain hackathon
  • • Review of the shared repertoire
  • • Recognition ceremony

📱 Channel Stack

Async (text) A Slack/Teams channel with fixed topics: #questions, #cases, #resources. Avoid a single channel—polysemy kills the signal.
Sync (video) Zoom/Meet with a recording and summary published within 24h for those who didn’t attend.
Repository Notion/Confluence with case studies, a living glossary, and templates. This is the knowledge that remains when people leave.
In person At least once a year. Microsoft (2022): weak ties degrade 25%/year in fully remote environments.

⚠ Pitfall: too much cadence kills spontaneity. The best cadence is the sparser while still maintaining continuity — if members arrive tired, reduce the frequency and improve the quality.

5

🏆 Recognition and Gamification

The paradox of recognition in CoPs: money kills intrinsic motivation. Edward Deci and Richard Ryan (Self-Determination Theory, 1985-2000) demonstrated that extrinsic rewards reduce engagement in activities people already do for pleasure. This doesn't mean ignoring recognition — it means recognize in a way that amplifies intrinsic motivation, not to replace it.

🌟 3-Tier Recognition System

Layer 1: Internal Visibility

Zero cost

Public mention in an internal newsletter, a post in the company's general channel, presentation of cases at all-hands. Visibility among peers is a stronger motivator than an individual bonus (Amabile & Kramer, "The Progress Principle", 2011).

Layer 2: Access to Opportunities

Low cost

Active members get priority to represent the company at conferences, participate in pilots for new projects, access external courses, and co-present with the C-level at events. Recognition opens the door to more learning — closing the intrinsic motivation loop.

Layer 3: Light Gamification

Use with care

Badges, leaderboards, and points work well for new members who have not yet internalized the value of the community. For veterans, heavy gamification is patronizing. Rule: gamify onboarding, not long-term participation.

✓ Recognition that works

  • •Specific: “Your case about X helped Y people”
  • •Immediate: published right after the contribution
  • •Peer-based: validated by the community, not just the manager
  • •Linked to business impact

✗ Recognition that distorts

  • •Participation bonuses — create passive attendance
  • •Individual ranking — creates competition, not collaboration
  • •Awards only at the annual event — cycle is too long
  • •Linked to formal performance reviews

💡 Reference: the Toyota model

Toyota’s engineering CoPs (obeya and jishuken) don’t use points or badges. Recognition comes from responsibility for a real kaizen that delivers visible results on the production line. The work is the reward—and it’s why the Toyota Production System has survived 70 years of management turnover.

6

🚀 How to Start and Keep the Community Active

Wenger warned: "CoPs aren't created—they're cultivated." The garden metaphor is more accurate than the engineering one. You don't build a CoP the way you build a process; you prepare the soil, plant seeds, remove obstacles, and let living organisms grow at their own pace. A manager's role is to create the conditions, not control the outcomes.

📅 Launch Roadmap (0-6 Months)

M1
Months 1-2: Find the enthusiasts

Identify 5-8 people who are already practicing informally. One-on-one interviews: "What would you like to learn? What could you teach?" Don't announce it yet—avoid sign-ups driven by status.

M2
Months 2–3: Founder meeting

A 2-hour meeting to co-create the domain, define the core team, and agree on the first ritual. The meeting isn’t for presentations—it’s for real work on a real problem.

M3
Months 3–4: Controlled launch

Invite 15-20 people through referrals from the founders. Open the channel and publish the first case study. Referrals ensure a strong concentration of interest before scaling.

M4
Months 4–6: First tangible result

A CoP needs a "showcase result"—a problem solved, a framework created, documented savings. That result legitimizes its existence in the eyes of sponsors and undecided peripheral members.

🌿 CoP Health Signals

Healthy

  • ✓New members arrive through referrals from people already here
  • ✓Questions come up spontaneously in the channel
  • ✓Members help one another without the champion's involvement
  • ✓The repertoire grows without external forces

In risk

  • ✗Only the champion posts in the channel
  • ✗Attendance drops when the champion is absent
  • ✗Discussions stay superficial, with no disagreement
  • ✗No new members in more than 3 months

💡 Wenger's rule for longevity

In an interview with Harvard Business Review (2000), Wenger said: "The longest-lasting CoP is the one that learns to reinvent itself. When the original domain is resolved, the community needs to find the next relevant problem—or dissolve with dignity." A CoP that has fulfilled its purpose and should be closed is a sign of success, not failure.

📋 Module Summary

✓
CoP = domain + community + practice (Wenger) — without all three elements, it’s just an interest group
✓
CoPs survive through social legitimacy, not mandates — which is why they resist leadership changes that kill formal programs
✓
Clear roles without hierarchy: champion, sponsor, facilitators — the champion is chosen through practice, not by title
✓
Rituals create identity; a steady cadence maintains quality — weekly async + monthly sync + in-person every six months is the proven standard
✓
Intrinsic recognition beats bonuses; gamification only during onboarding — 0-6 months: cultivate genuine enthusiasts, not status seekers

Next Module:

3.11 - The Future of Innovation

← Back to Track 3.11 - The Future of Innovation →