# Cultivating Communities of Practice ## PROMPT 0 — Source, provenance, and reading contract ### Source record This is Etienne Wenger, Richard McDermott, and William M. Snyder’s 2002 practitioner book, not the 2022 scan date carried in the PDF metadata. The local PDF’s title page, copyright page, contents, and author page identify the work and its three authors. Its 304-page publisher edition is listed by [Harvard Business Review Press](https://store.hbr.org/product/cultivating-communities-of-practice-a-guide-to-managing-knowledge/3308); the local scan has 312 physical pages because of scan matter. I read the complete extracted source. Spot-render checks of the contents, chapter 1, chapter 4, chapter 8, chapter 10, and end matter show that the text extraction is legible enough for analytical use. The book reports organizational cases and practitioner experience; it is not a comparative study that can establish that a community of practice caused every reported business outcome. ### Source hierarchy | Layer | What it supplies | Limits | | --- | --- | --- | | L1 | Complete local book: arguments, cases, frameworks, cautions | Case narratives often lack counterfactuals or independent measures | | L2 | HBR publisher record | Confirms bibliographic identity, not the claims’ truth | | L3 | Later scholarship on conceptual ambiguity and limits | Helps test the model; not evidence that this book’s cases failed | | L4 | Vault connections and proposed practices | My synthesis, never author attribution | No Readwise file or embedded reader-highlight layer was available. Do not read system-selected passages or this review’s emphasis as Courtney’s selections. ### Connection contract This book belongs beside [[4. Archives/Book reviews/Mastering Community Management]], [[4. Archives/Book reviews/The Community Manager’s Playbook]], [[3. Resources/Literature Notes/Community Architecture - What Makes Communities Thrive vs Extract - Literature Note]], and [[3. Resources/Permanent Notes/A Project Is the Community Not the Code]]. It supplies a knowledge-and-practice lens that makes those community-management notes less event- or audience-centered. The book is useful for DevRel only if “community of practice” remains distinct from a customer audience, user forum, marketing list, or project team. Its strongest question for this vault is: *where do people who share a difficult practice gain enough trust, time, and authority to improve that practice together?* ### Reading risks and safeguards - Treat reported Chrysler, Shell, World Bank, McKinsey, and construction cases as illustrative case evidence, not universal proof. - Separate voluntary participation from coerced “community” programs. A mandatory internal network may use community language while lacking community agency. - Test whether a named domain is consequential and shared. A generic “engagement community” lacks the focus the authors require. - Treat belonging and trust as conditions with distributional questions: who can join, speak, be believed, access the tools, and contest norms? - Do not use community health metrics to monitor individuals or reward public loyalty. ## PROMPT 1 — Questions, priors, and success conditions ### Open questions 1. What makes a community of practice different from a team, audience, professional association, guild, or Discord server? 2. Can management resource a community without turning it into a compliance program? 3. What evidence shows that shared knowledge changed a practice rather than merely generated conversation? 4. Whose knowledge becomes canonical, and who bears the cost of participating? 5. What appeal path exists when a coordinator, sponsor, or core group excludes someone? 6. How does a distributed community retain local knowledge instead of standardizing it away? 7. Which DevRel work belongs in a community of practice and which belongs in support, product feedback, documentation, or marketing? 8. Does story-based value evidence preserve causal complexity or invite favorable anecdote selection? 9. How should an organization close, pause, or renew a community whose domain no longer matters? 10. What conditions allow a public-facing professional community to have real autonomy when its host organization controls the platform? ### Starting priors | Proposition | Prior | Why | | --- | --- | --- | | Shared practice can produce useful peer learning | High | Plausible mechanism and broad experience, though magnitude varies | | Sponsorship can help without control | Medium | Depends on resource terms and autonomy safeguards | | Participation counts show value | Low | Counts do not show changed practice or outcomes | | Stories can illuminate a contribution chain | Medium-high | Strong for mechanism discovery, weak for sole causal proof | | Tight communities can exclude and stagnate | High | The authors identify this directly; it accords with group dynamics | | One CoP model transfers unchanged across cultures and power structures | Low | Local conditions, language, employment status, and technology differ | | A customer brand community is automatically a CoP | Low | Shared consumption is not necessarily shared practice | ### Success conditions for this review The review succeeds if it preserves the authors’ domain–community–practice model, names where the evidence is case-bound, connects it to the vault’s community and knowledge notes, and makes exclusion, accessibility, worker power, and governance design first-class tests rather than an afterthought. ## PROMPT 2 — Inspectional map and thesis ### Structure and reading map | Unit | Function | Anchor | | --- | --- | --- | | Preface | Positions communities as practical infrastructure for knowledge work | PDF 15–18 | | 1. Value to organizations | Defines CoPs and gives the organizational value case | PDF 19–42 | | 2. Structural elements | Defines domain, community, and practice | PDF 43–68 | | 3. Seven principles | Offers an adaptive cultivation approach | PDF 69–92 | | 4. Early development | Planning, launching, and coordinator work | PDF 93–120 | | 5. Mature development | Growth, stewardship, renewal, and change | PDF 121–140 | | 6. Distributed communities | Local/global structures and technology-mediated participation | PDF 141–166 | | 7. Downside | Failure, exclusion, ownership, factionalism, and organizational barriers | PDF 167–190 | | 8. Value creation | Causal stories plus documented evidence | PDF 191–216 | | 9. Knowledge initiatives | A portfolio and organizational support structure | PDF 217–244 | | 10. Beyond organizations | Civic and global extensions | PDF 245–268 | | Notes, bibliography, index | Citation trail and vocabulary | PDF 269–312 | ### Provisional thesis Communities of practice are not containers for content. They are ongoing social learning arrangements in which people who care about a shared domain build relationships and a repertoire of practice. Organizations should cultivate their conditions of life rather than command their output: support evolution, maintain dialogue with the organization, allow peripheral participation, create public and private space, attend to value, mix familiarity with novelty, and maintain a workable rhythm. The authors argue that this arrangement can make tacit and explicit knowledge available for action, and that it should be assessed through documented stories that trace activity, knowledge resource, changed practice, and outcome. The book’s best corrective is also its weakest institutional challenge: it says communities can hoard knowledge, reproduce social prejudice, capture expertise, and become barriers to learning, but its remedies rely largely on attentive design and sponsors. For this vault, that means combining cultivation with explicit governance, accessibility, consent, and an independent way to contest harm. ### Key terms | Term | Operational definition in this review | Guardrail | | --- | --- | --- | | Community of practice | Ongoing social learning around a consequential shared practice | Not simply any group or customer audience | | Domain | The shared issue that gives members legitimacy and purpose | Must not be a vague corporate slogan | | Community | Relationships of mutual engagement, trust, and identity | Trust must not mean uncritical conformity | | Practice | Shared tools, stories, language, methods, and standards | A document repository alone is not practice | | Cultivation | Creating conditions for a community’s own development | Not managerial manufacture | | Core participant | Member investing sustained energy in community work | Core status must not become gatekeeping authority | | Peripheral participant | Legitimate, lower-intensity participant | Not a second-class member | | Value creation story | Account tracing activity to knowledge resource to use and outcome | Needs disconfirming evidence and context | ### Seven principles, source-checked 1. Design for evolution. 2. Open a dialogue between inside and outside perspectives. 3. Invite different levels of participation. 4. Develop both public and private community spaces. 5. Focus on value. 6. Combine familiarity and excitement. 7. Create a rhythm for the community. ## PROMPT 3 — Classification and conceptual controls ### What kind of book is this? It is a practitioner-oriented management and organizational-learning guide. It draws on cases, the authors’ consulting and facilitation experience, examples, and conceptual framing. It does not present a reproducible research method, sampling frame, effect sizes, or a cross-case causal analysis. Its claims should therefore be read as design hypotheses and practice guidance. ### Distinctions that prevent category errors | Confusion | Why it fails | Better distinction | | --- | --- | --- | | CoP = online community | A platform may host many relationship types | Ask whether people develop a shared practice | | CoP = project team | Projects have bounded deliverables; CoPs steward an ongoing domain | Link them, but do not merge them | | CoP = customer community | Customers may share interest without improving a practice together | Treat practitioners, contributors, and customers differently | | CoP = knowledge base | Documents are a resource, not mutual learning | Pair capture with relationships and use | | CoP = culture | Culture is broad; a CoP has a particular domain and repertoire | Define the boundary and purpose | | Facilitation = control | Convening can support agency or impose it | State who decides purpose, norms, and closure | | participation = inclusion | Attendance does not prove safety, access, voice, or influence | Audit participation by role and outcome | | anecdote = proof | A persuasive story can omit alternatives | Preserve counterfactuals and disconfirming cases | ### Tensions the book handles well - Organic participation versus designed support. - Internal community perspective versus organizational priorities. - Public convening versus private peer exchange. - A committed core versus legitimate peripheral participation. - A familiar rhythm versus periodic novelty. - Local relevance versus distributed connection. ### Tensions it leaves underdeveloped - Informal power, retaliation, and an appeal path for harm. - Labor conditions: participation time, unpaid community labor, precarity, and career risk. - Accessibility beyond technology choice, including pace, sensory access, language, and cognitive load. - Data governance for stories, archives, participation records, and social graphs. - Indigenous, racialized, disability, and Global South knowledge traditions when organizations set the domain’s terms. ## PROMPT 4 — Claim inventory and argument dependencies ### Stable claim inventory | ID | Claim | Source label | Evidence expected | Falsifier or limiter | | --- | --- | --- | --- | --- | | C-01 | CoPs deepen knowledge through ongoing interaction around a concern or passion. | EA | Observed shared learning and practice change | A group with interaction but no repertoire or changed practice | | C-02 | Domain, community, and practice are mutually necessary elements. | EA | Cases showing loss when one is absent | Durable counterexample lacking one element | | C-03 | A domain gives members legitimacy, purpose, and focus. | EA | Members can name a consequential problem | Generic label with no shared problem | | C-04 | Community trust enables people to expose uncertainty and ask for help. | EA | Help-seeking and reciprocal correction | Fear of error or silent participation | | C-05 | Practice includes stories, tools, language, documents, and methods. | EA | Repertoire used in work | Repository never used or discussed | | C-06 | Organizations can support but cannot simply command a living CoP. | EA | Autonomy under resource support | Mandated group still showing no agency | | C-07 | Evolutionary design fits CoPs better than a fixed blueprint. | EA | Iteration responding to member practice | Stable context where a fixed design outperforms | | C-08 | Multiple participation levels can widen access without demanding equal intensity. | EA | Peripheral routes into meaningful exchange | Periphery systematically unheard or blocked | | C-09 | Both public and private spaces are needed. | EA | Different disclosure and learning functions | One format meeting all tested functions well | | C-10 | Rhythm sustains participation without overload. | EA | Attendance, contribution, and reported usefulness over time | Rhythm producing exhaustion or exclusion | | C-11 | Distributed CoPs need deliberate local/global links. | EA | Exchange that retains local applicability | Centralized flow suppressing local knowledge | | C-12 | CoPs can hoard knowledge and block innovation. | EA | Gatekeeping, stagnant repertoire, outsider reports | Open learning and contestation over time | | C-13 | CoPs can reproduce broader prejudice and exclusion. | EA | Membership and voice patterns | Equity claim without disaggregated evidence | | C-14 | Strong community can become a way of avoiding learning. | EA | Unquestioned assumptions and resistance to challenge | Routine dissent and external learning | | C-15 | Value assessment should trace activity, resource, application, and outcome. | EA | Documented contribution chain | Claimed impact with missing links | | C-16 | Counts need causal stories to become meaningful. | EA | Contextualized quantitative and narrative evidence | Counts independently tied to decisions/outcomes | | C-17 | Stories need rigorous documentation to avoid pure impression. | EA | Consistent collection and review protocol | Selective success stories only | | C-18 | Community-based knowledge initiatives work through a portfolio of communities and organizational supports. | EA | Role, resource, and connection map | One-size central program displacing local practice | | C-19 | CoPs can address problems beyond organizations. | EA | Civic examples with accountable local participation | Global rhetoric without local agency | | C-20 | CoP work maps to DevRel when practitioners improve a shared craft, not when they are merely marketed to. | RI | Evidence of peer practice exchange | Audience engagement mistaken for practice | | C-21 | The model needs an explicit governance and appeals layer. | RI | Written norms, escalation, review, and repair | Sponsor discretion as only remedy | | C-22 | Knowledge capture does not equal formation. | RI | Shared use, revision, and relationships | Large archive with no changed practice | | C-23 | Community metrics should not become individual surveillance. | RI | Data minimization and aggregate reporting | Participation data used for performance control | | C-24 | Community health is inseparable from accessibility and distribution of voice. | RI | Access and influence audit | Mere attendance treated as inclusion | EA means authorial argument. RI means review inference. C-20–C-24 are not claims made by Wenger, McDermott, or Snyder. ### Dependency map ```mermaid flowchart TD A["Consequential shared domain"] --> B["Trusting relationships"] B --> C["Shared repertoire and practice"] A --> C C --> D["Learning activity"] D --> E["Knowledge resource"] E --> F["Application in work or civic practice"] F --> G["Outcome and value evidence"] H["Resource, legitimacy, and autonomy"] --> A H --> B I["Governance, accessibility, and appeal"] --> B I --> C J["External perspectives"] --> A J --> C ``` The load-bearing premise is not “community causes performance.” It is the smaller proposition that ongoing peer interaction can generate resources that are then applied. Each later link needs its own evidence. ## PROMPT 5 — Evidence policy and priors ### Evaluation policy This is qualitative, case-based practitioner literature. I use confidence bands rather than pretend the book contains effect estimates. | Grade | Meaning here | | --- | --- | | A | Directly demonstrated with independent, transparent evidence; none awarded | | B | Well-supported conceptual or case-based claim with plausible mechanism and clear limits | | C | Plausible but case-bound, selective, or underspecified | | D | Materially limited, overextended, or weakly evidenced | | N/A | Normative or theological claim not apt for empirical grading | Evidence sources within a single favorable organizational case are dependent. A case report, its selected performance indicator, and its executive testimony count as one evidence family, not three confirmations. HBR’s publisher page confirms the book’s identity but does not upgrade a case claim. ### Prior-to-posterior controls - Update on mechanisms, not prestige of named firms. - Give positive and negative cases equal search space. - Keep “contribution” separate from sole causation. - Record who supplied the story and who had reason to show success. - Ask what would have happened without the community, while admitting that a true counterfactual may be unavailable. - Do not convert a management objective into a measure of a person’s worth or belonging. ### Initial confidence bands | Claim group | Prior | Rationale | | --- | --- | --- | | Definition and structural distinctions (C-01–C-05) | B | Coherent and usable conceptual framework | | Cultivation principles (C-06–C-11) | B/C | Strong practice logic, context-sensitive outcome evidence | | Failure and exclusion risks (C-12–C-14) | B | Source states them directly; historical examples are illustrative | | Measurement model (C-15–C-17) | B/C | Good contribution discipline, weak for causal proof alone | | Organization/civic extensions (C-18–C-19) | C | Scope enlarges faster than evidence detail | | Vault inferences (C-20–C-24) | B as design safeguards | Derived from the book plus vault context, not source proof | ## PROMPT 6 — Analytical scaffold ### Argument spine 1. Knowledge work depends on social learning, especially where knowing cannot be fully codified. 2. CoPs supply a durable form for social learning around a domain. 3. Their anatomy is domain, community, and practice. 4. They should be cultivated through seven adaptive principles rather than produced as a fixed program. 5. They pass through early, mature, distributed, and renewal challenges. 6. They can fail through stagnation, ownership, prejudice, factionalism, and organizational interference. 7. Their claimed value should be traced through contribution stories and systematic documentation. 8. Organizations can support a portfolio of communities; the authors extend the idea to public life. ### Evidence ledger | Evidence family | What it can support | Main limitation | | --- | --- | --- | | Chrysler and other business cases | Plausible organizational mechanisms and use cases | Selection and causal attribution limits | | Authors’ facilitation experience | Design sensitivity and practitioner detail | Not independently audited research | | Structural model | Clear diagnostic vocabulary | Definitions can travel beyond their original evidence | | Downside chapter and historical examples | Anti-romanticization and risk detection | Remedies remain broad | | Value-creation stories | Contribution tracing | Story selection can privilege success and sponsors | | Later CoP criticism | Conceptual caution and power questions | Does not invalidate every local CoP | ### Weakest links and repairs | Weak link | Why it matters | Repair in current use | | --- | --- | --- | | Performance claims from cases | Could become ROI theater | Publish contribution chains, negative cases, and uncertainty | | Sponsor/community boundary | Managers may redefine autonomy as compliance | Set written decision rights and no-retaliation protection | | Inclusion discussion | Identifies prejudice but lacks operational equity method | Audit access, voice, influence, and remedy by affected group | | Global extension | Risks exporting a corporate model | Start from local knowledge holders and accountable governance | ### Prompt 7 entry conditions Before calling a proposed CoP successful, name: domain; participant roles and access; practice outputs; time and resourcing; decision rights; data policy; harm/appeal process; a contribution chain; negative or null signals; and a renewal or closure condition. ## PROMPT 7 — Fair evaluation and updated judgments ### Evaluation summary | Grade | Claims | Judgment | | --- | --- | --- | | B | C-01–C-06, C-08–C-10, C-12–C-17, C-20–C-24 | Useful, bounded design claims or necessary safeguards | | C | C-07, C-11, C-18, C-19 | Plausible but more context-dependent or overextended | | D | None | No central claim is rejected outright, but several need stronger conditions | | A | None | The source does not supply independent causal evidence at this level | ### What stands up The domain–community–practice triad is an unusually good diagnostic. It stops three common failures: forcing a generic social channel into a “community,” treating a library as learning, and confusing a temporary project group with a continuing practice. The seven principles are also useful as tensions to manage rather than a checklist. In particular, legitimate peripheral participation and private spaces correct the assumption that everyone should perform visible engagement. The downside chapter is the book’s most durable contribution. It explicitly says communities can hoard knowledge, limit innovation, hold others hostage to expertise, reproduce prejudice, and become part of the problem they are meant to solve. That warning belongs in every downstream Community Health framework. ### What needs repair The value chapter appropriately resists empty activity metrics. But “systematic anecdotal evidence” still needs a selection protocol, disconfirming examples, and a statement of attribution uncertainty. A story can show how participants understood a contribution; it normally cannot isolate the community from staffing, leadership, market timing, or other changes. The authors advise a sponsor to support rather than control communities. That is necessary but not sufficient. If a sponsor controls budget, platform, employment evaluation, or who gets recognized, informal voluntariness can become coercive. Modern implementation should add transparent sponsorship terms, minimum data collection, an appeal route outside the core group, and a review of who benefits from the community’s work. Later scholarship has also questioned the concept’s conceptual looseness and its use as management ideology. [Roberts’s review of limits](https://doi.org/10.1111/J.1467-6486.2006.00618.X) and [Cox’s critique of ambiguity](https://doi.org/10.1177/0165551505057016) are not refutations; they are reasons to define membership, domain, authority, and outcomes before launching a program. A 2024 study of practice alignment in international relations likewise distinguishes organic community formation from top-down cultivation ([Bicchi](https://academic.oup.com/isagsq/article/4/1/ksad076/7603152)). ### Bias and fallacy scan - **Success-case selection:** named firms and improvement stories may privilege visible wins. - **Post hoc attribution:** improvement after community formation does not establish it as the cause. - **Managerial framing:** “value” often means organizational performance, not member wellbeing or worker autonomy. - **Community romanticism:** the book counters this better than many management texts, but its repairs depend on good sponsors. - **Representation gap:** historical examples acknowledge exclusion, yet do not produce a full intersectional governance method. ## PROMPT 8 — Context, systems, and intellectual lineage ### System map ```mermaid flowchart LR P["Practitioners"] --> C["Community of practice"] C --> K["Shared knowledge resources"] K --> W["Work, service, or civic action"] S["Sponsors and organizations"] -->|"time, legitimacy, tools"| C S -->|"priorities and control pressure"| C X["External peers, customers, and local contexts"] --> C G["Governance, accessibility, and redress"] --> C C -->|"learning and challenge"| S ``` The book sits in the early-2000s knowledge-management moment: intellectual capital, lessons learned, global firms, and collaboration technology. It argues against treating knowledge as merely stored information. That correction still matters in an AI-assisted documentation environment, where content production can outpace shared understanding. Its intellectual lineage includes situated learning and social practice, organizational learning, knowledge management, and practitioner community design. Its limits are also historical: it treats organizational sponsorship as more benign than many platform workers, open-source maintainers, contractors, and marginalized employees may experience it today. ### Vault synthesis | Connection | What this book adds | What the connected note adds back | | --- | --- | --- | | [[4. Archives/Book reviews/Mastering Community Management]] | The domain–community–practice test and a learning value chain | RENEW and care-oriented community operations help make role work humane | | [[4. Archives/Book reviews/The Community Manager’s Playbook]] | A non-brand-centric purpose for community work | Strategy, listening, and response disciplines that this 2002 book under-specifies | | [[3. Resources/Literature Notes/Community Architecture - What Makes Communities Thrive vs Extract - Literature Note]] | A mature vocabulary for participation, spaces, rhythm, and practice | An anti-extractive test for sponsorship and resource capture | | [[3. Resources/Permanent Notes/Information Capture Is Not Formation]] | Explains why a capture system needs social use and practice | Prevents treating a knowledge base as the desired endpoint | | [[3. Resources/Permanent Notes/A Project Is the Community Not the Code]] | Shows how practice can connect a project’s people, methods, and learning | Guards against treating technical artifacts as the whole project | | [[3. Resources/MOCs/Commons & Community Governance MOC]] | A concrete institutional form for shared knowledge work | Governance, polycentricity, boundaries, and anti-capture checks | | [[3. Resources/MOCs/DevRel MOC]] | A test for when developer participation becomes peer practice | Product feedback, docs, events, and support routes that must remain distinct | ## PROMPT 9 — Inclusion, accessibility, power, and transfer ### Inclusion audit | Dimension | Source strength | Missing operational control | Current implementation requirement | | --- | --- | --- | --- | | Race and ethnicity | Names apartheid-era exclusion and broader prejudice | No measurement or remedy process | Review access, influence, sponsorship, and retention with affected members | | Gender | Names guild exclusion of women | No gendered labor or safety analysis | Track who convenes, documents, mentors, and receives recognition; offer redress | | Disability | Distributed participation implies useful flexibility | No substantive disability framework | Accessible asynchronous options, captions, plain language, pace choice, sensory alternatives | | Class and labor | Recognizes resource constraints | Understates unpaid work and employment power | Compensate labor, protect work time, state employment-data boundary | | Language and geography | Discusses distributed communities | Risks English/center dominance | Local-language pathways, regional autonomy, asynchronous participation | | Sexuality and gender identity | Not addressed as a governance issue | No safety or belonging model | Conduct expectations, confidential reporting, trained response | | Data rights | Not a 2002 focus | Stories and participation can expose people | Consent, minimization, retention limits, aggregate reporting | ### Transferability rules 1. Begin with a local practice problem, not an organization chart. 2. Fund participation time before demanding contribution. 3. Give people a low-visibility or asynchronous path to legitimate involvement. 4. Document who sets norms and who can change them. 5. Keep public knowledge sharing separate from confidential peer support when needed. 6. Do not score people by participation volume. 7. Make coordinators accountable to the community and an independent harm route. 8. Revisit the domain when the work, technology, or membership changes. ### Accessibility test before launch - Can someone join without real-time speaking, travel, camera use, or high-bandwidth video? - Are agendas, materials, and outcomes available in accessible formats before and after sessions? - Can a newcomer understand jargon and find a human point of contact? - Is private participation genuinely private from managers and platform administrators? - Does the community’s rhythm work across caregiving schedules, time zones, and religious observance? ## PROMPT 10 — Notes pipeline and network proposals This session remains one file by request. These are proposed atomic notes, not newly created files. ### Fleeting notes - A community of practice is a social learning arrangement, not a content container. - Domain, community, and practice give a quick diagnostic for whether “community” is doing real work. - Peripheral participation can be legitimate participation, not a failure to engage. - Private spaces protect learning that public performance can suppress. - A useful value story traces activity, knowledge resource, application, and outcome—but still needs a counterfactual check. - Tight communities can become mechanisms for avoiding learning. - Sponsorship without decision-rights clarity can become control. - The cost of participating is part of community design. ### Literature notes | Candidate | Claim | Links | | --- | --- | --- | | Domain, community, practice | All three are needed for a CoP; each alone is insufficient | [[3. Resources/MOCs/DevRel MOC]] | | Seven cultivation tensions | Design for evolution rather than a fixed launch plan | [[3. Resources/Literature Notes/Community Architecture - What Makes Communities Thrive vs Extract - Literature Note]] | | Legitimate periphery | Different levels of participation can support learning without demanding performance | [[3. Resources/Permanent Notes/A Project Is the Community Not the Code]] | | Community downside | Trust and identity can harden into exclusion and stagnation | [[3. Resources/MOCs/Commons & Community Governance MOC]] | | Systematic anecdotal evidence | Stories need documented contribution chains and negative cases | [[4. Archives/Book reviews/Mastering Community Management]] | ### Permanent-note candidates 1. **A repository is a knowledge resource, not a community of practice.** Confidence: high. Scope: knowledge-management and DevRel design. 2. **Participation can be legitimate without being frequent, public, or synchronous.** Confidence: high. Scope: community access and facilitation. 3. **Community health requires a governance and repair path, not only trust.** Confidence: high. Scope: hosted and workplace communities. 4. **A community metric is meaningful only when it connects to a defined practice and decision.** Confidence: medium-high. Scope: measurement design. 5. **Organizational support is helpful only when it preserves community agency.** Confidence: medium. Scope: sponsorship arrangements. ### MOC routing - [[3. Resources/MOCs/DevRel MOC]]: shared developer practice, community strategy, feedback, documentation, and learning loops. - [[3. Resources/MOCs/Commons & Community Governance MOC]]: boundary design, institutional capture, participation rights, and redress. - [[3. Resources/MOCs/Book Review Synthesis MOC]]: organizational learning and community-management comparison cluster. ## PROMPT 11 — Teaching and facilitation pack ### Four-session sequence | Session | Objective | Activity | Check | | --- | --- | --- | --- | | 1. Is this a CoP? | Distinguish CoP, audience, team, and repository | Map a real group using domain–community–practice | Name the missing element | | 2. Design without capture | Apply the seven principles and decision-rights test | Redesign a mandated “community program” | Identify one autonomy safeguard | | 3. Test value claims | Build a contribution chain without false certainty | Trace activity → resource → application → outcome | Add a counterfactual and null signal | | 4. Govern for belonging | Recognize downside, access, and power risks | Conduct an inclusion and appeal-path audit | Publish a repair or closure condition | ### Facilitator cautions - Do not ask participants to disclose workplace conflicts in a setting their managers can observe. - Do not treat silence as lack of expertise. - Offer asynchronous, written, captioned, and low-bandwidth participation routes. - Avoid case exercises that turn people’s lived marginalization into a classroom scenario without consent. - Make it normal to say that a group should not become a CoP; sometimes a support queue, project, union channel, or document is the better structure. ## PROMPT 12 — Actions, experiments, and drift watch ### Practical actions | Horizon | Action | Evidence of progress | Stop condition | | --- | --- | --- | --- | | This week | Inventory three existing groups with the domain–community–practice test | Clear classification and missing-element notes | If no shared practice exists, do not relabel it a CoP | | This month | Convene a small practitioner listening session around one recurring DevRel problem | Members define a domain and preferred rhythm | If sponsor agenda overrides participants, pause | | This quarter | Pilot a contribution-chain record for one practice improvement | Resource and application are visible; uncertainty stated | If records become individual surveillance, remove fields | | This quarter | Publish participation and appeal norms | Members can explain decision rights and redress | If no independent escalation exists, do not claim safety | | Six months | Review renewal, closure, or handoff | Members assess value and burden | Close or redesign if the domain lost urgency | ### Reversible experiments 1. Run two 45-minute peer practice clinics with an anonymous pre-question option. 2. Test a public summary plus private office-hour model rather than requiring disclosure in one channel. 3. Invite core, active, and peripheral participants to define what legitimate participation looks like. 4. Record one contribution story and one null story using the same template. 5. Pilot a rotating coordinator role with clear time compensation and a confidential feedback channel. ### Drift watch | Drift | Signal | Response | | --- | --- | --- | | Community becomes marketing audience | Content calendar dominates practitioner problems | Restore domain-setting authority to practitioners | | Core group capture | Same people decide, speak, and receive recognition | Rotate roles; add appeal and external perspective | | Metric theater | Counts rise but practice cannot name a change | Replace vanity counts with a contribution chain | | Archive substitution | Documentation grows while peer exchange falls | Pair resources with inquiry, use, and revision sessions | | Accessibility erosion | Video-first pace, inaccessible files, time-zone exclusion | Offer equivalent asynchronous and accessible pathways | ## PROMPT 13 — Visual specifications ### Core model ```mermaid flowchart TB D["Domain\nWhat consequential practice do we share?"] C["Community\nHow do we relate, learn, and challenge?"] P["Practice\nWhat repertoire do we build and use?"] D <--> C C <--> P P <--> D ``` ### Contribution-chain visual ```mermaid flowchart LR A["Community activity"] --> B["Knowledge resource"] --> C["Applied practice"] --> D["Observed outcome"] E["Alternative explanations and null cases"] -.-> D F["Documentation and consent"] -.-> A F -.-> B F -.-> C ``` ### Governance overlay ```mermaid flowchart TD S["Sponsor resources"] --> C["Community"] C --> V["Shared value"] R["Participation rights"] --> C A["Accessible participation"] --> C H["Harm and appeal path"] --> C C --> Q["Renew, redesign, or close"] ``` ### Suggested Excalidraw card, not created - Green center: “Shared practice, not audience.” - Blue ring: domain, community, practice. - Orange ring: seven cultivation principles. - Red risk band: capture, exclusion, stagnation, surveillance, and unpaid labor. - Purple connections: [[3. Resources/MOCs/DevRel MOC]], [[3. Resources/MOCs/Commons & Community Governance MOC]], [[4. Archives/Book reviews/Mastering Community Management]], and [[4. Archives/Book reviews/The Community Manager’s Playbook]]. ## Session completion check | Check | Result | | --- | --- | | Complete local source coverage recorded | PASS | | Reader emphasis represented accurately | PASS: none recoverable | | Prompts 0–13 present once and in order | PASS | | Author claims separated from review inference | PASS | | Causal and evidence limits stated | PASS | | Accessibility, power, and inclusion audit included | PASS | | Existing vault notes and MOCs linked | PASS: outbound links only under one-file constraint | | No separate atom, MOC, or visual files created | PASS | | Current external checks cited and bounded | PASS | | Final status synchronized | PASS | ### Final verdict This remains a strong field guide for distinguishing a learning community from a communication channel or repository. Its enduring value is diagnostic: domain, community, practice; adaptive cultivation; and a candid account of community failure. Its blind spot is institutional power. Use the model with explicit participation rights, accessibility, data boundaries, paid time where work is involved, and independent repair paths. In this vault, it is the bridge between community-management practice and a knowledge system that forms people through shared work rather than merely collecting their information.