Institutional knowledge is what a company knows that lives in people rather than documents: why decisions were made, which workarounds keep a process running, what each client expects. It is lost when people leave. To keep it, interview the people who hold it, write each answer as a short page, and store it where your team and your AI tools can read it.
Free: the Second Brain Starter Kit
Seven plain markdown files to set one up this week, in Obsidian or any editor, with Claude or any AI.
What is institutional knowledge?
Institutional knowledge is the collective know-how of an organization that is held by its people rather than written down: how things really get done, why past decisions were made, who to ask, and what has already been tried. It builds up over years of work and is usually invisible until the person who holds it leaves.
The meaning is in the word: it belongs to the institution, but it is stored in individuals. A process document says what the steps are. Institutional knowledge says which step everyone skips, why the second approval exists, and which supplier you call when the usual one is late.
It overlaps with tacit knowledge, the know-how people find hard to put into words, but it is wider. Plenty of institutional knowledge is easy to say out loud. Nobody has asked for it yet. That makes it the cheapest knowledge to capture once you go looking. At the scale of one person, the same idea is a second brain: what you know, written where you and your tools can find it. Our guide to building an AI second brain walks through that setup, and the team version follows the same steps.
What are examples of institutional knowledge?
Common examples: why a price, policy or vendor was chosen; the workaround that keeps a broken process running; which clients need extra care and why; the history of a product decision; who actually approves things; and the lessons from projects that failed. Each one is something a new hire can only learn by asking someone.
A quick test for any team: list the questions a new hire asked in their first month. Every question that got a spoken answer instead of a link is institutional knowledge. In a marketing team the usual ones are the real brand voice rules (not the ones in the old PDF), which claims legal pushed back on, and what was tried last year and why it stopped.
For a founder, most of it sits in one head: why the offer is priced the way it is, what customers said on calls, which hires did not work out. Our guide to a second brain for founders covers getting that written down while the company is small.
Why is institutional knowledge lost when people leave?
It is lost because nobody writes it down while it is cheap to capture. People are busy doing the work, documentation feels like a side job, and the knowledge seems obvious to the person who holds it. Then a resignation gives two weeks of notice, and a handover document covers the steps but not the reasons.
The loss rarely shows on the day someone leaves. It shows months later, when a client asks why something was set up the way it was, or a team repeats an experiment that already failed. By then the person who knew is gone, and the cost lands as rework and slower decisions.
Small companies feel it most. One person often holds a whole area, so one departure can take an entire client history or process with it. The fix is not a bigger wiki. It is a habit of capturing answers when they are given, with a named owner for each page.
