Every institution eventually loses people who know things that matter. Employees retire, specialists change organisations, managers rotate between responsibilities and experienced professionals move into new roles, taking with them not only information but years of accumulated judgement about how the institution actually works. Some of what they know will already exist in documents, databases and formal procedures, but much of it may be less visible: an understanding of why a process evolved in a particular way, an ability to recognise unusual cases, knowledge of which relationships make coordination possible, awareness of earlier failures that still influence present practice, or simply the practical judgement required to distinguish an ordinary problem from one that deserves attention. When such a person leaves, the institution may discover that what appeared to be organisational capability was partly individual capability being temporarily carried on the institution’s behalf.

This vulnerability is often recognised only at the moment of succession, when colleagues realise that a departing employee has become an informal repository for knowledge that nobody deliberately designed them to hold. Questions suddenly accumulate around the person who is leaving: which files matter, which contacts should be preserved, what unfinished issues need explanation and what somebody else will have to learn quickly enough to maintain continuity. The familiar response is to capture as much knowledge as possible before departure, perhaps through handover documents, interviews or repositories. These measures can certainly help, but they also reveal a deeper architectural problem, because institutional memory that depends primarily on extracting knowledge from people immediately before they leave has already become dangerously dependent on succession as an emergency event.

Designing memory that survives succession therefore requires a broader question than how to document what one person knows. The real issue is how knowledge becomes sufficiently institutionalised during ordinary organisational life that the departure of any one carrier does not cause a disproportionate loss of cognitive capability. Documentation is part of that architecture, but documentation alone cannot preserve every form of knowledge that institutions need. A written procedure may record the official sequence of a task without capturing the judgement involved in handling exceptions; a database may preserve historical cases without explaining which features experienced practitioners considered significant; a project archive may contain every formal decision while omitting the informal reasoning through which competing interpretations were resolved. Knowledge can be recorded extensively and still remain difficult for a successor to use.

This is why redundancy matters. In many technical systems redundancy is deliberately created so that the failure of one component does not destroy the capability of the whole, and institutional knowledge can be considered in similar terms. If only one person understands a critical process, relationship or judgement, the institution possesses a cognitive single point of failure regardless of how competent that person may be. Creating redundancy does not mean that everybody should know everything, which would undermine the advantages of specialisation and impose impossible learning costs. It means that consequential knowledge should not depend entirely on a single carrier when its disappearance would materially weaken institutional performance. A second person may understand the process, a team may share enough contextual knowledge to reconstruct it, or the relevant expertise may be distributed across several roles so that no individual departure removes the whole cognitive structure.

Role architecture is equally important because knowledge continuity depends partly on whether institutions know where particular forms of memory are supposed to reside. When important knowledge accumulates around individuals purely because they happen to have been present for a long time, succession becomes unpredictable: the institution may not even recognise which capabilities are at risk until departure exposes them. By contrast, roles can be designed with clearer expectations about what knowledge should be maintained, transferred and made available beyond the current occupant. The aim is not to eliminate personal expertise, which remains indispensable, but to ensure that institutional responsibility for knowledge does not disappear behind the biography of whoever currently possesses it.

Some forms of knowledge require transmission through practice rather than storage. An experienced professional may be able to explain how a difficult judgement is made, yet the explanation alone may not give a successor the ability to make it. Much practical knowledge is learned through exposure to cases, observation, guided participation and opportunities to compare one’s own judgement with that of more experienced colleagues. Mentoring, shadowing, overlapping appointments and communities of practice can therefore contribute to succession memory because they allow knowledge to move while it is still being used rather than waiting for a departure to force its extraction. What passes between people in these settings is often not a fixed package of information but a developing ability to notice, interpret and respond.

Procedures provide another layer of continuity because experience can become embedded in the way work is organised. A requirement for a second review may preserve the consequence of an earlier failure; a consultation step may ensure that expertise from another unit enters a decision; a particular sequence of checks may embody lessons accumulated through repeated experience. Such procedural memory can be remarkably durable, but it must be treated carefully. As the preceding problem of institutional memory shows, a procedure can survive after its rationale has faded, so embedding knowledge in routines should ideally preserve enough contextual explanation for later generations to understand what the arrangement was designed to achieve. Succession memory is stronger when successors inherit not merely instructions but some capacity to interpret the institutional reasoning those instructions contain.

Technology can support each of these mechanisms without replacing them. Searchable repositories can make earlier work easier to retrieve, collaboration systems can preserve traces of decision processes, expertise directories can help people locate knowledgeable colleagues and AI systems may increasingly assist institutions in finding connections between current problems and accumulated records. Used well, these technologies can reduce dependence on personal recollection and make institutional knowledge more accessible across organisational boundaries. Yet they cannot automatically transform human experience into durable institutional memory, because they are strongest where knowledge has left usable traces and weakest where understanding remains tacit, relational or deeply dependent on context. A technologically sophisticated archive can therefore coexist with serious succession vulnerability if the institution assumes that storing information is equivalent to preserving capability.

The most resilient approach is consequently layered rather than singular. Critical knowledge may be documented where explicit representation is possible, distributed sufficiently to avoid unnecessary single points of failure, embedded in roles and procedures where continuity matters, transmitted through mentoring and practice where judgement cannot be reduced to instructions, and supported technologically so that accumulated knowledge remains discoverable. Different forms of knowledge require different combinations of these mechanisms, and the architecture should reflect the consequences of losing them rather than pursuing exhaustive preservation. Institutions do not need to preserve everything every employee knows; they need to understand which losses would materially reduce their capacity to act, learn or interpret their environment, and design continuity around those vulnerabilities.

This also means that succession should not be treated exclusively as an event occurring at the end of someone’s tenure. By the time a departure is imminent, the institution may have only weeks to reconstruct knowledge accumulated over decades, and some of the most important forms of understanding may be precisely those the departing person finds hardest to articulate because they have become habitual. Memory that genuinely survives succession is built before succession becomes urgent, through everyday arrangements that allow knowledge to circulate, become visible, leave traces and acquire carriers beyond the person who first developed it. The goal is not to make individuals replaceable in the crude sense that their experience has no distinctive value, but to ensure that the institution does not become cognitively dependent on their permanent presence.

There is also a necessary limit to preservation. Institutional memory should not become an argument for reproducing every inherited practice indefinitely, because succession is sometimes an opportunity for revision as well as continuity. New people may legitimately question assumptions that long-serving employees considered obvious, and some accumulated knowledge may reflect environments that no longer exist. A robust succession architecture therefore preserves enough knowledge for successors to understand what came before without requiring them to reproduce it uncritically. Continuity should make informed revision possible rather than make revision impossible.

Seen in this way, successful succession is not demonstrated simply by filling a vacant position or completing a handover document. The deeper test is whether the institution retains enough of the relevant capability after personnel change to continue acting intelligently, while remaining able to interpret and revise what it has inherited. When the departure of one person produces a sudden collapse in knowledge, the problem is not merely that the individual knew a great deal; it is that too much of what mattered remained attached to the individual rather than becoming sufficiently supported by institutional architecture.

Institutional memory survives succession when knowledge has more than one way to remain consequential: through records that can be found, roles that carry responsibility, colleagues who share understanding, practices through which judgement can be learned, procedures that preserve experience and technologies that make accumulated knowledge accessible. The objective is not to create an institution that loses nothing when people leave, which would be neither possible nor desirable, but one in which personnel change does not routinely force the organisation to relearn what it had already learned simply because the person who carried that learning is no longer there.