ThemeKnowledge & Systems
CardCard 30 of 66
Questions5 to explore

Knowledge

Knowledge, blueprints, insights & tricks

The most valuable knowledge in any organization is the kind that exists only in people's heads, and it leaves with them when they go.

Every organization accumulates knowledge that is not in any document: the workaround someone found for a recurring problem, the insight from a project that was never written up, the institutional understanding of why a customer relationship works the way it does. This is the knowledge that makes experienced people so effective, and it is the hardest to transfer.

Making this knowledge visible starts with identifying it. What do people ask the same expert for again and again? Which tasks grind to a halt when a specific person is unavailable? Those concentrations of knowledge are where the risk is highest and where documentation effort pays off most.

The goal is not to document everything. It is to capture enough that the organization can function without any single person being irreplaceable, and that new people can get up to speed without needing months of informal apprenticeship.

What to capture

For this part of the company brain, what is worth writing down and keeping current. The goal is not a complete archive but a living record that new people can read and returning people can trust.

Blueprints & how-tos

Step-by-step guides for recurring tasks, especially the ones that look simple but have non-obvious steps that only experienced people know. Capture the workarounds, not just the official process.

Lessons from past projects

What worked, what failed, and what the team would do differently: documented at the end of significant projects before the team moves on and the detail is lost.

Concentrated expertise

Who holds knowledge that nobody else has, and what that knowledge actually is. A map of knowledge concentrations helps prioritize what to document first.

Where knowledge lives

The single source of truth for each kind of knowledge: which tool, which folder, which document. Without this, knowledge exists but nobody can find it.

Questions to explore

Use these on your own or in a group. There are no right answers, only better conversations.

Which person in the organization would cause the most disruption if they left suddenly, and what knowledge would leave with them?
What recurring task do people consistently have to ask someone else how to do, even when they have done it before?
Are there lessons from past projects that the current team does not know because they joined after the project ended?
Where does someone go when they need to find out how something works and no one is available to ask?
What is the last piece of knowledge that only you know, that you have not written down anywhere?

Things to notice

Knowledge bases that are hard to search are nearly as useless as no knowledge base at all. Before adding more content, make sure what already exists is findable.
Expert knowledge is often tacit: the person who knows something may not realize it is unusual or worth documenting. Interviews and shadowing often surface more than asking people to write things down themselves.
Documentation that is accurate when written becomes misleading as soon as the process changes. Pair every how-to with a clear owner and a review trigger so it does not silently go out of date.