Forgetting as a Managerial Skill

Forgetting has a poor reputation in management. When we speak of it at all, we speak of it as loss: knowledge that walks out the door when an expert retires, institutional memory eroded by turnover, hard-won lessons that leak away because no one wrote them down. Forgetting, in this telling, is simply the failure of memory, and the remedy is always more capture, more documentation, more retention.

There has always been a minority tradition that saw further. Four decades ago, Hedberg argued that organizations must not only learn but unlearn—that they must actively discard obsolete beliefs and routines to make room for new ones, and that the discarding is a distinct capability, not merely the absence of learning. More recently, work on organizational forgetting has drawn a crucial distinction between the accidental loss of knowledge an organization needed and the purposeful release of knowledge it should no longer hold—arguing that the failure to forget can be every bit as damaging as the failure to learn. Yet this line of thought has stayed at the margins, admired and unused, while the machinery of the field points relentlessly in the other direction.

The reason forgetting is so hard for institutions is structural. Everything an organization builds is designed to retain. Documentation preserves; standardization entrenches; "best practice" canonizes; precedent accumulates; onboarding transmits the accumulated stock to each new arrival. There is an owner for capturing knowledge and an owner for storing it, but there is no owner of expiry. No one's job is to decide that a practice should stop being taught, that a playbook has aged out, that a lesson everyone still cites was true only under conditions that have passed. And so nothing is ever retired; it is only added to.

The cost of this shows up as a curve that anyone who has worked in an old, proud organization will recognize. Too little retained knowledge is plainly bad—the organization relearns everything, repeats solved problems, cannot compound. But too much retained knowledge is also bad, and beyond a certain point additional memory is not neutral ballast. It actively crowds out the perception of change. The organization keeps reaching for a lesson that was genuinely valid once, applying it to a problem that merely resembles the old one, and calling the misapplication experience. Somewhere between remembering nothing and remembering everything lies the range where an organization can actually adapt.

Staying in that range requires telling two kinds of forgetting apart. There is harmful forgetting—the loss of tacit knowledge the organization still needs, the very erosion the retention machinery was built to prevent. And there is healthy forgetting—the deliberate release of knowledge that no longer holds. The managerial skill, almost entirely undeveloped, is distinguishing them. Most organizations are poor at both at once, which is the worst possible combination: they lose the tacit understanding they cannot afford to lose, while clinging to the explicit doctrine they can no longer afford to keep.

Done well, forgetting is not neglect. It is curation, and curation is demanding. It requires knowing, for each thing an organization believes it knows, under what conditions that knowledge was true and whether those conditions still hold—so that a lesson can be reviewed when its world changes and retired when its world is gone. That is a far more active relationship with memory than storage, and almost no institution maintains it.

Deliberate forgetting must also be distinguished from mere deletion, which is one reason it cannot simply be automated away. To delete is to remove a record; to forget well is to decide that a belief no longer governs action while remembering, if it matters, that it once did and why it stopped. The distinction is not pedantic. A retired lesson often needs to leave a trace—a note that this was tried, believed, and outgrown—so that the organization does not later rediscover the obsolete idea and adopt it again with fresh enthusiasm, mistaking a dead end for an insight. And there is a human obstacle that no system dissolves: practices have parents. Someone built the routine now due for retirement, staked a reputation on it, perhaps still manages by it and is respected for it. Retiring the practice is never only a technical act; it is a social one, which is precisely why organizations flinch from it and let the obsolete quietly stay.

Until forgetting is somebody's explicit responsibility—until an organization can name what it has chosen to stop believing, and why—it will keep mistaking the sheer accumulation of memory for the growth of wisdom. The two are not the same, and in a fast-moving world they increasingly point in opposite directions. Learning to forget well may be the more difficult, and by far the more neglected, half of learning.