Every leadership transition carries a version of the same quiet disaster: a competent successor walks into an office that looks orderly, inherits a filing system that seems complete, and then spends the next eighteen months discovering what was never written down. The institutional memory, the trusted relationships, the unspoken rules about who actually makes decisions and who merely approves them—none of it appears in the handover binder. This is not carelessness on anyone's part. It is, rather, a structural failure in how organisations think about knowledge: we document outputs and overlook the processes, relationships, and judgment calls that produce them. What follows is an attempt to name the things that get forgotten, and to offer a practical method for surfacing them before the outgoing leader walks out the door for the last time.
The handover document and its comfortable illusions ¶
Picture a Tuesday afternoon in late November. The outgoing CEO—call her Miriam—sits at the long table in the boardroom with a junior HR partner, working through a template the company has used for every senior departure since 2009. There are sections for active projects, budget responsibilities, direct reports, and key external contacts. Miriam fills them in diligently. She is thorough, well-intentioned, and genuinely committed to leaving things in good order. And yet, when her successor arrives in January, he will discover within six weeks that the template captured almost none of what he actually needed to know. The external contact list, for instance, named the CFO of their largest client but said nothing about the fact that Miriam had a decade-long friendship with that CFO, that they spoke informally every quarter, and that this relationship had quietly smoothed over a contract dispute two years earlier that never made it into any minutes. The template had a field for contact name and phone number. It had no field for context, history, or relational texture. This is not a flaw in the template—it is a flaw in the assumption that a template can capture these things at all.
Three categories of knowledge that never make the document ¶
Organisational knowledge worth transferring tends to cluster into three categories, and all three are systematically under-documented. The first is relational knowledge: who trusts whom, who has been burned by whom, which external partners respond to formal process and which respond only to a personal call from a senior figure. The second is interpretive knowledge: how to read a situation the organisation has seen before, the pattern-recognition that comes from having watched five budget cycles and three restructures and knowing, without quite being able to explain it, that a certain kind of email from the legal team means trouble is coming. The third—and most underestimated—is informal authority. In most organisations, the person with the title is not always the person whose approval actually moves things. There is frequently a long-serving operations manager, a quietly influential board member, or a chief of staff who has accumulated real decision-making power over years, and whose cooperation the incoming leader will need but whose role the outgoing leader may not even consciously register as significant, because it has always simply been part of how things work.
How to surface what the outgoing leader doesn't know they know ¶
The most useful tool here is not an interview—it is a structured conversation designed around situations rather than topics. Ask the outgoing leader to walk through the last twelve months as a sequence of events: what went wrong, what went better than expected, and what would have gone badly if not for a specific person, relationship, or piece of institutional memory. This narrative approach bypasses the categorical thinking that structured templates encourage and instead surfaces tacit knowledge—the kind that lives in stories rather than spreadsheets. A useful prompt: 'Tell me about a time in the last year when you made a decision that no one else in the organisation could have made.' That question, asked well, typically produces thirty minutes of material that a handover document could never have anticipated. Run this conversation at least twice, with at least two weeks between sessions, because memory is not linear and the second conversation almost always surfaces things the first one missed.
The relationship map no one draws ¶
One practical exercise worth doing is what some transition consultants call a relationship audit: a visual map of every significant external relationship the outgoing leader holds, annotated not just with names and titles but with the nature of the relationship, its history, and what would be required to maintain it. This is painstaking work and it tends to make outgoing leaders slightly uncomfortable, because it requires them to acknowledge that some of what they have accomplished is inseparable from who they are—and that transferring it requires real effort rather than a name on a contact list. The map should note, for each relationship: how long it has existed, what its origins were, whether it is formally documented anywhere, and what the incoming leader would need to do in the first ninety days to preserve it. In practice, this often means a series of introductory conversations—not handover meetings, which can feel clinical—but something closer to a genuine introduction: Miriam calling her contact at the client and saying, simply, 'I want you to meet the person who is taking over, and I want you to hear from me directly why I trust them.'
Informal authority: the hardest thing to hand over ¶
Informal authority is accumulated slowly and lost quickly, and it almost never survives a transition intact. This is not necessarily a problem—new leaders should earn their own authority rather than inheriting it wholesale—but it becomes a problem when no one acknowledges the gap exists. An incoming leader who does not know that a particular board member's informal sign-off has historically preceded every significant capital decision will simply not know to seek it, and will instead wonder why their formally approved proposals keep stalling. The outgoing leader's job here is to name the informal architecture explicitly: who are the five or six people whose quiet support determines whether things actually happen, and what does each of them care about, and how have you managed those relationships over time. This is not political manoeuvring—it is institutional transparency, and it is the part of leadership that most handover processes are simply too polite to address directly.
The overlap period: what it should actually look like ¶
Most overlap periods are designed for the comfort of the outgoing leader rather than the utility of the incoming one. The outgoing leader shadows, introduces, explains—and the incoming leader listens politely while privately struggling to absorb an enormous amount of information under significant social pressure. A better model inverts the dynamic earlier than feels comfortable. Within the first two weeks of overlap, the incoming leader should begin attending all the outgoing leader's significant meetings not as an observer but as a participant-in-training, asking questions openly, making small decisions with the outgoing leader present to correct or endorse them. This approach accelerates the transfer of credibility—arguably more important than the transfer of information—because the people around them begin to see the new leader making real judgments, not just listening to explanations. The outgoing leader's role shifts from teacher to validator, and that shift, when it happens visibly and in the room, does more for the incoming leader's informal authority than any number of formal introductions.
What to do in the ninety days after the door closes ¶
No handover process, however thorough, will surface everything. There will be a moment—probably around week ten or eleven, when the new leader has settled enough to notice what they do not know—when the gaps become apparent. The most important thing at this stage is to resist the impulse to fill the gaps through performance: projecting confidence about things one does not yet understand, or making decisions that require institutional knowledge one does not yet have. The better move is to identify two or three trusted people inside the organisation—not necessarily direct reports, and not necessarily senior figures—who have been there long enough to carry the institutional memory and who are invested enough in the organisation's wellbeing to share it honestly. These people are frequently found in operations, in finance, or in executive support roles. A new leader who spends thirty minutes a week in genuine conversation with a long-serving operations coordinator will learn more about how the organisation actually works than they will from six months of leadership meetings.
A leadership handover is not an administrative event. It is, at its most accurate, the transfer of a particular kind of accumulated human judgment—and that transfer requires more honesty, more time, and more structural intentionality than most organisations are willing to give it. The organisations that do it well are not the ones with the longest handover templates. They are the ones willing to ask the uncomfortable questions before the door closes, and to sit with the answers long enough to act on them.