Skip to content

Collective Learning System

Capture local learning and propagate it across the system so adaptation does not remain isolated.

The Diagnostic Story

Symptom: The same avoidable failure reappears in different parts of the system, or one team has solved a hard problem that every other team is still struggling with. Lessons-learned reports are written and filed; nobody reads them. New teams start from scratch despite years of accumulated experience. Learning rituals close with action items that do not update anything at the system level.

Pivot: Capture local lessons, validate whether they transfer across context differences, codify or contextualize them for reuse, actively diffuse them to relevant actors, and monitor whether adoption actually updates behavior — not just whether the report was filed.

Resolution: Avoidable failures recur less because useful adaptations travel across units before the next incident. Institutional memory strengthens across turnover. Cross-unit coherence improves without flattening the local context that makes knowledge usable.

Reach for this when you hear…

[incident response] “We wrote the post-mortem, put it in Confluence, and six months later the same outage happened in a different region.”

[clinical quality] “The ICU figured out a better protocol two years ago but it never made it into the training for the other floors.”

[field operations] “Every new crew rediscovers the same workaround by trial and error because there is no path from the field back into the standard operating procedure.”

Mechanisms / Implementations

  • After-Action Reviews: Captures lessons from completed work, incidents, exercises, or operations.
  • Cross-Team Retrospectives: Surfaces patterns and lessons across multiple teams or units.
  • Lessons-Learned Databases: Stores lessons, cases, actions, owners, tags, and boundary conditions.
  • Communities of Practice: Enables practitioners to exchange, validate, adapt, and diffuse situated knowledge.
  • Internal Case Libraries: Preserves context-rich examples for future reasoning and adaptation.
  • Best-Practice Diffusion Protocols: Spreads validated practices with boundary conditions and adoption support.
  • Learning Review Cadences: Maintains the learning system through recurring review and revision.
  • After-Action Review
  • Best-Practice Diffusion Protocol
  • Community of Practice

Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.

Built directly on (3)

Also references 11 related abstractions

Variants

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

Incident Learning System · risk or failure variant · recognized

A collective learning system centered on failures, near misses, safety events, outages, breaches, or shocks.

Project Learning System · temporal variant · recognized

A collective learning system organized around project starts, milestones, completions, and post-project transfer.

Practice Diffusion Network · mechanism family variant · recognized

A variant that identifies locally successful practices and spreads them through peer networks, exemplars, and adoption supports.

Organizational Memory Curation · implementation variant · candidate

A memory-heavy variant focused on preserving, indexing, pruning, and retrieving accumulated lessons across time.