Why a Procedures Manual Won’t Capture What the Founder Knows

The procedures manual may be excellent. It tells the team how to open the day, price the standard order, approve a return, inspect the work, and close the books. It reduces variation and keeps ordinary knowledge from depending on memory.

Then a perfectly acceptable order arrives from one particular customer and the founder refuses it. The successor sees the policy, the available capacity, and the margin. Everything points toward yes.

The missing line is not a step. It is ten years of history: an old payment pattern, an unusual promise, the way demand from this account changes just before trouble, and a threshold the founder learned through an expensive mistake.

A novice sees the facts that are easiest to name. An experienced person may see a pattern, anomaly, or absence that has become meaningful through repetition. They often cannot explain the difference until a real case brings the cues back into view.

Research on expert-to-novice transfer has found that experts can provide more abstract instructions and omit concrete task information novices need. Expertise makes performance efficient; it can also make explanation unexpectedly difficult.[Bothered by Abstraction: The Effect of Expertise on Knowledge Transfer and Subsequent Novice Performance]

This is why “write down everything you know before Friday” produces long documents with surprisingly little of the judgment everyone was trying to save.

Ask for the last time the ordinary rule was wrong. What first looked routine? When did the founder’s reading change? Which detail mattered? What did they expect to happen next? Which acceptable option did they reject?

The purpose is not to collect war stories. It is to recover distinctions another person can use: this customer request resembles the usual case except for one signal; this production number is safe at one point in the cycle and worrying at another; this employee conflict needs patience until one phrase appears.

Family-business research involving 860 firms has argued that firm-specific tacit knowledge can make insiders sensible successor choices under particular conditions. That does not prove a specific capture method, but it does support taking company-specific knowledge seriously rather than treating every role as interchangeable.[Promoting Family: A Contingency Model of Family Business Succession]

A blank page asks the founder to summarize thirty years. A difficult incident gives the conversation a place, a sequence, and a consequence.

Reconstruct the event from the first cue to the final result. Use emails, numbers, drawings, calendar entries, or photographs where they help. Pause at the points where the interpretation changed. Ask what the founder knew then—not what everyone knows after the ending.

The Critical Decision Method and related Cognitive Task Analysis approaches use incident-centered questioning to examine cues, expectations, goals, alternatives, and decision points in demanding work. Skagway draws from that lineage without claiming that an interview can download a person’s mind.[Critical decision method for eliciting knowledge][Applied cognitive task analysis (ACTA): a practitioner's toolkit for understanding cognitive task demands]

One case rarely reveals the boundary. Put it beside a similar case in which the founder made a different decision. What changed? Timing, reversibility, customer history, capacity, trust, downside, or the quality of the evidence?

The contrast can expose a threshold the founder no longer realizes they use. Below it, the team can proceed. Above it, more evidence is required. Under one relationship history, a concession protects trust. Under another, the same concession teaches the wrong lesson.

These distinctions belong beside the procedure. They show the successor when to follow the route, when to slow down, and when the map itself needs revision.

A founder’s decision was made under particular conditions. Preserving it as “always do this” can make old wisdom dangerous. The successor needs the reason, uncertainty, and conditions around the choice—not a museum of answers.

Label illustrative cases. Preserve disagreement. Note what the outcome did and did not prove. Ask which signal would have changed the decision. This gives the next leader room to recognize the pattern without being required to repeat the predecessor’s call.

The strongest transfer creates a better question in the successor’s mind at the right moment. When that judgment still has only one holder, Does Owner Dependency Lower the Value of My Business? follows the question into transferability and economic risk. The aim here remains narrower: preserve enough of the reasoning for another person to recognize when the ordinary rule has ended.

Procedures keep ordinary work from being reinvented. Decision cases preserve some of the history, cues, exceptions, and thresholds needed when ordinary work bends. Relationships and live practice carry what neither document can hold alone.

The unanswered question is the one most companies discover late: what does this person know that nobody knows to ask? The first clues are already present in the decisions people bring them, the exceptions they catch, and the moments everyone waits for their reading.

See What Goes With Them to follow those traces before choosing how much of the work needs The Map.