Get AI summaries of any video or article — Sign up free
I'm Restarting my Obsidian Vault After 2 Years... thumbnail

I'm Restarting my Obsidian Vault After 2 Years...

John Mavrick Ch.·
5 min read

Based on John Mavrick Ch.'s video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

He’s restarting because his vault drifted from conceptual, connected notes with personal reflections to highlight hoarding, which reduced his own critical thinking.

Briefing

After two years and more than 5,800 notes, John Mavrick is restarting his Obsidian vault because the system he built stopped producing his own thinking. The core issue wasn’t storage—it was the quality of processing. For months, he shifted from conceptual, connected notes with personal reflections to collecting highlights and leaving them largely unprocessed, creating a backlog of extracted ideas with “little of my own.” Over time, that imbalance weakened critical thinking and introspection, the very outcomes personal knowledge management is meant to strengthen.

He also points to a second failure mode: keeping source material intact while still not transforming it. By archiving highlights without the compounding effect of building ideas on top of each other, his vault became a set of fragments scattered across input notes rather than an evolving knowledge base. He describes the result as disappointing—especially because the damage could have been prevented with consistent maintenance early in his Obsidian journey, when his notes were more conceptual and reflective.

Rather than mourn what’s been lost, he frames the restart as a chance to rebuild a “second brain” that supports self-actualization. The new vault will be designed from the start for intrinsic content creation and for publishing, so his note-taking process can be observed end-to-end: inputs become conceptual notes, which then turn into output notes that can feed future videos. When he learns something new, he plans to publish links that connect readers to the relevant areas inside the vault, enabling ongoing exploration.

A key operational change is how he will publish. Instead of using Obsidian Publish, he plans to use the digital Garden plugin, chosen because it can render DataView queries—an “indispensable” part of his vault. He’ll also start from a fresh copy of the “ultimate starter Vault” to reduce setup time and avoid the difficulty of retrofitting a heavily evolved vault into new structures and workflows.

Finally, he’s tightening the habits and the philosophy behind the system. He wants note-making and writing to become a consistent daily practice, and he’s creating a personal philosophy for knowledge management—highly opinionated mindsets, methods, and tools—that will likely live as an area inside the vault. The restart is therefore both a technical reset and a behavioral one: less highlight hoarding, more reflection, more connection, and a publishing workflow intended to make the knowledge grow beyond private storage through evergreen newsletters and videos.

Cornell Notes

John Mavrick is restarting his Obsidian vault after two years because his note-taking drifted from connected, conceptual writing into highlight collection. The backlog of mostly other people’s ideas reduced his own critical thinking and introspection, and the vault stopped producing compounding knowledge. His new plan centers on intrinsic self-driven creation: daily note-making, stronger personal reflections, and a workflow that turns inputs into conceptual notes and then into output notes for future videos. He also wants publishing from the start, using the digital Garden plugin (not Obsidian Publish) so his site can render DataView queries. To speed the transition, he’ll begin with a fresh copy of the ultimate starter Vault and customize it for his life inputs like YouTube videos, a weekly newsletter, and anime.

What specific behavior shift made the vault feel less useful to him?

He stopped doing the “processing” work that turns inputs into his own thinking. Instead of actively creating conceptual and connected notes with personal reflections, he began collecting highlights more than connecting notes or doing his own analysis. That mindset produced a growing backlog of extracted quotes and ideas with little vivid capture of his realizations—the part he considers most important for personal knowledge management.

Why does he say the vault’s structure failed even though sources were preserved?

Keeping the original sources didn’t create growth. His notes became fragments scattered across input notes, with no compounding effect—ideas weren’t built on top of each other to generate something new. Without that layering, the knowledge didn’t evolve over time, so the system didn’t strengthen his ability to think critically or reflect deeply.

What does “publishing in mind” change about his note-taking workflow?

Publishing forces the system to support an end-to-end pipeline. He plans to show how inputs become conceptual notes, then output notes that can support future videos. When he learns something new, he’ll publish links to the related areas inside his vault so readers can follow the trail of ideas rather than seeing isolated “shiny new objects.”

Why choose the digital Garden plugin instead of Obsidian Publish?

He wants his publishing setup to render DataView queries, which he calls indispensable to his vault. The digital Garden plugin fits that need, letting his published pages reflect the same query-driven structure he relies on internally.

How will starting from the ultimate starter Vault affect the restart?

He’s avoiding the time sink of updating a heavily evolved vault to new structures and workflows. By using a fresh copy of the ultimate starter Vault, he can customize it for different node types in his life—such as YouTube videos, his weekly newsletter, and anime—while spending more time on note-making instead of migration work.

What role does his “philosophy” play in the new vault?

It’s meant to add highly opinionated examples of mindsets, methods, and tools for personal knowledge management. He already has an Obsidian setup based on the ultimate starter Vault, but the philosophy area will provide more concrete, personal guidance and examples, likely updated continuously as his views evolve.

Review Questions

  1. How did collecting highlights without connecting notes change the quality of his thinking, according to his description?
  2. What pipeline does he want to make visible through publishing (inputs → conceptual notes → output notes), and why?
  3. What technical and workflow choices (digital Garden, DataView rendering, ultimate starter Vault) support his goals for evergreen growth and easier iteration?

Key Points

  1. 1

    He’s restarting because his vault drifted from conceptual, connected notes with personal reflections to highlight hoarding, which reduced his own critical thinking.

  2. 2

    Preserving sources alone didn’t create knowledge growth; the notes lacked compounding structure where ideas build on each other.

  3. 3

    The new vault will be designed for intrinsic self-driven creation and for publishing from the start, showing the full workflow from inputs to outputs.

  4. 4

    He plans to publish using the digital Garden plugin because it can render DataView queries, which are central to his vault.

  5. 5

    He’ll start from a fresh copy of the ultimate starter Vault to avoid migration pain and to spend more time on writing and note-making.

  6. 6

    He’s committing to a consistent daily habit of note-making and writing, rather than relying on backlog collection.

  7. 7

    He’s creating a personal philosophy for knowledge management to provide opinionated methods and examples inside the vault.

Highlights

The restart is triggered by a shift from connected conceptual notes to collecting highlights—an imbalance he says weakened introspection and critical thinking.
He wants publishing to reveal the transformation chain: inputs become conceptual notes, which then become output notes for future videos.
digital Garden is chosen specifically to support DataView queries in published pages, keeping the vault’s query-driven structure intact.
Starting from the ultimate starter Vault is meant to reduce setup and migration time so iteration focuses on writing and system use.
His “second brain” goal is explicitly tied to self-actualization, not just archiving information.

Topics

Mentioned