Capturing Tacit Know-How From Experienced Process Owners

01Choose a decision where experience changes the result

Ask the process owner to identify the decisions that novices escalate repeatedly or that have produced avoidable rework. Prioritize tasks with ambiguity, changing context or significant consequence. Simple routine actions are usually better covered by an ordinary work instruction; complex judgment deserves a structured capture exercise.

Use recent examples to define the boundary. What conditions were observed? What alternatives were considered? Why was one option rejected? What evidence would have changed the outcome? Capturing the decision environment is more useful than asking the expert for a retrospective list of personal tips.

Capture objective. Define the ability you want to transfer: detecting an abnormal sound, deciding when to quarantine a batch, interpreting inconsistent customer evidence or escalating a supplier deviation. The scope determines whether a video, decision tree or coached trial is appropriate.

Technical context: ISO 30401:2018 (with amendments) — Knowledge management systems — Requirements is one verified source for the concepts discussed here.

02Observe work instead of relying only on recollection

Arrange a safe observation of routine and exceptional work. Have the expert narrate the cues they inspect, the checks they repeat and their reasons for stopping or continuing. Avoid interrupting a safety-critical task to collect material; use replay, simulation or debrief when observation would alter the work.

Compare the expert’s explanation with approved instructions and actual records. A skilled person may have developed a legitimate local adaptation, but an undocumented shortcut might breach customer, safety or regulatory obligations. The capture team must distinguish valuable experience from an unauthorized workaround.

Observation prompt. Ask what an inexperienced colleague would notice too late, which exception is easy to misclassify and what the expert would never decide without another person. The answers expose tacit thresholds and escalation signals.

Using specific artifacts changes the interview. Place two inspection images, maintenance trend logs or approved exception records beside each other and ask the expert to identify the distinguishing cue. Their first explanation may describe an intuition; subsequent questions can uncover measurable observations and a rule about uncertainty. The capture team should not assume that every implicit pattern can be converted into a fixed threshold.

03Use contrasting cases to reveal judgment

Collect a pair of similar-looking cases that demand different decisions, such as two surface defects with different root causes. Ask the expert to explain the discriminating evidence. A single success story encourages imitation without teaching the underlying criterion. Contrast develops conditional reasoning: if the signal is absent or the machine variant differs, the recommended action changes.

Record assumptions about customer specification, machine capability, personnel authorization and the date of the information. Experienced judgment can be correct within one equipment configuration and unsafe on another. An explicit scope protects the receiving team from applying a memorable anecdote as a universal rule.

Interview technique. Use real artifacts such as approved photos, traceable inspection readings or historic change notes. The expert’s narrative should explain the artifact, not replace the technical evidence behind the accepted decision.

It is important to preserve the conditions under which the expert learned the lesson. A manufacturing veteran may have experienced a particular raw material, software revision or supplier behavior that no longer exists. Record the historic context and then ask whether the principle still holds. Technical review may decide to retain the story for background reasoning while refusing to approve it as a current operational instruction.

04Turn an interview into usable material

Synthesize the capture into a concise set of recognizable triggers, questions, evidence checks, decision limits and escalation paths. An annotated process example or troubleshooting card may be more useful than a lengthy transcript. Retain the complete interview only when it serves a defined retention, confidentiality or audit need.

Let the subject expert verify the factual draft, but seek independent technical approval when the content changes operational practice. The expert being interviewed should not be the sole author, verifier and approver of a high-consequence control if independent review is reasonably available.

Artifact design. Include enough detail for the next user to find the situation, determine applicability and understand what action is authorized. Leave ambiguous observations clearly labeled as unverified rather than turning uncertain recollections into instructions.

Expert involvement should end in an approved operational home for the insight. A technical owner can place validated thresholds in an instruction, rare exception examples in a controlled knowledge card and open questions in an investigation log. This prevents the full interview transcript from becoming an unofficial alternative procedure. The expert’s contribution remains traceable without making the repository dependent on that person forever.

05Transfer through demonstration and teach-back

Have the receiving employee apply the captured insight to a different example. Observe whether they identify the correct warning signal and limits, seek help at the right point and retain evidence of the decision. Teach-back exposes gaps between an expert’s vocabulary and the concepts the next person actually understands.

A training certificate or signed acknowledgement shows participation, not mastery of tacit judgment. Use task-based competence assessment where the consequence warrants it, with a qualified supervisor determining readiness. A role may be able to perform routine work while remaining unauthorized for exceptional release decisions.

Assessment boundary. Design test cases that remain within safe simulated conditions; do not manufacture dangerous faults to prove competence. Where observation is impractical, review previous decisions and discuss a realistic hypothetical exception.

06Protect sensitive knowledge and attribution

Review confidentiality, intellectual property, personal data and customer restrictions before recording audio, photographs or supplier processes. Explain the intended audience and retention of recordings to participants. The organization should preserve process knowledge without exposing information it is not entitled to redistribute.

Maintain provenance: contributor role, source case, revision, approval and withdrawal conditions. Avoid presenting an opinion as externally verified fact. If an expert disputes the accepted method, route the conflict to engineering or governance instead of publishing both directions without interpretation.

Control check. Keep approved decision aid separate from raw notes and recordings. Restrict raw materials as needed while giving authorized operators direct access to the controlled guidance they must use.

Video can communicate motion and sequence better than text, but it may conceal judgment. Pair a short demonstration with annotated prompts explaining which signal matters and what invalidates the technique. The receiver should then examine a second case and articulate the decision without the expert’s guidance. Where the explanation depends on highly variable circumstances, coaching may remain a necessary long-term control.

07Make capture a normal part of knowledge renewal

Schedule capture before planned retirement or role transfer, but do not wait for departure. Use corrective actions, complex customer issues and introduction of new equipment as triggers. The expert can explain why a new rule replaced the old one while the context is still fresh.

Review the resulting guidance when inputs change. New tooling, standards, products and customer requirements may invalidate precisely the experience that once made the expert successful. Assign an operational owner who can update or retire the item and a practical feedback path for users.

Success test. A capable alternate can reason through a new case, recognize uncertainty and invoke the right authority. The goal is not to reproduce the expert’s personal style; it is to preserve the organization’s ability to make reliable decisions.

Develop a capability transfer record that describes the task, observed practice, assessor, conditions, limits and follow-up. A signature that content was received is weak evidence compared with successful independent interpretation. When the receiving employee cannot explain the stop criterion, keep the relevant activity under supervision. Treat this as an operating authorization decision, not a criticism of the learner.

Closing Perspective

Tacit know-how becomes organizational knowledge only when another competent person can use the insight in the correct context and demonstrate an appropriate decision.