PARA vs. Zettelkasten vs. CODE vs. Johnny Decimal: Which PKM Framework Fits Your Workflow?

Why You Keep Switching Frameworks

You have heard about PARA. Zettelkasten. CODE. Johnny Decimal. Maybe you have tried one, maybe two, maybe you are still reading articles and bookmarking guides without ever committing. The familiar loop: a new framework appears, it sounds elegant, you reorganize your folders, and two weeks later your notes are scattered again and you are back to Google Docs.

I have been there too. Three PKM systems in two years. Each one promised clarity. Each one collapsed under the weight of real projects, real emails, real deadlines. The issue is not that the frameworks are bad. The issue is that each framework solves a different problem, and treating them as rivals guarantees frustration.

The most honest statement I have seen on this comes from a comparison that says most working PKM systems use PARA for filing and Zettelkasten or BASB for thinking. The filing spine handles your projects and areas; the thinking method handles your ideas. They are not competing. They are complementary.

The Four Frameworks at a Glance

Here is a quick reference so you can see the differences side by side.

Zettelkasten: A Thinking System, Not a Filing Cabinet

Let me start with the number you hear most often. Niklas Luhmann produced 70+ books and 400+ academic articles from roughly 90,000 notes over 30 years. That is extraordinary output. It is also misleading for most of us.

Luhmann was a full-time academic with institutional support — a secretary, a research assistant, uninterrupted writing time. The connection between note-taking volume and output is real, but the 90,000 notes figure is the product of a career, not a hobby. If you start Zettelkasten expecting to write 70 books, you will be disappointed.

What Zettelkasten does well is generate ideas. Each note is atomic — one idea, one link, one connection. Over time, the network of links surfaces unexpected relationships. That is powerful for writers, researchers, and anyone whose work depends on synthesizing information. But the daily demand is real: you need to write notes habitually, link them deliberately, and revisit your archive to maintain the graph. That is not a filing system. It is a thinking system.

PARA: Easy to Start, Not So Easy to Maintain

PARA, on the other hand, is a filing system. Tiago Forte's method divides everything into four folders: Projects, Areas, Resources, and Archives. The rule is simple: organize by actionability, not by subject. That means a note about a meeting goes into the project folder if it relates to an active deliverable, not into a broad category like "client meetings."

PARA is easy to start. Four folders are easy to remember. But the claim that it is easy to maintain needs scrutiny. In practice, Areas and Resources bloat because people are reluctant to archive things that might be useful later. An Area like "Health" collects articles, notes, and checklists until it becomes a cluttered drawer. Discipline matters more than the folder structure. If you do not regularly move closed projects to Archives, your PARA system becomes a storage room.

What PARA does not do is generate ideas. It organizes existing work. For project-driven knowledge workers — people whose primary unit is a deadline, not an insight — that is exactly the right tool.

The Hybrid That Works: PARA for Filing, Zettelkasten for Thinking

The conclusion is clear: the most effective PKM system is not a single framework. It is a combination. Use PARA as your filing spine for projects, areas, and actions. Then, within the Resources folder (or a dedicated notes folder), use Zettelkasten-style atomic notes with bidirectional links for your thinking and research material.

This is not a theoretical ideal. Most working PKM systems already do this. The key is to keep the Zettelkasten portion small and contained. If you try to turn every project note into an atomic linked note, you will burn out. Reserve the Zettelkasten practice for writing projects, research streaks, or topics you plan to publish on. Everything else lives in PARA's action-oriented folders.

Concretely: your folder structure might be Projects / Areas / Resources / Archives, and inside Resources you have a folder called "Notes" where each file is a single atomic note with links to other notes. The PARA folders stay clean; the Zettelkasten folder grows ideas. You need both.

Niche Tools: CODE and Johnny Decimal

CODE — Capture, Organize, Distill, Express — is the pipeline behind Building a Second Brain (BASB). Its distinctive technique is progressive summarization: a 5,000-word article becomes 500 highlighted words, then 100 bolded, then a 20-word summary. The idea is that each layer lets you rediscover the essence without rereading the original.

The summarization layers are time-intensive. You do not get from 5,000 to 20 words in a single pass. You highlight, then later you bold, then later you summarize. For some people this is a productive friction. For others it is an unfinished pile of half-distilled notes. If you are a writer, a podcaster, or anyone who turns research into publishable content regularly, CODE gives you a repeatable output mechanism. If you capture notes mostly for personal reference, the overhead may not be worth it.

Johnny Decimal is the odd one. It uses a strict numeric hierarchy — 10 Areas (00–90), each with up to 10 Categories, each with up to 10 items. Everything gets a number. That makes retrieval deterministic: if you know the number, you know exactly where the file lives. No searching, no browsing.

The rigidity is both the strength and the weakness. Johnny Decimal works well for systematic thinkers who hate filing ambiguity — engineers organizing documentation, lawyers managing case folders, anyone who would rather have one correct place than a flexible space. The cost is upfront hierarchy design (you need to map your 10 areas before you start) and almost no support for cross-idea discovery. If your work requires creative connections, this is not your framework.

Decision Flowchart: How to Choose Your Starting Point

The flowchart below summarizes the decision process. Start with your primary work style and follow the branches. If you are project-driven, start with PARA alone. If you write or research regularly, start with Zettelkasten. If you produce content from research, consider CODE. If you crave deterministic order, consider Johnny Decimal.

For a deeper methodology comparison of how these frameworks interact with each other and with tools, read our framework-first decision guide.

Commit 90 Days, Then Tweak

Here is my honest recommendation for most knowledge workers: start with PARA. It is the easiest to begin — four folders, no special tool required, works in any note-taking app. If after a few weeks you find yourself wanting to capture deeper connections between ideas, introduce a small Zettelkasten practice within Resources. Do not try to do everything at once.

The single most important action is not choosing the perfect framework. It is committing to one for 90 days. The 90-day commitment claim comes from the same comparison: avoid tool-hopping, pick a tool and commit for a minimum of 90 days. Switching every few weeks is the real productivity killer. Consistency matters more than correctness of initial choice.

A 30-day starter workflow typically yields around 100 notes, according to the same source. That is enough volume to see whether the method clicks or grates. If you stick with PARA for three months, you will have a clear picture of what it handles well and where you need an addition. Then you can tweak — add a Zettelkasten layer, try progressive summarization, or restructure your Areas.

Two internal guides will help you get started: How to Choose Your First PKM Framework walks through the decision criteria in more detail. The 30-Day Starter Workflow gives you a day-by-day plan for building your first 100 notes.