Organizational Memory Loss
Why Learning Doesn’t Stick
Issue 258, April 2, 2026
A senior leader at a client I work with told me something recently that has stayed with me. Her organization had just completed a major strategic initiative, the third of its kind in four years, and by most measures it had gone reasonably well. On time. On budget. Acceptable progress to date. But when she pulled up the reports from the previous two initiatives, she found something that was both fascinating and deeply troubling.
The same breakdowns had occurred in all three initiatives. Misaligned stakeholder expectations resulting in periods of crisis communication. Lack of ownership in assigned departments leading to “critical alignment meetings” and pre-launch changes that complicated timelines and forced teams into reactive mode. The result: high near-launch stress, a bumpier launch than planned, and tension across teams that took time to dissipate.
The prior two efforts had identified these issues. Twice, process changes had been documented to address them.
Each time, the next team started from scratch as if the prior experiences and process changes did not exist.
“We have this extraordinary ability,” she told me, “to learn things and then completely forget we learned them.”
What she described wasn’t an isolated failure. It was a pattern.
Her observation captures something I encounter across industries, sectors, and organizational sizes with startling consistency. Organizations invest real effort in learning. Reviews are conducted. Lessons are documented. Postmortems are written and circulated.
There is no shortage of intention. And yet, the same issues continue to surface. Strategies launch without clear ownership. Transformations stall at the same points. Decisions are revisited without resolution.
This is not a failure of intelligence or intent. It is a failure to activate organizational memory.
The Storage Fallacy
Organizational memory is almost universally treated as a storage problem. The assumption is simple: if we document what we learned, we will retain it and use it. So organizations invest in repositories, knowledge bases, and shared drives filled with retrospective summaries and best practice guides.
The infrastructure is often impressive. The outcome is almost always disappointing.
The reason is that storage is not the same as memory.
Hermann Ebbinghaus, whose research on memory and retention remains foundational more than a century after it was conducted, demonstrated what he called the forgetting curve: information decays rapidly when it is not reinforced, applied, and kept in the active awareness of the workforce. His experiments showed that memory declines sharply in the first hours after exposure, with the majority of newly learned material lost within a day or two if it is not revisited.
The critical finding was not that forgetting is inevitable. It was that active retrieval, repeated application, and spaced reinforcement dramatically slow the decay. Memory is not a static recording. It is something that must be continually reactivated to remain functional.
Organizations behave the same way. Lessons are captured and shared, then they fade because nobody reactivates them. Nobody pulls them into planning conversations. Nobody asks, before launching a new effort, what was learned last time and how it applies now.
The information exists. The organization doesn’t use it. If memory decays without reinforcement at the individual level, the question becomes: what reinforces it at the organizational level?
In most cases, the answer is nothing.
Why Work Is Structured to Forget
The structure of work actively reinforces the knowledge decay. There is only so much focus, there is only so much one can keep in their mind, and with the constant barrage of new information, there is a continuous battle to sift through what is needed.
Further adding to the challenge: employees change roles, move to different teams or departments, or leave the organization entirely. What was learned in one context, because more often than not, context is everything, rarely transfers to the next. Rarely is there a mechanism ensuring that it does.
A 2025 study in the Journal of Public Administration Research and Theory examined organizational memory in federal IT projects across 94 U.S. agencies. It found that employee turnover significantly disrupted outcomes when knowledge resided primarily in individuals. When knowledge was embedded in processes, communication structures, and repeatable workflows, organizations experienced continuity.
The distinction is critical. When memory is individual, it walks out the door. When it is systemic, it remains.
Most organizations rely on individuals. The person who was in the room becomes the memory. When they leave or shift roles, the organization resets. The next team begins with confidence driven by not knowing what has already been tried.
I have written about related dynamics in several recent issues of this newsletter. In Issue 257, Policy as Proxy Leadership, I explored how organizations substitute rigid procedures for human judgment. The relationship to organizational memory is direct: policy proliferation is often a symptom of memory failure. When organizations cannot reliably transfer what was learned from past experience, they compensate by writing rules, adding checkpoints, and building approval layers.
The Trap of Single-Loop Thinking
Chris Argyris and Donald Schön’s work on organizational learning provides a useful framework for understanding why memory fails even when organizations invest in it. I outline Argyris and Schön’s related findings in Episode 019 of The Human Factor Podcast where I discussed structural silence.
They distinguished between two types of learning. Single-loop learning focuses on correcting errors within existing frameworks. The organization identifies what went wrong and adjusts its approach, but the underlying assumptions, structures, and mental models remain unchanged. Double-loop learning goes further. It examines and adjusts the underlying conditions that produced the error in the first place.
Most organizations operate almost entirely in the first loop. They fix the issue in the moment. They document what happened. They implement a corrective action. And they then move on. But the underlying conditions remain unchanged. The same organizational structures that produced the failure are left intact. The same incentives, communication patterns, and decision-making processes continue to operate. And so the problem reappears, not as a random anomaly, but as a pattern embedded in the operational system. Most do not see the patterns, unfortunately.
Argyris also identified a deeper challenge. He found that organizations often maintain what he called “theories-in-use” that differ significantly from their “espoused theories.” The espoused theory is what the organization says it values: learning, adaptation, and continuous improvement. The theory-in-use, however, is what actually governs behavior. I explored this gap directly in Issue 256, Structural Silence, where I examined how organizations claim to want candor while systematically training people that silence is the safer choice. A similar dynamic operates with organizational memory. Organizations claim to value learning. But their structures, expectations, incentives, and rhythms of work ensure that learning never compounds.
The gap between what organizations say about learning and what they actually do with it is most often enormous.
Optimized for Delivery, Not for Learning
There is a structural tension embedded in most organizations that is rarely acknowledged openly. Organizations are optimized for delivery, not for learning. Speed is rewarded. Outputs, not outcomes, are measured. Forward progress is prioritized in every planning cycle, every quarterly review, every leadership conversation about what comes next. Reflection, by contrast, is treated as a pause. An interruption to execution. Something that happens at the end of an initiative, if there is time, which there almost never is.
This creates a dynamic where learning is episodic rather than continuous. It happens at the conclusion of work, if at all. But by that point, the context has already shifted.
I wrote about a closely related pressure in Issue 254, Decision Theater, where I examined how organizations fill calendars with the rituals of decision-making while avoiding the actual act of deciding. The same organizational metabolism that produces Decision Theater also undermines organizational memory. When every hour is consumed by execution and alignment activities, there is no structural space for reflection. Learning becomes something that happens only when the pace of work allows it, which in most organizations means it does not happen at all.
Amy Edmondson’s research on psychological safety connects to this dynamic in an important way. Edmondson has demonstrated that teams with higher levels of psychological safety are not just more candid. They are more effective at learning from both successes and failures, because the environment allows people to surface what actually happened rather than what the organization prefers to believe happened.
When psychological safety is absent, postmortems become tasks of on-stage performance. People share what is politically safe rather than what is operationally true. The lessons captured are sanitized versions of reality, and the organization’s memory becomes even more corrupted.
The Cost of Repetition
Over time, this leads to a specific inefficiency: repetition.
Work feels new but mirrors what has already been done. Problems appear situational but are systemic. Experience accumulates in individuals but not in the organization.
Teams solve problems that were already solved. Leaders’ commission analyses that replicate prior work. The cost is operational, but also very human.
People lose trust when they see the same issues recur despite repeated assurances that “we have learned from this.” Credibility in leadership erodes when commitments to change are repeated without evidence of actually changing. Something more subtle and more damaging takes hold: people stop believing that learning has value, because they do not see it change outcomes.
From Archive to Capability
Organizational memory must be embedded into how work is performed. Not stored after the fact, but activated at the start. Before a new initiative begins, prior experience must be surfaced, not as a checkbox, but as a standard part of design.
Where have we seen this before?
What did we learn?
How does it apply here?
Knowledge moves through people. Connecting individuals with relevant experience to new efforts is one of the most reliable ways to transfer learning.
Leaders also need to signal what matters. If they do not reference prior learning, the organization won’t either. If every initiative is treated as a fresh start, people stop investing in documenting what they learn because they know it won’t be used.
The Leadership Responsibility
Reversing memory loss requires more than better systems. It requires a shift from archive to capability. Memory as a capability means that learning influences action. That past experience shapes present decisions. That reflection is integrated into execution.
Most organizations don’t lack learning. They lack the discipline to use what they’ve already learned.
This requires acknowledging that the organization has been here before. That the problem is not entirely new. That, without changing how learning is applied, the outcome will repeat.
The organizations that do this well build learning into the front end of work. They connect experience to execution. They treat prior learning as an input, not an artifact. And their leaders model that behavior consistently.
Because learning is not what an organization knows. It is what it does differently because of what it knows.
Until that changes, organizations will continue to move, produce, and experience.
But they will not progress.
They will repeat.
Join the Conversation
Have you seen your organization struggle to apply what it has already learned? What strategies or practices have you found effective for building genuine organizational memory? I would love to hear your perspective. Share your thoughts with me on LinkedIn or subscribe to Ideas and Innovations for weekly insights on leadership, transformation, and the human side of organizational change.
The Truth About Transformation
If this article resonated with you, my book The Truth About Transformation explores why most transformation efforts fail and what leaders can do differently. Available on Amazon.