Most PKM systems are idea-centric: notes about concepts, books, and projects. But knowledge work is deeply relational. The people you interact with are sources of ideas, collaborators on projects, and participants in your professional network. A Personal CRM uses PKM infrastructure to manage relationships systematically, turning the "people" dimension from an afterthought into a first-class knowledge domain.
What Person Notes Contain
Each person in your network gets a dedicated note with structured metadata: name, role, organization, how you met, communication channels, birthdays, shared interests, interaction history. Beyond metadata, the note becomes a knowledge hub linking outward to meeting notes where they participated, quotes or ideas they shared, books or resources they recommended, projects you collaborate on, and follow-up actions.
The Knowledge Hub Effect
A person note is not a contact card. It is a relationship node in your knowledge graph. When you link a meeting note to the person notes of all attendees, both the meeting and the people gain context. When someone recommends a book and you create a literature note, linking it back to their person note creates an attribution trail. Over time, a person note accumulates a rich picture of the relationship: what you discussed, what they taught you, what you are working on together.
This hub effect makes preparation effortless. Before a meeting, open the person notes of all attendees. Instantly see: last interaction, open follow-ups, shared interests, recent topics. No more scrambling to remember what you discussed six months ago.
Relationship Nurturing
Relationships decay without maintenance, similar to Knowledge Decay for notes. A Personal CRM makes this maintenance systematic. Track last interaction dates. Surface relationships that have gone cold (no interaction in 90 days). Flag upcoming birthdays and anniversaries. Queue follow-up actions from past meetings. This is not about turning relationships into transactions; it is about ensuring that relationships you value do not fade through neglect.
Implementation in Typed Note Systems
In a Typed Notes system, "Person" is a note type with its own template, properties, and folder location. Properties include: name, organization, relationship type (friend, colleague, mentor, client), first met date, last interaction date, communication preference, and tags for shared domains. The template ensures consistency across all person notes, and structured properties enable queries: "show all people I have not interacted with in 60 days," "list all people tagged with PKM."
The People Dimension Most Systems Ignore
PKM literature focuses overwhelmingly on ideas and information. People are mentioned in passing (as sources or collaborators) but rarely get their own note type or systematic treatment. This is a blind spot. Ideas do not exist in isolation; they come from conversations, are tested in discussions, and are refined through collaboration. A PKM system without a people layer is missing the social context that makes knowledge meaningful.
Key Points
- Person notes are relationship nodes in the knowledge graph, not just contact cards
- Each person note links to meetings, quotes, books, projects, and follow-ups
- Preparation for meetings becomes trivial when person notes accumulate context
- Systematic tracking prevents relationship decay through neglect
- Most PKM systems ignore the people dimension entirely
Open Questions
- Where is the line between systematic relationship management and surveillance?
- How should AI agents use person notes (e.g., pre-meeting briefings, relationship health alerts)?
- Should person notes be shared or strictly private?
References
- Vault: Obsidian Starter Kit - Theory, Obsidian Starter Kit - Reference - Note Types