Tribal Knowledge
Definition
Critical know-how that lives only in individual heads: edge-case product behaviour, competitor-specific positioning, compliance nuance, the political read on a recurring objection. Invisible while its holders stay, lost the day they leave. Converting it into institutional knowledge — captured, searchable, compounding — is the core knowledge-ops problem in presales.
What it actually consists of
Not product documentation. It is the accumulated set of answers to questions that have already been asked: which requirement wording hides a gap, which competitor claim collapses under one follow-up, what a particular customer's architecture team objected to two years ago, which internal expert actually knows the answer.
Why it reads as a personnel event but is a systems one
When a senior engineer leaves, the visible loss is relationships. The larger loss is that every question they used to answer in ninety seconds now takes a day, and some are never answered correctly again. Ramp time for the replacement is long for the same reason — the knowledge exists only conversationally.
Why knowledge bases fail here
Every previous attempt failed the same way: a repository that required filing discipline nobody had. Capture has to come from the work itself — the RFP being analysed, the questionnaire being answered — or it is empty within a quarter.
The cheap first step
Date the answers. Every reusable answer gets a last-verified date and an owner; anything past its date is flagged rather than silently reused. That is a spreadsheet-level change with an outsized effect on both speed and accuracy.
Related terms
- Institutional Knowledge
- Sales Knowledge Base
- Knowledge Reuse Rate
- SE Ramp Time
- Sales Engineer
- Security Questionnaire
Further reading
See how this works on a real deal
WinIQ turns RFPs, competitor data and account research into deal-specific output your SEs can defend.
Request a Demo