Capturing tacit knowledge in regulated organizations
Tacit knowledge is the reasoning an experienced person applies without writing it down: which exceptions are defensible, which escalation path works, what a regulator actually meant. It is captured not by asking people to document more, but by reconstructing the decision record they already generated and modelling the constraints behind each decision.
Why documentation programs fail
Handover documents describe process, not judgment. A departing risk officer can write down the approval workflow in an afternoon. What they cannot write down is the pattern recognition built from nine hundred credit files, because they do not experience it as a rule. Asking harder does not surface it.
What a decision episode captures instead
Assembled across thousands of episodes, this produces something documentation never does: a model of how this organization decides, distinct from how the industry decides.
- The situation as it was presented, including what was unknown at the time.
- The constraint set: policy, regulation, capital position, client commitment.
- The decision taken and the named person accountable for it.
- The outcome, where it is known, and any subsequent correction.
Governance is not optional here
Reconstructing internal decision history creates a system that is, by design, opinionated about precedent. In a regulated environment that must be governed: role scoping so answers reflect the right accountability, live policy checks so superseded precedent is not repeated, and human approval before anything consequential is acted on.
WisdomTwin.ai deploys the Institutional Judgment Layer on infrastructure the customer controls, with policy checks, required human approval and full audit lineage on every answer.
Frequently asked questions
What is tacit knowledge in a business context?
The judgment an experienced person applies without articulating it, such as which exceptions are defensible or which escalation path actually resolves an issue. It is not present in process documentation.
Why do knowledge transfer programs fail to capture it?
They ask people to document process, which is explicit. Tacit judgment is pattern recognition the holder does not experience as a rule, so it cannot be written down on request.
How can tacit knowledge be captured with AI?
By reconstructing the decision record the organization already produced into structured decision episodes, capturing the constraints and accountability behind each one rather than asking for new documentation.
What triggers a tacit knowledge project?
Usually senior attrition in a role with concentrated judgment, a succession gap, or an examiner question about how a class of decisions has historically been made.