“A teammate asked how they managed capture ideas in a format that connects them to related ideas automatically. They started explaining and realized every step ran through obsidian. Specifically, graph view for visualizing note connections had become load-bearing.”
When I'm they've just read a paper on collective intelligence that connects to a note the, I want to capture ideas in a format that connects them to related ideas automatically, so I can build a knowledge base that compounds over time rather than becoming a graveyard of notes.
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.
To reach the point where capture ideas in a format that connects them to related ideas automatically happens through obsidian as a matter of routine — not heroic effort. Their deeper aim: build a knowledge base that compounds over time rather than becoming a graveyard of notes.
obsidian becomes invisible infrastructure. Capture ideas in a format that connects them to related ideas automatically works without intervention. The old problem — mobile sync that's slower or less reliable than desktop — notes are everywhere, the tool shouldn't be — is a memory, not a daily fight. Mobile app performance that matches desktop removes the "I'll capture this later".
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.
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.
The proof is behavioral: capture ideas in a format that connects them to related ideas automatically happens without reminders. They've customized obsidian beyond the defaults — especially local-first markdown files with full ownership — and their usage is deepening, not plateauing. Their vault has a consistent naming convention and folder structure they've maintained for months.
The trigger is specific: plugin conflicts that are only discovered after a workflow has been built around them, combined with a high-stakes deadline. obsidian fails them at exactly the wrong moment. They needed to collaborate with a team and Obsidian's single-player design was a dealbreaker. What makes it irreversible: they fundamentally believe your notes are your thinking — owning the format means owning your thoughts, and obsidian just proved it doesn't share that belief.
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.