A great deal of “tacit knowledge” is merely knowledge that has been too expensive to observe, record, and model. AI changes all three costs.
But codification will not always mean writing a textbook. It may mean a model can reliably reproduce a skill from demonstrations while being unable to state a compact rule for it. The knowledge becomes operationally explicit—copyable, testable, and teachable—even if it remains difficult to verbalize.
Likely candidates
Debugging intuition
Experienced engineers often say things like:
- “This looks like a race condition.”
- “The database probably isn’t the real bottleneck.”
- “That metric is too clean; the instrumentation is broken.”
- “This failure smells like stale state.”
Today this intuition is scattered across incident histories, terminal sessions, dashboards, code navigation, and memories of prior failures. An AI observing thousands of complete debugging trajectories could learn:
- Which hypotheses experts consider first
- Which signals they distrust
- What diagnostic experiment best separates competing explanations
- When to stop investigating locally and inspect another layer
- Which apparently irrelevant details predict a particular failure
The result could be a debugging policy trained from traces, not merely a searchable collection of postmortems.
Code-review taste
Much of code review consists of judgments that style guides do not capture:
- An abstraction is premature.
- An API invites misuse.
- A change is locally elegant but increases system-wide complexity.
- A test passes without testing the important behavior.
- A dependency will become an operational liability.
- The code is technically correct but will be incomprehensible during an incident.
Review comments, later revisions, bugs, rollbacks, and maintenance costs could turn some of this “taste” into learned evaluation systems. Organizations may train models on their own history of accepted and rejected changes.
Architectural judgment
Architecture is often taught as patterns, while expert practice depends on context: team size, expected growth, failure costs, migration constraints, and organizational politics.
If design decisions can be linked to years of outcomes, systems may learn more concrete rules about:
- When a monolith should remain a monolith
- Which boundaries stay stable as requirements change
- When eventual consistency becomes intolerable
- Which services generate disproportionate coordination costs
- When to buy, build, fork, or abandon a component
Architecture decision records could evolve from prose justifications into executable predictions and continuously updated decision models.
Operating legacy systems
A surprising amount of institutional value lives in statements like:
“Ask Maria before changing that job. It says it runs nightly, but finance manually restarts it on quarter-end unless the European feed is late.”
AI can extract this from email, tickets, screen recordings, meetings, system traces, and observed exceptions. It can construct a living process model showing what the organization actually does rather than what the documentation says.
This may be one of the largest near-term opportunities: turning organizational folklore into queryable, testable operational knowledge.
Product taste and user understanding
Product managers and designers make judgments such as:
- Users request a feature but actually need reassurance or control.
- A workflow has one step too many.
- A metric improvement is caused by confusion rather than value.
- A polished interface feels untrustworthy in this domain.
- Enterprise buyers and daily users have conflicting needs.
Models with access to interviews, support calls, behavioral traces, experiments, and subsequent retention can codify part of this judgment. They may identify recurring gaps between what users say, what they do, and what improves their outcomes.
That will not eliminate taste, but yesterday’s exceptional taste can become tomorrow’s baseline product heuristic.
Expert search strategies
Researchers, lawyers, intelligence analysts, and engineers often know where to look before they know the answer. Their expertise includes:
- Choosing useful search terms
- Recognizing authoritative sources
- Following unusual citation chains
- Knowing when absence of evidence is informative
- Detecting that several sources derive from the same original claim
- Abandoning a tempting but unproductive line of inquiry
Capturing full research trajectories—including failed searches—could codify these strategies much better than finished reports do. The dead ends are often the most informative training data.
Scientific experimental craft
Laboratory protocols omit many small actions:
- How vigorously to mix something
- What a healthy cell culture looks like
- Whether an instrument’s noise is normal
- When a sample has been contaminated
- How room conditions affect a procedure
- When to deviate from the nominal protocol
Continuous multimodal recording, instrument telemetry, robotic execution, and outcome data can make such details measurable. A model may discover that a supposedly irrelevant hand motion, delay, temperature fluctuation, or visual feature predicts success.
“Lab hands” could partly become a sensor-rich control policy.
Medical pattern recognition
Clinicians acquire sensitivity to gait, voice, skin appearance, patient demeanor, symptom combinations, and whether “something seems off.” Historically, only a thin textual summary entered the medical record.
Multimodal longitudinal data could make some of this knowledge reproducible:
- Subtle changes in speech or movement
- Patterns across repeated visits
- Which apparent symptoms deserve urgent escalation
- How presentation differs across populations
- Which questions elicit diagnostically useful answers
This is technically plausible but institutionally difficult because of privacy, liability, distribution shifts, and the danger of encoding past clinical bias.
Skilled trades and maintenance
Technicians recognize abnormal sounds, vibration, resistance, smell, wear patterns, and combinations of minor symptoms. With wearable cameras, microphones, force sensors, and repair outcomes, models could learn:
- Which noise indicates which mechanical fault
- How much force should be applied
- Which repair-manual steps can usually be skipped—and when they cannot
- How to diagnose a machine from indirect signs
- Which temporary fixes are safe
Augmented-reality guidance or robots could then reproduce parts of a senior technician’s skill. The physical dexterity may remain difficult even after the diagnostic knowledge is codified.
Negotiation and sales
Strong practitioners notice:
- Who actually has authority
- Whether an objection is literal or face-saving
- When silence indicates resistance
- Which issue matters emotionally rather than financially
- Whether pressing for a decision will close or kill the deal
- How an organization really buys something
Conversation histories combined with deal outcomes can expose some of these patterns. AI might make high-quality call preparation, objection diagnosis, stakeholder mapping, and follow-up strategy widely available.
However, once both parties use such systems, behavior changes. Codifying a social tactic can destroy its effectiveness.
Management and organizational diagnosis
Experienced managers detect:
- A project is “green” only because nobody wants to report bad news.
- Two teams have incompatible incentives.
- A high performer is becoming a coordination bottleneck.
- A recurring technical dispute is really a dispute over status or ownership.
- A deadline is fictional but socially useful.
- A meeting’s formal decision is not the actual decision.
Analysis of communication patterns, project histories, surveys, calendars, and outcomes could codify some of this. It would also create an extraordinary surveillance risk. The ability to infer organizational reality does not imply that employers should collect everything required to do so.
Teaching and coaching
Good teachers adjust explanations based on tiny signals:
- The learner can repeat the words but lacks the concept.
- A mistake reflects a specific misconception.
- Another example will help more than another definition.
- The student needs a hint rather than an answer.
- Confusion is productive, or it is about to become discouragement.
Longitudinal tutoring systems can test these judgments at enormous scale. Pedagogical skill could increasingly be represented as a policy for selecting the next question, example, analogy, or intervention for a particular learner.
Writing and editing
Editors often cannot fully formalize why a passage feels wrong:
- The argument arrives before the reader is prepared for it.
- A sentence is clear locally but confusing in context.
- The author is hiding uncertainty behind abstraction.
- A detail is interesting but damages the piece’s shape.
- The prose imitates a style without understanding its purpose.
Models trained not just on final texts but on drafts, edits, reader responses, and editor–author discussions could make more of editorial judgment explicit. Generic polish will be cheap; coherent selection and structure may take longer to codify.
Security intuition
Security engineers develop an adversarial habit of mind:
- “What happens if these two harmless features interact?”
- “Which component is implicitly trusted?”
- “Can the attacker control the parser boundary?”
- “This permission will eventually be reused outside its original context.”
- “The logged event is not evidence that the intended action occurred.”
Attack traces, red-team sessions, exploit development, and incident outcomes can train systems to reproduce parts of this thinking. The same codification also benefits attackers, making this a particularly adversarial domain.
How tacit knowledge becomes codified
The general pipeline is likely to be:
-
Capture the process, not just its output.
Record screens, tool calls, alternatives considered, questions asked, physical actions, and moments of uncertainty.
-
Connect actions to delayed outcomes.
A design decision may look good today and create failures two years later. Without outcome linkage, the model learns style rather than judgment.
-
Collect contrasts and exceptions.
“Why did you do A here but B in the apparently similar case?” is often more revealing than asking for a general rule.
-
Intervene experimentally.
Observational data confuses habit with necessity. Controlled variation reveals which details actually matter.
-
Build better sensors and environments.
Smell, force, hesitation, visual context, social relationships, and hidden system state are absent from most current datasets.
-
Turn the learned behavior into tests or policies.
The result might be a checklist, simulator, evaluator, recommendation model, or autonomous agent.
-
Continuously audit it against reality.
Once people know the rule, they adapt to it; environments change, measurements become targets, and the codification decays.
What is less likely to become fully codified
Some knowledge is tacit not because recording is expensive, but because it is inseparable from participation:
- Knowing what a particular person will tolerate
- Navigating status and trust in a changing group
- Acting under moral responsibility
- Choosing goals when values conflict
- Functioning in genuinely novel situations
- Skills dependent on a specific body or physical environment
- Judgment whose correctness is only defined through social acceptance
Even these can be assisted, but they resist becoming stable universal rules.
There is also a moving frontier. Once today’s tacit skill is automated, work shifts toward the exceptions that were not captured, the goals the system should pursue, and the question of whether its apparent success deserves trust. Tacit knowledge will not disappear; it will migrate to the boundary between the model and a changing world.
For a software engineer, the practical implication is to seek access to rich feedback loops. Do not merely become good at producing code. Learn domains where you can observe decisions, consequences, exceptions, and failures. That puts you in a position either to codify valuable tacit knowledge yourself or to evaluate systems that claim to have done so.