Being “bad” in Obsidian and doing something “wrong” is the correct way to go about things.

There are many systems out there that are more opinionated than what is essentially a wiki. There are plenty of project/productivity/graph drawing/etc tools that are all more specialized at what they do and can put prettier UI's on things with more one-click buttons.

But the hidden value of doing something poorly in Obsidian, rather than the default way somewhere else, is that you get to make it just what you want.

Take CRM. Dave Sivers in his book Your Music and Your People doesn't even talk about using an app, but just calls it a database that you should use to help stay connected to people. What's a better people database than one that matches exactly what you want to capture?

Sure Obsidian does some things better than others. Fields are easy. Tags are easy. Journaling is easy. TODOs are easy. Connections are easy. Updates are... just as tedious as other systems. While on the other hand its connections to social and ability to mail merge are definitely lacking.

But you know what? You probably don't need most of that stuff.

Starting from a blank text file forces you to pick the most important things first. That in itself is already key. Without toying with a few ideas on your own first, you might gravitate toward the prettiest or most/least expensive tool, even if it's not right for you.

The plugin ecosystem gives you a tremendous leg up for specifics, but an Obsidian plugin will never beat a polished alternative at that use case. The Tasks plugin will never be Todoist. This is a good thing.

The rough edges are your personal feedback for knowing what's working and what isn't. Treasure that feedback.

Once you dive into the mindset that being bad (or at least starting bad) is the point, there's a lot of power that's unlocked to you.

Dive in, do something poorly, then tweak. It's more fun, and more effective than aiming for perfection from the outset.

#Obsidian #PKM #Agile

One thing I want to highlight before I even get there, though, is just how daunting it is to get started.

It's not even that the process of turning more temporary notes into your own synthesized ideas is that difficult to understand. It's that a key step in the process, linking new ideas to previous ones, is frightening when you're staring at a blank page.

Does everything have to be bottom up from new material? I do have some ideas floating around in my head, can I scaffold those first? Do I need to flag them to come back to later?

My inclination so far is to do the crappiest thing possible, and fix it later if I have to. Perfection in PKM is far more the problem than never creating and toying with ideas at all.

So here's to diving into imperfection! After all, anything worth doing is worth doing poorly.

#BASB #Zettelkasten #ToolsForThought #PKM

First, it's absolutely amazing to me how fast development is going with the Obsidian space. The number of things that are 1-2 weeks old that radically alter my workflow are just mind boggling.

https://write.as/ftwynn/interstitial-journaling-in-obsidian-with-a-stripped-down-quickadd

I wrote that less than a week ago, and now that script is a proper plugin. It's so hot off the press it isn't in the Obsidian UI yet, but I'm looking forward to when it is (which will hopefully resolve some weirdness I had with the script version).

Current Use Cases I'm Investigating for it:

1. Interstitial Journaling (super helpful thus far)
2. Changelog at the bottom of any notes files (need to toy with it a bit more)

Both are good for the “capturing a quick thought from anywhere in a timely manner” case.

#Obsidian #ToolsForThought #PKM #BASB