How to onboard a successor using the knowledge base
A knowledge base changes what onboarding is: instead of reconstructing context through months of asking around, the successor queries thirty years of reasoning from day one. The method: give access immediately, let his own questions drive the tour, build the query-first habit, track what the base can't answer as a capture backlog, and let his decisions extend the graph — the base is his to grow, not a museum of his predecessor.
Before you start
This guide assumes a captured knowledge base exists (see the capture guide) and a successor is starting. It works for external hires and internal promotions alike — the internal candidate overestimates what he already knows, which step 2 corrects quickly.
The steps
Step 1 — Open the base on day one
Access to the Knowledge Space is part of the welcome package, with a one-hour guided tour: which domains are covered, how deep, how attribution works, where the known gaps are. Honest framing of coverage prevents both blind trust and premature dismissal.
Pitfall: Positioning the base as 'documentation to read'. It is not a reading assignment; it is a colleague to question. The habit forms in week one or not at all.
Step 2 — Make his questions the curriculum
Have the successor keep a running list of everything he wonders — from strategy to 'why does this client get net-60'. Every question goes to the base first. His list, not a generic program, is the onboarding curriculum: it targets exactly his gaps.
Pitfall: A fixed reading path through the base. The successor's actual confusion is a better index than anyone's guess at it.
Step 3 — Install query-first, verify-with-humans
The working rule: ask the base, then verify what matters with people. This keeps humans in the loop for judgment while sparing them the hundred context questions. Sourced answers make the verification cheap — he checks the origin, not the whole claim.
Pitfall: Letting the base replace conversations entirely. The team's trust is built in the verifying conversations; skipping them onboards the knowledge but not the person.
Step 4 — Track the unanswerables as a capture backlog
Every question the base can't answer well is logged. Weekly, that log becomes the capture agenda: follow-up intake with the predecessor (if agreed), or capture from whoever else holds the answer. The successor is, for a few months, the best gap-detector the company will ever have.
Pitfall: Treating gaps as base failures. A gap found is the system working — it turns an invisible unknown into a scheduled capture.
Step 5 — Let him extend the graph
From month one, the successor's own significant decisions and their reasoning join the base — his meetings can feed it like his predecessor's did. This flips the psychology: the base stops being the predecessor's monument and becomes the role's living memory, currently curated by him.
Pitfall: Freezing the base at the predecessor's last day. A frozen base decays into an archive; a growing one compounds.
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. With MentX this flow is native: DigiME is the query interface (sourced answers, no political capital), the unanswerable log feeds the Deepen track's follow-up sessions, and Connect ingests the successor's meetings so the same Knowledge Space keeps growing. The temporal graph keeps predecessor and successor reasoning distinguishable — dated, attributed, both queryable.
Checklist
- Knowledge Space access in the day-one package, with guided tour
- Successor's running question list = the curriculum
- Query-first, verify-with-humans rule agreed with the team
- Weekly capture backlog from unanswered questions
- Successor's own meetings feeding the base from month one
