Where Does Organizational Memory Reside When Everyone Works From Home?

In their foundational treatment of organizational memory, Walsh and Ungson made a point that is easy to read past: memory is not one thing kept in one place. It is distributed across several stores, or retention bins—the individuals who carry expertise, the culture that encodes shared assumptions, the routines and procedures that hold lessons in their very structure, the roles and hierarchies that fix who knows what, and, not least, the physical setting in which work happens. To these they added external archives. An organization "remembers," on this account, through the combined action of all of these, most of which no one manages deliberately.

The bin we overlooked was the setting itself—and the culture that lived inside it. An enormous amount of what an organization knew was held in co-presence. It lived in the overheard phone call that taught a junior colleague how a hard conversation is handled; in the whiteboard left up from yesterday's argument; in the new hire absorbing what is and isn't done here simply by sitting near people who know; in the quiet correction offered in a corridor before a mistake reached a client. None of this was ever documented, because it never had to be. The building remembered it. Proximity did the work that a knowledge-management system is supposed to do, and did it better, because it transmitted the tacit dimension that no document captures.

Distributed and asynchronous work removed the building. What was already explicit—the documents, the tickets, the recorded decisions—survived the move to distributed work, because explicit knowledge travels. What was tacit and spatial did not. The result is not really amnesia; it is exposure. We discovered how thin the deliberate record always was, how much we had been relying on ambient memory that we never counted as memory at all.

It is tempting to believe the digital tools have replaced the room. They have not, and confusing the two is the central error. A chat archive is a complete record of messages and a near-total loss of the context that made those messages meaningful. Search will find the document; it will not find the judgment that would have told you the document was superseded, or written for a client we no longer serve, or right in every particular except the one that mattered. The tools capture transactions with great fidelity. They capture understanding hardly at all.

The loss falls unevenly, and it falls hardest on the newest people. A seasoned employee carries years of absorbed context and can work around a thin record; a new hire, dropped into a distributed organization, has no corridor to learn in and no ambient culture to absorb by proximity. What such a person receives instead is documentation—accurate, abundant, and mute about nearly everything that matters most: which rules are real and which are merely nominal, whom to ask, what the last three attempts at this taught, why the obvious approach is a trap that has caught others before. The organization believes it has onboarded the new arrival because it has granted them access. But access to explicit records is not the same as inheritance of understanding, and the gap between the two used to be closed, invisibly and at no cost, by the simple fact of being in the room while experienced people worked.

So organizations that once let the workplace remember for them now face a task they have never had to perform on purpose: deciding what the institution should retain, and building the means to retain it, in the absence of a shared physical world that used to do this silently and free. This turns out to be harder than buying more storage. Storage has never been the constraint; a distributed organization drowns in captured material. The constraint is curation—knowing what is worth keeping, in a form that preserves not just the fact but the conditions under which the fact was true.

That is a design problem, and most organizations are solving it by accident, if they are solving it at all. They have replaced a memory that maintained itself with one that must be maintained, and they have not yet appointed anyone to the maintenance. We used to let the workplace do our remembering. Now that the workplace is a set of login sessions, remembering has become something an organization must choose to do—and, just as importantly, must choose what not to do. We will return to that second, stranger half of the problem.