Tags:
New hire, week three. She has asked the same question to four different people and gotten three different answers. Not because anyone lied to her. Because nobody actually knows the real process. They know their version of it.
This is what onboarding looks like in a business that runs on tribal knowledge. It is not a training problem. It is a structural one.
The Problem Has a Name
Call it institutional improvisation. It is what happens when the way things actually get done lives in people’s heads and habits rather than in anything documented. Every employee builds their own working version of the process, based on who trained them, what they personally experienced, and what they figured out along the way. None of these versions are written down. None of them are identical. All of them are confidently delivered as the correct answer.
A logistics company in Bengaluru discovered this when their most experienced dispatch coordinator went on a month of medical leave. The two people who covered for him had each learned the role from him directly, at different points in his own learning curve. Neither version matched. Decisions that used to take minutes started taking hours, because every choice required someone to figure out, from scratch, what the right call actually was.
Why It Happens
Nobody sets out to build a business on tribal knowledge. It happens by accumulation. Someone joins, learns the job from whoever is available, and starts doing it their way. The business is small enough that this works. The people who know things are still around. Questions get answered quickly because the answer is two desks away.
Then the business grows. More people join. The original few who held the knowledge are now managing instead of doing, or have moved on entirely. The new hires are learning from the second generation of people who learned informally themselves. Each generation loses a little precision. The process drifts further from whatever the original logic was, and closer to whatever has been collectively agreed upon through repetition rather than design.
Documentation always feels like something to do later. There is always something more urgent. And the people who know the most are usually the busiest people in the business, which means they have the least time to write any of it down.
What It Looks Like in Practice
A specialty food manufacturer in Coimbatore had a quality control process that existed entirely in the head of one long-serving line supervisor. New hires learned it by shadowing her for two weeks. When she retired after eleven years, three different former trainees were each running a slightly different version of her process. Two products failed a client audit within four months. The investigation traced the failure back to a quality check that had quietly dropped out of the process somewhere between the original supervisor and the third generation of people doing her old job.
A customer support team at a SaaS company in Pune had no written escalation matrix. Each support agent had learned, through experience, which issues to escalate and to whom. New agents took roughly six weeks to build the same instinct, during which time customer complaints were either escalated unnecessarily or sat unescalated for too long. The company had built a product. It had never built the operating manual for supporting it.
A construction project management firm in Ahmedabad ran site approvals through a process that existed only as a set of unwritten norms among the senior project managers. A new project manager, hired specifically to bring more structure, spent his first three months simply trying to understand what the actual approval process was, since nobody could describe it consistently and nothing was written down. He was hired to fix a system that nobody could first agree existed in a single, describable form.
Different industries. Different functions. The same underlying gap. The knowledge was real. It was just never made transferable.
The Cost Nobody Calculates
Time to productivity for a new hire is rarely measured against what it would be with proper documentation. Most businesses accept that a new employee takes a few months to become fully effective, without asking how much of that timeline is the natural learning curve and how much of it is the cost of having to reconstruct undocumented knowledge from scratch, often from multiple conflicting sources.
There is also a quality cost. When the process exists only in people’s heads, it drifts. Each retelling loses something or adds something. The version running in the business today is rarely identical to the version that worked well enough to get the business to where it is. Nobody notices the drift until something fails in a way that traces back to a step that quietly disappeared three generations of employees ago.
The retention cost is real too. Skilled employees who inherit undocumented, inconsistent processes often spend their early months frustrated rather than productive. Some of that frustration translates directly into early attrition, which restarts the entire cycle with the next hire.
None of these costs appear as a line item called tribal knowledge. They appear as slower onboarding, inconsistent quality, and replaceable-seeming roles that turn out to be far harder to fill than anyone expected, because the real requirement was never written down in the first place.
The First Step
Pick one process. Not all of them. Just one that a new hire struggled with recently.
Sit down with the person who actually knows it best and write down what they do, in the order they do it, including the parts that feel too obvious to mention. Those obvious parts are usually exactly the ones that get lost between generations of employees.
This is not a knowledge management project. It is a single afternoon, applied to one process, that tells you how much tribal knowledge your business is actually running on.
Industry Context
This pattern is sharpest in operationally dense businesses where process knowledge is the actual product. Manufacturing, where quality and safety procedures often live in the experience of senior floor staff rather than in written form. Logistics and supply chain, where dispatch and exception handling depend heavily on individual judgment built over years. Professional services, where client handling norms are absorbed by watching senior colleagues rather than taught explicitly.
It is also acute in businesses experiencing leadership or team transitions. A business preparing for its founder to step back, or a team absorbing a wave of senior departures, is often discovering for the first time how much of what worked was never actually written anywhere. That discovery usually arrives at the worst possible moment, mid-transition, when there is the least slack to absorb the gap.
The knowledge that built the business is real and valuable. The risk is not that it exists. The risk is that it only exists in one form: memory.
A business that cannot describe its own processes without a specific person in the room has not built an operation. It has built a dependency.
