Personal knowledge route from capture friction to review triggers

Meeting notes become searchable when properties and backlinks are treated as retrieval fields, not decorative metadata.

Notion Help describes database properties as context that can help filter, sort, and search database items. Obsidian Help describes properties as structured data for notes, and its Backlinks plugin shows notes that link to the active note, including linked and unlinked mentions. These features are useful only when the meeting note captures the fields people will actually search later.

For a small team, the retrieval fields can be minimal: date, project, decision, owner, source link, and next review. The body of the note should include the unresolved question and the exact phrase people will remember. If the meeting was about pricing, write pricing. If it was about onboarding emails, write onboarding emails. Do not hide the memorable term behind a private taxonomy that only the note writer understands.

Backlinks help when the meeting note links to durable pages: project page, customer page, incident page, launch page, or policy page. Later, opening the durable page shows which meetings referenced it. Properties help when the team needs a table view: all decisions by project, all notes with open questions, all source links awaiting review. The two tools solve different retrieval problems.

The useful test is whether a teammate can find the note without knowing the exact title. If they can search by project, decision phrase, linked page, date, or owner, the note has retrieval fields. If they must ask the original writer where it went, the note is stored but not yet findable.

Meeting notes become searchable when properties and backlinks are treated as retrieval fields

// COMMENTS

ON THIS PAGE