Seven Seconds
Every plank of the ship gets replaced, so what makes it the same company is memory. We have started filling our companies with workers who have none.
On the 27th of March, 1985, a virus found its way into the brain of a British musician named Clive Wearing and took his memory apart. He was, until that week, a conductor and scholar of early music, an acknowledged expert at the height of his career with BBC Radio 3. The virus was herpes simplex, the same ordinary one behind cold sores, which in rare cases climbs the nerves into the brain. In his case it burned out the hippocampus, the small structure that turns a passing moment into something a person can keep. What it left behind was a man who could no longer hold on to the present.
Clive Wearing's memory now lasts somewhere between seven and thirty seconds. Not his memory of his childhood, though much of that is gone too, but his memory of the present. A thought arrives, holds for a few seconds, and then there is nothing behind it, and the next moment begins with no thread connecting it to the last. He keeps a diary, and the diary is hard to read. It is close to the same entry, over and over, hundreds of times: each one insisting that he has, this very minute, woken up or come to consciousness for the very first time. The doctors who studied him were careful about this: the conviction is not simply the amnesia talking but a delusion in its own right, a separate and unshakeable belief that he has only this second come to, and it has held for years. Each entry is written a few minutes after the one above it, and each earlier line is crossed out, because by the time he writes the new one he has no memory of writing the old and takes it for the note of someone who was not yet properly awake.
He is not diminished as a person. He can still sit at a piano and play something complex and beautiful, sight-read a score, lift his hands and conduct a choir. His wife, Deborah, walks into the room and he greets her with the joy of a man reunited after years apart, and he does this every time, because every time, to him, it has been years. She set all of this down in a memoir: the music he keeps, and the greetings that never once wear thin. The skills survived. Much of what he knew survived. What did not survive is the thread. The thing that lets one moment of a life know that it belongs to the same life as the moment before it.
The company you work for lives closer to this than you would like. And we have just begun filling it with workers who arrive, by default, with no memory of us at all.
The ship that is entirely new and still yours
Start with an old puzzle. A ship goes out to sea for many years, and over those years every plank, every nail, every sail is replaced one at a time as it wears out, until not one original piece remains. Is it the same ship? People have argued about it for two thousand years and never quite settled it, and the reason it will not settle is that the puzzle is not really about ships. It is about you. Most of what you are made of has rebuilt itself many times since then. Your gut lining is a few days old, your skin renews within weeks, your blood cells within months. Not all of it goes: the neurons reading this sentence are about as old as you are. But so much of the material has been swapped out and replaced that, by the plain physical accounting, you share far less with the child in your oldest photograph than it feels like you should. And yet you do not doubt for a second that you are the same person.
There is a good answer for why. What makes you the same person as that child is not the matter, which is long gone, but the memory. An unbroken chain of remembering links you back to them, this moment holding the one before it, which held the one before that, all the way down. Break the chain and something strange happens, which is exactly what happened to Clive Wearing. The body stays continuous. The person does not. Each few seconds, someone new wakes up in his chair, delighted, certain it is the first time.
Now hold a company up to the same light. Who works there turns over completely. The engineers who built the core of the product leave. The people who were in the room for the decision that shaped your entire pricing model move on, retire, get poached. The code gets rewritten many times over. Same name over the door. Different planks, every one of them.
Something has to make it the same company, and by the argument above only one thing can: an unbroken chain of memory. Not memory of what the code says, which is written down plainly, the code is the body and the body persists. Memory of why. Why the pricing works the odd way it works. Why that integration is built the strange way it is built and must not be quietly simplified. Why you walked away from an entire category of customer three years ago, after it nearly took the company down with it. You could object that a company's identity is really its mission, or its brand, or its customers. But a mission whose reasons no one remembers is a slogan, and a brand no one can explain is a logo, and both stay alive only on the same underlying thread. The reasons are the thread. They are what lets the company of next year know that it is the same company as this one, and not a group of capable strangers who happen to have inherited the building.
The company that wakes up new
Here is the trouble. Almost no company actually keeps that thread. The reasons live in people, and people leave. They live in a Slack channel that scrolls away, a call nobody wrote up, a constraint that was obvious to the four people who lived through it and was never once obvious to anyone who came after. So every few years, as the people who held the reasons walk out with them, the company does a slow version of the thing Clive Wearing does every few seconds. It wakes up. It looks around at a product and a codebase it can no longer fully explain, and it begins, brightly, from scratch. It reopens a question that was settled and paid for two years ago. It rebuilds a thing that was deliberately torn out. It re-makes, with real confidence, a mistake it has already made and already learned from, because the learning left when the person who learned it did. Now I am awake, it writes across a fresh planning doc, for the first time.
You could survive this, roughly, for a long time, because it was slow. The thread frayed only at the speed people quit, and that gave the memory a chance to pass hand to hand, from the person leaving to the person staying, in the overlap before the door closed. The system leaked, but slowly enough to bail.
Then we handed the work to agents. An AI coding agent is, in the exact sense we have been circling, an amnesiac by construction. It arrives with enormous skill and no autobiography. It has never sat in one of your meetings. It did not live through the incident. It picks up a task, reads the code in front of it, and does something fluent and reasonable. Out of the box it arrives with no memory of your company, and unless something has put your hard-won reasons in front of it, it works from the code and its own defaults. Whatever it does pick up, it holds for the length of a session, and then, like Clive Wearing, it wakes up new.
That would be harmless if agents did a sliver of the work. They are quickly coming to do a great deal of it. And the more of your building is staffed by workers who cannot hold the thread, the faster the thread comes apart, because now the forgetting is no longer paced by resignations. It runs at the speed code gets written, which is to say all day, faster than any person could catch and correct. The company was already a shaky amnesiac getting by on the goodwill of a few people who still remembered why. We have started handing their work to brilliant strangers who wake up new for every task and fall asleep the moment it is done.
Memory is the thing that shows up on its own
What it takes for a company to stay itself is not a wiki. Everyone already has a wiki, and the wiki is where reasons go to die, because it is a place you have to remember to visit, and the entire problem is that nobody remembers. The thread has to live somewhere outside any one person's head, so that it does not leave when they do. And it has to arrive on its own, at the moment someone reaches the exact fork the reason governs, whether that someone is a new hire in their first week or an agent that has never heard your company's name. Memory you have to go hunting for is not really memory. It is storage. Memory is the thing that shows up, unasked, precisely when it bears on what you are about to do.
Brief is a company's memory of itself. It holds the reasons, each decision with the why underneath it, in one place that does not resign, and it draws on them in the moments that matter: checking a new choice against the ones already made, the way a continuous self does not casually contradict its own past; handing the one relevant piece of context to whoever is doing the work, person or agent, at the moment they are doing it; letting a newcomer inherit the thread on day one instead of spending a year absorbing it, or never quite getting it at all. Those look like four separate jobs. They are one job seen from four sides, and the job is keeping a company the same company while every person and every agent inside it is quietly swapped out.
Clive Wearing cannot be handed his thread back. The structure that would hold it is gone, and no notebook can stand in for the thing itself, which is the quiet tragedy his diary records so exactly. A company is luckier than that. Its thread was never lost to damage. It was only ever left unwritten, kept nowhere that could outlast the people who carried it in their heads. That is a fixable problem, and it is worth fixing now, in the same moment we are moving more and more of the work onto minds that cannot carry it at all.
Your company will still have its name over the door in five years. The harder question is the one Clive Wearing writes, and crosses out, and writes again. When it wakes up that morning, will it be the same company that went to sleep the night before, or a bright and confident stranger, awake, it is quite sure, for the very first time?
Frequently asked questions
Why do companies keep losing institutional knowledge? Because the knowledge that matters most, the reasons behind decisions, lives in people's heads and in informal channels, not in the code or the docs. The artifacts a team produces stay behind when they leave, but the reasoning that produced them walks out the door with them. So a company keeps the what and loses the why, and after enough turnover nobody can fully explain why the product is shaped the way it is.
Do AI coding agents remember my company's decisions? No. An AI agent has broad general skill but no memory of your specific company. It has not attended your meetings or lived through your incidents, and by default it retains nothing about you from one session to the next. It works from the code in front of it and from reasonable defaults, which means it will confidently re-make choices your team already settled, unless the reasons are put in front of it at the moment of the work.
What actually keeps a company's identity consistent as employees turn over? Continuity of memory. A company whose staff turns over and whose code is rewritten many times is still the same company only if an unbroken record of its decisions and the reasons behind them survives the turnover. Without that thread, each new generation re-derives the product from scratch, and the company effectively resets, keeping its name while losing its accumulated judgment.
How do you preserve institutional memory when you use AI agents? Keep the reasons behind your decisions in a shared, durable layer that both people and agents read at the moment of work, rather than in wikis or individual memories that have to be sought out. A product navigator like Brief does this: it stores each decision with its rationale and surfaces the relevant one to whoever, or whatever, is making a change, so the company's memory arrives on its own instead of leaving with the people who held it.
← Back to Blog