liveBook · Manning

Tacit knowledge

Also called tribal knowledge

Tacit knowledge is practical, experience-based understanding held by individuals or groups that is not fully articulated or captured in accessible documentation.

How 2 Manning books explain it

Think Like a Software Engineering Manager

Undocumented knowledge held by a limited group or individual rather than recorded in accessible organizational documentation.

How it is used
Flags undocumented expertise as a risk to delegation, maintainability, and team handovers.
How deep it goes
Explains consequences and practical responses through delegation, documentation, and code-review scenarios.
Examples
Uses a sole-expert manager, legacy services with production fixes, and shared troubleshooting documents as examples.
What you can do after
Apply it by distributing expertise through delegation, documentation, and shared code reviews.

Read how Think Like a Software Engineering Manager explains tacit knowledge →

Vibe Engineering

Tacit knowledge is practical, often organization-specific understanding held by individuals or groups that is not explicitly documented or standardized.

How it is used
Turns informal engineering judgment into explicit context, governance, and machine-queryable structure for AI-assisted development.
How deep it goes
Explains organizational sources and operational risks, then gives documentation, graph-query, and blast-radius practices without detailing knowledge-capture implementation.
Examples
Uses context pyramids, governance rules, dependency queries, package tags, affected-consumer tests, and pull-request disclosures.
What you can do after
Apply it via context artifacts, build-graph queries, governance rules, and affected-consumer testing to reduce agent guessing.

Read how Vibe Engineering explains tacit knowledge →

Also covered in

What to know first

Related concepts

Questions about tacit knowledge

What is tacit knowledge?

Tacit knowledge is practical, experience-based understanding held by individuals or groups that is not fully articulated or captured in accessible documentation.

Which Manning books explain tacit knowledge?

Think Like a Software Engineering Manager and Vibe Engineering.

What should I know before learning tacit knowledge?

Manning books that teach tacit knowledge usually introduce feedback first.

What is the difference between tacit knowledge and specification?

Tacit knowledge is practical, experience-based understanding held by individuals or groups that is not fully articulated or captured in accessible documentation. A specification is a description of the requirements, expected behavior, properties, interfaces, or constraints that a system or component is expected to satisfy.

What is tacit knowledge also called?

Tacit knowledge is also called tribal knowledge.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.