The Tacit Knowledge Problem

Every organization has that guy. The one who knows everything, builds everything, fixes everything, and writes down absolutely nothing.

He's fast. He's reliable. And he is a ticking time bomb.

What Is Tacit Knowledge?

Tacit knowledge is any information that exists inside your organization but has never been recorded in company documentation. It lives in three places: embedded in the implicit structure of your processes, encoded in group dynamics, and held as individual expertise.

It's the layer beneath the official process, the "how things actually get done" that no wiki page captures. In a one-person company, individual and institutional knowledge overlap completely. But as the team grows and specializes, the gap between what people know and what the organization knows widens fast.

Three Levels Where It Hides

Institutional rhythm. Every organization has an unwritten cadence. When are things actually due versus the stated deadline? Who do you talk to first? Is the due date a hard line, or does everyone finish in half the allotted time? This rhythm is rarely articulated. It is almost always implicit. And when a new hire disrupts it, everyone feels it.

Departmental process. This is the navigation layer. The knowledge of which Confluence page is current, which version of the Word template is actually in use, and how a Slack thread from six months ago connects to the Excel checklist that nobody updated. The translation between these documents is itself tacit knowledge, and it is where the real operational gold sits.

Individual expertise. The senior analyst who knows which corners cause problems, which shortcuts are safe, and which report template is the right one. This person produces at twice the speed of anyone else because they have internalized what others still look up. Requiring them to document everything would cut their output in half.

Why People Resist Documenting

There is a real trade-off between speed and documentation. The fastest workers are usually the worst documenters, not because they are lazy, but because writing everything down would make them significantly less productive.

Beyond speed, there is job security. Not writing it down makes a person harder to replace, and some people know that. Others simply cannot articulate what they do. Their expertise has become automatic, like muscle memory. Asking them to explain it is like asking a cyclist to describe balance.

Then there is the writing problem itself. In any organization, roughly 20% of people produce 80% of the documentation. Timmy and Susie always write the docs. So why would Jared, Terry, or Carl bother? And some people do take notes, but in personal sketchpads the organization never sees.

The Cost of the Gap

Replacing an undocumented employee costs multiples of what a documented one does. New hires get a Teams note with twelve unfiltered links and are expected to figure it out. But the real risk is catastrophic loss.

I once worked at an organization where a senior analyst, call him John, handled the entire reporting architecture for a major marketing campaign. He worked until two in the morning finishing reports. One day, John went home with a headache. The next day, his wife called his manager to say he had passed away. His reporting relationships, his client context, his campaign analytics. All of it died with him. A piece of the organization simply ceased to exist.

At another company, a leader I will call Lindsay had been embedded for over a decade. He managed analytics, data engineering, and developer integration. He knew why a tracking migration would be costly, how to satisfy international privacy requirements alongside domestic tracking, and how to account for every pipeline change coming down the road. If Lindsay were hit by a bus tomorrow, the damage would dwarf John's scenario. Lindsay held institutional knowledge, interpersonal relationships, and cross-departmental process understanding that no document could reconstruct.

What Now?

Your organization is full of Johns and Lindsays. The question is not whether you will lose one. It is whether you will be ready when you do. In Part 2, we will cover how to actually extract what people know before it walks out the door.