Niklas Luhmann, the German sociologist, kept roughly 90,000 handwritten index cards in wooden drawers and credited them with helping him publish more than 70 books. Tiago Forte’s PARA method asks you to keep exactly four top-level folders. Those two numbers describe the gap between the systems better than any feature list: one is built to grow a dense web of ideas over decades, the other to keep the next deliverable within two clicks.
At work the choice matters more than it does for a hobby notebook. Your notes feed 1:1s, interview loops, performance reviews, incident write-ups and the promotion case you will need to make in 18 months. Pick a system that fights the way your job generates notes and it will be abandoned by March. The interesting shift over the last few years is that fewer people pick one; they run a hybrid, and the reasons say a lot about what each method is actually good at.
Two systems answering two different questions
Zettelkasten: a note system in which each note holds one idea, written in your own words, with a permanent identifier and explicit links to related notes. Structure emerges from the links rather than from folders. Sönke Ahrens popularised the method for a general audience in “How to Take Smart Notes” (2017), describing three kinds of note: fleeting notes jotted during the day, literature notes taken while reading, and permanent notes that get filed into the slip box.
PARA: a filing scheme with four categories. Projects have a goal and a deadline. Areas are ongoing responsibilities with a standard to maintain, such as “hiring” or “team health”. Resources are topics of interest. Archives hold anything inactive from the other three. Forte described it on his blog around 2017 and expanded it in “Building a Second Brain” (2022), alongside the CODE workflow: Capture, Organize, Distill, Express.
The question Zettelkasten answers is “what do I think about this, and what else does it connect to?” The question PARA answers is “what do I need for the thing I am doing right now?” Both are legitimate. Work generates both kinds of need, but in very unequal proportions depending on the role.
A delivery manager running six parallel launches lives almost entirely inside the second question. A staff engineer writing architecture proposals, or a researcher building a point of view on a market, lives much more in the first. Most professionals sit somewhere between, which is why a straight “which is better” comparison usually produces a fake answer.
One more difference is easy to miss. PARA is explicitly about movement: a note travels from Projects to Archives when the project ends, and a resource can be promoted into a project when it becomes actionable. A Zettelkasten note, once filed, does not move. It accumulates links instead. That gives the two systems opposite relationships with time.
Side by side on the jobs work notes actually do
The table compares the two on the tasks that fill a typical knowledge worker’s week. The ratings describe how naturally each system handles the job without extra tooling or discipline.
| Job | Zettelkasten | PARA |
|---|---|---|
| Unit of storage | One idea per note | Any file or note, sized as needed |
| Organizing principle | Links between ideas | Actionability: project, area, resource, archive |
| Finding notes for this week’s deadline | Weak without a project index | Strong: open the project folder |
| Preparing a 1:1 or interview loop | Awkward; meeting notes are not atomic ideas | Natural fit under an Area |
| Writing a strategy memo or proposal | Strong: linked arguments already exist | Medium: material sits in Resources but is not connected |
| Building performance review evidence | Medium | Strong if wins are logged per project |
| Setup time | 2 to 4 hours to learn the conventions | Under 1 hour |
| Weekly maintenance | Continuous; every reading session produces notes | A 20 to 30 minute review |
| Typical failure mode | Thousands of orphan notes, no output | A Resources folder that becomes a junk drawer |
| Common tools | Obsidian, Logseq, Zettlr, The Archive, paper cards | Notion, Obsidian, OneNote, any file system |
Two rows deserve comment. “Finding notes for this week’s deadline” is the core daily need for most employees, and pure Zettelkasten is weak there by design: Luhmann had no deadlines driving his cards. Practitioners compensate with “structure notes” or index notes that collect links for a topic, which work well but reintroduce a layer of hierarchy.
“Writing a strategy memo” is where the slip box earns its reputation. If you have spent a year writing small notes on pricing experiments, customer interviews and competitor moves, each linked to the others, the first draft of a pricing proposal is largely a matter of following links and arranging what you find. With PARA you would have the same raw material, but split across project folders that ended months ago and a Resources folder with no internal structure.
What each system costs per week, in minutes
Comparisons usually skip the cost side, and at work the cost side decides adoption. The figures below are an illustrative budget for someone who attends about 15 meetings a week, reads 3 to 5 substantial documents and writes one longer piece every two weeks. Your numbers will differ; the ratios are the useful part.
PARA, run lightly, costs:
- 2 minutes per meeting to file notes into the right project or area folder: about 30 minutes a week.
- A weekly review of 20 to 30 minutes to archive finished projects and clear the inbox.
- Near zero cost per document read, because reading notes simply go into Resources.
That totals roughly 55 minutes a week. The output is fast retrieval for current work and very little help with synthesis.
Zettelkasten, run properly, costs:
- The same 30 minutes for meeting notes, because those still need a home.
- About 10 to 15 minutes per permanent note: rewriting an idea in your own words, checking for an existing note, adding 2 or 3 links. Producing 8 notes a week means 80 to 120 minutes.
- Occasional maintenance of structure notes: perhaps 20 minutes a week.
That totals roughly 130 to 170 minutes a week, so about two and a half to three times the PARA cost. The return comes later and unevenly. In the first three months a slip box with 100 notes rarely surprises you. Somewhere past a few hundred linked notes, people consistently report that writing gets faster because arguments arrive pre-assembled.
The trend toward hybrids follows directly from this arithmetic. Running PARA for everything and reserving Zettelkasten-style permanent notes for the two or three themes your career depends on keeps the weekly cost near 90 minutes while preserving the compounding benefit where it matters. In tools like Obsidian this is literally a folder: a “Notes” or “Slipbox” area inside Resources, with links allowed to cross into project folders.
A mini-case: a product manager six months into each
This case is illustrative, a composite of patterns rather than a specific person. Maya is a senior product manager at a 300-person B2B software company. She owns two products, runs 4 to 6 interviews a month for her team, and is expected to write a quarterly strategy memo.
In January she sets up a strict Zettelkasten in Obsidian, inspired by a podcast. By the end of February she has 140 permanent notes, beautifully linked, mostly about pricing psychology and onboarding research. She also has a growing problem: when her VP asks for the status of the March release, the relevant notes are scattered across daily notes with no project grouping.
Interview feedback for candidates lives in a separate HR tool, so it never enters the system at all. She starts keeping a parallel to-do document, and by April that document is where real work happens.
In May she switches to PARA. Each release becomes a project folder; “Hiring” and “Team” become areas; her research notes move into Resources. Retrieval for current work improves immediately. Her weekly review takes about 25 minutes. When the quarterly memo comes due in June, though, she notices she is rereading old research from scratch, because nothing in Resources links to anything else.
By September her system is a hybrid. PARA governs the folders. Inside Resources sits a slip box limited to three themes: pricing, activation and her product’s competitive landscape. Meeting notes stay messy and dated in their project folders. Every Friday she promotes one or two genuinely new ideas from those notes into permanent notes with links. Her slip box grows by about 6 notes a week instead of 20, and her memo prep time drops from roughly three days to one and a half.
The case shows the pattern, not a law. Maya’s job mixes high-volume operational notes with periodic synthesis. Someone whose job has no synthesis component would have stayed on PARA in May and been right to.
Mistakes that make either system collapse at work
Both methods fail in predictable ways inside companies, and most of the failures have nothing to do with the method itself.
- Treating meeting notes as permanent notes. A 1:1 record is a dated log, not an atomic idea. Forcing it into Zettelkasten format wastes time and produces notes nobody links to.
- Putting confidential material in a personal system. Candidate feedback, salary data and performance issues usually belong in the company’s HR tool, governed by its retention policy. A personal vault on a laptop is the wrong place, whatever the method.
- Building the system before having notes. Spending a weekend designing tags, templates and folder icons is the most common way to stall. Both methods work better when the structure follows a few weeks of real notes.
- Letting Resources become an attic. PARA users tend to file every interesting article into Resources and never open it again. If something has not been touched in 6 months, archive it.
- Collecting instead of writing. The slip box only compounds if permanent notes are rewritten in your own words. Copy-pasted highlights with links are a bookmark manager with extra steps.
- Mirroring the org chart. Folders named after teams break with every reorganisation. Projects and areas named after outcomes survive them.
- Never archiving. A PARA system with 40 active “projects” has no projects, only a list of worries.
A related mistake is moving tools instead of fixing habits. Switching from Notion to Obsidian, or from Obsidian to Logseq, rarely solves a system that failed because nobody did the weekly review.
Choosing by role with a five-question decision tree
Run through the questions in order and stop at the first answer that sends you somewhere.
- Does most of your week go to delivering defined projects with deadlines (launches, client engagements, hiring pushes)? If yes, start with PARA and go to question 4. If no, go to question 2.
- Does your job require you to produce original written arguments regularly, such as proposals, research reports, strategy memos or talks, at least once a month? If yes, go to question 3. If no, use PARA; a slip box will cost more than it returns.
- Do you expect to work on the same two or three themes for at least two years? If yes, a Zettelkasten is worth its weekly cost, so start one for those themes. If no, use PARA and keep a small “ideas” note per project instead.
- Do you write at least one substantial document per quarter that draws on accumulated knowledge rather than current project facts? If yes, go to question 5. If no, stay with plain PARA.
- Can you protect 30 to 40 extra minutes per week for writing permanent notes? If yes, add a slip box inside Resources for your core themes. If no, stay with PARA and revisit the question at your next performance review.
Most managers land on plain PARA or the hybrid. Most researchers, staff engineers and consultants who publish land on Zettelkasten or the hybrid. Very few people with a busy calendar should run a pure Zettelkasten for everything.
There is a fair counterargument from Zettelkasten purists: that PARA is a filing system, not a thinking system, and that the hybrid is a compromise that delivers neither. The criticism has force for academics and writers whose main output is ideas. For people whose output is shipped work, it underweights how much of a working week is spent finding the right document for today.
When should you adopt neither? If your company already runs a well-maintained wiki and expects decisions and meeting notes to live there, a parallel personal system can split the truth into two places and create real problems when colleagues search for context you never shared.
If you are new in a role and still learning what kinds of notes the job produces, wait 6 to 8 weeks before building anything formal. And if you notice you spend more time tending the system than using it, that is the clearest signal to stop.