A procedure tells the next person what to do; institutional memory also explains why: the problem it addressed, the evidence and assumptions behind the decision, and the result it was meant to achieve. To pass that reasoning on, record it, invite the people who know the work to test it, turn lessons into assigned changes, and check whether those changes take hold.
What does “the why” need to preserve?
“The why” is not a slogan or a manager’s after-the-fact explanation. It is the reasoning that makes a practice intelligible: the conditions it was designed for, what was known at the time, whose perspectives were considered, what trade-offs were accepted, and what outcome the organization intended.
As an Amazon Associate I earn from qualifying purchases.
That distinction matters when people, tools, or circumstances change. A successor who inherits only an instruction may follow it in the wrong context, repeat a problem the procedure was meant to prevent, or discard a useful safeguard because its purpose is invisible. A decision record should make it possible to understand both the action and the conditions under which it still makes sense.
The UK Government’s Lessons Management Best Practice Guidance describes a lesson as: “A ‘Lesson’ articulates an update in knowledge or understanding that has been gained through experience.” That is more than a note that something happened. It connects observation to changed understanding.
#1 Best Overall
Why doesn’t knowledge transfer happen automatically?
Knowledge does not move simply because it has been written down or placed in a shared repository. Linda Argote’s 2024 review defines transfer in terms of how far one organizational unit learns from, or is affected by, another unit’s experience. Transfer can be seamless in some cases and incomplete in others; the review points to opportunities to learn, the nature of the knowledge, the transfer mechanism, motivation, and the recipient’s depth of consideration as factors that help explain the difference.
Some context is difficult to express as a rule. A colleague may know which exception matters, which signal is reliable, or why an apparently efficient shortcut was rejected. That practical understanding may need conversation, examples, and access to the people involved—not just a document. George L. Roth’s 1999 paper on “learning histories” describes projects that used documentation and conversation to capture and diffuse organizational experience, learning, and change.
Rank #2
- we like to ship out right away
Documentation remains useful, but it is one part of a transfer process. A record no one can find, question, or apply is not yet shared understanding. For technology teams, this can mean adding rationale to an operational runbook or design decision, then making space to revisit it when the system or its risks change.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →How can a team capture a useful lesson?
The UK Government guidance offers a process developed for civil-contingencies resilience. It can be adapted as a practical model in other workplaces, not treated as a universal standard. Its sequence moves from identifying and prioritising lessons to implementing them and embedding the resulting learning in ordinary practice.
Rank #3
- Capture observations and analyze them. Describe what happened, when and where it happened, who was involved, and why it matters. Separate direct observations from interpretation, and look for the issue or root cause rather than recording only a symptom.
- State the lesson and intended action. Explain what the experience changed in the team’s understanding, what should change in response, and what outcome the action is intended to produce.
- Prioritise. Decide which lessons warrant action first, taking account of their significance and the consequences of leaving them unaddressed.
- Assign and track implementation. Give an accountable owner authority to act, set a way to track progress, and connect the action to the systems, governance, or training it affects.
- Embed and review. Make the updated practice part of normal work, then review whether it is being used and remains appropriate.
For a decision or lesson record, useful fields include:
- the decision or practice, its context, and its date;
- the problem being addressed and the evidence considered;
- the perspectives included, root cause, and assumptions;
- options considered, trade-offs, and intended outcome;
- the action, accountable owner, and review date; and
- the conditions that would justify revisiting the decision.
This is a practical synthesis, not a quoted or validated template. Its purpose is to preserve enough context for a future reader to understand the decision, challenge its premises, and know when it may no longer apply.
Who needs to be involved?
People closest to the work often hold details that formal reports miss, while leaders may have the authority to change policy, systems, or resourcing. A sound lesson process needs both kinds of contribution. The UK guidance emphasizes accountability and action tracking; in practice, that means naming who can decide, who must carry out a change, and who should be consulted because they understand the work or will live with the consequences.
Make it safe to describe failure, uncertainty, and disagreement candidly. If people expect blame for raising a problem, records can become polished accounts that preserve the approved explanation but lose the evidence needed to improve. Invite relevant perspectives before settling on a root cause, and distinguish what is established from what remains an assumption.
Best Value
- Author: Bungay Stanier, Michael.
- Publisher: Page Two
- Pages: 244
- Publication Date: 2016-02-29
- Edition: 1
How should the rationale change as a practice is implemented?
A rationale should be durable enough to explain a decision, but not frozen when evidence changes. Rousseau and ten Have’s 2022 article frames evidence-based change management around four sources: scientific evidence, organizational evidence, stakeholder perspectives, and practitioner experience. It also describes continuing practices such as setting goals, communicating a vision, and using feedback to redesign implementation.
That approach gives teams a useful discipline: communicate the reasons for change, then update the record when implementation reveals a mismatch between the original assumptions and real conditions. Keep the original decision intelligible while documenting what has changed and why; otherwise, a later revision can erase the learning that led to it.
How can a team tell whether the why was passed down?
Publication or announcement is not proof that learning has transferred. Check whether the people expected to use a change can explain its purpose, know what to do, and recognize the conditions that would make the guidance unsuitable. Review whether the assigned actions are complete and whether the revised practice appears in the relevant workflows, governance, systems, or training.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesSet a review point and a way to gather feedback from the people doing the work. If the new practice is not being followed, find out whether the cause is unclear rationale, poor access, missing authority, an impractical process, or changed circumstances. The response may be to improve communication, redesign the change, or revisit the original decision—not simply issue the same instruction again.
Further reading
For a transportation-sector perspective, the National Academies Press lists The Business Case for Knowledge Management: A Guide (NCHRP Research Report 1164, 2026), a 154-page paperback for state departments of transportation and other transportation agencies. It addresses assessing knowledge-management activities, including identifying, capturing, and transferring institutional knowledge. Its audience is sector-specific, but the subject may be useful to readers working in transportation.
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.
