I take notes
I take lots of notes. Many of them are ideas to research, explore, and think about, while others are rather tasks or possible projects.
As I collect them continuously, their number grows. After a while, it becomes hard to look through them and prioritize for action.
The obvious way to do this, of course, is to categorize them under topics or themes.
This produces a hierarchical tree-like structure. There a few problems with this:
- There always be some idea or task which does not belong to a single category alone but under multiple ones.
- As the number of notes and, therefore, the number of categories and sub-categories becomes high, you need to dig very deep to find some notes. If the hierarchies are obvious, this is not really a problem. However, as the number of hierarchy levels and branches grow, the previous issue (i.e., notes belonging under multiple categories) become even more prominent.
There is also the problem of concept drift. While we refer to a particular thing or category with a specific term, later on, we start to refer to it with a related but different one. Similarly, we do the same with categories.
This shift can happen for multiple reasons, but the most obvious ones are terminological shifts or our changing ‘use’ of the original idea or category.
Concept drift, deep hierarchies, and the overlapping category boundaries can lead to the ‘forgetting’ of notes. They can also lead to making multiple, ‘almost similar’ but ‘slightly different’ versions of them at different places of the hierarchy.
And, even whether the relationship between two ideas should be hierarchical or not also can change from use case to use case.
And note-taking is just the most obvious example for me. I had the same experience with software development (both as writing code and managing versions), technical writing, academic research, work organization, file organization, etc.