We have a wiki. Isn't that our knowledge base?
A wiki is a place where knowledge could go; a personality-aware knowledge base is a process that goes and gets it. That is the whole difference. Wikis work where writing is part of the culture and the knowledge is shared across many hands. They plateau exactly where the concentration risk lives: the busiest expert writes the least, the deepest knowledge is the hardest to write down, and what does get written decays without an owner.
What a company wiki actually delivers
Wikis and intranets earn their keep: team documentation, how-tos, onboarding pages, project notes — cheap, familiar, searchable, collectively owned. A wiki is enough if your knowledge is distributed across many contributors, mostly explicit, and your culture actually maintains it (the last condition is the rare one). For collaborative, living team documentation, a wiki remains the right tool — nothing below argues against having one.
What a personality-aware knowledge base actually delivers
A personality-aware knowledge base inverts the effort model: instead of waiting for the expert to write, it captures from what he already does — meetings, plus a guided intake track led by an interviewer. 'Personality-aware' is the second inversion: the base preserves how this person reasons, not just conclusions, which is what makes the answers usable judgment rather than orphaned facts. And every statement carries source and date, where wiki pages carry 'last edited 2021 by someone who has left'.
A company wiki vs a personality-aware knowledge base: at a glance
| Criterion | A company wiki | A personality-aware knowledge base |
|---|---|---|
| Effort model | Expert must write | Expert speaks; capture is the system's job |
| Coverage of the busiest expert | Lowest — no time to write | Highest — his meetings are the source |
| Tacit knowledge | Structurally absent | Targeted by the guided intake |
| Freshness | Decays; orphan pages accumulate | Living — fed by ongoing meetings |
| Trust | Page history, unclear authority | Full source attribution, dated, per statement |
| Reasoning style | Whoever wrote the page | The expert's own |
| Best at | Distributed team documentation | One key person's critical knowledge |
When you need both
A fictional case every IT manager will recognize: an engineering firm relaunches its wiki with templates, a taxonomy and a kickoff lunch. Six months later the graphs tell the story — forty contributors the first month, four by month six, and the pages about the topics that actually worried management (the senior engineer's domain) were stubs. He wasn't unwilling; he was busy, and writing is the most expensive way to extract knowledge from a busy expert. The wiki stayed — genuinely useful for project documentation — and the senior's knowledge needed a different instrument: one that captures from speech and meetings. Wiki for the many, capture program for the critical few.
Where MentX fits
MentX is that instrument: a personality-aware knowledge base that captures the key person's knowledge — from meetings and a guided intake track — into a living, temporal knowledge graph with full source attribution. The wiki keeps doing team documentation; MentX covers the one head the wiki never captured. How the capture works →
