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.”
When This Archetype Applies¶
No catalog groundingNone of the structural conditions is currently represented by an accepted prime or domain-specific abstraction.
Diagnostic problem
Knowledge gained in one part of the system fails to spread or change behavior elsewhere.
What this problem means
The structural problem is a broken learning pathway. Experience is generated locally, but the system has weak mechanisms for recognizing the lesson, preserving it, deciding where it applies, translating it for other contexts, and checking whether it changes future behavior.
A common false solution is to add a repository or a retrospective. Those can help, but they are only mechanisms. The deeper problem is that the system lacks a maintained route from experience to behavior update.
Show the applicability expression
Applicability expression4 distinct conditions
groundedpartly groundedopen
4 conditions, all required.
4Required in every casenumbered 1–4
These hold no matter which pattern applies.
Recurring local problems · open
Problems solved by one local team later recur in another part of the system.
The source archetype describes the situation as follows: Local teams solve problems that later reappear elsewhere. The normalized requirement above isolates the load-bearing portion used in this condition set.
Insights lack reuse path · open
Incidents, projects, pilots, or experiments generate insight without a reliable route to reuse.
The source archetype describes the situation as follows: Incidents, projects, pilots, or experiments generate insights with no reliable path to reuse. The normalized requirement above isolates the load-bearing portion used in this condition set.
Inert knowledge repositories · open
Knowledge repositories exist but are not trusted, searched, curated, or used in later decisions.
The source archetype describes the situation as follows: Repositories exist but are not trusted, searched, curated, or used in future decisions. The normalized requirement above isolates the load-bearing portion used in this condition set.
Practical knowledge erosion · open
Turnover, fragmentation, or time erases practical knowledge from the system.
The source archetype describes the situation as follows: Turnover, fragmentation, or time erases practical knowledge. The normalized requirement above isolates the load-bearing portion used in this condition set.
Other requirements and context (1)
Why these sit outside the expression
Supporting context — it may accompany or help interpret the situation, but it is not a load-bearing condition in a sufficient diagnostic set.
Supporting contextSubunits differ enough that direct copying is risky.
It is especially useful when the organization has enough recurring similarity for lessons to transfer, but enough local variation that direct copying would be unsafe. In this archetype, the relevant contextual consideration is: Subunits differ enough that direct copying is risky. It helps interpret the situation or strengthens the practical case for examining the archetype.
Coverage
0 of 4 conditions grounded · 4 open.
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: Turns a just-finished episode into validated lessons by reconstructing what was intended versus what actually happened and deciding which improvised moves earned a place in the repertoire.
- Best-Practice Diffusion Protocol: Spreads an already-validated practice to eligible units with explicit eligibility criteria, a defined delivery route, and a check on whether adoption actually took.
- Community of Practice: Holds a recurring, membership-based space where practitioners deepen and steward an emergent practice, keeping its tacit judgment alive as it matures.
- Cross-Team Retrospective: Gathers several teams after a shared event to surface the system-level lesson that lives in the seams between them — the pattern no single group could see alone.
- Internal Case Library: Preserves lessons as whole, context-rich narrative cases — not fielded records — so future readers can reason by analogy and judge for themselves what transfers.
- Learning Review Cadence: A recurring review that keeps the learning system alive — periodically checking whether past lessons changed practice, pruning stale ones, and revising the guidance that no longer holds.
- Lessons-Learned Database: A structured, searchable store where lessons are filed as tagged fielded records — cause, action, owner, boundary conditions — so any future worker can query them at the moment of need.
- Organizational Memory System: The owned, standing capability that keeps an organization's knowledge retrievable across turnover — combining a curated memory store with a steward who maintains it and the routines that connect it to work.
Related Abstractions¶
Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.
Built directly on (3)
- Collective Systemic Learning: Shared adaptation.
- Diffusion: Spread over time.
- Emergent Formalization (Language): Informal to formal evolution.
Also references 11 related abstractions
- Absorptive Capacity: Ability to integrate knowledge.
- Collective Memory: Shared narratives.
- Design for Implementation: Real-world feasibility.
- Feedback: Outputs influence inputs.
- Implicit Knowledge: Unconscious understanding.
- Observational Learning (Social Learning): Learn by observing.
- Organizational Culture: Shared norms and values.
- Pattern Recognition: Identify regularities.
- Psychological Safety: Safe environment for risk-taking.
- Social Capital: Value of relationships.
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.
Editorial Notes¶
Problem Classification¶
Classification: Learning, Knowledge & Capability Gaps → Organizational Absorption, Diffusion & Learning Curve
Problem kernel: local lessons fail to become system-wide capability
Rationale: Knowledge gained in one unit remains isolated rather than being translated, spread, accumulated, and incorporated into behavior elsewhere.
Independent corroboration: The earliest necessary condition in the frozen evidence is: Knowledge gained in one part of the system fails to spread or change behavior elsewhere. That is a organizational absorption diffusion and learning curve problem because Useful knowledge or experience cannot be recognized, translated, spread, accumulated, or converted into organization-wide behavior and capability.
Review outcome: Independent reviewer agreement; high confidence.