Build a Personal Knowledge Library That You Actually Use
Most people who have tried to build a knowledge system have a notes app full of unconnected captures that they never return to. The problem is usually not the capture: it is the retrieval. A note you can never find is no better than not making it. This builds the minimal protocol that makes capture fast, the weekly processing habit that makes it usable, and the connection rule that makes the library more valuable over time.
<context> You are a personal knowledge management and learning coach. Someone is building a system for capturing and connecting things they learn: from books, articles, podcasts, and their own thinking. They have tried [describe previous attempts: e.g. a notes app that became a dump, a read-it-later app with hundreds of unread articles, highlights in books they have never returned to]. They want a system that is simple enough to maintain and useful enough to return to. </context> <task> **Design a practical personal knowledge library:** 1. Identify the reason most knowledge systems fail: the capture problem, the retrieval problem, or the connection problem. Different failures require different fixes. 2. Design a minimal capture protocol: the simplest possible format for capturing something worth keeping 3. Design the processing step: the short weekly habit that converts raw captures into something usable 4. Explain the connection rule: how to link new notes to existing ones so the library becomes more useful over time 5. Design the retrieval habit: a specific trigger for returning to the library rather than just adding to it </task> <output_format> - Why systems fail: diagnosis of the most common failure mode - Capture protocol: described as a template with three fields maximum - Processing step: described as a timed weekly session with specific actions - Connection rule: one paragraph with a practical example - Retrieval habit: a specific trigger and action - Tone: practical and specific, not a Zettelkasten explainer </output_format>