Institutional Memory: How Biases Shape What Organizations Remember
Early in my career, a CEO approved $1.8 million for a project our organization needed but hadn’t budgeted for. We had suggested waiting until the following year, but he wanted the work completed sooner. At the next budget review, he questioned why we were $1.7 million over budget. We explained that we had spent less than the amount he had authorized. He said he didn’t remember approving it. We were held accountable, and some people missed their bonuses. We should have documented the budget variance and had the CEO document a written approval when the decision was made, rather than relying on everyone’s recollection of the conversation.
Institutional memory depends on the people, records, and shared accounts that preserve an organization’s experience. People use that history to evaluate performance, allocate resources, and decide which approaches to repeat. However, the same people who preserve that history also interpret it through their own experiences. Their accounts can emphasize different contributions, costs, and commitments. As people leave an organization and new people join, the memory changes. As with any human experience, institutional memory is subject to biases. An organization can therefore have an extensive, disconnected, and diverse memory without having a complete account of the decisions that produced it.
Recency bias: Last week gets more weight than last year
Recency bias gives recent events greater weight than earlier ones. Consider a performance review in which a mistake from last week receives more attention than several important contributions from six months ago. The recent mistake is readily available in the manager’s memory. Earlier contributions may receive less attention even when they produced more value. This is particularly challenging when considering performance reviews, which can overweight the timing of events rather than their relative importance. A recent mistake still deserves an appropriate response, but it should not substitute for an assessment of the whole year.
I recommend keeping a record of contributions and challenges throughout the year. Include the work completed, the result, and how you responded when something went wrong. Keep your job description current as responsibilities change. Bring those changes into the performance discussion alongside the record of your work. Give your manager enough information to assess the job you actually perform, rather than relying on what they remember from the last few weeks.
Negativity bias: A mistake receives disproportionate attention
Negativity bias can give unfavorable information more influence than comparable favorable information. Negative feedback may attract more attention and receive more detailed processing than positive feedback. This creates a different problem from recency bias. Recency concerns when something happened, while negativity concerns how unfavorable information influences judgment. A recent mistake can involve both mechanisms, which makes it important to examine its actual consequences before assigning its weight in an evaluation.
Loss aversion describes a related but narrower effect. People can assign greater subjective weight to a loss than to an equivalent gain, measured against a reference point. That distinction is important because remembering criticism and evaluating a potential loss involve different judgments. When reflecting on a past project or a pilot program, I recommend separating the consequences of an error from the strength of the reaction it produced. Examine the cost, recurrence, and corrective action rather than assuming that the most memorable event deserves the most weight.
The Pollyanna principle: The successful launch replaces the difficult project
The Pollyanna principle describes a tendency to favor pleasant information in processing and recall. A recent positive outcome can also cloud history. This does not mean that people always remember positive events better than negative ones. Research on memory shows that favorable recall and strong reactions to negative information can coexist. The important question for leaders is whether the account used for the next decision preserves the full experience.
Consider a project that promises a wide commitment of benefits for a $10 million investment. After new information and unexpected complications, the organization spends $15 million and many of the benefits are moved out of scope or never realized, but the team celebrates the launch as a success. Months later, people remember the successful launch while giving less attention to the missed commitments. The project may still have produced useful results, but those results do not explain the difference between the original promise and the final delivery. If the next project uses only the favorable account, the organization has little reason to adjust its estimates. Your system should monitor the results against the original business case before using that project as a model for future work.
Self-serving bias: My leadership explains the success, but someone else explains the failure
Self-serving bias directs people toward explanations that credit themselves for success and place responsibility for failure elsewhere. That pattern can protect a favorable view of their own competence. It also changes the account they give of a shared result. A leader may emphasize their coordination and communication when a project succeeds, then emphasize the team’s mistakes when it struggles. The explanation gives the leader a central role in success and a smaller role in failure. Research supports this attributional tendency, although its strength varies across people and contexts.
My concern is what the organization learns from that account. If leaders document their own contributions while overlooking the team’s work, the record gives an incomplete explanation of the result. It also gives the team a different reason to remember the project. I recommend being as specific about contributions as you are about mistakes. Describe who contributed, what they did, and how that work supported the outcome. Apply the same attention to the decisions and circumstances that contributed to problems. A useful review should give the next team an account they can learn from, rather than an account organized around protecting someone’s reputation.
Hindsight bias: The outcome changes what people believe they knew
Hindsight bias changes how predictable an event appears after people know the outcome. New information can influence their recollection of what they previously expected. A result that once involved debate and uncertainty can later seem obvious. This mechanism differs from self-serving bias, which concerns how people assign credit and responsibility. Hindsight bias concerns the apparent predictability of the outcome. During a review, that can encourage people to judge an earlier decision using information that was unavailable when they made it.
Before an important decision, I recommend recording the expected benefits, the risks considered, and the reasons for choosing that approach. Preserve the assumptions alongside the approval. Afterward, compare the actual result with those expectations. Examine whether a risk failed to occur because you overestimated it or because actions or externalities prevent it. Review the alternatives that were available at the time, rather than treating the final outcome as inevitable. Use the differences between expectation and result to improve the assumptions behind the next decision.
Give institutional memory something to work with
Memory is useful only when people can use it to learn ~ not anecdotally, but with evidence. One of my favorite activities is conducting a knowledge audit to identify where process knowledge, customer knowledge, and decision histories are concentrated. Look for important information that depends on one person’s recollection. Ensure your decision processes capture the reasoning behind decisions. Make that record accessible to the people responsible for the next decision and ensure past reality is included in the next ROI model. Repeat the assessment as people change roles, projects develop, and responsibilities change.
Start with one completed project and its original business case. Compare the promised benefits with the benefits delivered. Compare the approved resources with the resources used. Identify the contributions that helped the project succeed and the circumstances that limited the result. Record which assumptions need to change before the next approval. Keep that comparison with the decision history so the next team can use the experience without depending on someone’s memory.
Comments