I read the phrase “corporate lobotomy” on a TikTok post and was completely enamored.
I had never heard the term before. The person talking about it was just cryptic enough that I stopped scrolling and went to figure out what the hell it meant. What I found was a concept describing something I had been watching happen in organizations for most of my career.
The term isn’t mine. Ray Bernard used “corporate lobotomy” to describe the loss of organizational knowledge when people who hold specialized knowledge and important connections are removed from the organization. There is also a significant body of research on knowledge loss when employees leave, particularly when the knowledge they carry isn’t easily documented or transferred.
But when I read about it, I immediately thought about Sharon/Bob.
Sharon/Bob isn’t necessarily a manager, a subject-matter expert, or someone leadership would identify as critical talent. They might be a coordinator, an analyst, a project manager, a designer, a developer. Their title doesn’t tell you much about their organizational value.
Sharon/Bob is the person who has accumulated operational knowledge that isn’t reflected in their job description.
They know how the work actually gets done. They know which report is wrong, which system doesn’t work the way everyone thinks it does, who to call when something breaks, and which exception nobody documented because they’ve been dealing with it for years.
They have become part of the operating system without anyone formally recognizing them as one of its components.
And most of the time, they’ve already told somebody.
Something doesn’t work, so Sharon/Bob finds a way around it. The work still has to get done, so they create a workaround. They do it long enough that nobody remembers they’re working around a problem. The workaround becomes part of the process.
Research on organizational workarounds describes this as a response to the gap between the process an organization designed and the work people actually have to perform. Sometimes the workaround is evidence that the underlying process was never working in the first place.
I’ve been Sharon/Bob.
I’ve left organizations and offered to remain available because I knew there were things nobody else knew. I’ve been on vacation and had former coworkers calling and texting because they needed me to explain something. At one point I told them, “Guys, I gave you guys SOPs.”
The manual wasn’t enough.
Eventually, I blocked the number.
I’ve also been laid off and hired back as a contractor months later because the organization didn’t have enough people who understood the system.
I’ve been on the other side, too. I’ve been the person brought in to extract knowledge from people like Sharon/Bob.
That’s where things get complicated.
Sometimes they’re happy to help. Sometimes they know exactly what’s happening and are trying to get as much knowledge out of their heads as possible before they leave. Sometimes they’re angry and simply don’t want to play anymore.
When you start digging, you often find that the person management thought was difficult had been compensating for problems for years.
They had raised the issue. Nothing changed. So they figured out how to keep the work moving.
That can go on for years.
Then the organization looks at Sharon/Bob and sees someone who has been there for fifteen years and costs too much money.
What it sees is their salary.
What it doesn’t see is everything they’ve been carrying.
So Sharon/Bob leaves.
That’s when everyone starts finding out what they actually did.
Someone can’t run the report. Someone doesn’t understand why a particular step exists. Someone discovers that the “standard” procedure hasn’t been followed in years because it doesn’t work.
I used to tell people they had ninety days to complain and blame somebody after a person left.
That wasn’t a scientific threshold. It was an observation from being inside these organizations. The first few months after someone leaves are when everyone discovers what that person was actually doing. It’s painful, but most of the time you can recover the knowledge. You figure things out. You rebuild the process. Eventually, the organization stabilizes.
Until somebody needs Sharon/Bob.
Usually, that call comes from someone who liked them.
“Hey, do you remember how you used to do this?”
Now the organization is relying on the goodwill of someone it no longer employs.
If Sharon/Bob wants to help, they help.
If they don’t, they don’t want to do shit.
And honestly, I understand that.
You made a decision that you didn’t need them. Now you’re asking them to help reconstruct the thing you decided you didn’t need.
This is why I don’t think a manual is the same thing as knowledge transfer. A manual can tell you what Sharon/Bob was supposed to do. It may not tell you what they actually did when the system didn’t work, which exceptions they knew to watch for, or why they stopped following the official process in the first place.
That’s the problem with institutional knowledge. We talk about it as though it sits somewhere inside the organization waiting to be retrieved.
Sometimes it doesn’t.
Sometimes it’s sitting in Sharon/Bob’s head.
Sometimes it’s the relationship they have with someone in another department. Sometimes it’s ten years of experience behind a decision nobody thought to document because, at the time, it was obvious.
And sometimes you don’t find out that knowledge exists until the person carrying it is gone.
That’s the corporate lobotomy I know.
It isn’t the only way an organization can lobotomize itself. I’ve seen other versions, and there are other stories worth telling. But this is one I’ve seen enough times to recognize almost immediately.
The answer isn’t to keep every longtime employee forever because they might know something important. It’s to recognize that operational dependency is a risk, even when the person creating it isn’t considered critical talent.
Before you eliminate Sharon/Bob, find out what the organization is actually losing.
Not the job description. Not the title. Not the SOP.
The knowledge.
What do they know that nobody else knows? What problems have they been quietly compensating for? What would stop working if they weren’t there to make it work?
If you don’t know the answers, you’re not ready to make the decision.
Because once Sharon/Bob leaves, you may discover that you didn’t eliminate a position.
You eliminated part of the operating system.
Take the problem seriously before the workaround becomes the job.