Our expert is out for months. How do we cope?
A long-term absence — illness, burnout, family leave — is the dress rehearsal nobody ordered: the knowledge is intact, but unreachable, and every question is now an ethical dilemma. Call the sick colleague or guess? Most teams do both, badly: the expert recovers worse for being half-consulted, and the company decides worse for half-guessing. A knowledge base changes the situation structurally — the knowledge stays askable while the person rests.
A concrete example: the phone that keeps buzzing
A fictional but familiar case: the technical manager of an installation firm is out with burnout — prognosis six months, doctor's orders: no work contact. Reality after three weeks: his phone buzzes daily. Every colleague apologizes, keeps it short, and calls anyway, because the alternative is a standing production line at a client. He answers, feels responsible, recovers slower. Management tightens the no-contact rule; now the team guesses instead. Two bad site decisions later, the rule quietly erodes. Everyone is doing their honest best inside a structure that only offers bad options.
What goes wrong without capture
Weeks 1–3
Goodwill phase: the team defers what can wait and batches questions. The backlog of undecidables grows.
Weeks 3–12
The dilemma phase: call and harm the recovery, or guess and harm the operation. Both happen. Quality of both recovery and decisions degrades.
Months 3–6
Workarounds calcify into habits — some wrong. If the absence extends, the company is now running a parallel, uncorrected version of the expert's playbook.
Return (or not)
Best case: the expert returns to a backlog of decisions to audit. Worst case: the absence becomes permanent, and the company discovers it has had a sudden departure in slow motion.
How MentX catches it
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. Captured beforehand, the knowledge absorbs the absence. Connect means months of the expert's meeting reasoning are already in the graph when the absence starts. Deepen has stored the exception playbook — precisely the knowledge the 2 a.m. phone calls are about. Converse replaces the dilemma: the team asks DigiME instead of the patient, gets his reasoning with sources, and the phone stays silent. If capture never happened, MentX offers a humane fallback once recovery allows: light intake sessions at the expert's pace can still be better for him than eight months of ad-hoc interruptions.
What to do this quarter
- Treat this scenario as a probability, not a hypothetical: one key person out for six months — what breaks first? That list is your intake priority.
- Start capture on the person whose absence would hurt most; illness gives no announcement.
- Agree contact rules for absences now, while nobody is absent — with the knowledge base as the first line instead of the phone.
- If an absence is running: batch the truly unavoidable questions, and consider light intake sessions only when medically cleared.
- When the expert returns: capture the workaround audit — what the team improvised is knowledge too.
