The Viable Edge
About
Login
Let’s talk
Work with meSystems and implementationPrivate team workshopsIndividual mentorship
LearnSecond Brain CoursePublic Maven workshopBlogNewsletter
About
Digital productsClaude Code Service OSFind a Client Skill PackHermes First Handoff KitBrand ArchitectBrand Architect live demoBrand snapshot audit
Let’s talkLogin
  1. Home
  2. /
  3. Blog
  4. /
  5. Institutional Knowledge: Meaning, Examples and How to Capture It
Institutional Knowledge: Meaning, Examples and How to Capture It
ai-era-strategy7 min read

Institutional Knowledge: Meaning, Examples and How to Capture It

Institutional knowledge is everything a company knows that lives in people rather than documents: why a decision was made, which client needs extra care, how a process really runs. It walks out the door when people leave. An AI interview and a plain-text knowledge base keep it.

AS

By Adam Sandler

Founder of The Viable Edge, with 20+ years of experience helping businesses build competitive advantage through strategic transformation. Expert in AI-era business strategy and systematic implementation.

Published November 16, 2026 · Updated November 16, 2026

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.

Key takeaways

  • Institutional knowledge is the know-how, history and context a team holds that no document records.
  • It leaves with people: a resignation, a retirement or a long holiday shows you where it sits.
  • Capture it by interview, not by asking people to write documentation in their spare time.
  • An AI tool can run the interview and draft the pages; the expert only corrects them.
  • Store it as plain text in a company knowledge base so AI tools can answer from 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.

No spam, ever
Unsubscribe anytime

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.

Free download

Start with the Second Brain Starter Kit

The capture inbox, note template, source log, weekly checklist, connect-your-AI guide and retrieval self-test, as plain markdown files that work in Obsidian or any editor, with Claude or any AI. Enter your email and the download starts.

No spam, ever
Unsubscribe anytime

How do you capture institutional knowledge with AI?

Use an AI tool as the interviewer. Give it the person's role and recent work, ask it to question them about decisions, exceptions and recurring problems, and record the answers. Then have the AI draft one short page per topic and send the drafts back to the expert to correct. The expert talks; the AI writes.

Asking experts to write documentation fails because writing is the slow part. Talking is fast. A 30-minute recorded conversation holds more usable knowledge than most handover documents, and an AI tool turns the transcript into pages in minutes. A workable flow:

  1. Prepare. Share the person's recent projects, processes and the questions colleagues ask them most.
  2. Interview. Ask the AI to question them one topic at a time: what they decide, what goes wrong, what a new person always gets wrong, and why each exception exists.
  3. Draft. Have the AI write one page per answer, with the date and who it came from.
  4. Correct. The expert edits the drafts. Corrections are quicker than writing, so this step actually happens.

Run it whenever someone gives notice, and before that too: once a quarter for whoever holds the most unwritten answers.

Where should captured institutional knowledge live?

It belongs in one company knowledge base: short pages, one topic each, with an owner and a review date, stored as plain text your AI tools can read. That way a new hire can ask a question in plain language and get an answer that cites the page it came from, instead of finding the one person who knows.

Keep the pages short and specific. "Why we stopped offering monthly billing" is a better page than "Billing history". When the knowledge base is readable by AI, it becomes the front door for questions, and every answer points back to a source someone can check.

We cover the rollout, from the first 20 pages to getting a team to use it, in our guide to building a company knowledge base. For the format that AI tools read reliably, see how to build a knowledge base for AI.

How do you stop captured knowledge from going stale?

Give every page an owner and a review date, and change owners the week someone joins or leaves. Answer every repeat question with a link to the page, so missing pages show up fast. Then test the knowledge base monthly with real questions and fix the page behind each wrong answer. Stale pages are worse than none.

An out-of-date page is dangerous when AI reads it, because the tool repeats it confidently to whoever asks. Our guide to keeping a knowledge base up to date has the review schedule, and the retrieval test has the scorecard for the monthly check.

For consultants and service providers

Build second brains for clients

Build and Deliver Professional Second Brains is a self-paced course on doing this for other people: scoping the engagement, building a knowledge base from a client's real material, testing retrieval, and handing it over, with a working knowledge base kit to build with. Plain files, no coding, no vector database.

Explore the course→

The second brain series

  • What Is a Second Brain? The Method, and the AI Version
  • Best Second Brain Apps 2026: Obsidian, Notion, Logseq and AI
  • Second Brain Template: A Free, AI-Ready Setup in Plain Markdown
  • The PARA Method: How to Organize a Second Brain AI Can Read
  • Progressive Summarization: How to Distill Notes With AI
  • Building a Second Brain Summary: The Book's Ideas, Updated for AI
  • Zettelkasten vs PARA: Which Second Brain Method Works With AI?
  • Personal Knowledge Management (PKM): A System That Works With AI
  • AI Knowledge Management: What It Is, How It Works, How to Start
  • Notion Second Brain: How to Build One That AI Can Use
  • Second Brain for ADHD: A System That Survives Bad Weeks
  • Second Brain for Students: A Study System AI Can Quiz You From
  • Trader's Second Brain Alternatives: An AI Trading Journal You Own
  • Second Brain for Founders: Run Your Company From Notes AI Reads
  • Obsidian Second Brain Template: A Free Setup Claude Can Read
  • Internal Knowledge Base: What It Is, Benefits and How to Build One
  • Company Knowledge Base: Build a Second Brain for Your Team
  • How to Keep an Internal Knowledge Base Up to Date
  • What People Ask Google About Second Brains: 3 Months of Data
  • How to Build a Knowledge Base for AI: A Second Brain It Can Read
  • AI Knowledge Management Tools: From Second Brain to Company Wiki

Related Articles

Company Knowledge Base: Build a Second Brain for Your Team

Which pages to write first, how to get a team to use it, and how to test it.

Internal Knowledge Base: What It Is, Benefits and How to Build One

What goes in, the benefits, and how to build one AI can use.

Second Brain for Founders: Run Your Company From Notes AI Reads

A decision log, customer notes and weekly reviews AI can draft from.

How to Keep an Internal Knowledge Base Up to Date

Owners, review dates, change triggers, and AI that drafts the fixes.

Work with The Viable Edge

Help your marketing team become AI-native.

Adam trains your team, redesigns the workflows, and builds the AI systems your team actually uses, starting from your real work.

Talk to AdamPrivate team workshopsThe course

Want the knowledge base built and kept current for you? Brand Architect does that. The first build is free, no credit card needed. Try Brand Architect →

The Viable Edge

Practical AI systems. Hands-on learning. Human judgment.

Work with me

Systems and implementationPrivate team workshopsIndividual mentorship

Learn

Second Brain CoursePublic Maven workshopBlogNewsletter

Digital products

Claude Code Service OSFind a Client Skill PackHermes First Handoff KitBrand ArchitectBrand Architect live demoBrand snapshot audit

Company

AboutWhy The Viable EdgeContactFAQKnowledge HubDevelopersLogin
© 2026 The Viable Edge. All rights reserved.
PrivacyTerms