Build a Useful Second Brain Without Collecting More Apps
A personal knowledge system should make useful information easier to recover. It does not need to capture everything you see. Begin with one place for active notes and a simple way to connect a note to the project or question that makes it worth keeping.
Why it matters
Saving is cheap, but reviewing and maintaining a collection takes attention. A note earns its place when you can explain how it might support a decision, a project or a concept you want to understand.
A practical workflow
- Choose one capture location and record a short reason whenever you save an article, idea or reference.
- Separate active project material from general reference so current work does not disappear inside a large archive.
- Write brief summaries in your own words and add links that explain meaningful relationships between notes.
- Review a small portion regularly, deleting or archiving material that no longer serves a purpose.
An example
If you save a tutorial on accessible forms, attach it to the website project where it could change your design. Add one sentence about the relevant lesson. A bare link in an unlabelled inbox is much harder to use when the design question returns.
A mistake to avoid
Avoid spending more time designing the system than using the information. Automated summaries and elaborate graphs can create an appearance of understanding without helping you explain or apply what you collected.
Try it and check the result
Choose a current project question and try to answer it from your notes. If useful material is hard to recover, improve the naming and project connections before moving everything to another app.
Reference and further reading
Obsidian: linking related notes.
The workflows and examples in this guide are illustrative. Product controls and availability can change; check the linked official guidance for your setup.
Continue with Run a Weekly Review with AI Without Creating More Admin or explore all blog topics.