
General PKM → General PKM
PARA vs. Zettelkasten vs. Johnny Decimal vs. Tags-Only: Which PKM Framework Fits Your Workflow?
A decision-matrix comparison of four personal knowledge management methodologies — PARA, Zettelkasten, Johnny Decimal, and tags-only — to help knowledge workers and students choose the right framework based on their primary output type: projects, ideas, taxonomy, or search.
⚠ Data loss risk: Low
Steps last verified: 2026-06-14
By Editorial Team
- PKM
- PARA
- Zettelkasten
- Johnny-Decimal
- tags-only
The Methodology Paralysis Problem
You have read the blog posts, watched the YouTube explainers, and bookmarked the Reddit threads. You know that PARA, Zettelkasten, Johnny Decimal, and tags-only are all viable approaches to personal knowledge management. Yet you still have not committed to one. You are stuck in methodology paralysis — the state where the act of choosing a system becomes a substitute for actually building one.
This article exists to break that loop. It will not tell you that one framework is universally superior. Instead, it will help you identify your primary output type — projects, ideas, rigid taxonomy, or flexible search — and match it to the methodology that serves that output best. If you have read our earlier comparison of PARA vs. GTD vs. Zettelkasten, you will notice a key difference: we have removed GTD entirely (it is a task-management system, not a knowledge-management one) and added Johnny Decimal and tags-only. The framing has also shifted from "what problem does each solve?" to "what kind of output does each produce?"
What a PKM System Actually Does: Capture → Organize → Use
Before comparing frameworks, it helps to agree on what a personal knowledge management system is supposed to do. Every PKM system, regardless of its philosophy, performs three functions:
- Capture: Get information into the system quickly, with minimal friction.
- Organize: Structure that information so it can be found later.
- Use: Retrieve and apply the information to produce something — a decision, a document, a project, an insight.
The reason methodology choice matters is that most people spend far too much time on step two (organizing) and not enough on step three (using). According to McKinsey research cited in a 2026 guide by GoLinks, knowledge workers waste an average of 9.3 hours each week searching for information, and nearly 20% of every workweek disappears into hunting for internal information or chasing down colleagues. A well-chosen methodology can return a significant portion of that time — but only if it matches how you actually work.

PARA: The Project-First System
PARA, developed by Tiago Forte, organizes all digital information into four top-level buckets: Projects, Areas, Resources, and Archive. A project is a desired outcome with a deadline (e.g., "Q3 marketing plan"). An area is a sphere of ongoing responsibility without a fixed end date (e.g., "Health" or "Finance"). Resources are topics of interest that may become useful later. Archive is everything you have completed or no longer need.
The genius of PARA is its simplicity. As the PageStash blog notes, it is "the easiest method to start with and the one most likely to survive a busy quarter, because it is hard to mis-file something across only 4 categories." When you are juggling multiple deadlines, you do not have the mental bandwidth to decide whether a note belongs in a "Zettelkasten slip-box" or a "reference folder." PARA gives you four clear choices, and you can make the call in under three seconds.
Where PARA Struggles
PARA has a well-documented weakness: the line between Areas and Resources is often blurry in practice. Is a folder of saved articles about "React performance optimization" a Resource (general knowledge) or an Area (ongoing professional development)? The answer depends on context, and that ambiguity can lead to inconsistent filing. Over time, users either develop personal rules to resolve the ambiguity (which adds cognitive overhead) or give up and dump everything into Resources, which defeats the purpose of the system.
PARA is best suited for knowledge workers whose primary output is completing projects — freelancers juggling client work, managers tracking quarterly initiatives, or students working through a semester's worth of assignments. If your work is defined by deliverables with deadlines, start with PARA. For a deeper walkthrough, see our dedicated guide to the PARA method.
Zettelkasten: The Idea-First System
Zettelkasten (German for "slip-box") was developed by the sociologist Niklas Luhmann, who used it to produce an astonishing body of work. Over 30 years, Luhmann wrote 70+ books and 400+ academic articles from a slip-box of roughly 90,000 linked notes. That is not a productivity hack — it is a compounding knowledge engine.
The core idea is atomicity and connection. Each note captures a single idea, written in your own words, and linked to other notes through explicit references. Over time, the network of links creates a structure that no single folder hierarchy could replicate. When you need to write an article or develop a thesis, you do not start from scratch — you traverse the existing links and discover connections you had forgotten.
Historically, Zettelkasten was labor-intensive: Luhmann used physical index cards with manual IDs and cross-references. Modern tools like Obsidian and Logseq have removed that burden. As the Atlas guide notes, "tools like Obsidian, Logseq, and Atlas make linking and graphing trivial, removing the manual ID-and-cross-reference burden." The 2026 version of Zettelkasten is a digital-first practice that rewards consistent note-making, not card-sorting.
For a complete breakdown of the method, including how to write atomic notes and build link structures, see our Zettelkasten method explainer.
Johnny Decimal: The Taxonomy-First System
Johnny Decimal takes the opposite approach from tags-only: it imposes a rigid numeric hierarchy on your entire digital life. The world is divided into 10 Areas (numbered 00 through 90). Each Area can contain up to 10 Categories. Each Category can contain up to 10 items. The result is a system where every file, folder, or note has a predictable, human-readable address.
For example, if Area 20 is "Client Projects," Category 23 might be "Acme Corp," and item 234 might be "Acme Corp — Q3 Proposal." Anyone who understands the system can navigate to that file without searching. This predictability is the system's greatest strength — and its greatest weakness.
The Setup Cost Is Real
As the PageStash comparison notes, Johnny Decimal has a "high setup cost — you need to design your taxonomy before you start. Doesn't adapt well as your work changes." If you assign Area 30 to "Marketing" and later decide that marketing should be split across two areas, renumbering everything is painful. The system rewards upfront planning and punishes iteration.
Johnny Decimal is best suited for users who need strict, predictable folder structures — archivists, compliance-heavy roles, or anyone managing a shared repository where multiple people must be able to find files without relying on the original creator's mental model. It is overkill for a personal note-taking system unless you have a strong preference for numeric order over semantic labels.
Tags-Only: The Search-First System
The tags-only approach is the simplest on paper: zero folder hierarchy, zero taxonomy design, zero setup time. You capture a note, slap a few tags on it, and move on. When you need to find something, you search by tag or keyword. This is the default behavior of most note-taking apps out of the box, and it works well — for a while.
The problem is tag proliferation. As PageStash puts it: "Tags proliferate. After a few months you have 200 tags." You start with "#meeting-notes" and "#project-alpha." Then you add "#meeting-notes-2026" and "#project-alpha-research." Before long, you have multiple tags that mean the same thing, tags that overlap, and tags you forgot existed. The system that required zero setup now requires ongoing maintenance — or you accept that your tag list is a mess and rely entirely on full-text search.
Tags-only works best for people who prefer flexible retrieval over rigid organization and are comfortable with search as the primary access method. If you have a good memory for keywords and you rarely need to browse your notes by category, this approach will serve you well. If you need to regularly review all notes related to a specific area, the lack of structure will become a bottleneck.

Comparison Table: Which Framework for Which Output?
The table below distills the four frameworks across the dimensions that matter most during the selection process. Use it as a quick-reference tool when you feel the pull of methodology paralysis creeping back.
| Dimension | PARA | Zettelkasten | Johnny Decimal | Tags-Only |
|---|---|---|---|---|
| Primary output type | Projects (deliverables with deadlines) | Ideas (long-term knowledge development) | Taxonomy (predictable file locations) | Search (flexible retrieval) |
| Setup cost | Low — 4 folders, start immediately | High — requires atomic note discipline and linking habit | Very high — must design full taxonomy before starting | Zero — start capturing immediately |
| Adaptability to change | High — easy to move items between buckets | Medium — links persist even if categories shift | Low — renumbering is painful | High — no structure to break |
| Ongoing maintenance | Low — occasional archive cleanup | Medium — each note requires linking effort | Low — structure is self-maintaining | Medium — tag consolidation needed periodically |
| Tool requirements | Any folder-based system or note app | Apps with bidirectional linking (Obsidian, Logseq, Roam) | Any file system or folder-based app | Any note app with search and tags |
| Best-fit persona | Freelancers, managers, students with deadlines | Writers, researchers, long-term thinkers | Archivists, compliance roles, shared repositories | Quick-capture users who prefer search over browse |
| Risk of abandonment | Low — easy to restart after a break | High — broken linking habit makes system decay | Medium — taxonomy may become outdated | Low — always works, even when messy |
How to Mix Methods: The Hybrid Approach
Here is a truth that most methodology guides gloss over: very few knowledge workers use a pure version of any single framework. The PageStash guide observes that "most effective knowledge workers end up with a hybrid: PARA folders for projects + a Zettelkasten area for permanent notes + tags for quick classification." The Atlas guide echoes this: "Most working PKM systems use PARA for filing and Zettelkasten or BASB for thinking. The spine is action-oriented, the meat is idea-oriented."
A concrete example of a hybrid system might look like this:
- Use PARA's four-bucket structure as the top-level spine of your note-taking app. Projects and Areas hold your active work. Resources holds reference material. Archive holds everything else.
- Within Resources, maintain a dedicated folder (or a separate vault) for Zettelkasten-style permanent notes. Each note is atomic, written in your own words, and linked to other permanent notes. This is where ideas develop over months and years.
- Add tags to every note for cross-cutting classification — by source type (book, article, podcast), by confidence level (draft, refined, published), or by emotional valence (inspiring, skeptical, actionable). Tags cut across the PARA hierarchy and the Zettelkasten network.
This hybrid avoids the weaknesses of each individual system. PARA's blurry Areas/Resources line matters less when your permanent notes live in a separate Zettelkasten zone. Zettelkasten's high per-note cost is manageable because you only write atomic notes for ideas that survive the PARA inbox filter. Tags provide a safety net for everything that does not fit neatly into either structure.

Decision Flowchart: Find Your Framework
If you are still unsure which framework to start with, work through the following questions in order. Each answer narrows the field until you arrive at a recommended starting point.
- Do you primarily manage projects with deadlines, or ideas that develop over time? If projects → PARA. If ideas → Zettelkasten. If both → start with PARA and add a Zettelkasten zone later.
- Do you need a predictable file structure that multiple people can navigate without instructions? If yes → Johnny Decimal. If no → continue.
- Do you prefer to organize by browsing folders or by searching keywords? If browsing → PARA or Johnny Decimal. If searching → tags-only.
- How much time can you invest in setup this week? Less than 30 minutes → tags-only or PARA. More than 2 hours → Zettelkasten or Johnny Decimal.
If you arrived at PARA, you are in good company — it is the safest starting point for most knowledge workers. If you arrived at Zettelkasten, commit to writing at least one atomic note per day for the first month to build the linking habit. If you arrived at Johnny Decimal, spend a full weekend designing your taxonomy before you move a single file. If you arrived at tags-only, set a calendar reminder for three months from now to review and consolidate your tag list.
Frequently Asked Questions
Can I switch frameworks later?
Yes, and most people do. The key is to avoid deep customization in the first three months. PARA users who later add a Zettelkasten zone typically keep their existing PARA structure intact and create a new folder for permanent notes. Tags-only users who outgrow the approach can migrate to PARA by sorting their existing notes into the four buckets over a weekend. The cost of switching is low if you have not invested in elaborate custom taxonomies.
How long does it take to set up each system?
- PARA: 15 minutes to create the four folders and define your active projects.
- Tags-only: 5 minutes to start capturing — no setup required.
- Zettelkasten: 2–4 hours to understand the method and set up your linking conventions, plus ongoing time per note.
- Johnny Decimal: 4–8 hours to design your taxonomy before you can start filing.
Do I need a specific tool for each framework?
No. PARA and Johnny Decimal work in any folder-based system — Google Drive, local file explorer, or any note app. Tags-only works in any app with tag support. Zettelkasten benefits from bidirectional linking, which is a feature of Obsidian, Logseq, Roam, and similar tools, but you can approximate it with manual links in any app that supports hyperlinks. The methodology matters more than the tool.
What if my work involves both projects and ideas?
This is the most common scenario, and it is exactly what the hybrid approach addresses. Start with PARA to get your project workflow under control. Once that feels natural, add a Zettelkasten zone for ideas that are not tied to any specific deadline. The two systems coexist: PARA handles the "what needs to get done" layer, and Zettelkasten handles the "what am I learning" layer. Tags bridge the two by providing cross-cutting access.
Comments
Join the discussion with an anonymous comment.