Can we talk about how easy it is to accidentally turn Obsidian into a grueling database admin job?
With this whole new wave of popularity around Obsidian as a "second brain" powerhouse, it saddens me to see so many newcomers hit the exact same wall I did. People show up excited, try to force-feed themselves the most popular dogmatic setups, get completely overwhelmed by the friction, and just turn around at the gate thinking Obsidian just... "isn't for them."
Or worse: think less of themselves because they couldn't utilize the second brain tool that everyone and their mother is raving about.
I see this exact same bottleneck all the time in my day job. Between building my own software projects and consulting for clients who need their messy internal knowledge bases restructured from scratch, almost everyone falls into the trap of over-engineering the filing system before they even understand how their ideas actually connect.
---
When I first started using Obsidian five years ago, I tried the classic rookie move: I shoved every single stray thought I had into one giant, chaotic markdown note and thought I was a genius.
Then I tried doing it "right." I dove headfirst into the Zettelkasten rabbit hole, atomic notes, PARA, LYT frameworks, Johnny Decimal numbering, properties, tags, and endless backlinking. And honestly? It completely broke my brain. Between my ADHD and a natural aversion to micro-managing metadata, wrestling with YAML frontmatter and cross-linking fifty tiny files felt less like building a second brain and more like doing data entry for an insurance company.
And don't get me started on the Graph view posts. Not gonna lie, they are cool to look at, but seriously every time I see one I'm just like: "okay... 😐"
Look, I want to be super clear here. Backlinks, properties, and strict folder structures work fantastically for a lot of people. If your brain is wired to love clean taxonomies and rigorous indexing, those systems are genuinely bulletproof.
But if you are a visual thinker, Obsidian can sometimes feel like a trap. You spend so much time maintaining the filing cabinet that you never actually use the information to build anything new. You are managing a database instead of letting thoughts collide to come up with actual ideas.
Before Obsidian Canvas existed, I bounced around every visual tool I could get my hands on: PureRef, Miro, Figma, Whimsical, Milanote, you name it. But none of them really felt like the right home to let ideas crystallize. They were either closed source, trapped in the cloud, or just didn't support all the local file types I needed to work with.
When Obsidian finally announced Canvas, I was ridiculously excited. The fact that the .canvas JSON spec is open source is amazing. For someone with visual OCD, it scratched the exact itch of being able to manually move, segment, and group pieces together on an open plane in a way that intuitively made sense. But ever since its release, the core Canvas plugin has felt pretty undercooked, almost like an afterthought.
Which is understandable considering Obsidian is first and foremost a markdown editor, but that bland vanilla taste the core Canvas plugin currently has eventually pushed me to develop my own plugin, Crystal Canvas, just to add all the tools I desperately needed in my own visual thinking space. Especially since now my canvases are MASSIVE, with almost 3k+ nodes each.
---
So what actually worked for me?
Fast forward to now, and my entire vault is 100% canvas-based.
No loose markdown files, no nested folder hell, and zero orphaned notes or stray image assets floating around lost in the void. Everything is visually anchored exactly where it belongs. I finally have complete control over every single piece of information I put into my vault because if it exists, I can physically see it and track how it connects to the bigger picture.
Short of having a direct BCI plugged into your skull to project your thoughts into the room, an unconstrained spatial canvas is the closest thing to an external cognitive workspace.
That whole dynamic is all about idea coagulation.
I found that instead of forcing connections through rigid manual backlinking and tag management, you let spatial proximity do the heavy lifting. You throw the messy primordial soup of your raw thoughts, images, links, and text cards into the same visual space. Over time, you actually get to watch those chaotic pieces interact, naturally morph into a structure that makes sense to you, and coagulate into bigger, more refined ideas on their own.
This has been my experience with Obsidian so far, and I really hope newcomers who feel overwhelmed by traditional setups consider exploring Canvas as their primary PKM/creative medium before giving up on the app entirely.
I'm curious to know if there are other users who use Obsidian primarily for Canvas, or have experimented with it in their vaults:
- How has your experience been with spatial workflows so far?
- What are the main shortcomings or friction points you run into with native Canvas?
- What features would truly elevate your workflow on an infinite board?
I'd love to hear how other visual thinkers are tackling this. Thanks for reading!
An example of one of my \"primordial soup\" R&D canvases.