Document 94

SEBoK *Knowledge Management*, Distilled

framework

SEBoK Knowledge Management, Distilled

Next-40 distillation #52 (Batch 2/5 in the third-batch sweep). Knowledge Management (KM) has no dedicated SEBoK article; the topic is treated under Information Management (IM, lead John Metcalf, Philip Hallenbeck, Sandrine Gonthier; Part 3 Technical Management Processes) and through reference works (DAMA-DMBOK, PMBOK). KM is distinguished from IM as operating "at organizational level to enable knowledge reuse," depending on IM when managing explicit knowledge captured in information assets. KM is the third third-batch stress-test of longitudinal-pulverization at the institutional rung (sister to lessons-learned SE-092), with a sharper distinction between explicit knowledge (IM-substrate) and tacit knowledge (community-of-practice substrate the IM-discipline cannot capture). The IM-vs-KM distinction is structurally Doc 372 hypostatic-boundary at the substrate rung: IM handles substrate-as-record, KM handles substrate-as-practice, and the boundary between them is not crossable by either discipline alone. Five forms bind partially.

I. Source

II. Source Read

The SEBoK does not publish a standalone Knowledge Management article. KM is treated under Information Management (lead John Metcalf, Philip Hallenbeck, Sandrine Gonthier; Part 3 Technical Management Processes). IM is "a technical management process that plans, executes, and controls the provision of information to designated stakeholders," ensuring data is complete, verifiable, and accessible. ISO/IEC/IEEE 15288's IM purpose is to "generate, obtain, confirm, transform, retain, retrieve, disseminate, and dispose of information to designated stakeholders." Six IM sub-activities: prepare for IM (scope and plan); collect information (capture from valid sources); organize information (categorize and structure); analyze (transform for decision support); distribute (share with authorized stakeholders); protect and manage end-of-life (security and obsolescence). KM is differentiated from IM: "Knowledge Management differs from IM, operating at organizational level to enable knowledge reuse. However, KM depends on IM when managing explicit knowledge captured in information assets like technical documentation, design patterns, and reusable processes." Reference works: PMBOK 7th edition; DAMA-DMBOK Guide (the primary reference for the IM article). Position: Part 3 → Technical Management Processes (after CM, before Quality Management).

III. Structural Read

Form V — Hypostatic Boundary (Doc 372), at the explicit/tacit knowledge boundary, the load-bearing read. The IM-vs-KM distinction is exactly a hypostatic-boundary: IM handles substrate-as-record (explicit knowledge in documents, designs, processes); KM handles substrate-as-practice (tacit knowledge in communities of practice, mentorships, on-the-job-learning). The boundary between them is not crossable by either discipline alone — IM cannot capture what is not articulable, KM cannot operate without the IM-substrate to anchor against. SEBoK's "KM depends on IM when managing explicit knowledge" formulation acknowledges the dependency in one direction; the corpus articulates the boundary symmetrically: each discipline depends on the other at the boundary, and neither can absorb the other. This is the cleanest hypostatic-boundary case in the third batch.

Form VI — Pulverization at the institutional rung (Doc 445 Refinement D). KM is sister to lessons-learned (SE-092) as institutional longitudinal-pulverization. The KM substrate (organizational knowledge) is the cross-engagement substrate against which engagements pulverize their practice. SE-092 emphasized the explicit-knowledge case (lessons captured in records); SE-094 surfaces the tacit-knowledge case (knowledge held in practitioners and communities). Together they are the two halves of the institutional longitudinal-pulverization discipline, split at the hypostatic boundary.

Form X — Institutional Ground (Doc 571 §X.5), with KM as the canonical enterprise-component case. KM is structurally the enterprise-component of the institution: the accumulated working tradition that the organization-component (formal procedures and documents, IM territory) cannot capture. Section X.5's organization-vs-enterprise distinction maps cleanly: IM is organization-component, KM is enterprise-component. The SE-092 Pattern B vulnerability (formal procedures installed without practice) is structurally a Pattern B at the IM-component while the KM-component is structurally simulation-resistant (you cannot fake a community of practice the way you can fake a documentation database).

Form III — Substrate-and-Keeper Composition (Doc 510), with multi-engagement and tacit-substrate extensions. KM extends the dyad twice: across engagements (institution-as-keeper, sister to SE-092) and across the explicit/tacit boundary (community-as-keeper for tacit substrate). The second extension is sharper: communities-of-practice are composite keepers without a single named locus. This is a multi-keeper-without-named-reconciliation-rung case, distinct from Doc 604's named-reconciliation-rung formalization. Worth recording as a Doc 604 sub-case or sibling extension.

Form III — Anchor-Article Distribution inverse, third dispersed-instrument instance. KM is the third third-batch case where SEBoK has no dedicated article (after WBS SE-088 and lessons-learned SE-092). The dispersed-instrument pattern is now well-attested at three independent instances; cluster-formalization is ready.

IV. Tier-Tags

  • KM-vs-IM distinction (organizational vs technical, tacit vs explicit) — π / α as cited; μ / β under corpus as Doc 372 hypostatic-boundary canonical case.
  • KM operates at organizational level for reuse — π / α.
  • KM depends on IM for explicit-knowledge management — π / α as cited; μ / β under corpus as one direction of the symmetric dependency.
  • IM six sub-activities — π / α.
  • Communities of practice as KM-substrate — corpus reading; ν.
  • Non-existence of dedicated KM article — corpus observation; ν.

V. Residuals

SEBoK's treatment of KM is one-directional (KM depends on IM). The corpus articulates the symmetric dependency (IM substrate is meaningful only because KM-discipline interprets it). This is a small structural residual.

The community-of-practice locus is unnamed in SEBoK; the corpus reads it as a multi-keeper-without-named-reconciliation-rung case.

CMMI's organizational training and innovation-deployment process areas are KM territory but are not cross-linked from the IM article; the discipline-cross-link is missing.

VI. Provisional Refinements

Doc 372 hypostatic-boundary canonical case at the explicit/tacit knowledge rung. SE-094 supplies the cleanest hypostatic-boundary instance in the third batch: IM and KM cannot absorb each other and the boundary between them is not crossable by either alone. Worth treating as the canonical worked example when Doc 372 is consolidated.

Doc 604 sibling extension: multi-keeper-without-named-reconciliation-rung. The community-of-practice case is structurally distinct from Doc 604's three composition rules (subordination-by-domain, coordination-by-rung, negotiation-by-priority) because there is no single named reconciliation rung — the community is the reconciliation, distributed. Worth recording as a fourth rule or a sibling extension.

Dispersed-instrument cluster reaches third instance. Cluster-formalization candidate is now strongly supported (WBS SE-088, lessons-learned SE-092, KM SE-094). Three independent instances cross the substantive-cluster threshold.

Doc 445 Refinement D explicit/tacit split. Lessons-learned (SE-092) is the explicit half; KM (SE-094) is the tacit half. The institutional-rung longitudinal-pulverization discipline has two halves split at the hypostatic boundary. Worth recording as a Refinement D sub-structure.

VII. Cross-Links

Form documents. Doc 372 (Hypostatic Boundary, canonical worked example), Doc 445 (Pulverization, Refinement D explicit/tacit split), Doc 571 (Institutional Ground §X.5, canonical enterprise-component case), Doc 510 / Doc 604 (multi-keeper-without-named-reconciliation-rung sibling extension), SE-039 D7 (anchor-article inverse, third dispersed-instrument).

Part-level reformulation. SE-006 (Part 3 — SE & Management, Technical Management Processes).

Related distillations. SE-047 (CM — adjacent technical management process). SE-092 (Lessons Learned — explicit half of institutional longitudinal-pulverization). SE-093 (CMMI — institutional-substrate sister).

Adjacent SEBoK concepts (per source). Information Management, Configuration Management, Quality Management, DAMA-DMBOK, PMBOK 7th edition.

Methodology refinement candidates. Doc 372 canonical worked example; Doc 604 sibling extension (no-named-reconciliation-rung); dispersed-instrument cluster formalization; Doc 445 Refinement D explicit/tacit split.

Appendix: Originating Prompt

"Apply refinements; report back for next 40" / "Continue"

(SE-094 is one of the third-batch SEBoK distillations. Batch 2/5.)

Referenced Documents

More in framework