When a team faces a problem it has seen before, a shared framework can bring earlier learning into the next decision: it supplies concepts, routines, and guidance that people can reuse. In that sense, frameworks can act as institutional memory—but they are only one part of it. Organizational memory also lives in records, people’s experience, relationships, and everyday practices, and it must be revisited when circumstances change.
What is institutional memory?
Institutional memory is the knowledge an organization retains and can draw on later. It is not simply a database or archive. In their 1991 analysis, researchers James P. Walsh and Gerardo Rivera Ungson describe organizational memory in terms of how information is acquired, retained, and retrieved, as well as where it is held. That knowledge may be recorded in documents, carried by employees, or embedded in repeated ways of working.
As an Amazon Associate I earn from qualifying purchases.
This broader view matters because having information somewhere is not the same as being able to use it. A lesson that cannot be found, understood, or applied by the people making a decision is weak memory in practice. The National Academies’ 2007 report on institutional-memory practices examines this challenge in U.S. and Canadian transportation agencies; its sector-specific focus offers a practical example of why organizations need both retained knowledge and ways to use it.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallHow can a framework carry earlier learning into a decision?
A framework makes some experience portable. It gives people shared concepts for interpreting a situation and repeatable practices for responding to it. Instead of relying entirely on the recollection of whoever happens to be present, a team can consult a common approach and coordinate its actions.
#1 Best Overall
But a framework is not a complete record of everything an organization knows. It can codify explicit guidance—such as decision criteria or a sequence of steps—while leaving out context, judgment, and the reasons a rule was adopted. Those may remain with experienced employees or be learned through practice. Frameworks therefore work best as a bridge between documented knowledge and people’s expertise, not as a substitute for either.
What does organizational learning require beyond documentation?
Knowledge management involves more than capture. In a 2003 framework, Linda Argote, Bill McEvily, and Ray Reagans distinguish three outcomes: knowledge creation, retention, and transfer. A document may help retain an insight, but it does not by itself ensure that the insight is shared across teams, adapted to a new setting, or used to create better knowledge.
- Creation: People develop knowledge through work, problem-solving, and experience.
- Retention: The organization preserves useful knowledge in records, people, structures, or routines.
- Transfer: Knowledge reaches the people or units that need it and can be applied in their context.
Whether transfer succeeds depends partly on the organizational unit, relationships among units, and the nature of the knowledge. A written procedure may transfer easily; tacit expertise that depends on practice or close collaboration may not. As Argote, McEvily, and Reagans emphasize, there is no single capture method that resolves all three challenges.
Why do teams repeat processes—and when does that become a problem?
Repeated routines can make coordinated work faster and more reliable. Michael D. Cohen and Paul Bacdayan describe routines as “multi-actor, interlocking, reciprocally-triggered sequences of actions” and argue that they are a major source of reliability and speed in organizational performance. Their 1994 laboratory study supports the idea that elements of routines can be stored in procedural memory.
The same persistence can become a liability. A team may apply a familiar routine automatically even when the situation has changed or the routine no longer fits. A framework that once preserved a sound lesson can then preserve an outdated assumption as well. The practical task is not to eliminate repetition, but to distinguish useful consistency from unexamined reuse.
How does organizational history shape a framework?
Frameworks inherit the circumstances in which they were formed. Structures, routines, and cultures can gain lasting influence during short periods of change, then carry that influence into longer stretches of organizational life. In a 2024 article, Christopher Marquis and Kunyuan Qiao distinguish these brief “junctures” from longer processes in which past influences may be strengthened, preserved, or weakened.
This perspective makes a framework neither neutral nor permanent. It may encode choices made under earlier constraints, including what the organization prioritized and what it overlooked. Reviewing a framework means asking not only whether it is clear, but whether its assumptions still match current conditions.
Recommended Free Tools
Can technology preserve institutional memory on its own?
Technology can help store, organize, and retrieve information, but an information system alone cannot guarantee organizational learning. In their 1998 discussion, Anand, Manz, and Glick argue that IT should be complemented by organization-level processes and attention to “soft” knowledge, including tacit knowledge, judgment, and intuition.
Best Value
- Author: Bungay Stanier, Michael.
- Publisher: Page Two
- Pages: 244
- Publication Date: 2016-02-29
- Edition: 1
A useful system needs human practices around it: people must contribute relevant lessons, maintain records, interpret what they find, and pass expertise to others. Some context-dependent knowledge is best shared through conversation, mentoring, or joint work rather than assumed to fit inside a formal framework.
How can an organization keep a framework useful?
Treat a framework as a maintained learning aid, not a final answer. When evaluating one, consider:
- Coverage: Does it capture documented knowledge as well as point users toward expertise or context it cannot codify?
- Retrieval: Can people find and understand the guidance when they need it?
- Transfer: Can another person or team apply it, and what relationships or explanation are needed?
- Revision: Is there a way to reconsider assumptions as conditions, evidence, or organizational goals change?
- Adaptation: Does it help people make a sound choice in the current situation, or does it encourage routine compliance when the fit is poor?
These questions connect the core work of knowledge management—creation, retention, and transfer—with the strengths and risks of organizational routines. A framework serves as institutional memory when it helps people retrieve prior learning and use it thoughtfully, while leaving room to improve what the organization has learned.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
