Persona Library
← All personas
obsidianproductivityAPP-056

The Obsidian PKM Builder

#obsidian#pkm#notes#knowledge-management#markdown#linked-thinking
Aha Moment

“What was the moment this product clicked?” —

Identity

A researcher, writer, software developer, or knowledge worker who has built their second brain in Obsidian and means it. They write in Markdown. They link notes intentionally. They have a vault structure they've iterated on at least twice. They use the graph view occasionally, for the pleasure of seeing their thinking made visible, not because it's the most useful view. They've installed 8–20 plugins. They have strong opinions about the right way to take notes, opinions that evolved over two years of using the wrong way.

Intention

What are they trying to do? —

Outcome

What do they produce? —

Goals
  • Capture ideas in a format that connects them to related ideas automatically
  • Build a knowledge base that compounds over time rather than becoming a graveyard of notes
  • Think on the page in a tool that gets out of the way and stays local
Frustrations
  • Mobile sync that's slower or less reliable than desktop — notes are everywhere, the tool shouldn't be
  • Plugin conflicts that are only discovered after a workflow has been built around them
  • The blank-vault problem for new users — the power is real but the path to it is long
  • Collaboration that doesn't exist: Obsidian is a single-player tool in a world that sometimes requires multiplayer
Worldview
  • Your notes are your thinking — owning the format means owning your thoughts
  • A tool that requires the internet to open a file is a tool that owns your notes, not you
  • Links between ideas are more valuable than the ideas themselves
Scenario

They've just read a paper on collective intelligence that connects to a note they wrote six months ago about organizational design. They're opening both notes. They're adding a link and a 3-sentence synthesis at the bottom of the newer note. In 18 months, when they're writing something about organizational cognition, this link will surface. They won't remember making it. They'll be grateful they did. This is what the system is for.

Context

Has a vault of 500–3,000 notes built over 1–4 years. Uses a folder structure (or no folders, just links — they have opinions about this). Uses core plugins: backlinks, graph view, templates, daily notes. Uses community plugins: Dataview, Templater, Calendar, and 4–10 others. Syncs across devices via Obsidian Sync or iCloud. Has exported their vault to a different tool once and come back. Recommends Obsidian to people who ask about note-taking tools and watches their eyes glaze over at the setup requirements.

Impact
  • Mobile app performance that matches desktop removes the "I'll capture this later"
  • moment that creates the note backlog that never gets processed
  • Plugin stability signals (tested against current Obsidian version, community maintained)
  • surfaced in the plugin browser reduce the broken-plugin discovery during a workflow
  • Collaboration features — even lightweight ones like shared vaults with edit history —
  • open the single-player tool to the pair-or-team use cases that currently force a switch
  • New vault templates with a starter structure, example notes, and recommended plugins
  • reduce the blank-vault barrier that stops new users before they find the value
Composability Notes

Pairs with `notion-primary-user` to map the networked thought vs. structured database knowledge system philosophy. Contrast with `dovetail-primary-user` for the personal knowledge management vs. shared research repository use case. Use with `superhuman-primary-user` for knowledge workers whose primary inputs are email and notes.