Skip to content

Knowledge Management

Communities generate enormous amounts of knowledge through discussion, shared resources, and collective experience. Most of it evaporates. Knowledge management is the practice of capturing, organizing, and making that knowledge accessible.

Without knowledge management:

  • New members can’t catch up
  • Solved problems get re-solved
  • Institutional memory lives in one person’s head
  • The community can’t learn from its own history
LayerPurposeTool Examples
ChatReal-time discussionSignal, Matrix, Discord
ForumThreaded, searchable discussionDiscourse, Reddit
WikiCurated, structured knowledgeStarlight, Outline, BookStack
ArchiveHistorical recordGit history, meeting notes

Information should flow up this stack: insights from chat become forum posts, forum posts become wiki articles, wiki articles reference archived sources.

You don’t need a complex setup. Start with:

  1. Pick a platform — Even a shared Google Doc works initially
  2. Seed with 5-10 articles — Meeting format, community norms, FAQ, key resources
  3. Make contributing easy — Lower the bar for edits (suggestions, not perfection)
  4. Assign a gardener — Someone who tidies, organizes, and reminds others to contribute
  • Meeting notes — Key decisions, action items, insights
  • Resources — Books, tools, links the community finds valuable
  • Processes — How to join, how meetings work, how to contribute
  • Lessons learned — What worked, what didn’t, and why
  • Member expertise — Who knows what (with permission)

The biggest challenge is getting members to contribute. Tactics:

  • Lower the bar — A rough note is better than no note
  • Rotate note-taking — Everyone takes turns
  • Celebrate contributions — Public acknowledgment for wiki edits
  • Make it part of the flow — “Who wants to write this up for the wiki?”

Adapted from the IrregularChat community, which maintains a 385-page community wiki with contributions from dozens of members.