One of the most common mistakes when building a knowledge management system is treating all information the same way. A large folder of notes is created, or everything is added to the same application without distinction, and the result is a large, pretty rubbish bin where nothing is found and nothing is used.
The first step towards designing a system that works is recognising that there are different types of knowledge, and that each one requires a different treatment.
Not all knowledge is the same
When you think about “what you know”, you mix very different things: a highlighted paragraph from a book, an idea you had on the train, the documentation for a project in progress, and a lesson learnt after a failure. These four things have different natures and serve different purposes.
I propose four categories that, without being exhaustive, cover most of what any person who works with ideas needs to manage.
Type 1: References
References are external information you want to keep because it may be useful in the future. It is not yours in origin: it comes from a book, an article, a video, a conversation, a podcast.
The problem with references is the illusion of knowledge: saving a highlighted paragraph or a favourite link gives us the feeling of having learnt something, when in reality we have only filed it. Knowledge requires processing; the reference is only the raw material.
References need an efficient capture system and a periodic review process. Without review, they become a graveyard of good intentions.
Type 2: Ideas
Ideas are connections you make yourself: your own hypothesis, an analogy that occurs to you, an opinion formed from several readings, a question you want to explore.
Ideas are the most valuable type of knowledge and the most fragile. They appear at the least convenient moments — in the shower, in the middle of a meeting, just before you fall asleep — and disappear just as quickly if you do not capture them.
The biggest mistake with ideas is not forgetting them (that too), but confusing them with references. An original idea must be written in your own language, in your own words, not as a quotation from someone else.
Type 3: Projects
Project knowledge is everything generated and needed in the context of a specific task or project: drafts, applied research, meeting notes, decisions taken and their reasons, previous versions of work.
What distinguishes project knowledge is its relative expiry: when the project ends, part of that knowledge stops being relevant in its original form. But part of it can become transferable learning.
The most frequent problem here is not separating project knowledge from the rest. Projects can become black holes that absorb all attention and leave no useful trace when they end.
Type 4: Learning
Learning is the most costly type of knowledge to generate and the most durable. These are the lessons you extract from experience: what works and what does not, the mistakes you do not want to repeat, the principles you have distilled over time.
Unlike references, learning is genuinely yours. Unlike ideas, it has been validated by experience. It is the most valuable residue of any project or period of life.
The problem is that learning is rarely collected actively. People accumulate it unconsciously, but do not capture it. A weekly or monthly reflection, even a brief one, can change this radically.
How they relate to each other
These four types do not live in sealed compartments. They have a dynamic relationship:
- Well-processed references generate ideas.
- Ideas applied to a context become projects.
- Completed projects produce learning.
- Learning enriches the way you read and select new references.
A complete knowledge management system must accommodate these four types and facilitate the flow between them. It is not a dead archive: it is a living system that helps you think.
In the next chapter we will talk about something fundamental before choosing any tool: the principles that make any system work, regardless of which application you use.
