How to make succession planning handle tacit knowledge
Standard succession planning transfers ownership and authority and hopes the knowledge follows by proximity — the plan's habitual blind spot. The fix is structural: give knowledge its own workstream with its own owner and budget, separate the tacit from the explicit (they need different instruments), elicit the tacit through case-based capture, and give the successor query access to the result before his first day.
Before you start
This guide assumes a succession is planned or plausible within a few years. The earlier the knowledge workstream starts, the better it works — capture quality drops sharply once the predecessor mentally checks out or the deal stress takes over.
The steps
Step 1 — Give knowledge its own workstream
Add a fourth track to the succession plan next to legal, financial and governance: knowledge, with an owner, a budget and milestones. If it lives inside another track it will be deprioritized by whichever advisor bills there.
Pitfall: Making it an HR agenda item. HR owns process, not content; the workstream needs someone accountable for what is actually captured.
Step 2 — Split tacit from explicit
Inventory the departing person's knowledge and sort it: explicit (procedures, structures, contacts — documents will do) versus tacit (judgment, relationships, history — needs elicitation). Budget accordingly: the tacit half costs most of the effort and carries most of the value.
Pitfall: One 'handover document' for everything. It captures the explicit layer and silently drops the rest — the plan looks complete and isn't. See what tacit knowledge is.
Step 3 — Elicit the tacit through cases
Run structured sessions on real decisions: walk through the last major client negotiation, the last crisis, the last pricing call — asking why at every fork. Record reasoning as spoken; structure later. Meetings the predecessor still runs are capture material too.
Pitfall: Asking for principles instead of cases ('what's your management philosophy?'). Principles produce platitudes; cases produce knowledge.
Step 4 — Arm the successor before day one
Give the successor query access to the captured base before the handover: his questions are the best test of coverage, and every gap found pre-handover is fixable. Asking the base costs him nothing; asking the predecessor costs political capital he needs elsewhere.
Pitfall: Timing knowledge transfer to start at the handover. That is when the predecessor's availability and authority to answer both start decaying.
Step 5 — Keep the channel open after handover
Agree the post-succession arrangement in writing while goodwill is high: how the base is maintained, whether follow-up sessions happen, who arbitrates when the successor's new course contradicts captured reasoning (answer: the successor — the base informs, it doesn't govern).
Pitfall: Letting 'he'll stay involved' float undefined. Undefined involvement becomes either interference or absence, usually both in sequence.
How MentX compresses this
MentX is a personality-aware knowledge base: it captures the knowledge of a company's key person — from meetings and a guided intake track — into a living, temporal knowledge graph with full source attribution. MentX is the knowledge workstream as a service: the intake track elicits the tacit layer case by case (step 3, led by us), meeting ingest captures the predecessor's live reasoning, and the successor converses with the result through DigiME — before day one, with full source attribution, no political capital spent. The veto rights and intake agreement settle step 5's governance up front.
Checklist
- Knowledge workstream in the succession plan — owner, budget, milestones
- Inventory split: explicit → documents, tacit → elicitation
- Case-based capture sessions running while the predecessor is fully active
- Successor querying the base before the handover date
- Post-succession maintenance and arbitration agreed in writing
