If a personal knowledge base feels unhelpful, test retrieval before adding more material. Choose a real question you recently needed to answer, find the relevant note, and check whether it still makes sense without the original context.
Diagnose one failed search
Write down the phrase you searched, the note you expected, and what was missing. Try the language you would naturally use now, not only the words used when the note was created. Give unclear titles a more descriptive name and add a short explanation of why the note matters.
In Obsidian, search can use exact phrases and file, path, or tag filters. Its documentation also notes that excluded files do not appear in results. Check the search scope before concluding that a note has disappeared. Search
Add links that explain a relationship
Obsidian supports internal Markdown links and wikilinks, and can update internal links when a note is renamed. Those are tool capabilities; they do not decide which relationships are useful. Internal links
Prefer a sentence explaining the connection to a collection of unexplained links. For example, connect a decision record to the requirements that motivated it and the later review that changed it. Keep the source and date next to an external fact so you can reassess it later.
Retest before reorganizing everything
Repeat the original search after improving one small set of notes. Ask whether the answer is now easier to locate and whether conflicting versions remain. Apply the same pattern elsewhere only if it helps.
This is a retrieval-first working method, not a promise that a specific app improves memory. Keep private work separate from material intended for sharing, and check backups before any bulk move or rename.
Sources
- Search — Obsidian
- Internal links — Obsidian