%% run start `![| banner](${file.properties.cover})` %% ![| banner](https://images.unsplash.com/3/doctype-hi-res.jpg?ixid=M3w0ODQwNzB8MHwxfHNlYXJjaHwxfHxrbm93bGVkZ2UlMjBtYW5hZ2V8ZW58MHwwfHx8MTcwMDY5NjA0MHww&ixlib=rb-4.0.3) %% run end %% #knowledge-management ## What is Knowledge Consolidation When you create notes in obsidian, many notes are incomplete and you need to enrich them later. But knowledge consolidation sometimes can be dangerous. Especially when you don’t know what it mean by Obsidian, you will fall into a rabbit but not getting anything done. ![Addicted to Obsidian??🤯](https://res.cloudinary.com/yomaru/image/upload/v1704448623/obsidian/nm9ihjwgetsngee5hckp.webp) ## What Define Good [[Knowledge Management]] ![[Knowledge consolidation 2024-01-01 21.14.27.excalidraw.svg]] %% ![[Knowledge consolidation 2024-01-01 21.14.27.excalidraw]] %% Any form of management should have a ==goal==. We don't do management for management. A knowledge base needs to have a goal too. Ask what is the goal of the knowledge and how to quantify the progress? In the [[How to think clearly?]], we know that the essence of thinking clearly is ==reusability==, which align with the diagram below. Another criteria is the ==maintainability==. This is a bit tricky, because for PKM people usually manage their knowledge base by themselves. The larger the vault is, the more difficult for a person to manage it. So no matter what method you use, once your knowledge get larger, it will more difficult to maintain. > [!question] Atomic note is a not a good management method from this point of view. Have you ever thought of record less but more important knowledge? The third important factor is the ==ease of relearn==. This factor focus on the quality of content. High quality content should be able to relearned very easily. ```mermaid graph LR A((new knowledge come in)) --> B C((question come in)) --> B B("hitting old knowledge") B -- revalidate knowledge --> B ``` ==Basically the faster this process, the better it is.== Therefore, what are the signs of having a poor knowledge management system. 1. When you create a note and find that the notes are actually duplicated with some old notes. 2. Difficulty in locating relevant information: If you struggle to find specific notes or information when needed, it suggests a lack of proper organization or indexing. This can lead to wasted time and frustration. 3. Inconsistent or outdated information ## What Need to Be Remember? What Doesn't? We write things down so as to forget. If the knowledge will forever be lost if we don't write it down, then we need to write it down. If we can find it somewhere in the internet with high confidence, probably we don't need to put it down. If things update frequently and we don't have the effort to keep track of them, don't put the content down. Just keep the reference. → But external reference cannot be search on obsidian → use [[Run|obsidian run]] with auto run to refresh the knowledge. In this way, we delegate the management to the world but not us. You should document things about yourself because this information is only known by you and not anyone else in the internet. > This is the reason why writing [[Diary]] is important. Among all the knowledge, making record of yourself and doing reflection probably is one of the most valuable things to do. ## How the Workflow Should Be Designed > [!warning] add more content %% INCOMPLETE(add more) %% > ### 1. Should have unique keywords in title When you search a file, the thing that affect search result the most is title. The title/alias should have unique keywords for you to retrieve it accurately. > ### 2. project management / time management > knowledge management , Action > Management Base on the things I said above, if knowledge management serves a specific goal, it would be more beneficial to prioritize project management and time management as they are more actionable. Therefore, project management and time management should be prioritized before knowledge management. > ### 3. knowledge management is more like documentation Therefore, the ultimate form of knowledge management with a specific goal in mind is very much like how technical documentation is written. They have a scope and a clear purpose. They don’t write less and extra. It should just enough for what the user should know to get things done. Because of this, we should think about what are the necessary that we need to put in Obsidian.