Home/ Volume 23/ Chapter 1
Show menu button
1

Definition

One long-serving tailor at MANIAC MINDZ held a specific, subtle quality judgment: knowing exactly when a certain fabric was "ready" for a particular technique. It existed only in that tailor's experience, never written down because it had never needed to be. When that tailor was unexpectedly unavailable for several weeks, orders requiring that judgment stalled completely.

Tacit knowledge

is what an experienced person knows but has never written down, a knack, a workaround, a judgment call made "by feel." Documenting it turns invisible expertise into a Knowledge Base anyone can consult, before it walks out the door with the person who holds it.

Why did nobody else feel confident making that same call? Because the tailor's judgment had never been broken down into anything another person could learn, it lived entirely as a feeling, not a set of signs someone could check for themselves. Knowledge that only exists in one person's experience is knowledge the business doesn't actually have, it's just borrowing it, one day at a time.

In One Sentence

This is Volume 02's whole argument at its most urgent: the moment a skilled employee resigns, retires, or becomes unavailable, everything they knew but never documented is gone with them. This chapter is about catching that knowledge on paper (or video) while it's still available to capture.

2

Signs Knowledge Is Dangerously Tacit

Tacit knowledge held in one person's head converted into a knowledge base, training manuals, videos, FAQs, and a mistake log
Warning SignWhat It Means
"Ask [specific person]" is the standard answerNobody else can currently answer that question
A task only one person has ever performedNo documented process exists to fall back on
A judgment call made "by feel"The reasoning behind it has never been put into words
A workaround for a known problem, never written downThe fix disappears the day the person who found it leaves
Memory Trick

If the answer to "how do we do this?" is a person's name instead of a document, that knowledge is one resignation away from disappearing.

3

Capturing It

A Knowledge Base entry doesn't need to be polished, it needs to exist. Interview the person who knows the task, write down the steps and the why behind each judgment call, and have someone unfamiliar with the task try to follow it, exactly like Volume 02's Two-Week Test.

4

Example Story: The Judgment Call Nobody Else Could Make

Here's the full version of the fabric-ready story from the start of this chapter.

One long-serving tailor at MANIAC MINDZ held a specific, subtle quality judgment: knowing exactly when a certain fabric was "ready" for a particular technique. It existed only in that tailor's experience, never written down because it had never needed to be. When that tailor was unexpectedly unavailable for several weeks, orders requiring that judgment stalled completely, with nobody else confident enough to make the call.

The tailor hadn't been hiding anything. The knowledge had simply never left their head. A single afternoon spent documenting the specific, concrete signs that tailor actually looked for, turning "I just know" into a written checklist, meant the next unexpected absence caused no disruption at all.

5

Across Industries

Every trade has its own version of a judgment call that lives in one person's experience and nowhere else.

BusinessTacit Knowledge Worth Documenting
Golden Crust BakeryKnowing dough is "ready" by feel and smell, not just a timer
Rapid Auto WorksDiagnosing an unusual engine sound before running the formal tests
Precision Print & PressJudging when a colour proof "looks right" beyond the numeric values
6

Common Mistakes

Common Mistake #1: Assuming Expertise Will Always Be Available

The exact risk in the example story, until it suddenly isn't.

Common Mistake #2: Waiting for a Resignation to Start Documenting

By then, the person with the knowledge may already be gone, or too rushed to properly explain it.

Common Mistake #3: Documenting the Steps but Not the Reasoning

"Do X" without "because Y" leaves a follower unable to adapt when circumstances differ slightly.

7

Quiz Yourself

Quiz 1
What's the clearest sign that important knowledge is dangerously tacit?
When the standard answer to "how do we do this?" is a specific person's name rather than a document, that knowledge is one absence or resignation away from disappearing.
Quiz 2
Why does documenting the reasoning behind a judgment call matter as much as documenting the steps?
Because steps alone don't transfer the judgment itself, writing down why a decision is made lets someone else adapt correctly when circumstances differ slightly from the exact documented example.
8

Practice Exercise

Identify one task in your business that only one person currently knows how to do well. Interview them using the Knowledge Base Entry Template this week.

9

Quick Summary

Quick Summary

  • Tacit knowledge, a knack, a workaround, a judgment call, disappears the moment its holder becomes unavailable.
  • The clearest warning sign: "ask [specific person]" as the standard answer to a real business question.
  • Document both the steps and the reasoning behind them, not steps alone.