Institutional Knowledge
Definition
Knowledge that belongs to the organisation rather than to individuals: captured as a by-product of doing the work, searchable when the next deal needs it, and intact after any single person leaves. The deliberate opposite of tribal knowledge — and the property that lets a new SE ramp on the team's accumulated history instead of shadowing whoever has spare time.
Three properties, and all three are required
It has to be captured without a separate documentation task, findable by someone who does not know it exists, and independent of any individual's memory. Miss the first and nothing gets written. Miss the second and it accumulates unread. Miss the third and you have tribal knowledge with a wiki in front of it.
The test is a resignation
When a senior SE leaves, what does the team lose? If the answer includes which objection that account raises every year, why the architecture was chosen, and which competitor claim turned out to be false, that knowledge was never institutional — regardless of how much content exists in the repository.
Capture beats documentation
Asking busy engineers to write things down afterwards has been tried everywhere and works nowhere. The only durable approach is making the record a by-product of doing the deal.
Related terms
- Tribal Knowledge
- Sales Knowledge Base
- Knowledge Reuse Rate
- SE Ramp Time
- PreSales Operations
- Win-Loss Analysis
Further reading
- What Actually Walks Out the Door When a Senior SE Leaves
- Knowledge Base vs Answer Library: Where Should Answers Live?
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