What is Institutional Knowledge?

Institutional Knowledge is a mental model used for better thinking and decision-making.

How do you apply Institutional Knowledge?

To apply Institutional Knowledge, identify situations where this framework is relevant, then use it as a lens to evaluate your options and decisions. The model is most useful when combined with other complementary mental models.

What category does Institutional Knowledge fall under?

Institutional Knowledge falls under the Business & Strategy category of mental models. Other models in this category can be found on the Business & Strategy hub page.

Why is Institutional Knowledge important?

Institutional Knowledge is important because it provides a structured way to think about problems that would otherwise be approached with intuition alone. Understanding this model helps you avoid common reasoning errors and make better decisions.

Institutional Knowledge Mental Model…

Institutional Knowledge Mental Model… | Faster Than Normal

Section 2

How to See It

Org Risk

You're seeing Institutional Knowledge when “only X knows how that works” or “we lost that when Y left” — the knowledge is critical but not documented or spread, so the org is fragile.

Scaling

You're seeing Institutional Knowledge when onboarding, runbooks, or “how we do X” docs exist and new hires or teams get up to speed without constant access to the original owner.

Section 3

How to Use It

Identify critical knowledge that’s in people’s heads: key processes, customer context, technical decisions. Capture it in docs, pair work, or handoffs so that at least two people can do or explain it. Treat “tribal knowledge” as technical debt — pay it down before it bites.

Decision filter

"If [key person] left tomorrow, what would break or slow down? For each answer, we have a knowledge-transfer gap. Who else needs to know, and what do we need to document or pair on?"

As a founder

Audit “single points of knowledge” — especially in you. Create runbooks, decision logs, and handoffs for the most critical flows. Build a habit of “write it down when you do it” and reward sharing and documentation so institutional knowledge becomes a shared asset.

Section 5

Founders & Leaders

Bill CampbellCoach to Jobs, Schmidt, Page; “Coach of Silicon Valley”

Campbell stressed that the best companies institutionalise their culture and operating principles so they outlast any one leader. He pushed execs to make “how we work” explicit — values, feedback, decision rights — so knowledge and norms lived in the system. Founders can apply this by codifying how decisions get made, how feedback flows, and what “good” looks like, so the org can scale without depending on a few people to explain it.

Section 7

Connected Models

Reinforces

Repeatable Systems

Repeatable systems are institutional knowledge made explicit: process, playbooks, checklists. Building repeatable systems is how you convert tacit knowledge into something the org can scale and hand off.

Tension

Organisational Debt

Organisational debt includes undocumentation and “we’ll fix it later.” Letting institutional knowledge stay in people’s heads is a form of that debt. The tension: pay it down by documenting and spreading knowledge before it becomes a single point of failure.

Leads-to

Bus Factor

Bus factor is how many people must disappear before something breaks. Increasing institutional knowledge — docs, pairing, handoffs — raises the bus factor and makes the org more resilient.

Section 8

One Key Quote

"Your title makes you a manager. Your people make you a leader. And the way you institutionalise how you work is what makes the company outlast you."
— Bill Campbell, quoted in Trillion Dollar Coach

Section 11

Summary & Further Reading

Institutional knowledge is the know-how that makes the org work; it’s an asset when shared and a risk when concentrated. Capture and spread it through docs, pairing, and handoffs to reduce dependency and raise the bus factor.

Trillion Dollar Coach — Eric Schmidt et al. (2019)

Book

Bill Campbell’s approach to culture and institutionalising how teams work.

The Phoenix Project — Gene Kim et al. (2013)

Book

Operations and knowledge transfer; runbooks and shared context.

Documenting Decisions (ADRs)

Concept

Architecture Decision Records; one pattern for capturing institutional knowledge.

Institutional Knowledge

Continue exploring

Popular Mental Models

Core Idea

How to See It

How to Use It

Founders & Leaders

Connected Models

One Key Quote

Summary & Further Reading

This connects to...

Continue exploring

Popular Mental Models

More like this, in your inbox

Core Idea

How to See It

How to Use It

Founders & Leaders

Connected Models

One Key Quote

Summary & Further Reading

This connects to...