PKM is not a system. It is a practice. The distinction matters because systems can be installed; practices must be cultivated. Most people who struggle with PKM do not have a system problem. They have a practice problem. They need to build a note-taking practice, not find a better note-taking system.
The MMT Framework
Three layers compose any PKM practice:
Mindset. Your beliefs about knowledge, learning, and growth. Do you believe knowledge compounds? That writing clarifies thinking? That ideas gain value through connection? Without the right mindset, no method or tool will sustain engagement. Mindset answers "why bother?"
Methods. The techniques for capture, organization, connection, and review. The Capture Habit, Active Note-Taking, Progressive Summarization, spaced review; these are all methods. Methods answer "how do I do this?"
Tools. The software that supports the methods. Obsidian, Roam, Logseq, Notion, pen and paper. Tools answer "what do I use?"
The layers are ordered by importance. A strong mindset with basic methods and simple tools beats a weak mindset with sophisticated methods and expensive tools every time.
The Tool Trap
Most people enter PKM through Tools and never develop Mindset or Methods. The pattern is recognizable: install Obsidian, spend weeks perfecting folder structure, try Roam, rebuild everything, try Logseq, rebuild again. The system obsession (testing every app, tweaking every setting, redesigning every template) is a symptom of underdeveloped practice.
This is why PKM Anti-Patterns identifies tool-hopping as a practice failure, not a tool failure. The tool is not the problem. The absence of practice is.
Practice Over System Design
A practice is something you do consistently. It has rhythm: daily capture, weekly review, monthly synthesis. It survives tool changes because the habits are in you, not in the software. A strong practitioner can switch from Obsidian to plain text files and continue producing insight. A weak practitioner can have the most elaborate Obsidian setup and produce nothing.
Consistent daily action matters more than system design. Five minutes of genuine active note-taking per day compounds faster than a weekend reorganizing your vault. The practice is the engine; the system is the chassis. A powerful engine in a mediocre chassis still moves. A beautiful chassis with no engine is furniture.
Building Practice
Starting a PKM practice means starting small and building consistency:
- Pick one method. Not five. One. Daily capture, or weekly review, or active note-taking on what you read.
- Do it for 30 days. Before evaluating, changing, or optimizing. The first month is about building the habit, not perfecting the output.
- Add the next method only when the first is automatic. Stack practices like habits: each new layer builds on a stable foundation.
- Change tools only when the tool genuinely blocks a method. If the tool works but you are bored, that is a mindset issue, not a tool issue.
Key Points
- PKM is a practice (cultivated daily), not a system (installed once)
- MMT framework: Mindset > Methods > Tools, in that order of importance
- Tool-hopping is a symptom of underdeveloped practice, not inadequate tools
- Consistent daily action compounds faster than periodic system redesign
Open Questions
- How long does it take for a PKM practice to become self-sustaining (intrinsically motivated rather than forced)?
- Can you develop Mindset through practice alone, or does it require deliberate reflection on beliefs about knowledge?
- Is there a minimum viable practice that works for everyone, or is it inherently personal?
References
- Bianca Pereira, MMT framework and PKM as practice
- Ev Chapman, practice-first PKM philosophy
- Vault: PKM Anti-Patterns, The Capture Habit