Every company runs on knowledge that was never written down. A supervisor knows which machine jams if you run it too fast. An account manager remembers why a major client insists on being invoiced a certain way. An operations lead could tell you, in thirty seconds, the three things slowing down her region and exactly how she'd fix them.
None of that information lives in a system, it lives in people. And when those people leave, get promoted, or move to another team, most of it goes with them. This is the cost of institutional knowledge loss, and most organizations only feel it once the person who held the knowledge is already gone.
A lot of this knowledge can be protected with discipline you may already have. But one type resists nearly all of those methods, and it happens to be the type that most directly affects your operating costs.
Institutional knowledge is the collective information, experience, and know-how that lives inside an organization's people, built up over time and rarely written down. It's the difference between what your process documents say happens and what your experienced employees know actually happens.
Institutional knowledge comes in three types, and each one is lost, and kept, in a different way:
For the first two types, the established methods work. If a task falls apart whenever a certain person is out, that's a procedural gap, and documentation closes it. If your teams keep relearning lessons the company already paid for, that's a historical gap, and better records close it.
But operational knowledge is where the playbook reaches its limit. Documentation and cross-training are built to preserve how the work is done, so they preserve the flaw right along with everything else. Continuous improvement practices like Kaizen events, retrospectives, and suggestion programs surface some of this knowledge when they're run well. But they tend to catch just a small portion of it, in bursts, on a schedule, and they depend on people volunteering a problem out loud.
A lot of operational knowledge still slips through, for three reasons:
Sometimes no one ever asks. Most people are hired to do a job, not to flag what's broken around them, so they do the work, notice the friction, and keep it to themselves, because reporting it was never part of the role.
Sometimes there's nowhere to put it even when they want to, because a survey asks about satisfaction, not about the invoice that takes two hours to redo.
And sometimes the reasons are more human. Raising a problem can feel like criticizing a colleague or admitting your own workaround. People are busy, and flagging something takes time they don't have. And if they've spoken up before and watched nothing change, they've learned that speaking up isn't worth the effort.
None of this means your people don't care, it just means the environment has taught them, reasonably, that staying quiet costs them less than speaking up. On top of all of it, the knowledge fades from view: a problem someone noticed in their first month becomes, by their second year, just "how things are." The friction is still there, but they've stopped seeing it.
Operational knowledge is so easy to lose because its departure doesn't look like anything. Most losses in a company announce themselves; this one doesn't.
When someone leaves or moves into a new role, their replacement learns the job as it currently runs, broken parts and all. The two-hour invoice becomes "just how we do it." The workaround becomes the standard. The work continues, nothing appears to break, and no report flags a problem, because from the outside there's nothing to see. The person who knew the process was broken and knew how to fix it is gone, and the people who inherited it never learned there was anything to question. You don't get an alert when this happens. You keep paying for it, quietly, for years.
And it doesn't take a resignation. The same knowledge can be lost inside an ordinary promotion.
Let’s look at an example.
A regional operations manager spots a scheduling change worth real money and takes it to her VP, who likes it and asks her to build the case. She does, and then the VP moves into another role. His replacement arrives with different priorities and no memory of the idea, so the manager starts over, only to have the next leader up move on before it's decided. Each handoff sends her back to the beginning, and eventually she stops trying. The fix was sound the whole way through, but it died because it never lived anywhere except in her head, so every change in leadership erased its progress. A promotion, a reorganization, or a slow approval cycle can cost you the same knowledge loss a departure does.
This is also why the loss adds up. You lose the fix and the savings it would have produced, and you lose the next problem that person might have raised, because someone who watched a good fix fade doesn't push as hard on the next one. The loss stays silent, which is why it can go unaddressed for a long time.
Some companies try to catch this on the way out, with an exit interview, but exit interviews rarely work because by the time someone is leaving they have little reason to be candid, and the problems they never got to fix tend to leave with them. What your people know is easiest to reach while they're still in the work and still care about it, not on their last day.
Retaining operational knowledge requires you to capture the problem and the fix while the person is still in the role and still engaged, and getting it onto the record while it's fresh.
Capturing it isn't the whole job. Someone still has to prioritize what comes in, decide what's worth acting on, and resource the fix. But none of that can happen if the problem was never captured in the first place, and capture is the step most companies skip.
Once you have it, what your people know stops depending on their memory to survive. When they move on, the specific problem and the proposed fix are already on the record, instead of leaving with them.
Tell Jules is built to capture the operational knowledge your people carry that rarely makes it into any document.
That knowledge is hard to keep because it doesn't come out of a form. If you ask "any concerns?" on a survey, you get "the invoice process is annoying." But the operational knowledge you actually need (that it takes two hours every week because the format stopped being compliant, and here's the change that would fix it) only comes out when someone knows to keep asking.
That's what Tell Jules does.
Tell Jules is a conversational tool that has a real, roughly ten-minute talk with the people closest to the work. It asks follow-up questions, as many as it takes, to move past the surface complaint to what's actually going on underneath, and to the fix or improvement the person would make. Because it comes pre-trained on your industry, it understands the work and speaks the language of the operation, so employees aren't explaining basics to a blank form; they're talking to something that gets it.
Then Jules turns that conversation into a written and structured report. The report lays out the problem and the proposed fix in the employee's own words, the way the person who runs the process described it. It doesn't get flattened into a summary or a satisfaction score, and it doesn't lose its specifics passing through four layers of management on the way up. The operational knowledge, what the employee saw, and what they'd do about it, arrives intact, so whoever reads it is working from the real thing rather than a secondhand version.
You also decide how it runs. In some environments anonymity gets more people to participate; in others, knowing who raised what lets the right person go deeper on it. Tell Jules works equally well either way, that's your call.
Because it lives in a written report, what your people know stops depending on one person's memory. If the manager who spotted that scheduling problem gets promoted next quarter, the problem and her proposed fix are already documented, along with a jump-start on analysis and which parts of the company would need to be part of solving it. Tell Jules doesn't run the resulting projects or make the decisions for you; it makes sure the operational knowledge your people carry is captured while it's fresh, so that turnover, promotions, and reorganizations don't quietly erase it.
This isn't AI inventing answers, it's a structured conversation that captures what a real person who does the work actually knows and puts it on the record.
The knowledge is already in your building. Your best people can see what's broken and know how to fix it right now. The question is whether you're capturing it while they're here, or waiting until it walks out the door.
We'd rather show you than sell you. Start a free pilot on one team of up to 100 people, and Tell Jules will surface what your people already know. Same method Harvest Earnings has run with clients for 30+ years
What is institutional knowledge?
The accumulated information, experience, and know-how held by an organization's people, often undocumented. It includes procedural knowledge (how work gets done), historical knowledge (why decisions were made), and operational knowledge (what employees know is broken and how they'd fix it).
Why do companies lose institutional knowledge?
Because most of it lives in people, not systems, and much of it is never asked for or recorded. When employees leave, get promoted, or change roles, their undocumented knowledge goes with them, especially operational knowledge, the specific problems and fixes that are rarely captured anywhere.
How do you stop losing institutional knowledge when employees leave?
It depends on the type. Procedural and historical knowledge are protected through documentation, SOPs, cross-training, and structured handoffs. Operational knowledge has to be captured continuously, while employees are still in the role, rather than at the exit.
What's the difference between knowledge retention and an exit interview?
An exit interview tries to capture knowledge at the moment of departure, when the employee is least motivated to share it. Knowledge retention captures what your people know continuously, while they're still in the work, so it doesn't hang on a single conversation at the end.
What kind of institutional knowledge does Tell Jules capture?
Operational knowledge, specifically the problems and improvement ideas people carry from doing the work every day — what's broken, what could be better, and the fixes they'd make. Tell Jules captures what your people know before they move on and turns it into a structured report, so it doesn't leave with them.
Discover how an operational intelligence loop can bridge the gap between frontline insights and decision-makers, enhancing your company's efficiency...
Tell Jules launches Jules, an AI voice agent that interviews employees and turns operational ideas into structured reports. Free pilots open now.
Discover how proactive employee listening enhances operational visibility, enabling teams to address issues before they escalate and improve...