Persona Playbooks
A guide for PKM and tools enthusiasts on how to share knowledge from their research library — move beyond sharing system tours and tool recommendations to
Most of what the PKM community shares isn't knowledge — it's furniture. The vault tour, the PARA breakdown, the daily note template: popular content, easy to produce, and almost entirely about the container rather than what's inside it. Meanwhile the actual research — the domain expertise accumulated over years of systematic capture — stays private, filed away as if it were the boring part.
That's backwards. Nobody outside the PKM community cares how your Obsidian vault is organized. Plenty of people care what you've learned about behavioral economics, philosophy of mind, or climate policy after two years of reading it systematically and annotating what you found. The tools are scaffolding; the domain knowledge is the building people actually want to walk through.
That doesn't mean abandoning system content entirely — there's a real audience for it, and plenty of PKM creators have built followings on it. But the highest-value version of that content includes the substance the system produced, not just the shelves it's stored on.
This guide is about sharing the building instead of the scaffolding — moving from system tours to the substance a well-maintained WebSnips library was built to hold.
Before addressing how to share, the prior question: what specifically is worth sharing from a knowledge system?
Worth sharing:
Less worth sharing (from a distinct-value perspective):
The domain knowledge your WebSnips library contains is unique to you — accumulated over your specific research trajectory with your specific questions and interests. Your tool setup is not unique; thousands of people use the same tools.
If you do share about your PKM system — and there's a genuine audience for this — the highest-value version includes the substance alongside the system:
Not: "Here's how I organize my Obsidian vault with PARA and linked evergreen notes."
Yes: "Here's how I've been tracking philosophy of mind research for 2 years with WebSnips and Obsidian, what the system has helped me notice about the evolution of thinking in the field, and the 3 most important insights I've surfaced from 300+ captures."
The second version shares the system in the context of the knowledge it has produced. The PKM community gets the system tour they came for; they also get the domain insight that most system tours don't include. This is genuinely distinctive.
One underused sharing format for PKM enthusiasts: the curated, annotated source list.
From a well-organized WebSnips Collection on a specific topic, produce a document: "The 10 most important sources on [topic] — annotated."
For each source: the citation, a 2-3 sentence explanation of why it's important, and what it argues or establishes that the reader should know.
This format takes 30-45 minutes to produce from an organized WebSnips Collection (the annotations already exist; you're selecting and presenting the best ones). It's useful to anyone interested in the topic, not just PKM enthusiasts. And it demonstrates exactly the domain depth that systematic capturing and organizing produces.
The PKM community has been influenced by the "building in public" trend from the startup and creator communities — sharing your work and thinking in progress rather than only publishing finished pieces. For PKM enthusiasts, building in public typically takes one of two forms:
Form 1: System building in public Sharing your PKM system development: what's working, what you've tried, what you've changed. This is the most common PKM community content, as discussed above.
Form 2: Knowledge building in public Sharing your research and thinking development on specific topics: what you've captured recently, what's changing your mind, what questions you're currently investigating. This form is rarer and more valuable.
The knowledge-building-in-public format from WebSnips:
Weekly domain update (LinkedIn, Substack, or X/Twitter thread): "This week I read 5 things about [topic]. The most important was [source] because [specific reason]. It changed my view on [specific thing]. What I'm now thinking about differently: [specific claim or question]."
This is 150-200 words, takes 10 minutes to write from your most recent WebSnips Stage 2 session, and is distinctively valuable because it reflects actual domain engagement rather than generic advice.
The domain thread: A serialized exploration of a specific topic — one post per week, each addressing one aspect of the topic with specific sources from your WebSnips library. The thread format matches the knowledge accumulation process: you don't know everything about a topic on day 1; you learn progressively. Sharing progressively is authentic and builds an audience with the same interests.
The digital garden model — popularized in the PKM community by Andy Matuschak, Maggie Appleton, and others — is a public knowledge system: a published, interlinked set of notes that grows over time rather than a series of discrete articles published at set dates.
A digital garden has:
For PKM enthusiasts, a digital garden is the most authentic expression of a knowledge system because it shares the system's actual content rather than products derived from it.
WebSnips' role in a digital garden:
WebSnips provides the source layer of a digital garden. When a digital garden note cites a claim, the citation links to the WebSnips annotation for the source — which provides the source details, verbatim quotes, and context that the garden note references. This keeps the garden notes focused on thinking (what you believe and why) while the WebSnips library provides the evidence layer (what sources support the belief).
A functional public digital garden from a WebSnips + main system combination:
Tool options: Obsidian Publish (native digital garden from Obsidian), Garden.io (for Notion), Quartz (static site from Obsidian markdown), or a hand-built site if you have web development skills.
Content strategy:
Starting minimal: Begin with 10-15 of your most developed evergreen notes on a single topic. A digital garden doesn't need to cover everything from the first day; it starts with the most developed area and grows from there.
For PKM enthusiasts who want to build an audience beyond the PKM community, the transition is from "content about knowledge management" to "content about [your actual domain interest]."
Your WebSnips library is the source of domain content. The audience for domain content is larger and more commercially relevant (people interested in philosophy, cognitive science, climate change, design, economics, literature) than the audience for PKM content (people interested in knowledge management tools).
The transition content:
Rather than "here's how I take notes about philosophy," write:
These pieces are written from your WebSnips library (the evidence is in your captures); they're addressed to people interested in the domain topic, not people interested in note-taking. The audience is vastly larger; the engagement from genuinely interested readers is more intellectually satisfying; and the reputation built is for domain expertise, not for PKM expertise.
A domain-focused newsletter from a well-maintained WebSnips library:
Format: Monthly. 500-800 words. Content: 3-4 things from your WebSnips captures this month that are worth sharing with someone interested in [your domain]:
This newsletter takes 20-30 minutes to write from the monthly WebSnips review that's already in your practice. It's honest about uncertainty (a rarer quality in domain content than it should be). It demonstrates systematic engagement with the domain rather than casual familiarity. And it's genuinely useful to readers who trust you to filter intelligently from the sea of available content.
There is a legitimate audience for PKM system tours, and PKM content creators have built real audiences with this content. If your audience is primarily PKM enthusiasts and you enjoy creating system-focused content, that's a legitimate creative choice.
But even within the PKM community, the highest-value system tours include domain substance alongside system description:
The before/after knowledge example: "Two years ago, I had a vague understanding of [topic]. After building my capture and review practice around it, here's the specific understanding I've developed — here are the 3 claims I can now make with specific evidence that I couldn't make before the system."
This format shows what the system produces, not just how it's structured. It makes the case for building a knowledge system by demonstrating what one has done for your specific understanding of a topic you care about.
The scenario: An Obsidian user with 2,000 followers on a YouTube channel focused on PKM system tours. Comments are positive but mostly from the PKM community. She wants to expand her audience to people interested in her actual domain interest: behavioral economics.
The transition strategy:
Month 1: Published "My Behavioral Economics Reading List — Annotated" from her WebSnips Collection. Produced from 45 minutes of work (selecting and presenting 10 existing annotations). 3,400 views — her highest-performing video in 6 months.
Month 2: Published "3 Things I've Learned About Decision Biases That Surprised Me — From 2 Years of Research." Built from WebSnips captures and main system notes. 5,200 views. 140 new subscribers who explicitly mentioned behavioral economics in their subscription notes.
Month 3: Started a monthly behavioral economics newsletter. First issue: 89 subscribers from existing YouTube audience. 6 months later: 340 subscribers, including 2 academics and 1 journalist who wrote about behavioral economics professionally.
Her reflection: "The PKM content built my initial audience, but the behavioral economics content is building the audience I actually want — people who are interested in the same things I'm interested in. The PKM system is still how I work; it's just no longer the primary thing I publish about. I'm using the system rather than showing off the system."
Comment from a subscriber: "I found your channel because of the Obsidian video, but I stayed because of the behavioral economics content. I didn't know that combination existed — someone who thinks carefully about knowledge management AND has serious domain knowledge. That's exactly what I was looking for."
The PKM enthusiast's knowledge system contains something valuable: the accumulated, organized, synthesized domain knowledge that represents years of systematic reading and thinking. Sharing primarily about the system that contains this knowledge — while keeping the knowledge itself private — inverts the value hierarchy. The system is the tool; the knowledge is the product. A publishing and sharing practice built on that knowledge — through domain-focused newsletters, annotated source lists, digital gardens with proper evidence sourcing, and a building-in-public practice that shows what you're learning rather than how you're organized — is both more valuable to audiences and more aligned with why most PKM enthusiasts built their systems in the first place: to understand their domain better and to have something worth saying about it.
See also: The Ultimate Guide to Web Clipping.
More WebSnips articles that pair well with this topic.
A guide for educators and course creators on how to share knowledge with your team or audience — systematically share teaching resources with colleagues
A guide for lawyers on how to share legal knowledge effectively — distribute regulatory intelligence and doctrine updates to clients through client alerts
A guide for marketers on how to share marketing intelligence effectively — distribute competitive intelligence to sales teams who need it for
A guide for remote team leads on how to share knowledge with their team and broader audience — distribute async communication best practices to the team
A guide for knowledge workers and consultants on how to share intelligence effectively — distribute domain expertise to junior team members who need it
A guide for product managers and strategists on how to share product intelligence effectively — with engineers and designers who need user context for