Organizational memory¶
The accumulated, retrievable knowledge of an organization preserved in people, routines, records, artifacts, and information systems.
Core Idea¶
Organizational memory is the store of encoded and embodied experience that can be retrieved to inform later organizational interpretation and action. Events are acquired, interpreted, embedded in people and structures, retained unevenly, and retrieved through search, routines, storytelling, training, or cues. The abstraction is therefore identified by a declared carrier, a transformation or constraint over that carrier, and an invariant that tells an analyst whether the named structure is genuinely present.
The load-bearing residual is not the broad topic of knowledge management. It is An archive is only one repository, and nominal retention without access or use is weak memory; inherited routines can preserve both knowledge and error..
Scope of Application¶
Organizational memory belongs to knowledge management and is useful where the analyst can specify an organization, members, archives and databases, routines and culture, acquired experience, retention and forgetting, retrieval practices, turnover, and present decisions, then evaluate knowledge persists beyond its originating event or actor and remains accessible enough to influence later organizational behavior. The scope is broad within that domain but bounded by the need for knowledge persists beyond its originating event or actor and remains accessible enough to influence later organizational behavior. The entry records a descriptive analytical identity; practical use requires the governing domain's evidence, standards, and safety obligations.
Clarity¶
The abstraction clarifies a crowded vocabulary by making knowledge persists beyond its originating event or actor and remains accessible enough to influence later organizational behavior the center of the account. A claim should name the carrier, the governing operation or relation, the applicable assumptions, and the recognition test. A bare label is insufficient because the name Organizational memory can be used for a formal identity, an implementation, or a neighboring result unless carrier and convention are stated.
Manages Complexity¶
Without the abstraction, an analyst must reason directly over many local details: the carrier roles, admissibility assumptions, competing conventions, derived invariants, boundary cases, and proof or validation obligations specific to Organizational memory. Organizational memory compresses them into the roles in the structural signature. That compression permits comparison across instances without erasing the variables that determine validity. It also exposes which details may be varied safely and which are constitutive.
Abstract Reasoning¶
- Identify the carrier. State what the elements, states, objects, or observations are: an organization, members, archives and databases, routines and culture, acquired experience, retention and forgetting, retrieval practices, turnover, and present decisions. Reject examples whose alleged carrier belongs to a different problem. 2. Lock the constitutive rule. Express knowledge persists beyond its originating event or actor and remains accessible enough to influence later organizational behavior independently of one notation or implementation.
Knowledge Transfer¶
Knowledge transfers strongly among subfields of knowledge management because they reuse an organization, members, archives and databases, routines and culture, acquired experience, retention and forgetting, retrieval practices, turnover, and present decisions, Events are acquired, interpreted, embedded in people and structures, retained unevenly, and retrieved through search, routines, storytelling, training, or cues., and type the carrier, state every parameter and convention in the definition, test that knowledge persists beyond its originating event or actor and remains accessible enough to influence later organizational behavior, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases.
Relationships to Other Abstractions¶
Current abstraction Organizational memory Domain-specific
Parents (1) — more general patterns this builds on
-
Organizational memory is a kind of Collective Memory Prime
The proposed strict upward parent is
prime:collective_memory.
Hierarchy path (1) — routes to 1 parentless root
- Organizational memory → Collective Memory → Representation → Abstraction
Neighborhood in Abstraction Space¶
Organizational memory sits in a crowded region of the domain-specific corpus (30th percentile for distinctiveness): several abstractions share nearly its structure, so a description that fits it tends to fit its neighbors too.
Family — Enterprise Strategy & Capability Management (27 abstractions)
Nearest neighbors
- Organizational capital — 0.94
- Organizational identity — 0.91
- I-Space (conceptual framework) — 0.90
- Management process — 0.90
- Ignorance management — 0.90
Computed from structural-signature embeddings · 2026-09-08