Decision support: what would he weigh here?
This use case turns the expert's judgment into a sounding board: before a significant decision, the team asks the Knowledge Space how the expert reasoned in comparable cases — what he weighed, what he checked, where he drew lines. Not to outsource the decision, but to inform it. Used by managers and senior staff facing choices the departed (or busy) expert used to carry.
How companies handle this today
Today, decisions after an expert's departure run on his conclusions without his weighing: the team knows the rules he left but not when he broke them, knows the price floor but not its exceptions, knows the policy but not the cases it was built from. The result is decision-making that is either too rigid (the rule applied where he would have deviated) or too loose (the deviation made where he never would have) — and each error surfaces expensively, months later.
With a Knowledge Space
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. A managing director faces a familiar-shaped choice: a big client demands a customization the company normally declines. She asks the base how her predecessor handled comparable requests and gets three episodes: the 2018 refusal and its reasoning, the 2020 exception and what made it exceptional, the boundary he articulated in an intake session. Sources under each. She decides differently than he might have — knowingly, with the history in view rather than discovered afterwards. The decision is hers; the context is his; both are on the record.
What you would ask
“How did he decide when a custom project was worth breaking our standard terms for?”
Returns his decision pattern across captured cases: the two factors he always weighed, the client category he never bent for, and the exception with its reasons — a framework, sourced, not a verdict.
“We're considering dropping the annual maintenance visit for small clients. What would he flag?”
Returns his reasoning about the visit's hidden function — early fault detection and relationship maintenance — with the churn episode from 2017 that shaped it. The cost side the spreadsheet misses.
“What did he check before approving a supplier switch?”
Returns his verification checklist as practiced, not as documented: the reference call he always made, the trial-batch rule, the contract clause he insisted on.
What it requires from the Knowledge Space
Depth on decision reasoning: the intake track must have walked real decisions (the elicitation method — cases, forks, exceptions), not just policies. Adoption tip: anchor it to one recurring forum — 'we check the base before every pricing committee' beats a general intention; one ritual carries the habit into the rest.
