The Reorg Resets the Clock

Category: Organisations and systems Every restructure is sold as the fix; mostly it just erases the memory that would have stopped the next failure.

A company I knew well had a problem with how it shipped orders. It had been told about the problem, in writing, more than once. The warehouse couldn’t keep up at peak, the system that was supposed to predict demand didn’t, and the people who actually packed the boxes had a list — a real, specific, unglamorous list — of the seven things that broke every December.

So they reorganised. The operations function was split into “fulfilment” and “customer logistics,” a new director was hired with a mandate to “transform the supply chain,” and the old structure, with all its tired arguments and its embarrassing list of seven things, was dissolved into an org chart with cleaner lines and more hopeful names. There was a town hall. There were slides with arrows on them. There was, genuinely, a sense of relief — the feeling you get when a stuck thing finally moves.

What happened to the list of seven things? Nobody could quite say. The man who had written it had been moved to a different team and was busy learning his new remit. The director he’d written it for had left during the reshuffle. The new director was, reasonably, starting from first principles — building his own picture, running his own discovery, forming his own view. He was not going to inherit a list of grievances from a structure that no longer existed; that would have been backward-looking, and he had been hired to look forward.

So the following December, the warehouse couldn’t keep up at peak, the demand system didn’t predict demand, and roughly five of the original seven things broke again. They were investigated with great energy, as if they were new. A working group was formed. Lessons, everyone agreed, would be learned.

It is worth being precise about what happened, because no one did anything wrong. Nobody buried the list. Nobody decided to forget the lessons. The reorganisation was defensible at every step — the function was too big, the structure was messy, a fresh leader with a clear mandate is often exactly what a stuck thing needs. And yet the sum of those defensible decisions was that a year of hard-won, specifically catalogued knowledge evaporated, and the organisation paid full price, again, for a lesson it had already bought.

The Principle

A restructure is sold as the fix for a problem, but its quieter effect is to erase accountability for everything that came before. Old commitments lose their owners, half-learned lessons lose their context, and unfinished problems get a clean slate — so the same failures are free to recur under new names. The reorg looks like change while resetting the very memory that would have prevented the next one.

The trick is that reorganisation feels like progress in a way that fixing the actual problem does not. Fixing the actual problem is slow, specific, and unglamorous — it looks like a list of seven boring things. Reorganising is fast, visible, and sweeping. You can announce it. You can draw it. It produces an immediate sensation of movement, and that sensation is easily mistaken for the thing it is standing in for.

And because the new structure has no past, it also has no debts. Whatever was owed under the old chart — the promises made, the problems acknowledged, the lessons paid for — does not automatically carry across. The clock goes back to zero, and zero feels clean.

Why It Is Inevitable

It is inevitable because of where commitments and lessons actually live. They do not live in the org chart. They live in people, in relationships, and in the specific context of who-said-what-to-whom about which problem. A reorganisation, by design, breaks exactly those things. It moves the people, severs the relationships, and dissolves the context. The structure survives the change on paper; the memory attached to the old structure does not.

It compounds because of who arrives and who leaves. A restructure almost always brings in a new leader, or moves an old one, and a new leader has every incentive to start fresh. Inheriting a predecessor’s unfinished problems means inheriting blame for them; building your own picture means the clock starts on your watch, with your baseline, against which you can only improve. There is no reward for a new director who says “my predecessor already diagnosed this correctly and I’m just going to finish their list.” There is enormous reward for one who “transforms” things. So the rational move, individually, is to treat the past as someone else’s country.

It compounds again because the people who held the lessons get scattered. The packer who wrote the list of seven things is not consulted, because consulting him would require knowing he wrote it, which would require the new structure to have read the records of the old one, which — busy building its own picture — it does not. The knowledge is still in the building. It just no longer has a path to the decision.

And it is helped along by relief. A reorganisation arrives at a moment of frustration, when something has been stuck for a long time. The change releases that frustration, and the release is genuinely pleasant. Nobody, in that moment of relief, wants to be the person pointing out that the old problems haven’t been solved — they’ve only been reshuffled. That would spoil the feeling. So the feeling wins, and the unsolved problems travel quietly into the new structure, unlabelled.

None of this requires cynicism, which is exactly why it is so reliable. The leaders ordering the reorg usually believe in it. The new director genuinely intends to fix things. Everyone involved would tell you, sincerely, that they are learning from the past. The system produces amnesia anyway, because the act of restructuring is itself the act of cutting the threads along which memory travels.

How It Shows Up

• A long-standing problem is met with a structural change — a new function, a new leader, new reporting lines — rather than a fix aimed at the problem itself
• The same failures recur after each restructure, but are investigated each time as if they were new
• “We’re building a fresh picture” becomes the polite reason not to read what the last team already wrote
• Commitments made under the old structure quietly lapse, with no one feeling responsible for the lapse
• The people who diagnosed the problem the first time are moved, scattered, or gone, and are never asked
• Post-mortems, root-cause documents, and lessons-learned files exist — but belong to a structure that no longer does, so no current owner reads them
• Each new leader’s tenure resets the baseline, so improvement is always measured from their arrival, never from the original problem
• The reorg is announced as “transformation”; the actual broken thing is mentioned, if at all, in the past tense

Why It Causes Damage

The damage is not the reorganisation itself. Structures do go stale, and sometimes a genuine redesign is exactly right. The damage is the repeated, expensive forgetting that rides along with it.

The first cost is that you pay for the same lessons more than once. A lesson learned is supposed to be a durable asset — you take the pain, you bank the knowledge, and you don’t take that particular pain again. The reorg writes the asset off. The seven things that broke are diagnosed afresh, the working group rediscovers what the last working group already knew, and the organisation buys back, at full price, knowledge it already owned. Done often enough, this is a tax on every restructure: not just the cost of the change, but the cost of re-learning everything the change erased.

The second cost is that accountability becomes unenforceable. A commitment only means something if someone can be held to it later — and “later” is precisely what the reorg removes. The person who promised it is gone; the person who would have chased it has a new remit; the structure it was made in no longer exists. So commitments stop being load-bearing. People learn, without anyone saying it, that any promise survives only until the next restructure, which is never far off. Why invest in finishing something hard when a reshuffle will dissolve the obligation anyway? The reorg doesn’t just erase old accountability — it teaches everyone that accountability is temporary, and that lesson outlasts the chart.

The third cost is the most insidious: the reorg lets you look like you are changing while changing nothing real. It produces all the signals of action — the announcement, the new names, the sense of movement — and consumes the appetite for action that might otherwise have gone toward fixing the actual problem. Having “done something big,” everyone is tired, and the boring list of seven things looks even less appealing than before. The energy that should have fixed the problem was spent looking like it was fixing the problem. So the underlying fault not only survives the reorg; it is protected by it, hidden behind the visible drama of the restructure, free to recur the moment peak season comes round again.

And because each recurrence arrives under a new name, in a new structure, to a new leader, it is genuinely hard for anyone to see the pattern. From the inside, it doesn’t look like the same failure for the fourth time. It looks like a new challenge for a new team. The org chart has changed so many times that the through-line — the actual unsolved problem, patiently waiting — is invisible to everyone except, perhaps, the packer who wrote the original list, and nobody is asking him.

There is a final cost that is harder to put on a slide. People are not stupid. After they have watched two or three reorganisations come and go without the thing in front of them getting any better, they stop believing in change altogether. The next restructure is announced, and instead of relief there is a quiet, practised cynicism — heads nod in the town hall, and then everyone goes back to their desks and waits for it to blow over. The reorg’s most reliable long-term product is not transformation. It is an organisation that has learned, from experience, that transformation is theatre. And once people believe that, even the reorganisation that would have worked arrives to a room that has already decided it won’t.

How To Counter It

You cannot counter this by refusing to reorganise — sometimes you genuinely should. You counter it by refusing to let the reorganisation erase the memory. The structure can change; the ledger of unfinished problems and unkept commitments must not be allowed to change with it.

• Make the problem ledger outlive the structure. Keep a register of known, unsolved problems and open commitments that is owned by the organisation, not by any function or leader, and that is explicitly handed across every restructure. The first job of any new leader is to read it — not to rediscover it. If your lessons-learned documents belong to teams that get dissolved, your lessons get dissolved too.
• Separate the restructure from the fix, out loud. When someone proposes reorganising to solve a problem, ask the awkward question: which specific failure does this new box prevent, and how? If the answer is vague, you are buying the feeling of change, not the change. A reorg is a tool for the wrong-shape-of-organisation problem. It is not a fix for the warehouse-can’t-cope problem, and pretending otherwise just buries the second one.
• Make new leaders inherit, not reset. Reward the incoming leader who finishes the predecessor’s diagnosis over the one who starts a fresh one. Build the handover so that the baseline carries across — measure improvement from the original problem, not from the new arrival’s first day. Take away the incentive to declare year zero.
• Ask who held the knowledge, and find them. Before any “fresh discovery,” locate the people who diagnosed the problem last time and ask them what they found. They are almost always still in the building. The reorg scattered them; it did not delete them. The cheapest investigation is the one someone already did.
• Track recurrence across names. Keep a record of failures that is indexed to the problem, not to the structure of the day, so you can see when the “new” issue is the old one wearing a new title. If December breaks every December, that fact should survive every reorg between Decembers.
• Be honest about the relief. Notice the pleasant feeling a reorganisation produces, and treat it as a warning rather than a verdict. The sense that a stuck thing has finally moved is exactly the sensation that lets unsolved problems slip through unexamined. The moment everyone feels relieved is the moment to ask what, concretely, has actually been fixed.

What Good Looks Like

Good looks like a restructure that changes the boxes without losing the memory.

It looks like an organisation where the list of seven things survives the reorg intact, handed to the new director on day one with the words “these are still open — your predecessor knew about them, and so do you now.” Where a new leader’s first instinct is to read what the last team learned rather than to launch a discovery that rediscovers it. Where commitments made under the old chart are explicitly carried, re-owned, or formally closed — never simply orphaned by the change.

It looks like a place that can tell the difference between we have the wrong structure and we have an unsolved problem, and reaches for a reorganisation only for the first. Where the question “which specific failure does this prevent?” is asked before the slides are made, and answered concretely, or the reorg doesn’t happen. Where the same December failure cannot quietly recur for a fourth time, because someone is tracking the problem across every name it has ever worn, and the pattern is visible even when the chart is not.

It does not look like an organisation that never restructures. It looks like one that restructures without amnesia — that treats hard-won lessons as durable assets to be carried, not debts to be written off, and that knows the clock on its real problems keeps running no matter how many times the org chart is redrawn. The healthy organisation changes its shape and keeps its memory. The unhealthy one changes its shape to lose its memory, and calls the forgetting progress.

A Reflective Question

Think of the last restructure you lived through. Which problems were genuinely fixed by it — and which ones simply changed their names, lost their owners, and are quietly waiting to recur under the new chart?