Institutional knowledge is the accumulated context, history, judgment, and lore that lives inside an organization. It includes why decisions were made, why some approaches were tried and abandoned, who knows what, and the unwritten conventions that govern how things actually work.
Institutional knowledge has two forms: explicit (written, queryable, durable) and tacit (held in people's heads). The explicit form survives turnover; the tacit form leaves with the person. Most organizations underinvest in converting the second form into the first.
In distributed teams, the question is not whether tacit knowledge exists but whether enough of it gets externalized that the team can survive a senior departure without losing major context.
Why Institutional knowledge Matters for Distributed Teams
Institutional knowledge is one of the highest-value organizational assets and one of the most poorly managed. It compounds when invested in and evaporates when ignored.
Frequently Asked Questions
What is institutional knowledge?
Institutional knowledge is the accumulated context, history, judgment, and lore inside an organization. It includes why decisions were made and the unwritten conventions that govern how things actually work. It exists in both explicit and tacit forms.
Related Terms
Tribal knowledge
Tribal knowledge is the unwritten know-how that circulates among long-tenured team members — how things actually work, w...
Read definitionShadow knowledge
Shadow knowledge is operational knowledge held informally inside an organization — in private notes, DMs, individual hea...
Read definitionDecision documentation
Decision documentation is the written record of decisions made by a team, including the question, the options considered...
Read definitionDecision log
A decision log is a chronological record of decisions made by a team. Each entry captures the question that was decided,...
Read definitionGet the vocabulary that makes distributed teams work
One email per week on async governance. No spam.
See institutional knowledge in action.
StandIn is built around these concepts. Engineers publish declared state before going offline. The next shift starts with full context.