AI Cures Organizational Dementia 2026w15 | lead > prompt #

People forget, but organizations forget at scale. AI is helping to plug that gap.

Welcome to Lead Prompt // executing leadership from the root. I’m your host, John Collins.

People forget. It is an immutable part of human biology. But organizations? Organizations forget at scale. And when you are operating in a complex technical environment, that collective amnesia isn’t just a minor operational annoyance, it is a critical architectural bottleneck. Lately, artificial intelligence has been stepping in to plug that exact gap, and a recent migration project with my engineering team brought this exact problem into absolute focus for me.

Recently, my team and I were tasked with moving a legacy application from Windows 2003 to Windows 2019. Now, on the surface, this might sound like standard life-cycle maintenance. But the migration was an absolute operational requirement to move this old application to a brand-new domain controller. Why? Because modern domain controllers flatly refuse to support Windows 2003 hosts trying to join the domain due to updated security protocols.

The application in question is at least 25 years old. To put that in perspective, the most recent comments left in the code are from engineers writing updates in 2003, all of whom have long-since left the organization. My current engineering team had no idea how it worked under the hood, or how we could safely lift a quarter-century-old application from a 32-bit Windows 2003 architecture and drop it into a modern, 64-bit Windows 2019 environment. Oh, and the cherry on top? The business ideally didn’t want us touching the core source code or executing a recompile. Fun times.

This harrowing journey down technical memory lane got me thinking about how organizations "forget at scale." It is a form of organizational dementia. The older a project becomes, the steeper the curve of institutional forgetfulness. Last year’s legacy application is a walk in the park compared to last decade’s.

So how do we handle such profound system amnesia?

Before we look at the modern solution, we have to look at the science of why this happens. In the field of management science, this phenomenon has been studied extensively under the label of organizational forgetting . We spend an enormous amount of time talking about organizational learning: how companies acquire knowledge, optimize delivery pipelines, and scale intellectual property. But academic research reveals that forgetting is an equally powerful, sometimes destructive force.

In a landmark study published in Organization Science by researchers Pablo Martin de Holan and Nelson Phillips titled “Remembrance of Things Past? The Dynamics of Organizational Forgetting”, the authors establish a foundational framework for how institutional memory breaks down. They separate organizational forgetting into two primary dimensions: intentional and unintentional.

Intentional forgetting, or "unlearning," can actually be a healthy strategic asset like intentionally purging obsolete routines to make room for new operating models.

Unintentional forgetting, however, is a silent organizational killer. It manifests as "knowledge loss" when key engineers walk out the door, or "asset depreciation" when the organization simply stops interacting with its own historical data repositories.

Furthermore, landmark quantitative research on manufacturing and corporate environments by scholars like Linda Argote has proved that corporate experience doesn't stay fresh indefinitely. In fact, knowledge acquired during production and development depreciates surprisingly fast if it isn’t continuously reinforced, documented, or embedded directly into everyday organizational routines. Without constant rehearsal, the organizational cues that trigger corporate memory disappear entirely. When you combine standard employee turnover with a total lack of continuous code interaction over two decades, you are left with an absolute cognitive vacuum.

In software engineering, this amnesia is uniquely toxic. Code is a perfect, frozen snapshot of historical logic, but the context around it, the why behind a specific hack, the underlying infrastructure dependencies, the environmental quirks, all evaporates completely.

When we started tackling this Windows 2003 migration, we fortunately had access to the original source code. It consisted of a classic ASP web front end calling Visual Basic 6 COM+ objects. Standing before that wall of ancient syntax, I was reminded once again of a saying a brilliant previous colleague of mine used to utter whenever we hit an undocumented feature or an opaque error: “Use the Force, read the Source.” He was clearly a massive Star Wars fan, and his philosophy was simple: the ultimate truth is always found in the code, not the outdated corporate Wiki.

But let's be completely honest with ourselves. In the past, "reading the source" of a 25-year-old application...