Learn

How to capture an expert's knowledge before it walks out the door.

Capture the expert's decisions, not just documents: the replies, reviews and calls where the judgment actually lives, with the expert's written consent. Then check the result against questions the expert already answered, and let the expert own it, correct it and decide who may ask.

Sources checked

The problem: tenure is shorter, and judgment is unwritten.

Research by eGain, which sells knowledge software, with Deloitte finds that average job tenure "has declined from 4.6 to 3.9 years over the past decade", while baby boomers "average more than eight years of tenure." Each departure takes judgment that was never written down.

Exit interviews and handover documents catch what an expert thinks to write. Most of the judgment lives elsewhere: in replies to colleagues, in reviews, in decisions made under pressure.

The OECD's AI incident monitor records companies in China building AI replicas of former employees from their work files and messages, "sometimes without explicit consent". An employment-law firm asks when such a replica stops being simply the employer's store of knowledge, and advises settling ownership and use after employment in contracts and policies.

So start where those questions end: the expert agrees in writing, chooses the sources, owns what is built, and can revoke the firm's access.

The method: decisions, roles, sources.

Read the expert's own words: sent replies, review comments, recorded decisions and corrections. Turn every named person and company into a role before anything is stored, and keep no message bodies. Extract each decision or rule as a node that cites the message it came from and the dates it applies.

Colleagues then ask, and every answer cites the past answer it rests on. A question with no precedent goes to the expert, or is marked unanswered rather than guessed.

What to measure.

Hold back questions the expert already answered, replay them, and count how often the captured knowledge would have answered the same way, as a share of the expert's own consistency when asked again. Report it per kind of question, because a single average hides where the gaps are.

Watch three more things: how often a question has no precedent, how quickly colleagues get an answer, and how often the expert corrects one. The corrections are the most useful: each is a rule that was never written down.

Side by side

Three ways to keep an expert's know-how.

DimensionExit interviews and handover documentsA knowledge baseAn expert-owned engram
What it capturesWhat the expert thinks to write, onceWhat people write for it on purposeDecisions and rules from the expert's own replies and reviews
Who writes itThe expert, on the way outWhoever has timeThe expert, in the course of the work, with Traide extracting it
How it stays currentIt does notWhen someone updates itFrom every new answer and correction the expert makes
How you know it is rightYou do notBy reading itReplayed against questions the expert already answered

Categories, not products: what each approach does by design.

Choosing

When each one is enough.

  • A handover document is enough when the knowledge is a procedure that can be written down once.

  • A knowledge base is enough when the answers are stable facts that many people need.

  • An expert-owned engram is what you need when the answers are judgment calls only the expert makes the way the expert makes them.

Questions

What people ask first.

Can a firm capture an expert's knowledge without asking?
Duplikate will not: it builds only from a person's own record, with that person's written consent. Whether a firm may do it some other way is a legal question for where it operates.
Who owns what is captured?
With Duplikate, the expert. The firm uses it under a written licence the expert signs, scoped to sources, colleagues and topics, and the expert can revoke it, export it or delete it.
What if the expert has already left?
Then what can be built from the record that remains, and with whose agreement, is a question for the firm, the former employee and their lawyers. Duplikate builds only with the expert's own consent.
How long does it take?
It depends on how much of the expert's own writing exists and which sources the expert chooses. We quote it in writing before a build, and do not publish a typical figure until enough builds stand behind one.
Does it replace the expert?
No. It answers from the past, cites what it rests on, and sends anything new to the expert. It keeps the expert in the loop, and out of every repeated question.
Talk to us

Talk to us about a pilot.

You'll talk to a senior engineer, not a sales rep, and leave knowing what your engram would be built from and how it would be measured.