CW-301g · Module 1

Team Knowledge Base Design

4 min read

A team knowledge base is the shared memory that ensures every team member's Claude sessions reference the same facts, use the same terminology, and produce consistent output. Without it, each person builds their own context from scratch, introduces their own terminology, and produces deliverables that are internally consistent but organizationally inconsistent.

The knowledge base has four sections. Glossary: every domain term with its canonical definition. "ARR means Annual Recurring Revenue, defined as the annualized value of active subscriptions excluding one-time fees." Facts: verifiable data points that Claude should treat as ground truth. "Our fiscal year ends March 31. Our primary competitor is Apex Corp. Our current headcount is 847." Templates: standard output formats for recurring deliverables. "Competitive briefs use this structure. Quarterly reviews use this structure." Decisions: key decisions with rationale, using the ADR format. Each team member loads the relevant knowledge base sections alongside their task context.

Do This

  • Maintain a canonical glossary that all team members load into Claude sessions — terminology consistency is foundational
  • Version the knowledge base and review quarterly — stale facts produce stale output
  • Assign ownership — someone must be responsible for accuracy, or no one is

Avoid This

  • Let each team member define terms differently in their own prompts — "churn" means three different things to three different people
  • Build a knowledge base once and never update it — it decays faster than you think
  • Make the knowledge base optional — if it is not required, it will not be used