My Obsidian PKM system became a substitute for real thinking—how do I break free?

Three years ago I discovered Zettelkasten and Obsidian, and I went all in. I kept adding methods (PARA, LYT, PQ6R, etc.), making MOCs, linking notes. It felt like thinking, and it gave me a deep (but false) sense of progress.

But recently I asked myself: What actually happens to these notes after three months? Do I ever use them? The honest answer: nothing. They just sit there. I realized I’d become a professional organizer, not a better thinker. The system turned into a goal in itself—thinking about thinking instead of actually thinking. It let me avoid the discomfort of taking a real position, disagreeing with an author, or testing an idea in the real world.

Meanwhile, many prolific researchers I admire just use paper or Word and produce great output. I now believe real progress = behavior change, not beautiful linked notes. I want to rewire myself to ask, “What will this change about how I act tomorrow?” rather than “Where does this fit in my MOC?”

Has anyone else hit this wall? How did you reframe your relationship with knowledge management to be more action-oriented and less system-obsessed? Did you quit the system entirely, strip it down to bare fundamentals, or something else? I’d really appreciate hearing your experiences.

4 Likes

The behavior change you seek will happen by changing your definition of progress, not simply by changing the approach you use to make the same “progress” happen.

Define the products that you want to deliver to others. Define the audience you want to receive those products, both freely delivered and delivered for a payment of some kind or another. Establish the product quality and delivery deadlines that your audience expects for your products.

Then, find the tools to move your products from creation to delivery. I have worked effectively with Kanban lanes (On Board, In Flight, Delayed, Landing) at a project level and a consistent, base template task structure (Plan, Do, Deliver, Close) within any given project.


JJW

2 Likes

I don’t think you have to throw out the concept of systems thinking, but you are onto something with orienting toward action. Something I see at my workplace and online is a tendency to introduce new tools (which often in themselves form a system) with the expectation that just by having the tools available people will use them to achieve some goal. For example in my workplace, data dashboards would be made available for class instructors, but instructors lacked the skills nor care to use them let alone work them into a workflow for evaluating their instruction.

I feel the same way about what most productivity gurus share. It’s easier to create dashboards, bases, folder schemes, and other “structural” elements of a system, but it’s much harder to see how it all comes together. To me, that’s the behavioral/procedural component which is much harder to figure out and much less sexy (take a complex Notion system, for example, that would be a nightmare to process diagram, and a process diagram wouldn’t sell your courses). An ad hoc approach could work, but if everything about how you interact with your system is ad hoc, you likely aren’t going to get the results you’re after.

That’s partly why the processing flow for GTD works really well. There’s a flowchart to decide what goes where and you work through your inbox item-by-item. Then you end up with a clean inbox and next actions to work through. The behavioral/procedural component of the Next Action system does not work for me, but I have my own task management system that does.

Some simple things that work for me are…

  • Numbered checklists: How do I engage with the system and incorporate actions that will lead me toward my outcome?
  • Dedicated time to work toward something specific: What is it that I want to produce (a piece of writing, a program, notes on a text/subject, etc.)? Set a timer for that and immerse myself in the system to accomplish that goal. This time is more ad hoc than a checklist, but sometimes I can’t anticipate the steps so a checklist doesn’t work.
  • A mixture of the latter two points: a checklist doesn’t have to be exact. I think it’s fine to have time-bound checklist items with one being “write the damn blog post” for 2 hours.
1 Like

Also, simplify. A complex structure requires complex interaction patterns which you probably won’t adopt without creating structure like checklists or routine for your behavior (which I love to do, but it takes time and thought). I think this is where the “minimize your use of plug-ins when first using Obsidian” advice is appropriate. Like you said about your admired researchers, they will just crank out work no problem by just using simple tools (although you can’t know everything they do to make that work - they likely have their own systems even if they are mostly internalized).

Can you see the parallel between the Zettelkasten and your own brain?

Remembering things works best, when using them frequently and/or when they are connected thoroughly within the system. Just as Hebb says: “use it or lose it.”

Think about it like that with your Zettelkasten. If you have trivial things that you have in your brain and that do not get extended by new information, they likely don’t need to go in the zettelkasten. If you add something, that is interesting but far outside you usual domain of thinking you could add it to remember it later, or just do not add it, because it may never be relevant again.

Also: You only “do something” with the zettelkasten if you want to produce something? Do you have a blog, engage in regular discussions with others, write articles, or do you just collect information?

Because information is there to be reformed in your mind and then shared.

I have faced this problem recently too when switching from institutional learning to self-organized learning.

The problems is not in how notes are organized, but in how they are written. A distinction between note writing paradigms itself is not commonly discussed within the PKM community.
One is concerned about linking, the top-down file hierarchy, etc. in the belief that it will solve all problems. All of these are however of secondary nature. It does not matter how you organize the notes if the notes themselves are the problem.

The norm is to create notes in a declarative manner: one names a note after a specific topic and writes down all the associated facts with this concept.
To put it bluntly, one is basically writing a fancy dictionary. A dictionary is good for lookups, but it will not improve thinking.
In the same way, reading a dictionary will not guarantee that learned words will directly enter your active vocabulary; more engagement is needed.

In this regard, such types of note-taking are not productive. After all, your goal is not to merely learn definitions, but to acquire some level of expertise.
You are learning about things because you need to apply them in practice.
Your notes should reflect this.

An example
this is an excerpt from my actual note structure, before applying the above myself:

├── behavior
│   ├── 'psychological processes behind group motivation.md'
│   ├── 'self determination theory.md'
│   └── skinner
│       ├── 'causes of behavior.md'
│       ├── conditioning.md
│       ├── 'operant conditioning.md'
│       ├── reflexes.md
│       ├── respondent conditioning.md
│       ├── 'Are mental states important?.md'
│       ├── 'behaviorism 101.md'
│       └── vocabulary.md
├── inbox
│   ├── '_subtle detachment.md'
│   ├── nutrition.md
│   ├── cooking.md
│   ├── REM.md
│   ├── saliency.md
│   ├── 'social identity theory.md'
├── log
│   └── 'thoughts about mindfulness.md'

Great, you are certainly writing things down, but can you actually do something with these notes? - Are you just rephrasing information and don’t know how to use or engage with them?

This is the revised version:

├── behavior
│   ├── 'belonging is important for motivation.md'
│   ├── 'groups enforce behavior.md'
│   ├── motivation.md
│   ├── 'one may stop being motivated if others recommend to do X.md'
│   ├── 'self determination theory.md'
│   ├── skinner
│   │   ├── 'common misconceptions in behaviorism.md'
│   │   ├── 'Are mental states important?.md'
│   │   └── vocabulary.md
│   └── social
│       ├── 'being part of a group reduces individual uniqueness.md'
│       └── 'groups provide individual support.md'
├── integration
│   ├── 'planning ahead detaches one from the present moment.md'
├── knowledge
│   ├── PKM
│   │   └── 'every pkm program is becoming emacs.md'
│   └── 'saliency can be effectively manipulated.md'
├── cooking
│   ├── nutrition.md
│   └── 'carbs increase REM-sleep.md'
├── log
│   └── 'mindfulness makes one more aware.md'

At first, this may seem a bit odd as notes seem to now be claims.
We are often told to not formulate claims but instead to approach everything from a scientific perspective, where one starts by learning definitions and slowly expands from there.

This leads to naivety, where one thinks it is better to not draw any conclusions instead of inaccurate ones. But someone who fears mistakes and becomes hesitant due to them can not make reasonable progress.

Instead, one should engage as much as possible practically with the matter that one studies. Note-taking is not the goal, it’s a byproduct.
In this example, it means:

  1. read texts (or your previous notes); try to comprehend what they convey in depth
  2. formulate claims (this is the new note title)
  3. within the note, argue to why this is true
  4. lastly, add to the note examples for situations in which this claim arises
  5. claims are a hypothesis: observe the claim in practice
  6. refute or delete the note if the claim does not hold up

You can do this procedure on paper, with sticky-notes, Obsidian, or anything else. I recommend for a start to reduce tools and functions to the minimum; use the system and then reflect to what is really needed.

To expand on this: all the claims listed in my example above indirectly incentivize or describe a certain type of behavior.
Additionally, within the procedure of writing these notes, we already added examples for when each action occurs. As such, we are more likely to associate these situations with the behavior.

To not forget these associations and also to revise our notes, a tool such as spaced repetition for notes may be useful.

Lastly, this note-taking approach answers a lot of questions commonly faced in note-taking:

  • How atomic should a note be / how much information should each note have?
    • enough so that you can argue for the claim
  • When do I know my notes are good?
    • Upon later revision, the line of thought should be easy to follow. If the note inspires other ideas (= claims), write them down in a new note and link to them from the first note.
      • (This also explained when to link notes: by intuition - it should reflect your thinking)
  • My written notes feel mundane; I can’t seem to get any value out of them?!
    • Try to find examples for when the information applies to your life.
      Can’t find any? Maybe that is because these notes actually have no meaning for you; re-evaluate your relation to this topic.
      Can you find applicable examples? The problem should have solved itself by now.

The core idea is from Andy Matuschak’s Evergreen Notes, I heavily recommend giving them a read.

1 Like

In my opinion the issue is not in the tool used (I use a Zettelkasten + bullet writing over Obsidian, for example), but having purposes for that tool. Not using the system for the only sake of having a system.

For example I’ve used obsidian-zettelkasten for learning zettelkasten itself (and this is not an easy job, as stated by problematic experiences of many people about). Once that initial need is met, at this moment I’m using the same system for learning how to eat better, how to run better, to develop my positions on certain relevant ethical and social issues, to acquire useful knowledge for my daily work, and to deepen my literary and musical tastes.

If you have a purpose for the knowledge you develop, that knowledge will rarely go unused. In the worst-case scenario, it might only be used once, but it is still used.

Can be anything. Cooking, gardening, photography theory and practice, developing knowledge for having conversations on any forum, solve everyday problems.

Whenever you need to use your head and pass the product of your thinking on to your future self, a system for thinking and managing information and knowledge can support you. And it’s not hard to encounter these moments in our lives: we just need to realize that when we use our heads on these occasions, we can lean on a system. It happens to me all the time, when I’m watching a video, reading an article, participating in a discussion, when a question pops into my mind, or when I need to formulate an answer.

This very response of mine is largely the result of what I have developed in this field (Obsidian, PKM, Zettelkasten) over time, even though I didn’t actually have to open my system to write this text. I feel capable of answering questions like these, having internalized the topic thanks to the practice.

1 Like