Knowledge Management Systems — Foundations
Why this is in the vault. The vault, the portal, the team alignment process — all of it is a KMS, intentionally designed. Understanding the field properly clarifies why we do what we do, what’s load-bearing vs decoration, and where the gaps are. Anchor doc for the
Knowledge Management/Concepts/folder.
1. What KMS is
A Knowledge Management System combines people · process · technology to deliberately create, capture, organize, share, and apply knowledge across an organization — so the organization gets faster, smarter, and less dependent on any single person.
Not a document repository. Not a search engine over files. Not a wiki. Those are tools that support KMS. The discipline itself is about turning individual know-how into organizational capability.
2. Five foundational concepts
Each has a dedicated note in ./Concepts/:
| # | Concept | Note |
|---|---|---|
| 1 | The hierarchy of data → wisdom | DIKW Pyramid |
| 2 | What knowledge is (Polanyi 1966) | Tacit vs Explicit Knowledge |
| 3 | How knowledge converts (Nonaka 1995) | SECI Model |
| 4 | The operational loop | KM Lifecycle |
| 5 | The personal–organizational split | Personal Knowledge Management |
Read those five before anything else if KM is new to you. ~20 minutes total.
3. Classification of KMS (Alavi & Leidner 2001)
The canonical academic taxonomy. See KMS Classification.
| Type | Purpose | NOTQIN today |
|---|---|---|
| Knowledge Repositories | Store explicit knowledge | ✅ The vault |
| Knowledge Directories / Expert Locators | Tell you who knows what | ⚠️ People Map (underused) |
| Knowledge Networks / CoPs | Connect people for socialization | 🟡 Team Discord (TBC at kick-off) — see Communities of Practice |
| Knowledge Application Systems | Embed knowledge into workflows | ⏳ Future Smartex Agent (NOTQIN Agent) |
4. Adjacent / overlapping disciplines
KMS borrows from and feeds into many fields. Map of which sibling discipline contributes what:
| Discipline | Contribution to KMS |
|---|---|
| Library / Information Science | Cataloging, taxonomy, controlled vocabularies, faceted classification |
| Information Architecture | Site structure, navigation, findability |
| Taxonomy & Ontology Engineering | Hierarchies + relationships (RDF, OWL, schema.org) |
| Knowledge Graphs | Entities + relationships + reasoning — the 3D version of UNS |
| Semantic Web | Machine-readable knowledge (RDF, SPARQL, linked data) |
| Enterprise Content Management (ECM) | Document lifecycle, retention, compliance |
| Learning Management Systems (LMS) | Structured training delivery |
| Business Intelligence (BI) | Information → insight via dashboards |
| Decision Support Systems (DSS) | Knowledge → decision in context |
| Organizational Learning | Learning Organization — why teams that learn outcompete |
| After-Action Reviews | US Army origin — structured learning from any event |
| Information Retrieval (IR) | Search algorithms, ranking, relevance |
| Augmented Intelligence | LLMs as retrieval prosthesis — see Augmented Intelligence and RAG |
| Innovation Management | KM as input to creating new value |
5. The modern technology stack
What goes into a serious 2026 KMS:
| Layer | Purpose | Examples |
|---|---|---|
| Capture | Get knowledge in | Notes apps, voice→text, meeting transcribers, screenshots |
| Storage | Persist it | Markdown + git, document DBs, vector DBs |
| Linking / structuring | Create relationships | Wikilinks, Knowledge Graphs, ontologies |
| Retrieval | Find it later | Full-text + semantic search, RAG |
| Synthesis | Combine pieces | Maps of content, AI summarization |
| Distribution | Right person sees it | Portals (Quartz), email digests, audience routing |
| Access control | Wrong person doesn’t | RBAC, Cloudflare Access, audience tags |
| Versioning | Track changes | Git, dated entries |
| Workflow integration | Knowledge in the tools of work | IDE plugins, Slack integrations, MES embeds |
6. The AI-era shift (2023–2026)
Three changes that broke / re-shaped classical KM:
- RAG — LLMs as a query layer over your knowledge base. Reading the vault through Claude Code IS RAG-by-conversation.
- Tools-of-thought — Obsidian, Roam, Logseq, Notion AI, Mem. PKM became dramatically more powerful. Org KM is still catching up.
- Agent memory — MCP + persistent memory blur the line between KMS and the tool that uses it. The
MEMORY.mdfile is an example.
Strategic implication for NOTQIN: tacit-to-explicit conversion got cheaper (transcription + LLM summarization), and synthesis (Combination, see SECI Model) is now near-free. The high-value investment is capturing tacit knowledge from operators and customers because everything else is now commodity.
7. How NOTQIN’s vault maps to KMS theory
| Vault construct | KM concept |
|---|---|
| Markdown files + git | Knowledge Repository |
audience: frontmatter + Quartz portal | Distribution layer with RBAC |
| Wikilinks + backlinks | Knowledge graph (implicit) |
MEMORY.md (Claude auto-memory) | AI agent memory / RAG context |
| NOTQIN Industrial Intelligence Operating Thesis 2026 | Externalization of the founder’s mental model |
Industrial Intelligence/Concepts/* (OEE, MTBF…) | Atomic explicit-knowledge units (Zettelkasten-style) |
Discovery Calls/<co>-<date>.md (when populated) | Externalization of customer interactions |
| Wave-end retros + Friday demos | After-Action Reviews / lessons-learned ritual |
| Weekly review template | Refine phase of the KM Lifecycle |
Sector Pack Audits/ | Knowledge embedded into code artifacts |
| Smartex Agent (future) | Knowledge Application System |
| The team itself (Mon/Wed/Fri rituals) | Communities of Practice |
| People Map | Knowledge Directory (expert locator) |
| Onboarding Pack | Internalization scaffold (see SECI Model) |
| Decision Log | Organizational memory anchor |
The honest read: the vault runs ~80% of a serious org KMS. The gaps are tacit capture from customers/operators (Discovery Calls folder still empty), Expert Locator under-investment, and Knowledge Application (Smartex Agent not yet decision-embedding).
8. Reading list, ranked by NOTQIN leverage
| # | Work | Author | Why for you |
|---|---|---|---|
| 1 | The Knowledge-Creating Company | Nonaka & Takeuchi (1995) | The SECI Model source. Foundational. |
| 2 | Working Knowledge | Davenport & Prusak (1998) | The practitioner’s bible. Tacit knowledge in orgs. |
| 3 | Building a Second Brain | Tiago Forte (2022) | Personal Knowledge Management bible. CODE method. |
| 4 | How to Take Smart Notes | Sönke Ahrens (2017) | Zettelkasten Method for atomic-note KM. Maps to your concept notes. |
| 5 | The Fifth Discipline | Peter Senge (1990) | Learning Organization foundations. |
| 6 | Cultivating Communities of Practice | Wenger / McDermott / Snyder (2002) | Communities of Practice canonical reference. |
| 7 | Information Architecture for the World Wide Web (4th ed.) | Rosenfeld & Morville | The IA bible. Your folder structure IS Information Architecture. |
| 8 | Knowledge Management Systems: A Perspective on the Field (MIS Quarterly 2001) | Alavi & Leidner | Academic anchor. Free PDF. PFE-defensible citation. See KMS Classification. |
| 9 | Personal Knowledge | Michael Polanyi (1958) | Origin of Tacit vs Explicit Knowledge. |
For the PFE viva: anchor #1, #2, #8 by name — these are the citations Moroccan examiners recognize.
9. Anti-patterns to avoid
| Anti-pattern | Why it kills KM |
|---|---|
| Hoarding without applying | Knowledge that is never re-used is decoration, not capability |
| Bureaucracy without trust | If people fear capture, tacit knowledge stays hidden |
| Combination-only loop | Endless synthesis from existing docs without new external/internalization → the system inbreeds |
| One-way pipeline (capture → forget) | Without the Apply phase the KM Lifecycle is broken |
| Tool-first thinking | ”Let’s adopt Notion” is not a KM strategy. The discipline comes first. |
| No access control discipline | Either too open (sensitive leaks) or too closed (capability hoarded) |
| Confusing documents with knowledge | A 200-page Word doc nobody reads is not “captured knowledge” |
| No expert locator | If “ask the person who knows” requires asking who that person is, KM has failed at Directory |
See also
- NOTQIN Industrial Intelligence Operating Thesis 2026 — the applied KMS for industrial intelligence
- Knowledge Base Map — vault navigation
- NOTQIN KM System — Master Index — venture-specific KM inventory
- Reading List — NOTQIN Founder Curriculum 2026 — founder learning roadmap
- All 12 concept stubs in
./Concepts/