8 min read
Somebody hands in their notice and the reaction in the room is mild. There is a card, a leaving lunch, a short conversation about backfilling the role. Everyone is a little sorry and nobody is alarmed, because the organization has been through this before and it went fine.
Then, some weeks later, a series of unrelated things go wrong at once. A renewal is missed. A report comes out with a number in it that nobody can reproduce. Two teams discover they had each assumed the other was handling a customer. None of these look connected, and in the ordinary telling they are attributed to a bad quarter.
They are connected. What departed was not a person doing a job. It was The Load-Bearing Person™ — the individual around whom a system has structurally organized itself by default rather than by design, whose presence conceals the system’s fragility and whose absence reveals it — and the delay between the exit and the damage is the single most misleading feature of the whole event.
The notice period is the quietest part
Handover, where it happens at all, covers tasks. It covers logins, recurring reports, the list of things in flight, the calendar of what falls due when. All of that transfers well, and it transfers in an afternoon, which is what produces the false confidence.
The leaver is usually a conscientious person and does a genuinely good job of this, which makes it worse rather than better. They write the documents. They record the walkthrough. They answer everything they are asked. The trouble is that handover is a question-and-answer format, and nobody in the room knows which questions to ask, because the things worth asking about are precisely the things that have never come up.
So the notice period ends with everyone reassured. The tasks are documented. The gap that has just opened is not visible anywhere, because it was never visible in the first place — the presence of the person was what kept it that way.
What actually leaves the building
Four things go out the door, and only the first appears on any handover list.
- The tasks. Genuinely transferable, usually transferred, and the least of it.
- The reasons. Why the exception for that client exists, why the second approval was added, why one supplier is handled differently from the others. The decisions are visible in the record; the reasoning behind them lives in one head, and without it a successor cannot tell a deliberate arrangement from an accident and will eventually tidy one of them away.
- The routing. The set of problems that came to this person because everyone had learned to send them there, without any of it being written down. After the exit those problems do not stop; they arrive at whoever seems closest, are handled inconsistently, and produce the impression of a general decline in standards.
- The absorption. The small daily catching of things that were about to fall — the check that was not in any process, the quiet correction before a document went out. This one is invisible even in retrospect, because there is no record of a problem that was prevented.
Three of those four cannot be extracted by questioning, because a question requires both parties to know what the subject is. This is what makes the timing so treacherous. Tasks fail immediately if they fail at all. Reasoning, routing and absorption fail on their own schedule, weeks later, at the first case that falls outside the pattern — and by then the departure is old news and nobody is looking in that direction.
Why the successor struggles for reasons nobody predicts
A replacement is hired or promoted, and within a few months there is a quiet consensus that they are not quite as good. This consensus is usually wrong, and it is worth saying exactly why.
The successor was recruited against the role, which is a written thing. What they inherited is the role plus the accumulated undefined work of several years, which is not written anywhere and which nobody thought to mention because nobody could see it. They are being measured against a predecessor’s output while holding a job description that covers only part of what that output required.
They also inherit it without the thing that made it survivable, which was relationships. The predecessor could resolve a cross-team problem with one message to somebody they had known for four years. The successor has to raise it formally, which is slower, more visible and reads to everybody else as friction that did not used to exist. Same work, same competence, worse conditions, and the difference is attributed to them.
The predictable end of this is that the successor either burns out or, more often, learns the same absorption behaviour within a year. At which point the position has been fully rebuilt around a new person, the organization has concluded that the transition is over, and nothing about the underlying arrangement has changed at all.
The lesson the organization takes, and the one it misses
After a departure like this, organizations reliably reach one of two conclusions, and both of them protect the arrangement.
The first is that the leaver was exceptional and irreplaceable, which is flattering, comforting and useless. It treats a structural exposure as a fact about one person’s talent, and it implies there is nothing to be done except hope the next one is similar.
The second is a documentation project. Everything must be written down, a template is circulated, and for about a quarter it works. It fails for a reason that is easy to state and hard to accept: documentation captures the gaps anyone can currently name, and undefined work keeps being produced. Write down everything today and the position starts rebuilding tomorrow, because the routing that sends new undefined work to one person has not been touched.
What actually gets missed is the reading. The departure was a diagnostic event — the one occasion on which the organization could see which of its functions were resting on a person rather than on a design. That reading is available for perhaps a quarter and then it decays into a story about a difficult period. Very few organizations write down what halted, and it costs almost nothing to do so.
If you are the one leaving
You are in an unusual position for about four weeks: the only person who can see the shape of what you hold, with more leverage than you will ever have again, and no remaining downside to describing it plainly.
Two things are worth doing, and neither is the handover document you have already been asked for. The first is a list of what has no owner once you go — not tasks, but the categories of question that will arrive at somebody and should not arrive at whoever is nearest. Ten lines is enough. Give it to a manager rather than to the successor, because the successor cannot act on it and the manager can.
The second is to say the reasoning out loud for the three or four arrangements that would look arbitrary to a stranger. Those are the ones a successor will eventually undo, in good faith, at the exact moment nobody remembers why they were there.
If you are the one covering
The instinct is to absorb, because things are visibly falling and you are able to catch them. Absorbing is how the last person got there, and the first six weeks after a departure is when the position is at its most transferable, because everything is being handled unusually anyway.
Send it up instead, on the day it arrives. Not a complaint and not a request for help — one line to whoever is covering the management of it, saying that this reached you, that nobody owns it, and asking where it should go. You will be told to just handle it perhaps half the time, and the other half is the half that matters, because each of those is a decision made while somebody is paying attention. A gap that gets named during a crisis gets filled; the same gap named in a quiet month is a preference.
Before it comes to that
The cheapest version of all of this is to take the reading before anybody resigns, and it does not start with a list of your tasks — the organization has those already. What it has never written down is which of its functions currently rest on a person rather than on a design. That is answerable in an afternoon by anyone senior enough to ask it, and it costs nothing, where the other way of finding out costs a quarter and somebody’s notice period.
For what has already accumulated, the Responsibility Reclaim System™ sets out a structured way to move what has drifted to you back where it belongs. It is built for someone prepared to have the ownership conversation and it supplies the words for it, which is not the same as a way around it. Related reading, if you want the argument from the other end: work breaks when you step away for a reason and you are not overworked, you are over-relied on.
Every organization eventually runs this test. Almost all of them run it by accident, on the day somebody hands in their notice and nobody in the room thinks to be worried yet.
— HCOS