KM Lifecycle
Definition
The operational loop a Knowledge Management System runs continuously. Several variants exist; the most common synthesis is six phases:
Create → Capture → Organize → Share → Apply → Refine → (back to Create)
Where the SECI Model is the theoretical engine of knowledge conversion, the KM Lifecycle is the operational day-to-day flow.
The six phases
| Phase | What happens | NOTQIN example |
|---|---|---|
| Create | New insight emerges | Discovery call surfaces an unmet customer pain |
| Capture | Insight gets recorded | Imrane writes Discovery Calls/<co>-<date>.md |
| Organize | Tagged, linked, classified | audience: frontmatter + wikilinks to CBAM, Sonasid |
| Share | Right person sees it | Portal + audience routing + Friday demo |
| Apply | Used in a decision or action | Cited in next cold email, pricing call, sector pack update |
| Refine | Updated as the world changes | Weekly review, wave-end retro, quarterly audit |
Where most orgs break
| Phase | Failure mode | Symptom |
|---|---|---|
| Create | No deliberate Externalization | Knowledge exists but never surfaces |
| Capture | Friction too high | ”I’ll write it up later” — never happens |
| Organize | No taxonomy | Search returns 200 results, none relevant |
| Share | Siloed | Right doc exists, wrong person reads it |
| Apply | Knowledge dies in docs nobody re-reads | Most common failure |
| Refine | No refresh ritual | Docs go stale, lose trust, get ignored |
Why it matters for NOTQIN
The vault’s weekly/Mon-Wed-Fri/wave-end rituals are explicitly Phase 6 (Refine). The Path-to-Pilot cadence and the Onboarding Pack are designed to force completion of all six phases — not just Capture and Organize, which most vault-based PKMs do well.
Common mistakes
- Equating KMS with Capture + Organize (the “build a wiki” trap)
- Skipping Apply by assuming “if it’s documented, people will use it”
- Treating Refine as optional — stale knowledge is worse than absent knowledge because it actively misleads
- Running phases in isolation (different team owns each) → handoff loss
See also
- SECI Model — the theoretical complement
- After-Action Reviews — a Capture→Refine mini-loop
- Personal Knowledge Management — the same loop scaled to one person
- Knowledge Management Systems — Foundations